I find no message about init.xxxx.rc as you said in kernel or logcat boot. I've also tried with these init.xxxx.rc names:
init.EMXX.rc init.emev.rc but still the script isn't called.... I'm getting crazy with it! What's irritating is that calling it manually everything goes fine. What else to check? On Friday, 7 December 2012 12:31:05 UTC+1, Vishveshwar wrote: > > On Friday, December 7, 2012 4:11:46 PM UTC+5:30, ffxx68 wrote: >> >> Hi, >> >> I'm struggling to find a solution to this problem. >> >> I have a device with the following definitions: >> >> emev.mk:PRODUCT_NAME := renesas_emev >> emev.mk:PRODUCT_DEVICE := emev >> emev.mk:PRODUCT_BOARD := emev >> >> PRODUCT_COPY_FILES += \ >> $(LOCAL_PATH)/init.rc:root/init.rc \ >> $(LOCAL_PATH)/ueventd.emev.rc:root/ueventd.emxx.rc \ >> $(LOCAL_PATH)/init.emev.rc:root/init.emxx.rc \ >> $(LOCAL_PATH)/init.emev.sh:system/etc/init.emev.sh \ >> >> >> (details here: https://github.com/Renesas-EMEV2/Renesas-device_emev) >> >> Now, in "init.emev.sh" there's the call to the insmod for the SGX >> graphics modules. >> When I boot the device, SGX modules aren't initialized, until I manually >> invoke the init.emev.sh, e.g. from host: >> >> adb shell /system/etc/init.emev.sh >> >> which allows to finally startup the SGX and complete device boot up. >> >> What's wrong in my build env? >> Is it PRODUCT_DEVICE, or PRODUCT_BOARD, that should be set to "emxx"? >> > > What is the machine name set in your kernel board file? This is what > android init expects your filename to contain. > . e.g for Nexus 7 (grouper) it is set to "grouper" like this in > arch/arm/mach-tegra/board-grouper.c > MACHINE_START(GROUPER, "grouper") > > Check the kernel boot log, you may see an error about init.xxx.rc not > found. > > -Vishveshwar > >> >> thanks >> Fabio >> >> >> > -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
