- l4-hackers - example.com Site

Fiasco.OC device driver
by Shabnam Engineer 21 Jul '15

21 Jul '15

Hi ,is fiasco.oc like other L4 family about supporting driver of devices ? does Fiasco run device drivers as normal user-mode application? thanks for your considering my question regards,shabnam

2 1

issues in building l4re
by AVK 20 Jul '15

20 Jul '15

Hello community, I have been trying to build l4re and have the following issue. I am building l4re snapshot with some other modules not included in the package. The issue is when i am building moe, and it has not been changed and is the one that is included in the package. I am building it on a virtualbox running xubuntu 15.04 (in case it helps to find the issue or could be the problem). I am not sure how to move ahead with this problem and am curious if anyone has ideas or pointers to look for/at. /obj/l4/x86/include/l4/re/error_helper:64:26: error: ‘L4_UNLIKELY’ was not declared in this scope if (L4_UNLIKELY(err < 0)) ^ /home/avk/Thesis/l4re-snapshot-2014092821/obj/l4/x86/include/l4/re/error_helper: In function ‘long int L4Re::chksys(const l4_msgtag_t&, const char*, l4_utcb_t*, long int)’: /home/avk/Thesis/l4re-snapshot-2014092821/obj/l4/x86/include/l4/re/error_helper:86:32: error: ‘L4_UNLIKELY’ was not declared in this scope if (L4_UNLIKELY(t.has_error())) ^ /home/avk/Thesis/l4re-snapshot-2014092821/src/l4/mk/binary.inc:818: recipe for target 'main.o' failed The build output can be seen here : http://pastebin.com/Xuu0eKAY -- --- Avinash Kundaliya avinash(a)avinash.com.np http://avinash.com.np

2 3

Adding more functionality on top of L4Linux
by Thotheolh Tay 18 Jul '15

18 Jul '15

Hi, Are there any guides which I can add the following features onto L4Linux ? - GCC, Make, CCID, PCSC If the features do not exist in L4Linux, how do I build my own L4Linux image with these features and what do I need to modify to ensure they work properly on L4Linux ? -- +---------------------------------------------------------+ | PGP Secure Email Key ID:6FBFC19D | +---------------------------------------------------------+

2 3

Some questions about L4 operating system
by Qing Wei 16 Jul '15

16 Jul '15

Hi, I am a beginner to L4, and very interested in it. I think it is great in terms of its minimality and security. However, I have some questions about it, (1) How is its performance compared to other monolithic kernel, say, Linux. Could it make use of multicore, multiprocessor to enjoy the performance scalability? (2) How is its ecosystem, fox example, how to support new hardware, does it need write the driver from scratch or could it make use of Linux driver? And how to write application on it, or, could it run Linux application without modification? (3) How is its virtualization support, could it run Linux vm, and does it need any modification to the guest os? Cheers, Qing Wei

3 3

Problem in final step
by Vlad Sof 16 Jul '15

16 Jul '15

Hi guys, So, I'm having a problem with the final step in booting and running the Fiasco.OC.I've gone through the building steps on L4Re -- The L4 Runtime Environment | | | | | | | | | L4Re -- The L4 Runtime EnvironmentThe L4 Runtime Environment: informations and more | | | | View on os.inf.tu-dresden.de | Preview by Yahoo | | | | | and The Fiasco microkernel - Building and Using | | | | | | | | | | | The Fiasco microkernel - Building and UsingThe Fiasco microkernel: prerequisites, compilation, booting | | | | View on os.inf.tu-dresden.de | Preview by Yahoo | | | | | When I try "make grub2iso E=hello MODULE_SEARCH_PATH=~/projects/src/kernel/fiasco/mybuild" I get the following error: make[1]: Entering Directory `/home/johng/projects/src/l4'Processing entry 'hello'Could not find 'bootstrap' with path '/home/johng/projects/src/kernel/fiasco/mybuild:/home/johng/projects/src/l4/mybuild/bin/x86_586:/home/johng/projects/src/l4/mybuild/bin/x86_586/l4f:/home/johng/projects/src/l4/mybuild/lib/x86_586:/home/johng/projects/src/l4/mybuild/lib/x86_586/l4f'make[1]: *** [grub2iso] Error 1make[1]: Leaving directory `/home/johng/projects/src/l4'make: *** [grub2iso] Error 2 A brief explanation: I'm running Ubuntu 14.04.1 as a virtualmachine guest on a Mac OSX host.I've configured l4re with : Target Architecture: x86-32 architecture CPU variant: 586 type CPUPlatform Selection: PC On the fiasco kernel configuration I just saved it without changing any of the settings. I've been trying to get this work for the past week and I don't know where I'm going wrong. I've followed all the steps up to this point, but for some reason this last step just wont work. Please help !

2 1

how does Fiasco achieve C++ support
by Yuxin Ren 06 Jul '15

06 Jul '15

HI, My big question is how Fiasco can support C++? I think in order to build Fiasco, we need some kind of c++ cross-compiler (in this case, it is gcc), this is because we build Fiasco and its applications on Linux. But on the other hand, I did not see any special configuration or modification of gcc when I build Fiasco. I want to know how Fiasco is build without a cross-compiler. In particular, I know gcc uses some its internal libraries to support exception handing, threads/locking and STL in C++. And those libraries may include libgcc, libstdc++. But I also do not find that hose libraries are ported to Fiasco. Without poring those libraries, how to support C++ in Fiasco? As those libraries may use some lock mechanisms like mutex and C library functions like malloc, I cannot understand how Fiasco provides such support (locks, C library) to those libraries. Thank you very for any help and explanation. Yuxin

2 9

TrustZone example on i.MX6
by Markku Ahvenjärvi 06 Jul '15

06 Jul '15

Hello hackers, I'm trying to run Fiasco.OC in secure world and Linux in non-secure world on i.MX6Q. For this I'm using the TrustZone example (pkg/examples/sys/vm-tz). To secure world I have given 128MB RAM starting from 0x10000000 and I modified the example to give NS world 256MB starting from 0x20000000. I've replaced atags with dtb of my board and it is copied to NS side like kernel and initrd. At first I encountered runtime exception, which I fixed by implementing following to arm_em_tz builds Thread::arch_ext_vcpu_enabled() { return true; } Now I'm having problems at early stages of NS boot, where Linux kernel is checking for the dtb magic. The code loads the dtb magic from the address I'm giving in r2 register (0x21000000), but the magic value usually have one byte or all of them incorrect. I've used JDB to dump the area of dtb after hitting that error and it shows the dtb magic properly. So for some reason the NS-world gets mangled value. Any idea what might be causing this? Thanks, Markku

5 29

Fwd: Running L4Linux + Fiasco on Freescale i.MX 6 Sabre SD
by Mahdi Aichouch 05 Jul '15

05 Jul '15

Hello, Thank you very much Mattias for you help. Now L4Linux goes further but it stops after mounting the root filesystem. Do you have an idea of what might be wrong. Thank you in advance. Best regards, Mahdi L4 Bootstrapper Build: #81 Thu May 28 10:36:41 CEST 2015, 4.8.3 20140320 (prerelease) Scanning up to 256 MB RAM, starting at offset 32MB Memory size is 256MB (10000000 - 1fffffff) RAM: 0000000010000000 - 000000001fffffff: 262144kB Total RAM: 256MB Scanning fiasco Scanning sigma0 Scanning moe Moving up to 10 modules behind 11100000 moving module 02 { 118aa000-118e363f } -> { 1199a000-119d363f } [235072] moving module 01 { 118a0000-118a938b } -> { 11990000-1199938b } [37772] moving module 00 { 11848000-1189fb17 } -> { 11938000-1198fb17 } [359192] moving module 09 { 11548000-11847fff } -> { 11638000-11937fff } [3145728] moving module 08 { 111d6000-11547497 } -> { 112c6000-11637497 } [3609752] moving module 07 { 111d5000-111d50bc } -> { 112c5000-112c50bc } [189] moving module 06 { 1107e000-111d446f } -> { 1116e000-112c446f } [1401968] moving module 05 { 1107d000-1107d17b } -> { 1116d000-1116d17b } [380] moving module 04 { 1102a000-1107cc1f } -> { 1111a000-1116cc1f } [338976] moving module 03 { 11010000-11029473 } -> { 11100000-11119473 } [103540] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x10002000 Regions of list 'regions' [ 10000000, 1000015f] { 160} Root mbi_rt [ 10001000, 10001aff] { b00} Kern fiasco [ 10002000, 10066fff] { 65000} Kern fiasco [ 10090000, 10096edf] { 6ee0} Sigma0 sigma0 [ 10098000, 1009e177] { 6178} Sigma0 sigma0 [ 10140000, 10171d77] { 31d78} Root moe [ 10178000, 101934ab] { 1b4ac} Root moe [ 11000000, 1100f58f] { f590} Boot bootstrap [ 11100000, 11937fff] { 838000} Root Module API Version: (87) experimental Sigma0 config ip:10090100 sp:00000000 Roottask config ip:10140260 sp:00000000 Starting kernel fiasco at 100012c8 Number of IRQs available at this GIC: 160 FPU0: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl L2: ID=410000c7 Type=9e340340 Aux=02070000 WMask=ffff S=0 L2: Type L2C-310 Size = 1024kB Ways=16 Waysize=64 GIC: Switching IRQ 58 to secure SERIAL ESC: allocated IRQ 58 for serial uart Not using serial hack in slow timer handler. Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2013 TU Dresden Rev: rexported compiled with gcc 4.8.3 for i.MX6 [] Build: #15 Thu May 28 10:35:21 CEST 2015 GIC: Switching IRQ 29 to secure Calibrating timer loop... done. MDB: use page size: 20 MDB: use page size: 12 SIGMA0: Hello! KIP @ 10002000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [4:10000000;10000fff] [0:10067000;1008ffff] [0:10097000;10097fff] [0:1009f000;1013ffff] [4:10140000;10171fff] [0:10172000;10177fff] [4:10178000;10193fff] [0:10194000;110fffff] [4:11100000;11937fff] [0:11938000;1effffff] IOMEM:---------------------- [0:0;fffffff] [0:20000000;ffffffff] MOE: Hello world MOE: found 236564 KByte free memory MOE: found RAM from 10000000 to 1f000000 MOE: allocated 240 KByte for the page array @0x1009f000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [11100000-11119474] [C:503000] l4re BOOTFS: [1111a000-1116cc20] [C:504000] ned BOOTFS: [1116d000-1116d17c] [C:505000] l4lx.cfg BOOTFS: [1116e000-112c4470] [C:506000] io BOOTFS: [112c5000-112c50bd] [C:507000] arm-rv.io BOOTFS: [112c6000-11637498] [C:508000] vmlinuz.arm BOOTFS: [11638000-11938000] [C:509000] ramdisk-arm.rd MOE: cmdline: moe rom/l4lx.cfg MOE: Starting: rom/ned rom/l4lx.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/l4lx.cfg' l4linux | libio: Warning: Query of 'vbus' failed! l4linux | PH 0 (t: 1) offs=00008000 vaddr=02000000 vend=023defa8 l4linux | phys=02000000 ephys=023defa8 l4linux | f_sz=00359394 memsz=003defa8 flgs=rwx l4linux | PH 1 (t: 4) offs=0031afe0 vaddr=02312fe0 vend=02313004 l4linux | phys=02312fe0 ephys=02313004 l4linux | f_sz=00000024 memsz=00000024 flgs=r-x l4linux | PH 2 (t: 1685382481) offs=00000000 vaddr=00000000 vend=00000000 l4linux | phys=00000000 ephys=00000000 l4linux | f_sz=00000000 memsz=00000000 flgs=rwx l4linux | Starting binary at 0x20002b0, argc=6 argv=0xafff4f8c *argv=0xb1007ff0 argv0=rom/vmlinuz.arm l4linux | External resolver is at 0xa8000788 l4linux | ======> L4Linux starting... <======== l4linux | Linux version 3.16.0-l4 (aichouch@aichouch-ThinkCentre-M90) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-29) ) #1 Wed May 27 18:04:14 CEST 2015 l4linux | Binary name: rom/vmlinuz.arm l4linux | This is an AEABI build. l4linux | Linux kernel command line (5 args): mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=4000 l4linux | CPU mapping (l:p)[1]: 0:0 l4linux | Image: 02000000 - 02400000 [4096 KiB]. l4linux | Areas: Text: 02000000 - 02332000 [3272kB] (a bit longer) l4linux | Data: 02332000 - 023543a0 [136kB] l4linux | Initdata: 02314000 - 02331024 [116kB] l4linux | BSS: 02359394 - 023defa8 [535kB] l4linux | Device scan: l4linux | Device scan done. l4linux | l4lx_thread_create: Created thread 413 (cpu0) (u:b3000e00, v:b3000c00, sp:02333fa4) l4linux | main thread will be 413 l4linux | l4x_register_pointer_section: addr = 02000000 size = 4059136 l4linux | section-with-init: Virt: 0x2000000 to 0x23defa7 [3963 KiB] l4linux | section-with-init: Phys: 0x1025a000 to 0x10638fa7, [3963 KiB] l4linux | Main thread running, waiting... l4linux | L4x: Memory size: 64MB l4linux | L4x: Setting superpages for main memory l4linux | L4x: Adjusted memory start: 02000000 l4linux | Main memory: Virt: 0x2400000 to 0x63fffff [65536 KiB] l4linux | Main memory: Phys: 0x11a00000 to 0x159fffff, [65536 KiB] l4linux | l4x: vmalloc area: 06400000 - 0e400000 l4linux | l4x_register_pointer_section: addr = 02000000 size = 4059136 l4linux | text: Virt: 0x2000000 to 0x23defa7 [3963 KiB] l4linux | text: Phys: 0x1025a000 to 0x10638fa7, [3963 KiB] l4linux | Loading: rom/ramdisk-arm.rd l4linux | INITRD: Size of RAMdisk is 3072KiB l4linux | RAMdisk from 00002000 to 00302000 [3072KiB] l4linux | l4lx_thread_create: Created thread 418 (timer0) (u:b3000a00, v:00000000, sp:02377fa0) Booting Linux on physical CPU 0x0 Linux version 3.16.0-l4 (aichouch@aichouch-ThinkCentre-M90) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-29) ) #1 Wed May 27 18:04:14 CEST 2015 CPU: Fiasco [412fc09a] revision 10 (ARMv7), cr=00000000 CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache Machine: L4 Ignoring unrecognised tag 0x00000000 Memory policy: Data cache uncached INITRD: 00002000 - 00302000 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 17209 Kernel command line: mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=4000 PID hash table entries: 512 (order: -1, 2048 bytes) Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 64808K/69636K available (2460K kernel code, 136K rwdata, 688K rodata, 116K init, 535K bss, 4828K reserved) Virtual kernel memory layout: vector : 0xbffff000 - 0xc0000000 ( 4 kB) fixmap : 0xffc00000 - 0xffe00000 (2048 kB) vmalloc : 0x06400000 - 0x0e400000 ( 128 MB) lowmem : 0x00000000 - 0x06400000 ( 100 MB) modules : Virtual kernel memory layout: vector : 0xbffff000 - 0xc0000000 ( 4 kB) fixmap : 0xffc00000 - 0xffe00000 (2048 kB) vmalloc : 0x06400000 - 0x0e400000 ( 128 MB) lowmem : 0x00000000 - 0x06400000 ( 100 MB) moNR_IRQS:220 l4timer: Using IRQ210 sched_clock: 64 bits at 1000kHz, resolution 1000ns, wraps every 2147483648000ns Console: colour dummy device 80x30 console [ttyLv0] enabled Calibrating delay loop... 1574.50 BogoMIPS (lpj=7872512) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) CPU: Testing write buffer coherency: ok Setting up static identity map for 0x22509d8 - 0x22509d8 VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 NET: Registered protocol family 16 DMA: preallocated 256 KiB pool for atomic coherent allocations Failed to create "l4x" debugfs directory: 1 Switched to clocksource l4kipclk NET: Registered protocol family 2 TCP established hash table entries: 1024 (order: 0, 4096 bytes) TCP bind hash table entries: 1024 (order: 0, 4096 bytes) TCP: Hash tables configured (established 1024 bind 1024) TCP: reno registered UDP hash table entries: 256 (order: 0, 4096 bytes) UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) NET: Registered protocol family 1 Trying to unpack rootfs image as initramfs... rootfs image is not initramfs (junk in compressed archive); looks like an initrd INITRD: Freeing memory. l4x: Checks passed. NetWinder Floating Point Emulator V0.97 (double precision) futex hash table entries: 256 (order: -1, 3072 bytes) msgmni has been set to 126 io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) L4 serial driver ttyLv0 at MMIO 0x1 (irq = 211, base_baud = 230400) is a L4 l4ser_shm: L4 shared mem serial driver l4cdds: No name given, not starting. brd: module loaded l4bdds: No name given, not starting. mousedev: PS/2 mouse device common for all mice TCP: cubic registered NET: Registered protocol family 17 RAMDISK: ext2 filesystem found at block 0 RAMDISK: Loading 3072KiB [1 disk] into ram disk... done. EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities EXT4-fs (ram0): mounting ext2 file system using the ext4 subsystem EXT4-fs (ram0): mounted filesystem without journal. Opts: (null) VFS: Mounted root (ext2 filesystem) readonly on device 1:0. Freeing unused kernel memory: 116K (02314000 - 02331000) Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b CPU: 0 PID: 1 Comm: init Not tainted 3.16.0-l4 #1 [<0200cc68>] (unwind_backtrace) from [<020057e4>] (show_stack+0x10/0x14) [<020057e4>] (show_stack) from [<0224ad50>] (panic+0x7c/0x1d0) [<0224ad50>] (panic) from [<0201dcdc>] (do_exit+0x7b8/0x7f0) [<0201dcdc>] (do_exit) from [<0201e858>] (do_group_exit+0x40/0xa0) [<0201e858>] (do_group_exit) from [<02028700>] (get_signal_to_deliver+0x148/0x4b4) [<02028700>] (get_signal_to_deliver) from [<02006e1c>] (do_signal+0x118/0x454) [<02006e1c>] (do_signal) from [<0200a4d4>] (l4x_vcpu_entry_c+0xa74/0x1dd4) [<0200a4d4>] (l4x_vcpu_entry_c) from [<0000c548>] (0xc548) ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b panic: going to sleep forever, bye l4linux | panic: going to sleep forever, bye On Thu, May 28, 2015 at 8:23 AM, Matthias Lange < matthias.lange(a)kernkonzept.com> wrote: > Hi, > > On 05/27/2015 06:43 PM, Mahdi Aichouch wrote: > > Hello, > > > > I tried to run L4Linux + Fiasco on a Freescale i.mx <http://i.mx> 6 > > Sabre SD board. > > > > The L4Linux is started but it stops at loading the ramdisk, as shown in > > the debug messages below. > > > > Does someone has an idea of what might be wrong. > > > > Thank you very much in advance. > > > > Best regards, > > > > Mahdi > > > > [...] > > > l4linux | l4x_register_pointer_section: addr = 02000000 size = 4059136 > > l4linux | text: Virt: 0x2000000 to 0x23defa7 [3963 KiB] > > l4linux | text: Phys: 0x1025a000 to 0x10638fa7, [3963 KiB] > > l4linux | Loading: rom/ramdisk-arm.rd > > l4linux | INITRD: Size of RAMdisk is 3072KiB > > l4linux | RAMdisk from 00002000 to 00302000 [3072KiB] > > l4linux | 'swp(b)' instruction at 0224f728 and faulting. > > Have you enabled CONFIG_ARM_ENABLE_SWP in your Fiasco config? > > Matthias. > > > -- > Matthias Lange, matthias.lange(a)kernkonzept.com, +49 - 351 - 41 88 86 14 > > Kernkonzept GmbH. Sitz: Dresden. Amtsgericht Dresden, HRB 31129. > Geschäftsführer: Dr.-Ing. Michael Hohmuth > >

3 12

Difficulty Booting L4RE on Raspberry Pi
by Robert Lowe 29 Jun '15

29 Jun '15

Hello, I've done some research and have been trying to get L4RE + Fiasco.OC to boot on my raspberry pi. I've managed to get the bootable image onto the PI, but the boot halts just after the kernel is loaded. I've tried different compiler toolchains, both linaro(which I hear there are issues with) and genode. Unfortunately I was unable to acquire the sourcery toolchain. In every case, it halts at the same point. Here is a serial dump: L4 Bootstrapper Build: #3 Sat Jun 27 23:26:20 EDT 2015, 4.7.1 20120402 (prerelease) Scanning up to 512 MB RAM, starting at offset 32MB Memory size is 512MB (00000000 - 1fffffff) RAM: 0000000000000000 - 000000001fffffff: 524288kB Total RAM: 512MB Scanning fiasco Scanning sigma0 Scanning moe Moving up to 5 modules behind 1100000 moving module 02 { 10a0000-10d163f } -> { 1191000-11c263f } [202304] moving module 01 { 1096000-109f357 } -> { 1187000-1190357 } [37720] moving module 00 { 1043000-1095ae7 } -> { 1134000-1186ae7 } [338664] moving module 04 { 1029000-1042597 } -> { 111a000-1133597 } [103832] moving module 03 { 100f000-1028473 } -> { 1100000-1119473 } [103540] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x2000 Regions of list 'regions' [ 1000, 19bf] { 9c0} Kern fiasco [ 2000, 62fff] { 61000} Kern fiasco [ 63000, 630e3] { e4} Root mbi_rt [ 90000, 966bb] { 66bc} Sigma0 sigma0 [ 98000, 9e177] { 6178} Sigma0 sigma0 [ 140000, 16daaf] { 2dab0} Root moe [ 170000, 186f13] { 16f14} Root moe [ 1000000, 100e4ff] { e500} Boot bootstrap [ 1100000, 1133fff] { 34000} Root Module API Version: (87) experimental Sigma0 config ip:00090100 sp:00000000 Roottask config ip:00140264 sp:00000000 Starting kernel fiasco at 000011a8 Hello from Startup::stage2 Attached is my kernel config, if it is of any help. Thanks for any assistance Robert Lowe

2 1

Open source development
by teclis High Elf 25 Jun '15

25 Jun '15

Hi, This is more just a general comment, but compared to other open source project I have contributed to Fiasco L4Re is difficult to work with. In most GNU open source projects new features and improvements are discussed actively on a mailing list and/or IRC channel so its easy to follow what is being done and jump in. While I very much appreciate that developers have taken the time to answer my questions, the l4-hackers mailing list seems to be just Q and A there is no discussion on what is currently being worked on for Fiasco and L4Re as there is in the Linux kernel or drivers. Also the svn logs just have generic import messages like: r67 | l4check | 2015-01-12 16:57:36 -0500 (Mon, 12 Jan 2015) | 1 line So it looks like all the core development is being done privately and then exported to a public repository. This makes it difficult in my opinion to build an open source development community. You can't look back through the svn logs messages and diffs to see the evolution of the system and get up to speed on the state of the art. For example, who is the committer? How would I go about submitting a patch for L4Re or Fiasco?

2 1