Hi,
I'm wondering if some of the coLinux developers could hop on the
networkmanager mailing list?
I submitted my patch for NetworkManager, but it seems the general
opinion there is that the coLinux network driver is not implemented
correctly. The discussion is over my head, and if I'm going to need to
submit a patch for coLinux instead, then some of the developers should
give their input to what it should look like. If the coLinux driver is
implemented correctly, then a case needs to be made for that, so
NetworkManager can be patched to accommodate.
Note: For reference, I have attached my patch for NetworkManager.
Bill
-------- Original Message --------
Subject: Re: Patch to support drivers compiled into the kernel
Date: Tue, 3 Mar 2009 19:29:48 +0100
From: Kay Sievers <kay...@vr...>
To: Bill C Riemers <bri...@re...>
CC: Dan Williams <dc...@re...>, Net...@gn...
References: <49A...@re...>
<1236093674.27170.11.camel@localhost.localdomain>
<ac3...@ma...>
<1236102533.27170.52.camel@localhost.localdomain>
<ac3...@ma...>
<49A...@re...>
On Tue, Mar 3, 2009 at 19:20, Bill C Riemers <bri...@re...> wrote:
> I'm sorry, it seems the list manager did not deliver all the replies Kay
> Sievers quoted...
> 13: udi = '/org/freedesktop/Hal/devices/net_00_ff_d3_da_b0_00'
> net.interface = 'eth0' (string)
> linux.sysfs_path = '/sys/class/net/eth0' (string)
> net.address = '00:ff:d3:da:b0:00' (string)
> info.parent = '/org/freedesktop/Hal/devices/computer' (string)
Seems the driver does not set its parent device properly in the
kernel. That nothing to fix in HAL or NM, it's a rather trivial kernel
driver fix. What's the driver that creates your eth0 interface? It's
usually one of that list:
ls -l /sys/bus/pci/drivers/
Also note, no recent kernel should set CONFIG_SYSFS_DEPRECATED=y.
Recent udev/HAL does not supports that old sysfs format properly
anymore. You should not see any "/sys/class/..." path in HAL, they
should all start with "/sys/devices/...".
Kay
|
