How the kernel scan the pci devices:
In /arch/x86/pci/legacy.c,
*pci_legacy_init()* invoke
- *pcibios_scan_root(0) *to scan pci devices from the root bus,
if the bus is already scanned then just return;
else the
- *pci_scan_bus_parented() *will be invoked, in this f
On Tue, Nov 23, 2010 at 3:07 AM, Yuchen Liao wrote:
> AFAIK, in the device_add() function (in driver/base/core.c), kernel will
> invoke "device_create_file()" function to create the "uevent" file;
> (The kobj is also added in this device_add() function by invoke
> kobject_add() function)
> In user
AFAIK, in the device_add() function (in driver/base/core.c), kernel will
invoke "device_create_file()" function to create the "*uevent*" file;
(The kobj is also added in this device_add() function by invoke
kobject_add() function)
In user space, the *udevd* is listening the NETLINK_KOBJECT_EVENT t
On Mon, Nov 22, 2010 at 13:37, Bond wrote:
> Hi, in some of the books I am reading I find
> a text which mentions MODULE_DEVICE_TABLE () macro makes a user
> defined structure available in the module image so that the module
> can be loaded on demand if the card is hotplugged.
> I am not clear w
