booting, therefore you better make
sure there is 8M to 16M difference between kernel and ramdisk.
-Subbu
On Thu, Jul 1, 2010 at 8:07 AM, fpirou fpi...@googlemail.com wrote:
Thanks for your help.
below the u-boot command line I run :
setenv bootargs_android 'setenv bootargs ${bootargs} init
system system
oneshot
On 29 juin, 18:12, Sean McNeil seanmcne...@gmail.com wrote:
My guess would be something regarding nfs options that make the file not
interpreted as a unix file. Either that, or theinit.rcis improperly
formed.
On 06/29/2010 10:32 PM, fpirou wrote:
Do you have any idea
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
Hi,
I am newbies at android porting.
I compiled 2.6.31 linux kernel and Android 2.1 (eclair) for an iMX25
(ARM926EJ-S) target.
But, when I mount Android file system, using an NFS server, on top of
linux kernel the /init.rc bash commands are NOT interpreted, as shown
below:
Is there some package
Hi,
I am newbies at android porting. I compiled both 2.6.31 linux kernel
and android 2.1 (eclair) for iMX25 based target (ARM926EJ-S) without
errors.
But, when mounting android file system, through NFS, on top of linux
kernel, the bash shell commands of the /init/init.rc file are NOT
interpreted
