From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: wait_for_sysfs problem
Date: Thu, 06 Jan 2005 20:55:28 +0000 [thread overview]
Message-ID: <1105044928.6646.42.camel@localhost.localdomain> (raw)
In-Reply-To: <41DA4F9B.7050008@multitech.co.in>
On Thu, 2005-01-06 at 19:30 +0530, shyam wrote:
> 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 ?
I have no idea what's going on here. Is there a public place where we
can get the driver to look at the sources?
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:[~2005-01-06 20:55 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
2005-01-06 15:37 ` shyam
2005-01-06 20:55 ` 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=1105044928.6646.42.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 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.