You can, alternatively, specify androidboot.hardware=emev to the kernel cmdline in your bootloader, or boot.img, whatever.
ffxx68於 2012年12月7日星期五UTC+8下午6時41分46秒寫道： > > 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: [email protected] website: http://groups.google.com/group/android-porting
