search for: busid

...dency Patches 6-7: Assist people with first-time build of nouveau Git complains about whitespace errors in patch 7, which for the sake of me I cannot see -- [PATCH 1/7] nouveau: Check if the device supports modesetting, after opening it [PATCH 2/7] nouveau: stop using dri1 function DRICreatePCIBusID [PATCH 3/7] nouveau: Do not load dri {sub,}module [PATCH 4/7] dri1: purge the final references [PATCH 5/7] nouveau: mandate dri2 build [PATCH 6/7] configure: require xorg-macros 1.8 [PATCH 7/7] configure: printout the configuration info -- configure.ac | 33 +++++++++++++++++++++++++++++++...

...Tue, Feb 28, 2017 at 09:47:42AM +0100, Viktor Mihajlovski wrote: > >>>> One could argue about back-level compatibility, but virtio by-path > >>>> naming has changed multiple times. We have seen virtio-pci-virtio<n> > >>>> (not predictable), pci-<busid> and virtio-pci-<busid> already. It > >>>> might be a good time now to settle on a common approach for all > >>>> virtio types. > >>>> > >>>> For the reasons above, I'd vote for <subsystem>-<busid>, which > >...

...Tue, Feb 28, 2017 at 09:47:42AM +0100, Viktor Mihajlovski wrote: > >>>> One could argue about back-level compatibility, but virtio by-path > >>>> naming has changed multiple times. We have seen virtio-pci-virtio<n> > >>>> (not predictable), pci-<busid> and virtio-pci-<busid> already. It > >>>> might be a good time now to settle on a common approach for all > >>>> virtio types. > >>>> > >>>> For the reasons above, I'd vote for <subsystem>-<busid>, which > >...

Here are a few patches adding some missing functions in NvPlatformProbe, which iirc is being used as of xserver 1.13 First patch adds a nouveau_kernel_mode_enabled helper, similar to xf86-video-radeon Second and third use the function in Nv{Pci,Platform}Probe And last one ensures we can still use ZaphodHead and relative head positioning via xorg.conf The coding style may be a bit off, despite my

...QUIRED_HW_INTERFACES: flag = (CARD32 *)data; (*flag) = 0; + if (xorgMir) + *flag |= HW_SKIP_CONSOLE; return TRUE; default: return FALSE; @@ -333,6 +335,23 @@ NVHasKMS(struct pci_device *pci_dev) } static Bool +NVHasMirSupport(struct pci_device *pci_dev) +{ + char *busid; + + busid = XNFprintf("pci:%04x:%02x:%02x.%d", + pci_dev->domain, pci_dev->bus, pci_dev->dev, pci_dev->func); + + if (xmir_get_drm_fd(busid) < 0) { + xf86DrvMsg(-1, X_ERROR, "[XMir] GPU %s not handled by Mir\n", busid); + free(busid); + return FALSE; + } +...

...by @@ -88,7 +108,7 @@ _X_EXPORT DriverRec NV = { NVAvailableOptions, NULL, 0, - NULL, + nouveau_driver_func, nouveau_device_match, NVPciProbe }; @@ -214,18 +234,46 @@ NVPciProbe(DriverPtr drv, int entity_num, struct pci_device *pci_dev, drmVersion *version; int chipset, ret; char *busid; + struct xwl_screen *xwl_screen = NULL; - if (!xf86LoaderCheckSymbol("DRICreatePCIBusID")) { - xf86DrvMsg(-1, X_ERROR, "[drm] No DRICreatePCIBusID symbol\n"); - return FALSE; - } - busid = DRICreatePCIBusID(pci_dev); - - ret = nouveau_device_open(busid, &dev); - if (ret...

...on complete (II) GLX: Initialized DRI GL provider for screen 0 for DRM I get this: $ grep -i drm /var/log/Xorg.0.log drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such device) drmOpenDevice: open result is -1, (No such device) drmOpenDevice: Open failed drmOpenByBusid: Searching for BusID pci:0000:01:00.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 7, (OK) drmOpenByBusid: drmOpenMinor returns 7 drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 7, (OK) drmOpen...

...28, 2017 at 09:47:42AM +0100, Viktor Mihajlovski wrote: >>>>>> One could argue about back-level compatibility, but virtio by-path >>>>>> naming has changed multiple times. We have seen virtio-pci-virtio<n> >>>>>> (not predictable), pci-<busid> and virtio-pci-<busid> already. It >>>>>> might be a good time now to settle on a common approach for all >>>>>> virtio types. >>>>>> >>>>>> For the reasons above, I'd vote for <subsystem>-<busid>, whi...

...47:42AM +0100, Viktor Mihajlovski wrote: > >>>>>> One could argue about back-level compatibility, but virtio by-path > >>>>>> naming has changed multiple times. We have seen virtio-pci-virtio<n> > >>>>>> (not predictable), pci-<busid> and virtio-pci-<busid> already. It > >>>>>> might be a good time now to settle on a common approach for all > >>>>>> virtio types. > >>>>>> > >>>>>> For the reasons above, I'd vote for <subsystem&gt...

...47:42AM +0100, Viktor Mihajlovski wrote: > >>>>>> One could argue about back-level compatibility, but virtio by-path > >>>>>> naming has changed multiple times. We have seen virtio-pci-virtio<n> > >>>>>> (not predictable), pci-<busid> and virtio-pci-<busid> already. It > >>>>>> might be a good time now to settle on a common approach for all > >>>>>> virtio types. > >>>>>> > >>>>>> For the reasons above, I'd vote for <subsystem&gt...

...0100, Viktor Mihajlovski wrote: >>>>>>>> One could argue about back-level compatibility, but virtio by-path >>>>>>>> naming has changed multiple times. We have seen virtio-pci-virtio<n> >>>>>>>> (not predictable), pci-<busid> and virtio-pci-<busid> already. It >>>>>>>> might be a good time now to settle on a common approach for all >>>>>>>> virtio types. >>>>>>>> >>>>>>>> For the reasons above, I'd vote for <...

...-[02-04]--+-00.0-[03]----00.0 G98 Quadro NVS420 | \-02.0-[04]----00.0 G98 Quadro NVS420 Full list of PCIs are in the attachment. DRI status is given here and shows that the second video card (card1) is not set to any PCI bus: dristat -a /dev/dri/card0 Busid: pci:0000:03:00.0 Version information: Name: nouveau Version: 1.0.0 Date: 20120316 Desc: nVidia Riva/TNT/GeForce VM map information: flags: (R)estricted (r)ead/(w)rite (l)ocked (k)ernel (W)rite-combine (L)ock: slot offset size type flags address mtrr 0...

...t by @@ -89,7 +115,7 @@ _X_EXPORT DriverRec NV = { NVAvailableOptions, NULL, 0, - NULL, + nouveau_driver_func, nouveau_device_match, NVPciProbe }; @@ -215,7 +241,28 @@ NVPciProbe(DriverPtr drv, int entity_num, struct pci_device *pci_dev, drmVersion *version; int chipset, ret; char *busid; +#ifdef XORG_WAYLAND + struct xwl_screen *xwl_screen = NULL; + if (xorgWayland) { + xwl_screen = xwl_screen_create (); + if (!xwl_screen) { + xf86DrvMsg(-1, X_ERROR, "Failed to initialise xwayland.\n"); + return FALSE; + } + if (xwl_drm_pre_init(xwl_screen) != Success) { + xw...

....org/view.php?id=1875 had only a WFM response. I've attached a gzipped text file of pertinent information. Briefly, kudzu did the right thing when I installed the second card. System-config-display also behaved correctly. X start ok, but will only use one head at a time. Adding a second "BusID" so that both cards are explicitly addressed didn't help. When the 2 "BusID" entries are switched, the active screen doesn't move (it's always "Screen0") and the ignored screen ("Screen1") remains the same. The monitor attached to the video card for &q...

Hi folks I have a Centos 5.3 Box and need to know how to configure a Netgear wg111v2 USB WLAN adapter. I already have an wireless LAN build with an AP and a windows XP PC with another Netgear wg111v2 USB adaptor running on it.. Thanks David -------------- next part -------------- An HTML attachment was scrubbed... URL:

..."0x00000000" Option "UseFastTLS" "2" Option "BlockSignalsOnLock" "on" Option "UseInternalAGPGART" "yes" Option "ForceGenericCPU" "no" BusID "PCI:1:0:0" # vendor=1002, device=4144 Screen 0 EndSection Section "Device" Identifier "ATI Graphics Adapter connector 1" Driver "fglrx" BusID "PCI:1:0:0" Screen 1 EndSection Section "Screen" Identifier &...

I just installed an Asus PCE-n13 wireless card into one of my CentOS 5.6 systems. It uses the RaLink 2680 chip set and I was able to get the driver loaded using modprobe rt2x00pci.ko. I saw no error and now see that the module is loaded along with mac80211 and other dependencies. Now I need to know how to create the wlan0 device. I can find nothing via Google searches on how to create that

...Xserver on Dom0 but an error occurres. I have a fresh Debian Lenny install. I''ve installed Xen via aptitude, restarted the system with Xen kernel, and then installed xfce4 with all dependencies. When i try startx i get this errors: (WW) RADEON; No matching Device section for instalnce (BusID PCI:4:0:1) found Fatal server error: xf86MapVidMem: Could not mmap framebuffer (0xdffe0000, 0x10000) (Invalid argument) Waiting for X server to begin accepting connections. giving up. xinit: Connection reset by peer (errno 104): unable to connect to Xserver. xinit: No such process (errno 3): Server...

...ch is almost never.) On the dom0 server I have to do the following steps: */usr/sbin/xm usb-list-assignable-devices* (get the bus-id of the USB device) */usr/sbin/xm usb-hc-create $Domain 2 2* (Create a USB 2.0 Root Hub with 2 ports in $Domain) */usr/sbin/xm usb-attach $Domain $DevId $PortNumber $BusId* (Attach the USB bus-id found in step 1 to the hub created in step 2) On the domU the lsusb looks like this after the above (before it returns nothing) * mgaca:~ # lsusb Bus 001 Device 002: ID 04e6:5116 SCM Microsystems, Inc. SCR331-LC1 SmartCard Reader Bus 001 Device 001: ID 1d6b:0002 Linux Found...

...sage that is followed. But I accidentally found a workround that with ``sudo'', the problem won't occor. Any idea ? KNIGHT:/cvs/emu/ssspsx$ wine SSSPSX libGL: XF86DRIGetClientDriverName: 5.0.3 radeon (screen 0) libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/radeon_dri.so drmOpenByBusid: Searching for BusID pci:0000:01:00.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 10, (OK) drmOpenByBusid: drmOpenMinor returns 10 drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0 ALSA lib seq_hw.c:455:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or dire...