l4-hackers January 2016

l4-hackers@os.inf.tu-dresden.de

7 participants
9 discussions

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

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 … [View More]

4 7

Device drivers and board support files
by Paul Boddie 27 Jan '16

27 Jan '16

Hello again, Emboldened by my recent modest success, and taking a look at the previously- mentioned MIP32 port of Fiasco.OC and L4Re [*], which doesn't really seem to have any community involved with it, I wondered whether there might be some general documentation about adding board support files to Fiasco.OC as well as writing drivers for L4Re. [*] https://github.com/MIPS/fiasco-l4re I've browsed around the L4Re site and have even looked at the TU Dresden teaching resources, but there … [View More]appears to be a lot of slideshows and not so much in the way of concise guidance on such topics. Are there any documents out there that cover writing the actual code involved? With regard to board support, I get the feeling that I could possibly get away with something rather similar to other MIPS-based boards, and if I'm launching Fiasco.OC from U-Boot, I might not even need to do the basic board setup tasks (which include things like setting up the DRAM on the SoC concerned). However, I suspect that I would have to look into things like interrupt controllers for the various timers that I suppose must be needed by the kernel. As for driver support, I noticed a previous message that gives an outline of what should be done: http://os.inf.tu-dresden.de/pipermail/l4-hackers/2015/007475.html Here, to be more specific, I imagine that the following things would be affected: 1. src/l4/pkg/io/config/<board>.devs would need populating with Device definitions employing those Mmio declarations 2. src/l4/pkg/io/config/vbus-config.vbus might need changing, perhaps to allow devices to match some bus identifier or other, although I don't completely follow this (I'm guessing that my driver should obtain a device reference via the vbus mechanism) 3. looking at the src/l4/pkg/drivers/lcd/src/lcd-omap3.c driver, which probably references devices in src/l4/pkg/io/io/config/plat- beagleboard/hw_devices.io, I see that the driver actually obtains a reference to the "dss" device using l4io_lookup_device, whereas the GPIO and I2C devices are obtained using l4vbus_get_device_by_hid, but I'm guessing that there is a distinction between specific and generic devices here 4. in src/l4/pkg/drivers/.../<device>.c the l4io_request_iomem call would employ the same physical addresses as those mentioned in (1) to access the device memory regions I did start looking at the existing LCD drivers, this being something that I've managed to get to work with bare-metal code on the board concerned, and I noticed that drivers/lcd seems to mention "arm" a lot, but would I be right in assuming that none of that code is actually ARM-specific? Thanks once again for any help you can offer! Paul [View Less]

2 1

Setting up network in L4Linux
by Nourhan Mohamed 26 Jan '16

26 Jan '16

I have been trying to configure *L4Linux *to connect to the internet through *L4Re/Fiasco.OC*. I am using *qemu *on a *Versatile Express* Machine with *Cortex-A15* cpu. Below is my current configuration: *L4re-snapsot:* l4re-snapshot-2015123115 *obj/l4/arm-ca/conf/Makeconf.boot:* MODULE_SEARCH_PATH=/home/nour/l4re/obj/fiasco/arm-mp-rv-a9-vexpress:/home/nour/l4re/obj/l4linux/arm-mp:/home/nour/l4re/files:/home/nour/l4re/files/cfg:/home/nour/l4re/src/l4/conf:/home/nour/l4re/src/l4/conf/examples … [View More]QEMU_OPTIONS += -M vexpress-a15 -cpu cortex-a15 -smp 4 QEMU_OPTIONS += -m 256 -serial stdio QEMU_OPTIONS += -net nic,model=lan9118 -net user PLATFORM_TYPE := rv_vexpress *l4re/files/cfg/arm-rv.devs:* -- vim:set ft=lua: local Res = Io.Res local Hw = Io.Hw Io.hw_add_devices(function() NIC = Hw.Device(function() Property.hid = "smc91x"; compatible = {"smsc,lan9118"}; Resource.regs = Res.mmio(0x10030000, 0x10030fff); Resource.irq = Res.irq(60); end); virtio_mmio3 = Hw.Device(function() compatible = {"virtio,mmio"}; Resource.mem = Res.mmio(0x10013600, 0x100137ff); Resource.irq = Res.irq(75); end); CTRL = Hw.Device(function() Property.hid = "System Control"; Resource.regs = Res.mmio(0x10000000, 0x10000fff); end); clcd = Hw.Device(function() Property.hid = "AMBA PL110"; compatible = {"arm,pl111","arm,primecell"}; Resource.regs = Res.mmio(0x10020000, 0x10020fff); end); kmi0 = Hw.Device(function() compatible = {"arm,pl050","arm,primecell"}; Resource.regs = Res.mmio(0x10006000, 0x10006fff); Resource.irq = Res.irq(44); end); kmi1 = Hw.Device(function() compatible = {"arm,pl050","arm,primecell"}; Resource.regs = Res.mmio(0x10007000, 0x10007fff); Resource.irq = Res.irq(45); end); end) *src/l4/conf/examples/l4lx-vbus.io <http://l4lx-vbus.io>:* local hw = Io.system_bus(); Io.add_vbus("l4linux", Io.Vi.System_bus { NIC = wrap(hw:match("smsc,lan9118")); }) src/l4/conf/examples/l4lx-net.cfg: -- vim:set ft=lua: local L4 = require("L4"); local lxname = "vmlinuz"; loader = L4.default_loader; vbus_l4linux = loader:new_channel(); local shmns = loader:create_namespace({shm = "ipctest"}); local cons = L4.default_loader:new_channel(); L4.default_loader:start( { caps = { cons = cons:svr() }, log = L4.Env.log, }, "rom/cons -k -a" ); L4.default_loader.log_fab = cons; loader:start( { caps = { sigma0 = L4.cast(L4.Proto.Factory,L4.Env.sigma0):create(L4.Proto.Sigma0); icu = L4.Env.icu; l4linux = vbus_l4linux:svr(); }, log = {"IO", "magenta"}, }, "rom/io -vvv rom/arm-ve.devs rom/l4lx-vbus.io"); loader:start( { caps = { shmns = shmns:mode("rw"), vbus = vbus_l4linux; }, l4re_dbg = L4.Dbg.Warn, log = {"l4linux", "cyan", "key=1"}, }, "rom/" .. lxname .. " mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-" .. L4.Info.arch() .. ".rd root=1:0 rw ramdisk_size=4000 l4shmnet.add=shmns,macpart=1"); *src/l4/conf/modules.list:* entry L4Linux-net roottask moe rom/l4lx-net.cfg module l4lx-net.cfg module l4re module ned module io module cons module l4lx-vbus.io module arm-ve.devs module vmlinuz module[perl] "ramdisk-$ENV{ARCH}.rd" *Run:* L4 Bootstrapper Build: #4 Mi 20. Jan 18:13:56 CET 2016, 4.7.3 Scanning up to 256 MB RAM, starting at offset 32MB Memory size is 256MB (80000000 - 8fffffff) RAM: 0000000080000000 - 000000008fffffff: 262144kB Total RAM: 256MB Scanning fiasco Scanning sigma0 Scanning moe Moving up to 13 modules behind 81100000 moving module 02 { 81a7c000-81aad49f } -> { 81b6c000-81b9d49f } [201888] moving module 01 { 81a6a000-81a7b33b } -> { 81b5a000-81b6b33b } [70460] moving module 00 { 819d8000-81a69ebb } -> { 81ac8000-81b59ebb } [597692] moving module 12 { 816d8000-819d7fff } -> { 817c8000-81ac7fff } [3145728] moving module 11 { 81256000-816d747b } -> { 81346000-817c747b } [4723836] moving module 10 { 81255000-81255446 } -> { 81345000-81345446 } [1095] moving module 09 { 81254000-8125415d } -> { 81344000-8134415d } [350] moving module 08 { 81222000-81253823 } -> { 81312000-81343823 } [202788] moving module 07 { 811f8000-81221623 } -> { 812e8000-81311623 } [169508] moving module 06 { 81085000-811f761b } -> { 81175000-812e761b } [1517084] moving module 05 { 8102b000-81084693 } -> { 8111b000-81174693 } [366228] moving module 04 { 81011000-8102a463 } -> { 81101000-8111a463 } [103524] moving module 03 { 81010000-810103cb } -> { 81100000-811003cb } [972] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x80002000 Regions of list 'regions' [ 80000000, 800001bf] { 1c0} Root mbi_rt [ 80001000, 80001b7f] { b80} Kern fiasco [ 80002000, 8009ffff] { 9e000} Kern fiasco [ 800c0000, 800c9f6b] { 9f6c} Sigma0 sigma0 [ 800d0000, 800d6177] { 6178} Sigma0 sigma0 [ 80140000, 80169457] { 29458} Root moe [ 80170000, 80176ff3] { 6ff4} Root moe [ 81000000, 8100f5df] { f5e0} Boot bootstrap [ 81100000, 81ac7fff] { 9c8000} Root Module API Version: (87) experimental Sigma0 config ip:800c0100 sp:00000000 Roottask config ip:80140260 sp:00000000 Starting kernel fiasco at 80001374 Realview System ID: Rev=1 HBI=190 Build=f Arch=5 FPGA=00 Hello from Startup::stage2 Per_cpu_data_alloc: (orig: 0xf008f010-0xf008f5d8) Number of IRQs available at this GIC: 160 FPU0: Arch: VFPv4(4), Part: VFPv3(30), r: 0, v: f, i: 41, t: hard, p: dbl/sngl ARM generic timer: freq=62500000 interval=62500 cnt=10064946 SERIAL ESC: allocated IRQ 37 for serial uart Not using serial hack in slow timer handler. Welcome to L4/Fiasco.OC! L4/Fiasco.OC microkernel on arm Rev: unknown compiled with gcc 4.7.3 [] Build: #1 Wed Jan 20 17:27:17 CET 2016 Per_cpu_data_alloc: (orig: 0xf008f010-0xf008f5d8) Allocate 1480 bytes (1KB) for CPU[9] local storage (offset=13557f0, 0xf13e4800-0xf13e4dc8) Number of CPUs: 1 Per_cpu_data_alloc: (orig: 0xf008f010-0xf008f5d8) Allocate 1480 bytes (1KB) for CPU[1] local storage (offset=115b7f0, 0xf11ea800-0xf11eadc8) FPU1: Arch: VFPv4(4), Part: VFPv3(30), r: 0, v: f, i: 41, t: hard, p: dbl/sngl Per_cpu_data_alloc: (orig: 0xf008f010-0xf008f5d8) Allocate 1480 bytes (1KB) for CPU[2] local storage (offset=115eff0, 0xf11ee000-0xf11ee5c8) FPU2: Arch: VFPv4(4), Part: VFPv3(30), r: 0, v: f, i: 41, t: hard, p: dbl/sngl Cache config: ON ID_PFR[01]: 00001131 00011011 ID_[DA]FR0: 02010555 00000000 ID_MMFR[04]: 10201105 20000000 01240000 02102211 CPU[2]: goes to idle loop Per_cpu_data_alloc: (orig: 0xf008f010-0xf008f5d8) Allocate 1480 bytes (1KB) for CPU[3] local storage (offset=1161ff0, 0xf11f1000-0xf11f15c8) FPU3: Arch: VFPv4(4), Part: VFPv3(30), r: 0, v: f, i: 41, t: hard, p: dbl/sngl Calibrating timer loop... Cache config: ON ID_PFR[01]: 00001131 00011011 ID_[DA]FR0: 02010555 00000000 ID_MMFR[04]: 10201105 20000000 01240000 02102211 CPU[1]: goes to idle loop Cache config: ON ID_PFR[01]: 00001131 00011011 ID_[DA]FR0: 02010555 00000000 ID_MMFR[04]: 10201105 20000000 01240000 02102211 CPU[3]: goes to idle loop done. MDB: use page size: 20 MDB: use page size: 12 SIGMA0: Hello! KIP @ 80002000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [4:80000000;80000fff] [0:800a0000;800bffff] [0:800ca000;800cffff] [0:800d7000;8013ffff] [4:80140000;80169fff] [0:8016a000;8016ffff] [4:80170000;80176fff] [0:80177000;810fffff] [4:81100000;81ac7fff] [0:81ac8000;8effffff] IOMEM:---------------------- [0:0;7fffffff] [0:90000000;ffffffff] MOE: Hello world MOE: found 234840 KByte free memory MOE: found RAM from 80000000 to 8f000000 MOE: allocated 240 KByte for the page array @0x800d7000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:103000] BOOTFS: [81100000-811003cc] [C:105000] l4lx-net.cfg BOOTFS: [81101000-8111a464] [C:107000] l4re BOOTFS: [8111b000-81174694] [C:109000] ned BOOTFS: [81175000-812e761c] [C:10b000] io BOOTFS: [812e8000-81311624] [C:10d000] fb-drv BOOTFS: [81312000-81343824] [C:10f000] cons BOOTFS: [81344000-8134415e] [C:111000] l4lx-vbus.io BOOTFS: [81345000-81345447] [C:113000] arm-ve.devs BOOTFS: [81346000-817c747c] [C:115000] vmlinuz BOOTFS: [817c8000-81ac8000] [C:117000] ramdisk-arm.rd MOE: cmdline: moe rom/l4lx-net.cfg MOE: Starting: rom/ned rom/l4lx-net.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/l4lx-net.cfg' Console Server cons> Created vcon channel: IO [41f000] cons> Created vcon channel: l4linux [420000] cons> IO | Io service IO | Verboseness level: 4 IO | unused physical memory space: IO | [00000000000000-0000007fffffff] IO | [00000090000000-000000ffffffff] IO | no 'iommu' capability found use CPU-phys for DMA IO | Loading: config 'rom/arm-ve.devs' IO | Loading: config 'rom/l4lx-vbus.io' IO | Real Hardware ----------------------------------- IO | System Bus: hid= IO | Resources: ==== start ==== IO | DMADOM [00000000000000-00000000000000 1] non-pref (32bit) (align=0 flags=6) IO | Resources: ===== end ===== IO | virtio_mmio3: hid= IO | Resources: ==== start ==== IO | IRQ [0000000000004b-0000000000004b 1] none (32bit) (align=0 flags=1) IO | IOMEM [00000010013600-000000100137ff 200] non-pref (32bit) (align=1ff flags=2) IO | Resources: ===== end ===== IO | clcd: hid=AMBA PL110 IO | Resources: ==== start ==== IO | IOMEM [00000010020000-00000010020fff 1000] non-pref (32bit) (align=fff flags=2) IO | Resources: ===== end ===== IO | kmi0: hid= IO | Resources: ==== start ==== IO | IRQ [0000000000002c-0000000000002c 1] none (32bit) (align=0 flags=1) IO | IOMEM [00000010006000-00000010006fff 1000] non-pref (32bit) (align=fff flags=2) IO | Resources: ===== end ===== IO | kmi1: hid= IO | Resources: ==== start ==== IO | IRQ [0000000000002d-0000000000002d 1] none (32bit) (align=0 flags=1) IO | IOMEM [00000010007000-00000010007fff 1000] non-pref (32bit) (align=fff flags=2) IO | Resources: ===== end ===== IO | NIC: hid=smc91x IO | Clients: ===== start ==== IO | NIC: [N2Vi9Proxy_devE] IO | Clients: ===== end ==== IO | Resources: ==== start ==== IO | IRQ [0000000000003c-0000000000003c 1] none (32bit) (align=0 flags=1) IO | IOMEM [00000010030000-00000010030fff 1000] non-pref (32bit) (align=fff flags=2) IO | Resources: ===== end ===== IO | CTRL: hid=System Control IO | Resources: ==== start ==== IO | IOMEM [00000010000000-00000010000fff 1000] non-pref (32bit) (align=fff flags=2) IO | Resources: ===== end ===== IO | warning: could not register control interface at cap 'platform_ctl' IO | Ready. Waiting for request. l4linux | PH 0 (t: 1) offs=00008000 vaddr=02000000 vend=0252b724 l4linux | phys=02000000 ephys=0252b724 l4linux | f_sz=004655df memsz=0052b724 flgs=rwx l4linux | PH 1 (t: 4) offs=004077b0 vaddr=023ff7b0 vend=023ff7d4 l4linux | phys=023ff7b0 ephys=023ff7d4 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 0x2001338, argc=8 argv=0xafff4f84 *argv=0xb1007ff4 argv0=rom/vmlinuz l4linux | External resolver is at 0xa800079c l4linux | ======> L4Linux starting... <======== l4linux | Linux version 4.3.0-l4 (nour@nour-vb) (gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-12ubuntu1) ) #1 SMP Wed Jan 20 17:53:39 CET 2016 l4linux | Binary name: rom/vmlinuz l4linux | This is an AEABI build. l4linux | Linux kernel command line (7 args): mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-arm.rd root=1:0 rw ramdisk_size=4000 l4shmnet.add=shmns,macpart=1 l4linux | CPU mapping (l:p)[1]: 0:0 l4linux | Image: 020000a0 - 02600000 [6143 KiB]. l4linux | Areas: Text: 020000a0 - 023ff7d4 [4093kB] l4linux | RO-Data: 0233f000 - 023e2000 [652kB] l4linux | Data: 02438000 - 02460fe0 [163kB] l4linux | Init: 02400000 - 02438000 [224kB] l4linux | BSS: 024655df - 0252b724 [792kB] l4linux | Device scan: l4linux | Device: L4ICU l4linux | Device: NIC l4linux | IRQ: 0000003c - 0000003c l4linux | MEM: 10030000 - 10030fff l4linux | Device scan done. l4linux | l4lx_thread_create: Created thread 41d (cpu0) (u:b3000e00, v:b3000c00, sp:02439fa4) l4linux | main thread will be 41d l4linux | section-with-init(-data): Virt: 0x2000000 to 0x252b723 [5293 KiB] l4linux | section-with-init(-data): Phys: 0x801a9000 to 0x806d4723, [5293 KiB] l4linux | section-with-init-text: Virt: 0x2000000 to 0x252b723 [5293 KiB] l4linux | section-with-init-text: Phys: 0x801a9000 to 0x806d4723, [5293 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: 0x2600000 to 0x65fffff [65536 KiB] l4linux | Main memory: Phys: 0x81c00000 to 0x85bfffff, [65536 KiB] l4linux | l4x: vmalloc area: 06600000 - 0e600000 l4linux | text: Virt: 0x2000000 to 0x252b723 [5293 KiB] l4linux | text: Phys: 0x801a9000 to 0x806d4723, [5293 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 423 (timer0) (u:b3000a00, v:00000000, sp:024bffa0) l4linux | Booting Linux on physical CPU 0x0 l4linux | Linux version 4.3.0-l4 (nour@nour-vb) (gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-12ubuntu1) ) #1 SMP Wed Jan 20 17:53:39 CET 2016 l4linux | CPU: Fiasco [412fc0f1] revision 1 (ARMv7), cr=00400000 l4linux | CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache l4linux | Machine: L4 l4linux | Ignoring unrecognised tag 0x00000000 l4linux | Memory policy: Data cache writealloc l4linux | INITRD: 00002000 - 00302000 l4linux | PERCPU: Embedded 9 pages/cpu @0651f000 s12864 r0 d24000 u36864 l4linux | Built 1 zonelists in Zone order, mobility grouping on. Total pages: 17716 l4linux | Kernel command line: mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-arm.rd root=1:0 rw ramdisk_size=4000 l4shmnet.add=shmns,macpart=1 l4linux | PID hash table entries: 512 (order: -1, 2048 bytes) l4linux | Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) l4linux | Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) l4linux | Memory: 64764K/71680K available (3441K kernel code, 163K rwdata, 652K rodata, 224K init, 792K bss, 6916K reserved, 0K cma-reserved) l4linux | Virtual kernel memory layout: l4linux | vector : 0xbffff000 - 0xc0000000 ( 4 kB) l4linux | fixmap : 0xffc00000 - 0xfff00000 (3072 kB) l4linux | vmalloc : 0x06600000 - 0x0e600000 ( 128 MB) l4linux | lowmem : 0x00000000 - 0x06600000 ( 102 MB) l4linux | .text : Virtual kernel memory layout: l4linux | vector : 0xbffff000 - 0xc0000000 ( 4 kB) l4linux | fixmap : 0xffc00000 - 0xfff00000 (3072 kB) l4linux | vmalloc : 0x06600000 - 0x0e600000 ( 128 MB) l4linux | loHierarchical RCU implementation. l4linux | Build-time adjustment of leaf fanout to 32. l4linux | RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=1. l4linux | RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=1 l4linux | NR_IRQS:282 l4linux | clocksource: l4kipclk: mask: 0xffffffffffffffff max_cycles: 0x1d854df40, max_idle_ns: 3526361616960 ns l4linux | l4timer: Using IRQ210 l4linux | sched_clock: 64 bits at 1000kHz, resolution 1000ns, wraps every 2199023255500ns l4linux | Console: colour dummy device 80x30 l4linux | console [ttyLv0] enabled l4linux | Calibrating delay loop... 410.41 BogoMIPS (lpj=2052096) l4linux | pid_max: default: 32768 minimum: 301 l4linux | Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) l4linux | Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) l4linux | CPU: Testing write buffer coherency: ok l4linux | CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 l4linux | Setting up static identity map for 0x20000a0 - 0x20000a0 l4linux | Brought up 1 CPUs l4linux | SMP: Total of 1 processors activated (410.41 BogoMIPS). l4linux | CPU: All CPU(s) started in SVC mode. l4linux | VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0 l4linux | clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns l4linux | NET: Registered protocol family 16 l4linux | DMA: preallocated 256 KiB pool for atomic coherent allocations l4linux | Added static device 'L4ICU' with 0 resources. l4linux | Added static device 'NIC' with 2 resources. l4linux | l4vbus: is running l4linux | L4IRQ: set irq type of 212 to 1 l4linux | l4vbus-root :l4vbus-root:0: added vbus root driver l4linux | clocksource: Switched to clocksource l4kipclk l4linux | NET: Registered protocol family 2 l4linux | TCP established hash table entries: 1024 (order: 0, 4096 bytes) l4linux | TCP bind hash table entries: 1024 (order: 1, 8192 bytes) l4linux | TCP: Hash tables configured (established 1024 bind 1024) l4linux | UDP hash table entries: 256 (order: 1, 8192 bytes) l4linux | UDP-Lite hash table entries: 256 (order: 1, 8192 bytes) l4linux | NET: Registered protocol family 1 l4linux | RPC: Registered named UNIX socket transport module. l4linux | RPC: Registered udp transport module. l4linux | RPC: Registered tcp transport module. l4linux | RPC: Registered tcp NFSv4.1 backchannel transport module. l4linux | Trying to unpack rootfs image as initramfs... l4linux | rootfs image is not initramfs (junk in compressed archive); looks like an initrd l4linux | INITRD: Freeing memory. l4linux | Hi from the sample module l4linux | sample module: Also a warm welcome to the console l4linux | l4x: Checks passed. l4linux | NetWinder Floating Point Emulator V0.97 (double precision) l4linux | futex hash table entries: 256 (order: 2, 16384 bytes) l4linux | NFS: Registering the id_resolver key type l4linux | Key type id_resolver registered l4linux | Key type id_legacy registered l4linux | jitterentropy: Initialization failed with host not compliant with requirements: 2 l4linux | io scheduler noop registered l4linux | io scheduler deadline registered l4linux | io scheduler cfq registered (default) l4linux | l4fb.0: looking for capability 'fb' as goos session l4linux | l4fb.0: init failed err=-2 l4linux | could not allocate fb device: fb l4linux | L4 serial driver l4linux | serial-ttyLv.0: ttyLv0 at MMIO 0x1 (irq = 211, base_baud = 230400) is a L4-vcon l4linux | l4ser_shm: L4 shared mem serial driver l4linux | l4cdds: No name given, not starting. l4linux | brd: module loaded l4linux | l4bdds: No name given, not starting. l4linux | PPP generic driver version 2.4.2 l4linux | NET: Registered protocol family 24 l4linux | shmns: Requesting, Shmsize 1024 Kbytes l4linux | mousedev: PS/2 mouse device common for all mice l4linux | NET: Registered protocol family 17 l4linux | Key type dns_resolver registered l4linux | Registering SWP/SWPB emulation handler l4linux | L4IRQ: set irq type of 211 to 1 l4linux | RAMDISK: ext2 filesystem found at block 0 l4linux | RAMDISK: Loading 3072KiB [1 disk] into ram disk... done. l4linux | EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities l4linux | EXT4-fs (ram0): mounting ext2 file system using the ext4 subsystem l4linux | EXT4-fs (ram0): mounted filesystem without journal. Opts: (null) l4linux | VFS: Mounted root (ext2 filesystem) on device 1:0. l4linux | Freeing unused kernel memory: 224K (02400000 - 02438000) l4linux | l4linux | Please press Enter to activate this console. However once I enter the console, ifconfig command displays no up interfaces. /proc/net/dev file indicates eth0 and lo available and I can run "*ifconfig eth0 up*" successfully. I configure a static IP using ip command but can't get any connection to my host machine. Also, adding *ip=dhcp* to the l4lx-net.cfg file in the start configuration of L4Linux fails with: l4linux | Waiting up to 110 more seconds for network. ... l4linux | Sending DHCP requests ...... timed out! l4linux | IP-Config: Retrying forever (NFS root)... I hope you can help me with that. Thanks in advance: Best Regards, Nourhan [View Less]

2 5

Fiasco-OC.UX, ux_con and the framebuffer examples
by Paul Boddie 22 Jan '16

22 Jan '16

Another year, another look at Fiasco-OC! ;-) I've been looking again at Fiasco-OC.UX and trying to make sense of the documentation. In particular, I'd like to be able to get the framebuffer examples working with the UX graphical console, but it isn't clear to me what I need to do. One thing I discovered straight away was that I needed to provide the -F option as part of the UX_OPTIONS variable when running UX via make. For example: cd src/l4 make O=mybuild ux E=hello MODULE_SEARCH_PATH=.… [View More]./kernel/fiasco/mybuild \ UX_OPTIONS='-G 800x600@24 -F ../kernel/fiasco/mybuild/ux_con' I suspect that to run a framebuffer example, such as the one in src/l4/conf/examples/x86-fb.list, I need to specify E=x86-fb-example and specify the list file using MODULES_LIST: make O=mybuild ux E=x86-fb-example \ MODULES_LIST=conf/examples/x86-fb.list \ MODULE_SEARCH_PATH=../kernel/fiasco/mybuild \ UX_OPTIONS='-G 800x600@24 -F ../kernel/fiasco/mybuild/ux_con' But this naive attempt gives me the following: Could not find 'x86-fb.cfg' with path '../kernel/fiasco/mybuild:/home/paulb/L4/src/l4/mybuild/bin/x86_prescott:... I imagine that I need to more effectively specify paths to various things and to check that they even make sense in the context of the UX environment. Should I even be using this x86-related stuff? Copying the different x86-fb files into one of my existing MODULE_SEARCH_PATH directories did seem to resolve the above immediate error, however, but I then appear to need to build various drivers. This seems to require chasing dependencies as they are reported as missing by the build system, and that makes me wonder whether I've overlooked a command that recursively checks out all dependencies for a given component. Anyway, running the above command with all dependencies compiled and with x86- fb (and x86-legacy.devs) files in the path gives an error like this... Ned: loading file: 'rom/x86-fb.cfg' IO | Io service IO | Find root Pointer IO | ACPI Error: Could not map memory at 0x000E0000 for length 131072 (20121018/tbxfroot-286) IO | Find root Pointer: 0 IO | Ready. Waiting for request. mag | Hello from MAG fbdrv | Trying execution of ``set VBE mode'' using x86emu fbdrv | L4Re[rm]: unhandled read page fault at 0xfd0 pc=0x1007d49 fbdrv | L4Re: unhandled exception: pc=0x1007d49 (pfa=fd4) fbdrv | L4Re: Global::l4re_aux->ldr_flags=0 ...which probably suggests that I really should be using something other than this x86-related stuff. Does anyone have any suggestions, or am I doing something that no-one thought sensible? (As mentioned last year on this list, I'm running everything under Debian on x86, and UX does work with the "hello" example.) Thanks in advance, Paul P.S. I've also found that various links on l4re.org to things like the "getting started" details are broken. For example: http://l4re.org/build.html -> http://l4re.org/doc/l4re_getting_started.html [View Less]

2 6

How can I get L4linux 3.10 code?
by liu.xiaodong2＠zte.com.cn 19 Jan '16

19 Jan '16

Hi, I want to use L4linux 3.10. I see that L4linux 3.10 is available now from https://l4linux.org/, but I can't find any other download-website except L4linux 4.3. Is there some place I can get the older version(3.10) of the L4linux? thanks a lot! -------------------------------------------------------- ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for … [View More]

2 1

Hiring engineers for seL4 work
by Gernot Heiser 12 Jan '16

12 Jan '16

Do you want to be paid for contributing to the seL4 microkernel and its ecosystem, and getting your code used in critical systems on a large scale? As part of a kick-ass team, while living in Sydney, one of the world’s most liveable cities? The seL4 team at DATA61 (formerly NICTA) is hiring OS engineers, see https://ssrg.nicta.com.au/jobs/OS-engineers2015 We’re also hiring: - proof engineers: https://ssrg.nicta.com.au/jobs/proof-engineers2015 - researchers/postdocs: https://ssrg.nicta.com.au/jobs/OS-researchers2015 Gernot

6 25

Question about memory management in L4 Fiasco O.C + L4re
by Mahdi Aichouch 04 Jan '16

04 Jan '16

Hello, I have some questions concerning memory management in Fiasco O.C + L4re. I would like to test two L4Linux instances, and for each L4Linux instance I want to reserve one static fixed physical memory partition. For instance, one 128MB for the first L4Linux and one 128MB for the second. Knowing that Fiasco O.C. uses "on demand paging" to allocate pages for user tasks, is it possible that each partition of L4Linux could be allocated a static physical memory region composed of contiguous … [View More]

2 37

L4Re Update
by Adam Lackorzynski 04 Jan '16

04 Jan '16

Hi, After a longer break I'm pleased to announce an update of the L4Re system software. https://l4re.org Besides bug fixes and enhancements, noteworthy changes and additions of this update include: All: - LLVM/Clang: Fiasco.OC is supported with Clang now, for the userland we're nearly there - Updates for recent GCC versions - CROSS_COMPILE is the preferred way to set the compiler prefix now - URLs have been consolidated to be under the l4re.org domain but old ones will remain to … [View More]

4 3

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

l4-hackers January 2016