From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: question about misc char devices, and relationship with udev
Date: Sat, 23 Apr 2011 08:09:40 -0700 [thread overview]
Message-ID: <20110423150940.GA28938@kroah.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1104230935370.10665@localhost6.localdomain6>
On Sat, Apr 23, 2011 at 09:45:39AM -0400, Robert P. J. Day wrote:
> but here's the confusing part. who or what created that /dev entry?
> i always thought that was the job of udev, but i never added any udev
> rule for this new driver. so how did that new /dev file come to be?
> is there some sort of generic udev rule that would have handled this?
Yes there is, udev took the default kernel name and created the device
node for it. The misc device is exported in sysfs automatically by the
misc core code, as you pointed out with the call to device_create().
And, in newer versions of your distro, devtmpfs created the device node,
udev just set the permissions on it.
Hope this helps,
greg k-h
next prev parent reply other threads:[~2011-04-23 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-23 13:45 question about misc char devices, and relationship with udev Robert P. J. Day
2011-04-23 15:09 ` Greg KH [this message]
2011-05-05 14:43 ` onlyfever
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=20110423150940.GA28938@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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).