From: onlyfever@gmail.com (onlyfever)
To: kernelnewbies@lists.kernelnewbies.org
Subject: question about misc char devices, and relationship with udev
Date: Thu, 5 May 2011 22:43:49 +0800 [thread overview]
Message-ID: <BANLkTinad6axAVd6ti12G6drkGSQGRozXg@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1104230935370.10665@localhost6.localdomain6>
> ?also, the ELDD book claims that misc_register() calls the kernel
> routine class_device_create(). ?i'm looking at the entire
> kernel implementation for misc drivers in drivers/char/misc.c, and
> what i see is a call to device_create() instead. ?i suspect i should
> start following the flow of control here, but i'm still curious as to
> how that /dev file came into existence without any obvious help
> from udev.
In linux 2.6.20,kernel still use class_device_create().
After linux 2.6.22(maybe,I can't remember),kernel use device_create()
instead of class_device_create().
prev parent reply other threads:[~2011-05-05 14:43 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
2011-05-05 14:43 ` onlyfever [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=BANLkTinad6axAVd6ti12G6drkGSQGRozXg@mail.gmail.com \
--to=onlyfever@gmail.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).