From: Greg KH <gregkh@linuxfoundation.org>
To: Li Haifeng <omycle@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: To built-in Driver, When the corresponding node under /dev created?
Date: Tue, 27 Mar 2012 13:53:20 -0700 [thread overview]
Message-ID: <20120327205320.GA20151@kroah.com> (raw)
In-Reply-To: <CAFNq8R5FqEZG1rx54LSv-iAcc9keG-dNKe5fAiEWMBe2sS-nSg@mail.gmail.com>
On Tue, Mar 27, 2012 at 02:39:37PM +0800, Li Haifeng wrote:
> As you know, the node under /dev are managed by udevd daemon.
Not always, usually the node is created by devtmpfs on most modern
distros.
> But to the built-in driver module, when the module is probed in kernel
> space, udevd daemon doesn't running. So, to ttyS node, when the
> built-in driver module was probed, when was the /dev/ttyS created?
devtmpfs does it.
Also, look at your distro startup code, it sets things up properly when
userspace starts up and has udev go through things and set up the nodes
then.
good luck,
greg k-h
next prev parent reply other threads:[~2012-03-27 20:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 6:39 To built-in Driver, When the corresponding node under /dev created? Li Haifeng
2012-03-27 20:53 ` Greg KH [this message]
2012-03-28 0:44 ` Li Haifeng
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=20120327205320.GA20151@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=omycle@gmail.com \
/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