From: shyam <shyamkumar@multitech.co.in>
To: linux-hotplug@vger.kernel.org
Subject: Re: wait_for_sysfs problem
Date: Wed, 05 Jan 2005 09:18:09 +0000 [thread overview]
Message-ID: <41DBAE01.7030801@multitech.co.in> (raw)
In-Reply-To: <41DA4F9B.7050008@multitech.co.in>
Thanks Kay,
It would be nice if anybody could tell me how to create a "dev" file in
my /sys directory. 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.
thanks once again,
shyam
Kay Sievers wrote:
>On Wed, 2005-01-05 at 10:03 +0530, shyam wrote:
>
>
>>Hi Kay,
>>I don't create a "dev" file in my /sys directory. How is that going to
>>help. Please give me some pointers on that.
>>
>>
>
>It is needed for udev to read the major/minor to be able to create the
>device node. Just look at any of the other class device drivers in the
>kernel.
>
>If you need further information, please reply to the list on the
>original thread. Answers may be helpful for/from others too.
>
>Good luck,
>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-05 9:18 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 [this message]
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=41DBAE01.7030801@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 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.