You need to run the insmod in a separate process launched by init. On Tue, Feb 24, 2009 at 4:10 PM, mvniekerk <[email protected]> wrote:
> > Android replaces udev and hotplug with its own substitute helper > program(s). While having a look at /system/core/init/devices.c I see > that it even has support for loading firmware (like in binary blobs > for wifi drivers), thus I deduct that init handles these calls. > > Now here's the problem, when I run "request_firmware" from my kernel > android init doesn't pick up the uevent (and obviously doesn't copy > the firmware to the right /sys file). > Even setting it as the firmware helper in the kernel (which normally > goes to hotplug) only results in the system hanging on bootup. > > So, all ye Android platform porters, what is the elegant Android way > of running an "insmod" that needs firmware? > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
