From: Greg KH <greg@kroah.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: udev/hotplug and automatic /dev node creation
Date: Tue, 17 Jan 2006 20:07:18 -0800 [thread overview]
Message-ID: <20060118040718.GA6579@kroah.com> (raw)
In-Reply-To: <20060118024710.GB26895@quickstop.soohrt.org>
On Wed, Jan 18, 2006 at 03:47:10AM +0100, Horst Schirmeier wrote:
> Hi,
>
> I'm looking for documentation regarding how to write a Linux kernel
> module that creates its own /dev node via udev/hotplug.
> register_chrdev() and a simple udev/rules.d/ entry don't seem to be
> sufficient...
Yes, register_chrdev() will do nothing for udev.
Take a look at the book, Linux Device Drivers, third edition (free
online). In the chapter about the driver model, there is a section
about what udev needs. The functions it says to use are no longer in
the kernel, but it should point you in the right direction (hint, use
class_device_create().)
If you have a pointer to your code, I can probably knock out a patch for
you very quickly.
thanks,
greg k-h
next prev parent reply other threads:[~2006-01-18 4:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 2:47 udev/hotplug and automatic /dev node creation Horst Schirmeier
2006-01-18 4:07 ` Greg KH [this message]
2006-01-18 12:13 ` Horst Schirmeier
2006-01-25 12:50 ` Horst Schirmeier
2006-01-25 15:33 ` Greg KH
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=20060118040718.GA6579@kroah.com \
--to=greg@kroah.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