From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Help with simple char device
Date: Fri, 31 Dec 2004 06:23:05 +0000 [thread overview]
Message-ID: <1104474185.6801.14.camel@localhost.localdomain> (raw)
In-Reply-To: <1104471165.7269.10.camel@penguin.montes2.org>
On Thu, 2004-12-30 at 21:32 -0800, Luis A. Montes wrote:
> Hi there,
>
> I'm trying to write a simple char device driver. I've used as starting
> point code that someone posted recently to the list (I can't find the
> post now, it was a file called mymod.c). Anyway, I do:
>
> alloc_chrdev_region()
> cdev_alloc()
> set owner and file operations
> kobject_set_name()
> cdev_add()
> class_simple_create()
> class_simple_device_add()
>
> It nicely creates a /dev/ entry, but it then complains:
>
> wait_for_sysfs[5689]: either wait_for_sysfs (udev 042) needs an update
> to handle the device '/class/mydevclass/mydev' 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>
>
> Any pointers to what else do I need to do?
Just upgrade udev to get rid of the message or simply ignore it.
(That's cause udev doesn't know about that class name and the default is
to expect a symlink to the physical device. Newer udev versions will not
print this message and kernel 2.6.10 will carry the information in the
hotplug environment to let udev explicitly know what to wait for.)
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
prev parent reply other threads:[~2004-12-31 6:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-31 5:32 Help with simple char device Luis A. Montes
2004-12-31 6:23 ` Kay Sievers [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=1104474185.6801.14.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).