From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: wait_for_sysfs problem
Date: Tue, 04 Jan 2005 15:38:49 +0000 [thread overview]
Message-ID: <1104853129.9042.18.camel@localhost.localdomain> (raw)
In-Reply-To: <41DA4F9B.7050008@multitech.co.in>
On Tue, 2005-01-04 at 13:41 +0530, shyam wrote:
> This is my first port to the group. I have an exar modem Card for which
> I am supporting the driver for 2.6.x kernel. The driver which I use
> works fine with kernel 2.6.5 ( fedora core 2 ) distribution but does not
> work with kernel 2.6.9( fedora core 3 which I understand incorporates
> the udev feature.
> Now during the registration of the driver I get the following
> /var/log/message .
>
> wait_for_sysfs[3794]: either wait_for_sysfs (udev039) needs an update to
> handle the device '/class/tty/cum25' properly ( class specific file
> unavailable) as the sysfs-support of your device driver needs to be
> fixed, please report to <linux-hotplug-devel@lists.sourceforge.net>.
Does your driver use the class driver core? Do you create a "dev" file
in /sys in the class directory?
Kay
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
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:[~2005-01-04 15:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-04 8:23 wait_for_sysfs problem shyam
2005-01-04 15:38 ` Kay Sievers [this message]
2005-01-05 9:18 ` shyam
2005-01-05 20:55 ` Kay Sievers
2005-01-06 14:12 ` shyam
2005-01-06 15:37 ` shyam
2005-01-06 20:55 ` Kay Sievers
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=1104853129.9042.18.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).