Dan Williams wrote: > On Tue, 2009-03-03 at 13:45 -0500, Bill C Riemers wrote: > >> Hmm. 2.6.22 is not very old. It is the most recent "stable" coLinux >> version. I certainly hope we don't decide this is a driver problem..., >> as that will be much more of a pain to try and get fixed. >> I wouldn't expect to find to find a virtual driver using the PCI bus. >> In fact, since Windows has control of the PCI bus, I would not be >> surprised if there are no PCI bus drivers for coLinux. >> >> [r...@localhost ~]# ls -la /sys/bus/pci/drivers >> ls: cannot access /sys/bus/pci/drivers: No such file or directory >> [r...@localhost ~]# uname -a >> Linux localhost.localdomain 2.6.22.18-co-0.7.3 #1 PREEMPT Sat May 24 >> 22:27:30 UTC 2008 i686 i686 i386 GNU/Linux >> >> As near as I can tell NetworkManager never actually uses the driver >> information, except in print statements. So setting a value like >> "<unknown>" or "<kernel>" is probably better than ignoring the network >> device. >> > > The driver gets used in a number of places for quirks. It's also a > mechanism to filter crappy drivers that don't set up sysfs correctly, > and to ensure that the device's information can be properly obtained by > applets, which need things like PCI/USB/PCMCIA device and vendor IDs. > If the driver isn't properly setting up the device link in sysfs, then > the driver needs to be fixed because it's a bug in the driver. We don't > improve the whole situation by working around the bugs, we fix the bugs > at their source... > > Dan >
OK. If I need to go and patch coLinux, I will. But what are the correct values? There is no PCI/USB/PCMCMIA device. This is virtual. Do I need to invent a dummy driver and label it as the parent? Bill _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
