<div>Hi Philipp,</div><div><br></div><div>The flow you mentioned is something which I was not aware of. I would like to see it happening in code. </div><div><br></div><div>My Queries are as follows:</div><div><br></div>1) "
The kernel then creates an uevent and notifies the userspace part of udev (udevd) through a netlink socket. " - What are the corresponding files that i need to check? If the question is too abstract, kindly explain me with respect to any sample Bus.<div>
<br></div><div>2) "The uevent is received by udevd and now udev can check for rules to add the device node to /dev" - Again the same thing. I would like to see it inside the code. Please help me in looking at the real code.</div>
<div><br></div><div>Thanks again Philipp for your valuable answer.<br><br></div><div>Regards,<br>-Manty<br><div class="gmail_quote">On Fri, Apr 20, 2012 at 7:24 PM, Philipp Ittershagen <span dir="ltr"><<a href="mailto:p.ittershagen@googlemail.com">p.ittershagen@googlemail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Manty!<br>
<div><div class="h5"><br>
On Fri, Apr 20, 2012 at 3:29 PM, manty kuma <<a href="mailto:mantykuma@gmail.com">mantykuma@gmail.com</a>> wrote:<br>
> Hi,<br>
><br>
> I want to know how a node is created when a hardware is connected to the<br>
> system.<br>
><br>
> Information that I know :<br>
> When a hardware is connected to the system, the device name is compared with<br>
> the driver name, if it matches, then probe is called.<br>
><br>
> Info i wish to know:<br>
> At which point is the node created and who is creating it(In other words, i<br>
> want to know where is mknod happening)?<br>
><br>
> This one thing is bugging my mind from so many months. Please tell me<br>
> programatically where is this happening. I will be very thankful.<br>
<br>
</div></div>Please correct me if I'm wrong, my understanding is this:<br>
<br>
The hardware is connected and the corresponding subsystem or bus will<br>
be notified (i.e. by interrupt of the device). The kernel then creates<br>
an uevent and notifies the userspace part of udev (udevd) through a<br>
netlink socket. The uevent is received by udevd and now udev can check<br>
for rules to add the device node to /dev. That's when the creation and<br>
naming of the device node happens.<br>
<br>
<br>
Greetings,<br>
<br>
Philipp<br>
</blockquote></div><br></div>