From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: wait_for_sysfs update for orinoco (eth)
Date: Wed, 03 Nov 2004 13:56:16 +0000 [thread overview]
Message-ID: <1099490176.20353.44.camel@localhost.localdomain> (raw)
In-Reply-To: <20041103095807.GA7456@maxmobil.umc.com.ua>
On Wed, 2004-11-03 at 14:58 +0200, Max Kutny wrote:
> 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?
Some devices are virtual only and don't have this symlink for good
reason. So wait_for_sysfs may need a new entry to handle it or the
driver needs to create the link - wait_for_sysfs can't be sure
what's wrong here.
But it's a good question. We may print a more specific message in the
class/net/eth* case. I will look into that.
Thanks,
Kay
-------------------------------------------------------
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_id\x12065&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
next prev parent reply other threads:[~2004-11-03 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-03 9:58 wait_for_sysfs update for orinoco (eth) Max Kutny
2004-11-03 11:11 ` Kay Sievers
2004-11-03 12:58 ` Max Kutny
2004-11-03 13:56 ` Kay Sievers [this message]
2004-11-03 14:20 ` Max Kutny
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1099490176.20353.44.camel@localhost.localdomain \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).