From mboxrd@z Thu Jan 1 00:00:00 1970 From: Max Kutny Date: Wed, 03 Nov 2004 12:58:26 +0000 Subject: Re: wait_for_sysfs update for orinoco (eth) Message-Id: <20041103125826.GA8306@maxmobil.umc.com.ua> List-Id: References: <20041103095807.GA7456@maxmobil.umc.com.ua> In-Reply-To: <20041103095807.GA7456@maxmobil.umc.com.ua> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Wed, Nov 03, 2004 at 12:11:28PM +0100, Kay Sievers wrote: > On Wed, Nov 03, 2004 at 11:58:08AM +0200, Max Kutny wrote: > > > > either wait_for_sysfs (udev 042) needs an update to handle the device > > '/class/net/eth1' properly (no device symlink) or the sysfs-support of > > your device's driver needs to be fixed. > > > > As I see, /sys/class/net/eth1 directory exists, so it's not the driver > > problem. > > Thanks, but the message will stay until the pcmcia sysfs support reaches > the mainline kernel and the pcmcia drivers can be changed to create > the "device" symlink to the physical device. Oh, I see now. Misunderstanding rised because syslog entry appeared to be a bit ambiguous. Since I'm not deep in udev I didn't realized from that message that there should be '/sys/class/net/eth1/device' symlink pointing to the physical device. Might it be worth to rewrite udev message? And one more unclarity: why udev writes that it needs an update in case it's a driver problem? -- Max ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_idU88&alloc_id065&op=click _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel