From: shyam <shyamkumar@multitech.co.in>
To: linux-hotplug@vger.kernel.org
Subject: Re: wait_for_sysfs problem
Date: Thu, 06 Jan 2005 14:12:06 +0000 [thread overview]
Message-ID: <41DD4466.1080006@multitech.co.in> (raw)
In-Reply-To: <41DA4F9B.7050008@multitech.co.in>
I used the class_simple file to create a "dev" file in the /sys and I
used the following functions
1)class_simple_create
2)class_simple_device_add
3)class_simple_device_remove.
Following are my observations-
a)I find my "dev" i.e. "modem" being created in /sys/class but the
directory is empty. Is it that I need to make nodes inside this directory?
b)Now should I make the nodes using mknod ?
While compiling the driver I *again* encountered the following message.
wait_for_sysfs[8956]: either wait_for_sysfs (udev 039) needs an update
to handle the device '/class/tty/cum8' properly (class specific file
unavailable) or the sysfs-support of your device's driver needs to be
fixed, please report to <linux-hotplug-devel@lists.sourceforge.net>
Kay Sievers wrote:
>On Wed, 2005-01-05 at 14:36 +0530, shyam wrote:
>
>
>>It would be nice if anybody could tell me how to create a "dev" file in
>>my /sys directory.
>>
>>
>
>You may look at:
> drivers/base/class_simple.c
>
>how a simple version of class device is doing it, which is needed for
>udev to create the /dev node automatically for you. If you don't need to
>roll you own class registration, you may even just use the class_simple
>and it will do it for you.
>
>
>
>>I do create the nodes in the /dev directory. I find
>>some ttyMU{0-31} files in /sys/class/tty directory. They do have the
>>same major number and minor number that I give in my make file but that
>>is not the name that I give in the makefile. For example I give ttyMU1{a
>>-h} in my make file which I update in the /dev directory.
>>
>>
>
>Hard to guess, is the driver publicly available somewhere?
>
>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
>
>
>
-------------------------------------------------------
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-06 14:12 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
2005-01-05 9:18 ` shyam
2005-01-05 20:55 ` Kay Sievers
2005-01-06 14:12 ` shyam [this message]
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=41DD4466.1080006@multitech.co.in \
--to=shyamkumar@multitech.co.in \
--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).