On Sun Jan 04, 2015 at 12:05:40 +, Lin wrote:
> I'm trying to get L4Android working on a PandaBoard ES(OMAP 4460). I managed
> to run Fiasco and L4Linux successfully, but L4Android give me some error:
> MOE: Starting: rom/ned rom/l4_gingerbread-arm.cfg
> MOE: loading 'rom/ned'
> Ned says: Hi W
Hi hackers,
I'm trying to get L4Android working on a PandaBoard ES(OMAP 4460). I managed
to run Fiasco and L4Linux successfully, but L4Android give me some error:
Welcome to Fiasco.OC (arm)!
L4/Fiasco.OC arm microkernel (C) 1998-2013 TU Dresden
Rev: unknown compiled with gcc 4.7.3 for Pandaboard
On 19.06.2012, at 15:49, ZhangEditing wrote:
> android_bus => new System_bus()
> {
> sys => wrap(hw-root.sys);
> prcm => wrap(hw-root.prcm);
> sysdma => wrap(hw-root.sysdma);
> gic => wrap(hw-root.gic);
> hsmmc1 => wrap(hw-root.hsmmc1);
> hsmmc2 => wrap(hw-root.hsmmc2);
> hs
On 18.06.2012, at 02:59, ZhangEditing wrote:
> > You should have a look into the Pandaboard TRM and gather the right MMIO
> > regions needed for MMC etc. Then connect those to the vbus for the
> > L4Android kernel.
>
> I tried to do so, but L4Android recognizes only SDHCI. Maybe I still missed
On 17.06.2012, at 15:28, ZhangEditing wrote:
> I tried to pack the system image of Android userland together with the kernel
> into a single U-image, but Pandaboard cannot finish loading the U-image.
Probably the size of the image is too big.
> So I unpacked the system image to a separate part
Hello, everyone!
I'm new to L4Android and I'm interested in running L4Android on Pandaboard
(OMAP4430).
I tried to pack the system image of Android userland together with the kernel
into a single U-image, but Pandaboard cannot finish loading the U-image.
If the system image
