Run L4linux on ARM platform
kashin08 at gmail.com
Mon Jul 9 11:11:11 CEST 2007
the l4linux system architecture from buttom to up is : hardware→ fiasco→
according to the webpage(
http://os.inf.tu-dresden.de/L4/LinuxOnL4/build-2.6.shtml ) description
, make l4env first then make l4linux,i am confused that the sequence of
compile full L4Linux system.
when to config fiasco & make it?
due to the l4linux system architecture mentioned above, the sequence of
build all system should
1. config fiasco
2. make fiasco
3. config l4env
4. make l4env
5. config l4linux
6. make l4linux
is it right? if not, what should it be?
2007/7/6, Adam Lackorzynski <adam at os.inf.tu-dresden.de>:
> On Thu Jul 05, 2007 at 23:31:38 +0800, kashin Lin wrote:
> > 2007/7/5, Adam Lackorzynski <adam at os.inf.tu-dresden.de>:
> > >
> > >
> > >On Thu Jul 05, 2007 at 00:15:15 +0800, kashin Lin wrote:
> > >
> > >> 2. as you metioned above, i should adapt the configuration of fiasco
> > >> to my target platform,
> > >> but... (1) when do i do this? before make anything?
> > >
> > >Not only the configuration but also the code. You probably need to
> > >write a e.g. UART driver for your platform. As I said, I don't know
> > >which UART is used on your board. Can you tell which type of UART is
> > >used there?
> > There is a UART (RS232 port) which can communicate with PC.
> > how to add that UART driver in fiasco?
> You need to add a new platform. Basically you can do the same thing as
> it's done with the integrator platform. The UART implementation goes to
> src/lib/uart/arm, and need to be hooked in
> > are there any other platform dependent things that need to touch the
> Most likely. The PIC implementation goes to src/kern/arm/pic-arm.cpp,
> and the timer goes to src/kern/arm/timer-arm.cpp. Other files to look at
> are Modules.arm to specify the label to build under and probably
> rules.cml to add a new platform. The CPU specific things may also need
> Adam adam at os.inf.tu-dresden.de
> Lackorzynski http://os.inf.tu-dresden.de/~adam/
> l4-hackers mailing list
> l4-hackers at os.inf.tu-dresden.de
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the l4-hackers