From: Doran Barton <fozz@iodynamics.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: airo_cs in Fedora Core 3 test
Date: Sat, 06 Nov 2004 02:26:14 +0000 [thread overview]
Message-ID: <20041106030754.GE1480@iodynamics.com> (raw)
In-Reply-To: <20041105231206.GC1480@iodynamics.com>
Not long ago, Kay Sievers proclaimed...
> > 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.
Okay- so it sounds like this is a combination of kernel/PCMCIA code and
udev code which should be resolved soon.
In the meantime, can I manually create the necessary symlink so I can use
the device? If so, what do I need to know?
-=Fozz
--
fozz@iodynamics.com is Doran L. Barton, president, Iodynamics LLC
Iodynamics: Linux solutions - Web development - Business connectivity
"Hospitals are sued by 7 foot doctors"
-- Headline seen in newspaper
-------------------------------------------------------
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
prev parent reply other threads:[~2004-11-06 2:26 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
2004-11-06 2:16 ` Kay Sievers
2004-11-06 2:26 ` Doran Barton [this message]
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=20041106030754.GE1480@iodynamics.com \
--to=fozz@iodynamics.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.