compile error svn rev 27 on x86

Adam Lackorzynski adam at os.inf.tu-dresden.de
Fri Nov 26 00:19:28 CET 2010


On Thu Nov 25, 2010 at 13:24:20 -0800, lkcl wrote:
> 
> WHA-HEY! success on x86 build and test "hello".  okay, now for something
> completely different: ever since i heard about it i always wanted to get
> l4linux up-and-running, i even mentioned it on LKML and it resulted in one
> of the larger flame-fests... *sigh* they were highly critical of OSKit, i
> _did_ mention that the l4linux team had done significant work on OSKit but
> they simply weren't interested in listening, it was more important that they
> prove themselves right and prove l4linux worthless... never mind...

Well, what should I say :)
 
> anyway: let's give it a shot.  so, here's what i want to do:
> 
> * first get x86 qemu running, but then move to an ARM-qemu'd l4linux. 
> regarding this: i've found
> http://os.inf.tu-dresden.de/L4/LinuxOnL4/use-2.6.shtml and
> http://wiki.tudos.org/L4Linux/configurations but no advice on what to do! 
> yes i see the grub2iso "hello" example, but... err... err? :)  so, am i just
> being spectacularly thick, here?  replace ... nope, i'm not mentally getting
> it.  help!  and how do i then use / enable l4con (add it to modules.list?
> help!) so that the l4linux kernel will use it?

There are config examples in l4/conf/examples. Launching the L4Linux is
just a matter of saying where to find all the files. So, given you have
qemu ready to run (i.e. version 0.13 or better), you can do in the l4
build root directory:
  make qemu E=L4Linux-mag-x86 MODULE_SEARCH_PATH=.../l4/conf/examples:.../fiasco/build-for-ia32:.../l4/pkg/io/config:../l4linux-x86-build:/tmp

Before, download: wget -O /tmp/ramdisk-x86.rd http://os.inf.tu-dresden.de/download/ramdisk-x86.rd

To make it easier for later calls, check l4/conf/Makeconf.boot.example, you can
put all the paths there. Then things like "make grub2iso E=L4Linux-mag-x86"
will just work (ISO will be in images dir).

> * find out how to develop apps; port directfb to l4re.  (directfb 1.5 has an
> abstraction layer, now, so this should be a bit easier).

Sounds good. L4Re has a framebuffer/event interface that perfectly fits for
that.
 
> * investigate (... don't freak out too much... :) porting webkit to l4re
> (using directfb). apparently uclibc is supported, so i don't see it being
> particularly monstrously hard.  the reason for considering this is that i've
> just had some success getting WebkitDFB up-and-running and the startup time
> on an embedded 400mhz ARM926 is QUICK.  like, 1 second startup "quick".  i
> figured therefore that it would be worthwhile to investigate cutting out
> even the linux kernel, and have a literally "switch the box on, it's
> running" web browser.  i feel it's worth doing.

Sound interesting.


Adam
-- 
Adam                 adam at os.inf.tu-dresden.de
  Lackorzynski         http://os.inf.tu-dresden.de/~adam/




More information about the l4-hackers mailing list