From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: who sends from the kernel an event to udevd netlink socket?
Date: Mon, 27 Mar 2006 11:30:38 +0000 [thread overview]
Message-ID: <20060327113038.GA13400@vrfy.org> (raw)
In-Reply-To: <dac45060603270310m6c5e91b2o2bfbc2ba75d66cd4@mail.gmail.com>
On Mon, Mar 27, 2006 at 01:10:29PM +0200, Mark Ryden wrote:
> Hello,
> I wonder:
> In the last versions of udev, which work **WITHOUT** hotplug:
> as I understand, there is a udevd daemon which listens on a NETLINK socket
> to events which come from the kernel.Suppose I plug to the USB socket
> an ov511 webcam; who
> sends the "ADD" event to the udevd NETLINK socket?
> I had looked at the code of ov511.c
> (drivers/usb/media in the kerbnel tree)
> I saw that there is creation of sysfs entries
> (in ov51x_probe, there is a call to ov_create_sysfs())
> So my question is : is this adding to sysfs is the one that causes sending
video_register_device -> class_device_register -> class_device_add -> kobject_uevent
Kay
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&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-03-27 11:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-27 11:10 who sends from the kernel an event to udevd netlink socket? Mark Ryden
2006-03-27 11:30 ` Kay Sievers [this message]
2006-03-27 13:13 ` Mark Ryden
2006-03-27 14:07 ` Kay Sievers
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=20060327113038.GA13400@vrfy.org \
--to=kay.sievers@vrfy.org \
--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).