All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: udev/hotplug and automatic /dev node creation
Date: Wed, 25 Jan 2006 07:33:03 -0800	[thread overview]
Message-ID: <20060125153303.GA18932@kroah.com> (raw)
In-Reply-To: <20060125125017.GD10068@quickstop.soohrt.org>

On Wed, Jan 25, 2006 at 01:50:17PM +0100, Horst Schirmeier wrote:
> On Tue, 17 Jan 2006, Greg KH wrote:
> > 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.
> 
> Now I'm using class_create() and class_device_create() (together with
> class_device_destroy() and class_destroy()), which works fine on
> 2.6.15 and 2.6.16-rc1, and with some hackish LINUX_VERSION_CODE-checking
> #define wrapper around class_device_create() also on 2.6.13 and
> 2.6.14...
> 
> But: Is there a common way to get this working on 2.6.12 or earlier?

Look at the class_simple* functions in that older kernel version.  They
should do much of the same thing of what you need.

Hope this helps,

greg k-h

      reply	other threads:[~2006-01-25 15:33 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
2006-01-18 12:13   ` Horst Schirmeier
2006-01-25 12:50   ` Horst Schirmeier
2006-01-25 15:33     ` Greg KH [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=20060125153303.GA18932@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.