From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Pci driver and udev...
Date: Tue, 07 Nov 2006 08:14:52 +0000 [thread overview]
Message-ID: <20061107081452.GA7048@kroah.com> (raw)
In-Reply-To: <acb938930611060831y61126785sf698369a19d2b2d4@mail.gmail.com>
On Mon, Nov 06, 2006 at 05:31:02PM +0100, Kris van Rens wrote:
> So I assume the cdev stuff is just for 'internal' registration of the
> character device and something else should be used to tell udev a new
> device is there?
Yes, that is true.
> So I found the part about udev and 'class_simple_*' in the ldd3 book
> but that was deleted from the kernel.
>
> As I understand it was replaced by the better version of 'class' but I
> kind of lost in all the functions in base/class.c...
>
> Can someone enlighten me?
class_device_create() is what you should look at. Actually, I'd
recommend just using device_create() with a class instead, it's what I'm
converting the kernel to use in all places for class_device_create().
thanks,
greg k-h
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2006-11-07 8:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-06 16:31 Pci driver and udev Kris van Rens
2006-11-07 8:14 ` Greg KH [this message]
2006-11-07 8:38 ` Kris van Rens
2006-11-08 11:14 ` Kris van Rens
2006-11-08 14:10 ` Kris van Rens
2006-11-08 17:32 ` Bryan Kadzban
2006-11-08 18:22 ` Kris van Rens
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=20061107081452.GA7048@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).