Chris, I think Dani is asking how the module can be loaded dynamically when a peripheral device has been plugged in during the run time. (Assume the .ko files have been put in the image file.)
To Dani, that is about the hotplug mechanism in the kernel, including platform driver, sysfs issues, etc. I believe these have been done in your drivers. The rest of the problem is how the modules can be loaded in automatically at run time, right? In current Linux, it basically relies on udev, with the help from sysfs, such as uevent. I see the similar features in the source of init for Android. However, I still haven't located which file is used to specify the config like the way used by udev. (Kinda busy these days. :( ) Wish the above info could help solve the question, if anyone can provide the answer right away. - William Liang 2011 7 28 02:02 於 "Chris Stratton" <[email protected]> 寫道： On Monday, July 25, 2011 3:46:59 AM UTC-4, David_lavi wrote: > > I have tried , to edit the file but... Have you 1) verified that you can manually insmod the module successfully from the command line? 2) verified that your changes to the configuration files and copying of the module are actually present on the file system after reboot (many systems uncompress their root filesystem from an image; changes have to be made to the image, not the running filesystem, if they are going to survive reboot) -- unsubscribe: [email protected] website: http://groups.google.com/group/and... -- unsubscribe: [email protected] website: http://groups.google.com/group/android-kernel
