thanks!
Unfortunaly, memchunk.vpu=8m memchunk.veu0=4m extra boot options did
not work as linux 'Unknown boot option'
i must admit the ramdisk usage and RAM location is a bit confusing to
me. :-/
I moved the ramdisk loading init to 0x81008000 (RAM base address +
more the 8MB) as you suggested :
Thanks for your help.
below the u-boot command line I run :
setenv bootargs_android 'setenv bootargs ${bootargs} init=/init
androidboot.console=ttymxc0 wvga calibration'
setenv bootargs_base 'setenv bootargs mem=64M rootwait
console=ttymxc0,115200'
setenv bootargs_SD 'setenv bootargs ${bootargs}
I suppose ramdisk mounting could be one of those reason why script
files are not able to execute, you better have to move the ramdisk
where it does not overlap with kernel and ram filesystem, as kernel
always relocates when it starts booting, therefore you better make
sure there is 8M to 16M
Do you have any idea why the init process does not interpret the
init.rc command file (invalid option)?
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
init.rc is not a shell script to have mkdir working, and it should comply
to its own syntax.,
the best write up i've seen is -
http://www.androidenea.com/2009/08/init-process-and-initrc.html
btw, commands like echois not available, but there is a 'write'
option.,
very few commands like chmod,
update: mkdir is actually supported command..,
http://www.kandroid.org/android_pdk/bring_up.html
it'll be helpful if u share ur init.rc..
On Tue, Jun 29, 2010 at 9:07 PM, Deva R r.deva...@gmail.com wrote:
init.rc is not a shell script to have mkdir working, and it should comply
to its own
My guess would be something regarding nfs options that make the file not
interpreted as a unix file. Either that, or the init.rc is improperly
formed.
On 06/29/2010 10:32 PM, fpirou wrote:
Do you have any idea why the init process does not interpret the
init.rc command file (invalid option)?
