l4-hackers March 2014

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

22 participants
31 discussions

Do L4 Linux lack source code about Freescale i.MX6 Quad ?
by Taeung 04 Aug '14

04 Aug '14

Hello , L4 hackers I always appreciate L4 hackers. I've succeed boot "helloworld + L4/Fiasco" on Freescale i.MX6q_sabre_sd. So, I've try to build L4 linux (|Repository : svn co http://svn.tudos.org/repos/oc/l4linux/trunk l4linux|). I've configured for build L4 Linux such as.. ====================================================== System type ---> ARM system type (Allow multiple platforms to be selected) Multiple platform selection ---> ARMv7 based platforms (Cortex-A, PJ4, Scorpion, Krait) Build type Freescale i.MX family Freescale i.MX support ---> i.MX6 Quad/DualLite support ====================================================== But I've meet errors even so often. such as .. 1. ERROR: CONFIG_ARM_PATCH_PHYS_VIRT must not be enabled. => So, I've force to change CONFIG_ARM_PATCH_PHYS_VIRT=y to =n . 2. irq.c:16:26: error: 'L4X_NR_IRQS_V_DYN' undeclared here irq.c:46:14: error: 'L4X_IRQS_V_DYN_BASE' undeclared and irq.c:48:14: error: 'NR_IRQS_HW' undeclared => So, I've included "#include <asm/generic/irq-vectors.h>" and "#include <asm/mach-arm/generic/mach/irqs.h>". 3. l4.c:57:13: error: 'L4X_IRQS_V_STATIC_BASE' undeclared ...etc. => So, I've included "#include <asm/generic/irq-vectors.h>" and "#include <asm/mach-arm/generic/mach/irqs.h>". 4. drivers/built-in.o: In function `clk_disable': clk.c:867: multiple definition of `clk_disable' arch/l4/built-in.o:/home/taeung/workspace/l4linux/arch/l4/kernel/arch-arm/l4.c:73: first defined here drivers/built-in.o: In function `clk_enable': clk.c:919: multiple definition of `clk_enable' arch/l4/built-in.o:/home/taeung/workspace/l4linux/arch/l4/kernel/arch-arm/l4.c:65: first defined here make[1]: *** [vmlinux] Error 1 make: *** [sub-make] Error 2 => So, I delete this lines in l4linux/drivers/clk/clk.c. 7. undefined reference to `__pv_phys_offset' from signal.c , init.c, mm.h ....etc. My question is.... Is it's problem that my config is wrong or l4 linux lack source code about Freescale i.MX6 Quad ? * Refer to > /home/taeung/workspace/l4linux/arch/l4/kernel/*irq.c* /home/taeung/workspace/l4linux/arch/l4/include/asm/generic/*irq-vectors.h* /home/taeung/workspace/l4linux/arch/l4/kernel/*pm.c */home/taeung/workspace/l4linux/arch/l4/kernel/arch-arm/*l4.c** */home/taeung/workspace/l4linux/arch/l4/l4lxlib/generic/*irq_gen.c* /home/taeung/workspace/l4linux/drivers/clk/*clk.c */home/taeung/workspace/l4linux/arch/l4/kernel/arch-arm/*signal.c */home/taeung/workspace/l4linux/arch/l4/mm/arch-arm/*init.c */home/taeung/workspace/l4linux/include/linux/*mm.h *

3 2

OKL4 vs L4::Pistachio
by Taylor Bioniks 15 May '14

15 May '14

How does OKL4 compare with L4::Pistachio as far as speed, security, responsiveness? L4::Pistachio uses kickstart to load it, the core kernel is contained in kernel, and the physical memory manager is stored in sigma0, I'm not even sure if it has a virtual memory manager. Does OKL4 have a built in memory manager, and does it handle virtual memory? Thank you.

3 3

L4Linux + Ubuntu
by Sai Prajeeth 23 Apr '14

23 Apr '14

Hi, I want to replace the standard Linux kernel on my Ubuntu Distro (12.04LTS) with the L4Linux kernel. Is this possible? If yes can someone give me an outline as to how to proceed?

5 11

Ankh Examples
by Ayad Mostafa 09 Apr '14

09 Apr '14

hello l4 hackers, i'm experimenting with ankh and so far failed to successfully ping morpork from my host machine. it seems that receive() blocks at wait_for_data() indefinitely. i can see irq activity on displayed on screen but wait_for_data() does not unblock. i appreciate any help or ideas... software version: l4re revision r63 (2014-02-28) gcc version 4.8.2 qemu version 1.7.0 qemu command: qemu -cpu core2duo -m 128 -cdrom ./morpork.iso \ -net nic,vlan=0,macaddr=00:e0:4c:c6:45:f4,model=rtl8139 -net tap,vlan=0,ifname=tap0 -serial stdio ping command: arping -i tap0 00:E0:4C:C6:45:F4 output: [32mankh | Initialized DDELinux 2.6 [0m [32mankh | <6>net_namespace: 636 bytes [0m [32mankh | Initializing DDE page cache [0m [32mankh | ddekit_pci_init [0m [32mankh | pci bus constructor [0m [32mankh | PCI: L4 root bridge is device 31ca0 [0m [32mankh | pci_irq_enable: [36mdev 0x118004 [0m [0m [32mankh | pci_irq_enable: [36mirq 11, pin 1, devfn 0 [0m [0m [32mankh | ddekit_pci_irq_enable: [32;1mdevfn 0, pin 0 [0m [0m [32mankh | ddekit_pci_irq_enable: [32;1ml4vbus_pci_irq_enable() = 11 [0m [0m [32mankh | IRQ: set irq type of 11 to 4 [0m [32mankh | l4dde26_register_rx_callback: [36mNew rx callback @ 0x1000200. [0m [0m [32mankh | Softirq daemon starting [0m [32mankh | init_wq_head [0m [32mankh | <6>8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004) [0m [32mankh | pci_irq_enable: [36mdev 0x118004 [0m [0m [32mankh | pci_irq_enable: [36mirq 11, pin 1, devfn 0 [0m [0m [32mankh | ddekit_pci_irq_enable: [32;1mdevfn 0, pin 0 [0m [0m [32mankh | ddekit_pci_irq_enable: [32;1ml4vbus_pci_irq_enable() = 11 [0m [0m [32mankh | IRQ: set irq type of 11 to 4 [0m [32mankh | enable_dev: 0 [0m [32mankh | <6>eth0: RTL-8139C+ at 0x109000, 0x11615cM, IRQ 11 [0m [32mankh | unimplemented: pci_set_master [0m [32mankh | <6>pcnet32.c:v1.35 21.Apr.2008 tsbogend(a)alpha.franken.de [0m [32mankh | <6>Intel(R) PRO/1000 Network Driver - version 7.3.21-k3-NAPI [0m [32mankh | <6>Copyright (c) 1999-2006 Intel Corporation. [0m [32mankh | open_network_devices() [0m [32mankh | opening lo [0m [32mankh | <6>device lo entered promiscuous mode [0m [32mankh | set interface to promiscuous mode. [0m [32mankh | opening eth0 [0m [32mankh | <6>device eth0 entered promiscuous mode [0m [32mankh | set interface to promiscuous mode. [0m [32mankh | Thread 0x85 for IRQ 11 [0m [32mankh | <6>eth0: link up, 100Mbps, full-duplex, lpa 0x05E1 [0m [32mankh | Opened 2 network devices. [0m [32mankh | lo IRQ: 0x00 MAC: 00:00:00:00:00:00 MTU: 16436 [0m [32mankh | eth0 IRQ: 0x0B MAC: 00:E0:4C:C6:45:F4 MTU: 1500 [0m [32mankh | Registered @ registry. [0m [32mankh | Gooood Morning Ankh-Morpoooooork! TID = 0x5a [0m [32mankh | Creating session factory. [0m [32mankh | Configuration: debug,promisc,device=eth0,shm=shm_morpork,bufsize=16384,phys_mac [0m [32mankh | Debug mode ON. [0m [32mankh | Using promiscuous mode. [0m [32mankh | Device 'eth0' requested. [0m [32mankh | SHM area 'shm_morpork' requested. [0m [32mankh | Buffer size: 16384 [0m [32mankh | Physical MAC requested. [0m [32mankh | shmc_create: 0 [0m [32mankh | Created shmc area 'shm_morpork' [0m [32mankh | Assigning MAC address: 00:E0:4C:C6:45:F4 [0m [36mmorpork | Using shm area: 'shm_morpork' [0m [36mmorpork | argv[2] = '16384' [0m [36mmorpork | My TID = 0x93 [0m [36mmorpork | Attached shm area 'shm_morpork': 0 [0m [36mmorpork | add_chunk: area 0x10555c0, name 'tx_ring', size 16420 [0m [36mmorpork | SND: signal RX 9b, TX 9c [0m [36mmorpork | buf @ 0x301c, area 0x10555c0 (shm_morpork), size 16420 [0m [36mmorpork | owner 0, name tx_ring, signal tx_signal [0m [36mmorpork | head @ 0x103030, lock state 'unlocked', data size 16384 [0m [36mmorpork | next_rd 0 next_wr 0 filled 0, data @ 0x103051 [0m [36mmorpork | add_chunk: area 0x10555c0, name 'rx_ring', size 16420 [0m [36mmorpork | SND: signal RX 9d, TX 9e [0m [36mmorpork | buf @ 0x3074, area 0x10555c0 (shm_morpork), size 16420 [0m [36mmorpork | owner 0, name rx_ring, signal rx_signal [0m [36mmorpork | head @ 0x10707c, lock state 'unlocked', data size 16384 [0m [36mmorpork | next_rd 0 next_wr 0 filled 0, data @ 0x10709d [0m [36mmorpork | SEND RB @ 0x3018 RECV RB @ 0x3070 INFO @ 0x30c8 [0m [32mankh | l4shmc_attach("shm_morpork") = 0 [0m [32mankh | Shm_chunk::get(0xcf98, "info", 36) [0m [32mankh | ... = 0xcec8 [0m [32mankh | RCV: signal RX 9d, TX 9e [0m [32mankh | RCV: buf size 16420 [0m [32mankh | buf @ 0xcd3c, area 0xcf98 (shm_morpork), size 16420 [0m [32mankh | owner 0, name rx_ring, signal rx_signal [0m [32mankh | head @ 0x16c07c, lock state 'unlocked', data size 16384 [0m [32mankh | next_rd 0 next_wr 0 filled 0, data @ 0x16c09d [0m [32mankh | SND: attaching to signal 9e (443000) [0m [32mankh | buf @ 0x16c07c [0m [36mmorpork | activated Ankh connection. [0m [32mankh | xmit thread started, data @ 0xcf38, TID: 0xa0 [0m [32mankh | RCV: signal RX 9b, TX 9c [0m [32mankh | RCV: buf size 16420 [0m [32mankh | buf @ 0xcf04, area 0xcf98 (shm_morpork), size 16420 [0m [32mankh | owner ffffffff, name tx_ring, signal tx_signal [0m [32mankh | head @ 0x168030, lock state 'unlocked', data size 16384 [0m [32mankh | next_rd 0 next_wr 0 filled 0, data @ 0x168051 [0m [32mankh | RCV: attaching to signal 9b (448000) [0m [32mankh | 16384 ... 16384 [0m [36mmorpork | RCV: signal RX 9b, TX 9c [0m [36mmorpork | RCV: buf size 16420 [0m [36mmorpork | buf @ 0x3114, area 0x10555c0 (shm_morpork), size 16420 [0m [36mmorpork | owner 0, name tx_ring, signal tx_signal [0m [36mmorpork | head @ 0x103030, lock state 'unlocked', data size 16384 [0m [36mmorpork | next_rd 0 next_wr 0 filled 0, data @ 0x103051 [0m [36mmorpork | SND: attaching to signal 9c (41c000) [0m [36mmorpork | buf @ 0x103030 [0m [36mmorpork | sender: 0x3100 [0m [36mmorpork | RCV: signal RX 9d, TX 9e [0m [36mmorpork | RCV: buf size 16420 [0m [36mmorpork | buf @ 0x317c, area 0x10555c0 (shm_morpork), size 16420 [0m [36mmorpork | owner 0, name rx_ring, signal rx_signal [0m [36mmorpork | head @ 0x10707c, lock state 'unlocked', data size 16384 [0m [36mmorpork | next_rd 0 next_wr 0 filled 0, data @ 0x10709d [0m [36mmorpork | RCV: attaching to signal 9d (41e000) [0m [36mmorpork | receiver: 0x3168 [0m [36mmorpork | Got assigned MAC: 00:E0:4C:C6:45:F4 [0m [36mmorpork | info @ 0x10b0c8 [0m [36mmorpork | 00:E0:4C:C6:45:F4 MTU 1500 [0m [36mmorpork | RX packets: 0 dropped: 0 [0m [36mmorpork | TX packets: 0 dropped: 0 [0m [36mmorpork | RX bytes: 0 TX bytes: 0 [0m [36mmorpork | recv->wait_for_data(); [0m kind regards, ayad

3 8

step forward on compilation
by Emanuel Berg 03 Apr '14

03 Apr '14

First: On - let's see - Fri, 28 Mar 2014 02:02:52 +0100 - I sent a message to this list with the subject "again, must know mechanics of compile" - previously, I was able to send to this list, but as for now, I can't find that message either in the group or in the web archive [1]. (I see my old posts though.) I looked for that message because I thought I build on that thread, that's how I noticed it wasn't there (?). Anyway, as for including header files, I found that you can indeed make a directory at the base package level, called "include" - and put a Makefile in it just like it is done for the other projects (but I'm unsure what the Makefile actually does - perhaps if you specify the include directory as a target in the *package* Makefile, you can drop it?). And, you can't use the C++ ".hh" extension, but ".h" works, if you include them like this: #include <l4/hs/task_scheduler.h> if your package is named "hs". In effect, this is quite the opposite of the #include "task_scheduler.hh", and then the -I flag to the compiler. As for -std=c++11, I found that you can pass that not with CFLAGS, but close - this works: CXXFLAGS += -std=c++11 [1] http://os.inf.tu-dresden.de/pipermail/l4-hackers/2014/thread.html -- underground experts united: http://user.it.uu.se/~embe8573

4 9

Custom ramdisk
by Tim Komarov 01 Apr '14

01 Apr '14

Hello, L4 hackers! I use Pandaboard for my practising with Fiasco.OC and L4Linux. 1) I got a problem with booting L4Linux with my own ramdisk. When I use 18 mb ramdisk, I got the following error: reading image.elf 24691072 bytes read ## Starting application at 0x81000000 ... ... ,,,[Everything is usual] ,,, NET: Registered protocol family 17 List of all partitions: No filesystem could mount root, tried: ext3 ext2 ext4 cramfs Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0) CPU: 0 PID: 1 Comm: swapper Not tainted 3.13.0-l4 #1 [<0200c624>] (unwind_backtrace+0x0/0xec) from [<020054c0>] (show_stack+0x10/0x14) [<020054c0>] (show_stack+0x10/0x14) from [<0222e63c>] (panic+0x7c/0x1b8) [<0222e63c>] (panic+0x7c/0x1b8) from [<022f2c40>] (mount_block_root+0x25c/0x29c) [<022f2c40>] (mount_block_root+0x25c/0x29c) from [<022f2f44>] (prepare_namespace+0x160/0) [<022f2f44>] (prepare_namespace+0x160/0x1b4) from [<022f2894>] (kernel_init_freeable+0x1) [<022f2894>] (kernel_init_freeable+0x174/0x1b8) from [<0222ccf0>] (kernel_init+0x8/0x118) [<0222ccf0>] (kernel_init+0x8/0x118) from [<020077d4>] (ret_from_fork+0x14/0x20) [<020077d4>] (ret_from_fork+0x14/0x20) from [<00000000>] ( (null)) panic: going to sleep forever, bye To make ramdisk I simply create a file, write 18 Mb of zeroes to it (with dd), create in that file ext2 partition and copy there files from ramdisk-arm.rd So, what should I do to get a proper working ramdisk? 2) Even more. If I create 20 mb ramdisk, I got this: reading image.elf 26788224 bytes read ## Starting application at 0x00000000 ... Than the booting hangs. Why so? Looking forward for your help, guys! Best wishes, Tim

2 3

I share attached this guide with you.
by Taeung 28 Mar '14

28 Mar '14

Hello, l4 hackers :-) !! I've promised a guide Document to you. It is "L4 / Fiasco porting guide on Freescale i.MX6 Quad SABRE SD(ARMv7)". I have had help from L4 Hackers. So, I was able to do booting "L4 Linux + L4/Fiasco.OC" on this board. I'm particularly grateful to /Tim Komarov /and /Ademd Ammar/ , /Adam Lackorzynski/, /Matthias Lange/. I don't know how much this document will help some beginner. I've thought that the guide Document might help them. But I share this document because I have had a big help from them. It is small but I am delighted to be able to contribute this open source community. :-) If it's contents is wrong , let me know your feedback. - Taeung -

3 2

hello/l4/fiasco.oc for realview pbxa9
by Alexis Fajardo Moya 27 Mar '14

27 Mar '14

Hello, recently I tried to run hello program in top of l4/fiasco.oc for exynos 4412 platform, but qemu doest'n have any platform that support it (at least my installed version) none empty machine collie Collie PDA (SA-1110) nuri Samsung NURI board (Exynos4210) smdkc210 Samsung SMDKC210 board (Exynos4210) connex Gumstix Connex (PXA255) verdex Gumstix Verdex (PXA270) highbank Calxeda Highbank (ECX-1000) midway Calxeda Midway (ECX-2000) integratorcp ARM Integrator/CP (ARM926EJ-S) (default) kzm ARM KZM Emulation Baseboard (ARM1136) mainstone Mainstone II (PXA27x) musicpal Marvell 88w8618 / MusicPal (ARM926EJ-S) n800 Nokia N800 tablet aka. RX-34 (OMAP2420) n810 Nokia N810 tablet aka. RX-44 (OMAP2420) sx1 Siemens SX1 (OMAP310) V2 sx1-v1 Siemens SX1 (OMAP310) V1 cheetah Palm Tungsten|E aka. Cheetah PDA (OMAP310) realview-eb ARM RealView Emulation Baseboard (ARM926EJ-S) realview-eb-mpcore ARM RealView Emulation Baseboard (ARM11MPCore) realview-pb-a8 ARM RealView Platform Baseboard for Cortex-A8 realview-pbx-a9 ARM RealView Platform Baseboard Explore for Cortex-A9 akita Akita PDA (PXA270) spitz Spitz PDA (PXA270) borzoi Borzoi PDA (PXA270) terrier Terrier PDA (PXA270) lm3s811evb Stellaris LM3S811EVB lm3s6965evb Stellaris LM3S6965EVB tosa Tosa PDA (PXA255) versatilepb ARM Versatile/PB (ARM926EJ-S) versatileab ARM Versatile/AB (ARM926EJ-S) vexpress-a9 ARM Versatile Express for Cortex-A9 vexpress-a15 ARM Versatile Express for Cortex-A15 xilinx-zynq-a9 Xilinx Zynq Platform Baseboard for Cortex-A9 z2 Zipit Z2 (PXA27x) For that reason I try to test hello/l4/fiasco.oc in realview pbxa9 platform. I create build directories for l4 and fiasco, configure and compile them for realview pbxa9 platform. Then I execute the following command: ~/build/l4.realview$ make -j2 elfimage E=hello MODULE_SEARCH_PATH=~/build/foc.realview SYSTEM_TARGET=/usr/local/arm-2012.03/bin/arm-none-linux-gnueabi- and this was the result: make[1]: se ingresa al directorio «/home/afmoya/src/l4» =========== Updating RAM_BASE for platform rv_pbx to 0x70000000 ========= ... Regenerating RAM_BASE settings make[2]: se ingresa al directorio «/home/afmoya/src/l4/pkg/sigma0/server/src» make[2]: atención: el servidor de tareas no está disponible: se utilizará -j1. Añada `+' a la regla padre del make. make[3]: se ingresa al directorio «/home/afmoya/build/l4.realview/pkg/sigma0/server/src/OBJ-arm_armv7a-l4f» ... Building Makefile.inc make[3]: se sale del directorio «/home/afmoya/build/l4.realview/pkg/sigma0/server/src/OBJ-arm_armv7a-l4f» make[3]: se ingresa al directorio «/home/afmoya/build/l4.realview/pkg/sigma0/server/src/OBJ-arm_armv7a-l4f» ==> Linking sigma0 ==> "sigma0" built ==> Installing sigma0 to local build-tree make[3]: se sale del directorio «/home/afmoya/build/l4.realview/pkg/sigma0/server/src/OBJ-arm_armv7a-l4f» make[2]: se sale del directorio «/home/afmoya/src/l4/pkg/sigma0/server/src» make[2]: se ingresa al directorio «/home/afmoya/src/l4/pkg/moe/server/src» make[2]: atención: el servidor de tareas no está disponible: se utilizará -j1. Añada `+' a la regla padre del make. make[3]: se ingresa al directorio «/home/afmoya/build/l4.realview/pkg/moe/server/src/OBJ-arm_armv7a-l4f» ... Building Makefile.inc make[3]: se sale del directorio «/home/afmoya/build/l4.realview/pkg/moe/server/src/OBJ-arm_armv7a-l4f» make[3]: se ingresa al directorio «/home/afmoya/build/l4.realview/pkg/moe/server/src/OBJ-arm_armv7a-l4f» ==> Linking moe ==> "moe" built ==> Installing moe to local build-tree make[3]: se sale del directorio «/home/afmoya/build/l4.realview/pkg/moe/server/src/OBJ-arm_armv7a-l4f» make[2]: se sale del directorio «/home/afmoya/src/l4/pkg/moe/server/src» make[2]: se ingresa al directorio «/home/afmoya/src/l4/pkg/bootstrap/server/src» make[3]: se ingresa al directorio «/home/afmoya/build/l4.realview/pkg/bootstrap/server/src/OBJ-arm_armv7a» ... Building .general.d ... Building Makefile.inc Building entry "hello". Merging image /home/afmoya/build/foc.realview/fiasco to mod00 [344kB] Merging image /home/afmoya/build/l4.realview/bin/arm_armv7a/l4f/sigma0 to mod01 [340kB] Merging image /home/afmoya/build/l4.realview/bin/arm_armv7a/l4f/moe to mod02 [2396kB] Merging image /home/afmoya/build/l4.realview/bin/arm_armv7a/l4f/l4re to mod03 [1227kB] Merging image /home/afmoya/build/l4.realview/bin/arm_armv7a/l4f/hello to mod04 [887kB] make[3]: se sale del directorio «/home/afmoya/build/l4.realview/pkg/bootstrap/server/src/OBJ-arm_armv7a» make[3]: se ingresa al directorio «/home/afmoya/build/l4.realview/pkg/bootstrap/server/src/OBJ-arm_armv7a» ... Generating bootstrap.ld ... Compiling exec.o ... Compiling module.o ... Compiling ARCH-arm/crt0.o ... Compiling region.o ... Compiling startup.o ... Compiling init_kip_v2.o ... Compiling init_kip_v4.o ... Compiling libc_support+.o ... Compiling patch.o ... Compiling koptions.o ... Compiling platform/rv.o ... Compiling loader_mbi.o ... Compiling ARCH-arm/reboot.o ==> Linking bootstrap.elf ==> Post-processing bootstrap.elf ==> "bootstrap.elf" built ==> Installing bootstrap.elf in image directory ==> Installing bootstrap.elf to local build-tree ==> Installing bootstrap_hello to local build-tree ==> Installing bootstrap_hello.elf to local build-tree ==> Installing bootstrap_hello in image directory ==> Installing bootstrap_hello.elf in image directory Image size(s) in bytes: bootstrap_hello.elf: 971420 Start address: 0x71000000 --> Build-Nr: 2 make[3]: se sale del directorio «/home/afmoya/build/l4.realview/pkg/bootstrap/server/src/OBJ-arm_armv7a» make[2]: se sale del directorio «/home/afmoya/src/l4/pkg/bootstrap/server/src» make[1]: se sale del directorio «/home/afmoya/src/l4» After that I execute: ~/build/l4.realview/images$ qemu-system-arm -M realview-pbx-a9 -kernel bootstrap_hello.elf -m 256 -serial mon:stdio -nographic this was the result of the execution: oss: Could not initialize DAC oss: Failed to open `/dev/dsp' oss: Reason: No such file or directory oss: Could not initialize DAC oss: Failed to open `/dev/dsp' oss: Reason: No such file or directory audio: Failed to create voice `lm4549.out' L4 Bootstrapper Build: #2 mié mar 26 13:02:05 CDT 2014, 4.6.3 Scanning up to 256 MB RAM Memory size is 256MB (70000000 - 7fffffff) RAM: 0000000070000000 - 000000007fffffff: 262144kB Total RAM: 256MB mod04: 710cb000-710e4580: hello mod03: 710b1000-710ca460: l4re mod02: 71077000-710b062c: moe mod01: 7106d000-71076378: sigma0 mod00: 71017000-7106cedc: fiasco Moving up to 5 modules behind 71100000 moving module 00 { 71017000-7106cedb } -> { 711ce000-71223edb } [351964] moving module 03 { 710b1000-710ca45f } -> { 71100000-7111945f } [103520] moving module 04 { 710cb000-710e457f } -> { 71100000-7111957f } [103808] ...and that was all. No "Hello world". After that I kill the qemu process. What 's the problem with my procedure? Sorry for the huge amount of lines of my email. Best regards! Alexis.

2 6

Have you modified L4 Kernel command line ?
by Taeung 27 Mar '14

27 Mar '14

Hello, L4 hackers :-) May I ask you a question about L4 linux ? Have you modified ' l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=4000 init=/bin/sh' in L4 kernel command ? I want to change it , as if the part of original linux's kernel command line is "root=/dev/mmcblk1p1 rootwait rw" Because I want to assign 'root' to '/dev/mmcblk1p1' or '/dev/mtdblock0' instead of 'rom/ramdisk-arm.rd'. To what I want is achieved, how to modify L4 linux kernel command line ?

2 1

Compiling L4Linux for Pandaboard ARM Error
by Erry Pradana Darajati 25 Mar '14

25 Mar '14

Hello L4 Hackers, i am doing a project that involve L4 and Pandaboard Rev.B1 So far, i am successful to boot Fiasco with L4Re in it. And now, i'm moving on to boot the L4Linux to Pandaboard I'm following the tuts from wiki tudos quickstart. But when i'm try to *make* the L4Linux, it gave me an error like this : =============================================== GEN /media/chiqiVstorage/l4resnap/src/l4linux/TArev2/Makefile CHK include/generated/uapi/linux/version.h CC scripts/mod/empty.o HOSTCC scripts/mod/mk_elfconfig gcc: error: unrecognized argument in option '-mabi=aapcs-linux' gcc: note: valid arguments to '-mabi=' are: ms sysv CC scripts/mod/devicetable-offsets.s gcc: error: unrecognized command line option '-mno-thumb-interwork' make[3]: *** [scripts/mod/empty.o] Error 1 make[3]: *** Waiting for unfinished jobs.... gcc: error: unrecognized argument in option '-mabi=aapcs-linux' gcc: note: valid arguments to '-mabi=' are: ms sysv gcc: error: unrecognized command line option '-mno-thumb-interwork' make[3]: *** [scripts/mod/devicetable-offsets.s] Error 1 make[2]: *** [scripts/mod] Error 2 make[1]: *** [scripts] Error 2 make[1]: *** Waiting for unfinished jobs.... make: *** [sub-make] Error 2 ================================================================ Is this error caused by my GCC ? i am using GCC from the default repository of ubuntu 13.10 And also, when i'm try to *make mrproper *it gave me error : ERROR: Cannot determine L4 source directory Please properly set the path to your L4 build directory in the configuration menu. But i'm sure i set in the wrong path Is there any solution about my problems above, I am appreciating any help and answer Thank you L4 Hackers -- *Regards,* *Erry Pradana Darajati | Student of Computer Engineering* *Politeknik Elektronika Negeri Surabaya / EEPIS, Indonesia*

2 1

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 March 2014