From: "Jike Song" <albcamus@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Creating dev nodes from driver or via uevent?
Date: Wed, 15 Oct 2008 15:23:49 +0800 [thread overview]
Message-ID: <df9815e70810150023w2a14fad5ge08ea4edad4ae0b1@mail.gmail.com> (raw)
In-Reply-To: <20081015063917.GA18487@true>
On Wed, Oct 15, 2008 at 2:39 PM, Fabiano Sidler <lists@fipscode.ch> wrote:
> Hi folks!
>
> Probably a very basic question, but is it better to directly mknod from a
> module's init funtion or to use the uevent/udev mechanism? If the latter,
> are there good overviews, explanations and comprehensive code samples
> especially for using udev,
You can refer to any in-tree driver that calls class_create() and
device_create_drvdata() afterwards. say drivers/char/raw.c
LDD3 by Greg has some descriptions on this, but since the interface
has changed..
--
Thanks,
Jike
next prev parent reply other threads:[~2008-10-15 7:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 6:39 Fabiano Sidler
2008-10-15 7:23 ` Jike Song [this message]
2008-10-15 8:45 ` 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=df9815e70810150023w2a14fad5ge08ea4edad4ae0b1@mail.gmail.com \
--to=albcamus@gmail.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®