linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: airo_cs in Fedora Core 3 test
Date: Sat, 06 Nov 2004 01:05:08 +0000	[thread overview]
Message-ID: <20041106010508.GA24694@vrfy.org> (raw)
In-Reply-To: <20041105231206.GC1480@iodynamics.com>

On Fri, Nov 05, 2004 at 04:12:06PM -0700, Doran Barton wrote:
> Hey people,
> 
> I'm running the 2.4.9-643 kernel for FC3t3 on a HP Pavilion zv5000z laptop
> (AMD Athlon 64 3000). With the 2.4.8 kernel on FC2, I had no problem using
> my Aironet 350 PCMCIA wireless network adapter, but there was no udev in
> FC2.
> 
> So, when I insert the card now, I get this in my messages file:
> 
>   Nov  5 14:49:29 moo kernel: eth1: index 0x05: Vcc 5.0, Vpp 5.0, irq 11, io
>   0x4100-0x413f
>   Nov  5 14:49:34 moo wait_for_sysfs[5906]: either wait_for_sysfs (udev 039)
>   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,
>   please report to <linux-hotplug-devel@lists.sourceforge.net>
>   Nov  5 14:49:34 moo wait_for_sysfs[5908]: either wait_for_sysfs (udev 039)
>   needs an update to handle the device '/class/net/wifi0' properly (no device
>   symlink) or the sysfs-support of your device's driver needs to be fixed,
>   please report to <linux-hotplug-devel@lists.sourceforge.net>
>   
> Could someone tell me if this a udev issue or a kernel issue?

It is caused by the fact, that the driver of the card does not create
the expected "device" symlink in the class device's sysfs representation,
pointing to the physical device in sysfs.  This symlink is necessary for
e.g. modern hardware integration to match the virtual with the physical
device.

1.
PCMCIA-sysfs is not supported now, but already in the -mm kernel, so this
should be fixed sooner than later.

2.
The latest wait_for_sysfs in the udev package will not print any error for
net devices.

3.
Kernel 2.6.10* and later will add what we can expect in sysfs to the hotplug
event, so we can handle that right, without useless waiting for the symlink
and printing errors.

o.k.? :)

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

  reply	other threads:[~2004-11-06  1:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-05 22:40 airo_cs in Fedora Core 3 test Doran Barton
2004-11-06  1:05 ` Kay Sievers [this message]
2004-11-06  2:16 ` Kay Sievers
2004-11-06  2:26 ` Doran Barton

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=20041106010508.GA24694@vrfy.org \
    --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).