Hi mvniekerk, Could you say more details about how you to add path on the init.rc? I met the same problem :'( Thanks.
Mike. mvniekerk於 2009年2月25日星期三UTC+8上午3時00分48秒寫道： > > Sorry, I had a pebkac problem. Typo on the path on the init.rc. It > works! Thanks David. > > On Feb 24, 8:53 pm, mvniekerk <[email protected]> wrote: > > By doing insmod manually works when in the sh shell, but putting > > "insmod /lib/modules/2.6.25/kernel/drivers/mmc/card/unifi_fs/ > > unifimodule.ko" does not work. Any pointers? > > > > On Feb 24, 5:32 pm, mvniekerk <[email protected]> wrote: > > > > > And the kernel, what must I do about the kernel firmware helper? (make > > > menuconfig->Device Drivers->Generic Driver Options->path to uevent > > > helper) > > > > > On Feb 24, 5:14 pm, David Turner <[email protected]> wrote: > > > > > > 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
