> modprobe is "smart" and knows what modules support what devices based on > the cache it creates when you run 'depmod' when a new kernel is > installed. > > That information is found in the drivers themselves. > > See the modprobe code for details if you wish to know the exact > mechanisms involved, it's pretty easy code to understand.
Hi Greg, Thanks a lot :) I just went through the depmod code and it seems that the tables are stored in the 'modinfo' section of the ELF object, and depmod extracts this and dumps it to a map file. And then udev would do a match with this map file whenever a new device is detected and load the required module using modprobe. Do you think my analysis is correct? Regards, -Joel -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to [email protected] Please read the FAQ at http://kernelnewbies.org/FAQ
