June 2016 - l4-hackers - example.com Site

Porting Fiasco + L4Re to Raspberry Pi 2
by Antoine DEBUT 26 Nov '17

26 Nov '17

Hello l4-hackers, I am currently working on porting the Fiasco.OC micro kernel onto the Raspberry pi 2. Therefore, I am struggling with memory mapping, and I encounter the following error when launching the default 'hello' entry: L4 Bootstrapper Build: #2 Tue Feb 23 11:57:19 CET 2016, 4.8.3 20140303 (prerelease) Scanning up to 1024 MB RAM, starting at offset 32MB Memory size is 1024MB (00000000 - 3fffffff) RAM: 0000000000000000 - 000000003fffffff: 1048576kB Total RAM: 1024MB Scanning fiasco Scanning sigma0 Scanning moe Moving up to 5 modules behind 1100000 moving module 02 { 10db000-110c4d7 } -> { 11cc000-11fd4d7 } [201944] moving module 01 { 10c9000-10da373 } -> { 11ba000-11cb373 } [70516] moving module 00 { 1043000-10c889f } -> { 1134000-11b989f } [546976] moving module 04 { 1029000-10425af } -> { 111a000-11335af } [103856] moving module 03 { 100f000-102849b } -> { 1100000-111949b } [103580] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x2000 Regions of list 'regions' [ 1000, 1aff] { b00} Kern fiasco [ 2000, 92fff] { 91000} Kern fiasco [ 93000, 930eb] { ec} Root mbi_rt [ c0000, c9c33] { 9c34} Sigma0 sigma0 [ d0000, d6177] { 6178} Sigma0 sigma0 [ 140000, 16905b] { 2905c} Root moe [ 170000, 17b58b] { b58c} Root moe [ 1000000, 100e4ff] { e500} Boot bootstrap [ 1100000, 1133fff] { 34000} Root Module API Version: (87) experimental Sigma0 config ip:000c0100 sp:00000000 Roottask config ip:00140250 sp:00000000 Starting kernel fiasco at 000012b8 Non-HYP kernel detected but running in HYP mode, switching back. Hello from Startup::stage2 Assertion failed at /home/adebut/Documents/snapshotTest/l4re-snapshot-2015123115/src/kernel/fiasco/src/kern/buddy_alloc.cpp:101: (unsigned long)block >= _base Press any key to reboot. I am currently working on the latest snapshot (2015123115), with U-Boot as a bootloader, and testing on a real board (Raspberry Pi 2 model B V1.1). The entry built is the standard 'hello', and I use the ramdisk-arm.rd given in the snapshot. I did add a custom Bsp for the board, mainly based on the first Raspberry Pi except for the Base Address, that is 0x3F000000 instead of the first Pi's 0x20000000. I highly think that it is an address configuration problem, because it first happened when I did expand the RAM size to 1024MB. With further investigation, I found out that it was the kernel memory allocation that causes this error, and suspect an incorrect MMU mapping. This suspicion comes from the fact that the assertion takes the address _base (0xf0400000) and the currently allocated block (0xee100000). I did not modify any parameter in the kern/arm/mem_layout-arm.cpp file on the Fiasco directory, which provides the default ARM addressing. Maybe that's where my error comes from ? How can I correctly configure my memory mapping, besides what I already configure in the Bsp (given in attachment) ? Also, it is the first time that I am assigned for porting a system, do you have some hints, like important steps to follow ? I am pretty sure it is a newbie error, but I cannot figure it out for now :( Thanks in advance for your time, -- Antoine Debut EPITA 2016 - GISTRE

3 7

Graphical desktop, l4con, mag
by teclis High Elf 02 Jun '17

02 Jun '17

Guten Tag, I've got the Hello app runing with fiasco and l4re in qemu, how do I get the graphical UI and console running that I see on the screen shots page? Do I need to use l4con and mag? I don't see an entry with l4con in modules.list. danke * <http://german.about.com/library/media/Audio/gutentag.wav>*

6 15

Benchmarks in l4
by Maxim Baryshnikov 01 Jun '17

01 Jun '17

Hello everybody, Does the L4re contain some kind of simple performance benchmarks which are already prepared to use? I've tried to launch some demos from the ferret package but not succeed... Thank you in advance for any suggestions. Sincerely, Maxim Baryshnikov.

4 11

libfs/ FUSE on L4Re
by Stark, Josef 31 May '17

31 May '17

Hello, yesterday I came across a very interesting paper titled "Porting FUSE to L4Re", accessible here: http://os.inf.tu-dresden.de/papers_ps/pester-beleg.pdf For porting FUSE, the author uses a library called "libfs" which provides filesystem request forwarding and processing, if I understood correctly. It reads as if libfs is already included in L4Re. However, I couldn't find neither FUSE nor libfs in the current L4Re snapshot. Are they by any chance publicly available somewhere else, or are both not to be published? Cheers, Josef

4 7

where can I download the previous version of L4linux?
by li94575 07 Jul '16

07 Jul '16

Hi, I want to use L4linux3.5 and L4linux3.10, but L4linux SVN repository and l4re-snapshot both are the latest release. Can anyone tell me where to download it? Thank you!

2 3

building fiasco on alpine linux
by Michael Schnupp 27 Jun '16

27 Jun '16

Hi, I tried to build fiasco on alpine linux. This will fail with the following line: auto/jdb_ktrace.cc:1:0: error: code model kernel does not support PIC mode Their gcc enables PIC per default for security reasons. Since fiasco seems to need PIC disabled I have to tell the build system either to add -fno-PIC explictly, or to -D__KERNEL__ in any way. (I already tried DEFINES += -D__KERNEL__ or CFLAGS := -fno-PIC in Makeconf without success.) What is the correct way to add such an option to the fiasco build system? Would it hurt to add -D__KERNEL__ per default on future releases? (After all it *is* a kernel.) BTW, the above file looks very much like a jdb file. Is it correct that this file is compiled even when I configured fiasco to not include jdb? BR, Michael

2 6

Cross-compiling L4Re for MIPS32
by Paul Boddie 22 Jun '16

22 Jun '16

Hello, I finally got round to looking at L4/Fiasco.OC again, and having previously looked at the MIPS32 port that was made available on GitHub... https://github.com/MIPS/fiasco-l4re ...I have been attempting to cross-compile Fiasco and L4Re using the l4re.org sources. Getting Fiasco to cross-compile was mostly a matter of repeating the same procedure as last time: cd src/kernel/fiasco make BUILDDIR=mybuild cd mybuild/ make config make However, I needed to edit src/kernel/fiasco/src/Makeconf.mips32 to change the compiler settings. I'm using the toolchains in Debian unstable: CROSS_COMPILE ?= mipsel-linux-gnu- Previously, I used a Makeconf.local file to set the following: SYSTEM_TARGET=mipsel-linux-gnu- SHARED_FLAGS=-mips32r2 -EL -msoft-float -mno-abicalls -fno-pic Maybe the previous work used some different mechanisms to those used by the more general source distribution, but this trick didn't seem to influence the build successfully this time around. However, the build did complete successfully with the toolchain set appropriately. Meanwhile, I had more problems with the L4Re part. I had expected to be able to do the following: cd src/l4 make B=mybuild make O=mybuild config make O=mybuild E=mips-fbspectrum (The target was something that I had managed to build previously after some messing around with packages and configuration files. I'd managed to build the fbspectrum example for Fiasco.OC-UX, as the list archives will attest.) However, I also had to change the compiler settings (as done above) in src/l4/mk/arch/Makeconf.mips, instead of using src/l4/Makeconf.local (as done previously). Again, maybe the way of doing things was different in the previous incarnation of this port. I also needed to edit src/l4/tool/gendep/syscall.c to add a definition before unistd.h gets included: #define __ARCH_WANT_SYSCALL_NO_AT I can't remember if I or anyone else has mentioned this before now, but without it, things like __NR_open are not defined. Unfortunately, I haven't yet reached a satisfactory conclusion in this latter exercise. Looking back at my previous messages, it seems that a bit more work might be needed to configure and build a suitable target, and so I was wondering if anyone had done this (and written it up) for any of the MIPS boards, perhaps the CI20. Indeed, I wonder if things like the framebuffer are even supported for the CI20 or other MIPS boards. Paul

2 10

L4Linux Compilation trouble with missing packages in L4
by Martin Gruber 13 Jun '16

13 Jun '16

Dear L4 community, i started diving into L4 stuff recently and it looks really interesting. Currently I am trying to get L4Linux working on top of Fiasco.OC. After configuring the L4 Kernel, I am getting following error message at build: ---------------------------------------------------------------------------- make O=../build/ make[1]: Entering directory '/home/gruber/l4re/l4linux/build' Package shmc was not found in the pkg-config search path. Perhaps you should add the directory containing `shmc.pc' to the PKG_CONFIG_PATH environment variable No package 'shmc' found Package rtc was not found in the pkg-config search path. Perhaps you should add the directory containing `rtc.pc' to the PKG_CONFIG_PATH environment variable No package 'rtc' found Getting required compilation flags failed. L4OBJ: /home/gruber/l4re/src/l4/l4build L4_REQUIRED_MODS: libc_be_minimal_log_io libc_minimal libc_minimal_l4re libsupc++_minimal log l4re_c-util libio libvcpu shmc rtc arch/l4/Makefile:391: *** Aborting.. Stop. make[1]: Leaving directory '/home/gruber/l4re/l4linux/build' Makefile:146: recipe for target 'sub-make' failed make: *** [sub-make] Error 2 ---------------------------------------------------------------------------- After checking the mailing list archive i found this question: http://os.inf.tu-dresden.de/pipermail/l4-hackers/2015/007635.html http://os.inf.tu-dresden.de/pipermail/l4-hackers/2015/007635.html I checked the l4/builddir/pc for missing libs and did not find them. Compilation of L4 worked fine, L4 also works with the small HelloWorld sample in QEMU. I checked the L4 config but was not able to find appropriate options. Does anyone have an tip for me what I am doing wrong? Thank you very much for your help! Kind Regards, Martin

2 1