... and the complete set of product names (in my emev.mk) is: PRODUCT_NAME := renesas_emev PRODUCT_DEVICE := emev PRODUCT_BOARD := emev PRODUCT_BRAND := emxx PRODUCT_MANUFACTURER := renesas
On Friday, 7 December 2012 11:43:43 UTC+1, ffxx68 wrote: > > Sorry, forgot to mention that the content of init.emxx.rc is a call to > init.emev.sh: > > > --------- > on boot > setprop net.dns1 192.168.0.1 > setprop ro.radio.use-ppp no > setprop ro.radio.noril yes > setprop ro.showcursor 1 > chown system system /sys/class/leds/led1/brightness > chown system system /sys/class/leds/led2/brightness > > service emev-setup /system/etc/init.emev.sh > oneshot > --------- > > > On Friday, 7 December 2012 11:41:46 UTC+1, 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"? >> >> thanks >> Fabio >> >> >> >> > -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
