Hi everyone,
I built again the Android source code using make ARCH=arm
CROSS_COMPILE=arm-crosstool-linux-gnueabi- and 2 hours later it was
completed.
Then i used the directory : mydroid/out/target/product/generic/root as
filesystem for the board (still using NFS)
Then when i boot the board :
/init
(I've moved init to the more appropriate /sbin directory).
Either that, or you'll have to mount your nfs as /.
FrancoisM wrote:
Alright, I got some progress.
My previous error comes from my ... wild patching. Later I did it
again smoothly using Meld which is a software I recommend
Ok I could chroot successfuly.
[1]+ Segmentation fault chroot /filesys /sbin/init
The result is the same as when I init ed with the run.sh script.
Any suggestion?
On Dec 11, 7:26 pm, Manav Gautama [EMAIL PROTECTED] wrote:
On Thu, 2008-12-11 at 02:23 -0800, FrancoisM wrote:
Oh
. Either your compiling for the wrong
architecture or your toolset is using improper instructions.
FrancoisM wrote:
Ok I could chroot successfuly.
[1]+ Segmentation fault chroot /filesys /sbin/init
The result is the same as when I init ed with the run.sh script.
Any suggestion
Alright, I got some progress.
My previous error comes from my ... wild patching. Later I did it
again smoothly using Meld which is a software I recommend to all of
you guys.
So I got a kernel which boots and is supposed to work with my Android
filesystem, I work with NFS.
I could boot with a
Hi,
I want to know if any of you guys have already ported Android to
DaVinci EVM ( I have the 6446 ) successfully. I happened to port the
m5 version months ago, and now I an going to port the 1.0 version.
Could I still use the 2.6.23 kernel on the board or do I need to
upgrade it to 2.6.25 ? If
