l4-hackers May 2014

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

17 participants
27 discussions

25 Sep '14

Hello l4-hackers, I get an error when trying to compile, respectively linking my program. /opt/gcc-linaro-arm-linux-gnueabihf-4.8-2014.03_linux/bin/arm-linux-gnueabihf-ld: cannot find -lld-l4 make[3]: *** [myProg] Fehler 1 My Program does not include this lib. It comes from the L4-make process (prog.mk). I have already compiled smaller programs, without problems. BTW before that missing lib error, i get a lot of "multiple definition of...". Any ideas? I use Debian 7 32bit. Thanks

3 4

I share a document to access HW on L4 Linux.
by Taeung 18 Aug '14

18 Aug '14

Thank you L4 Hackers. You have help me in securing Ethernet on L4 Linux. So, I succeeded it. I’m particularly grateful to Martin Schröder, Wei jin, Adam Lackorzynski, Matthias Lange. Although there is already a document 'L4 Runtime Environments : Io, the Io server' a link of which is http://os.inf.tu-dresden.de/L4Re/doc/io.html, I made a guide document for accessing HW on L4 Linux because of ethernet example. (I've used ARM platform Freescale i.MX6 Quad SABRESD ) This document is https://www.dropbox.com/s/abj9ao5uk9r3w72/The_Guide_to_access_HW_on_L4Linux… I don’t know whether this document can help someone in accessing HW on L4Linux. But I want to share this document in order to repay for l4hackers's kindness. - Taeung -

3 5

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

Documentation of Sched_context
by Valentin Hauner 03 Jun '14

03 Jun '14

Hi, what exactly is represented by a Sched_context? 'sched_context-fixed_prio.cpp', for example, contains members called '_prio' and '_quantum'. That would suggest that a Sched_context is a schedulable object like a task or a thread. However, the file mentioned above defines some sort of ready queue, too. That would indicate that a Sched_context is some part of the scheduler that organizes the schedulable objects in a data structure? Where are all those classes documentated? Using the search box, the official documentation (http://os.inf.tu-dresden.de/L4Re/doc/index.html) does not offer any information about these. Best regards, Valentin Hauner

2 1

Some confusing code of the kernel
by Yuxin Ren 01 Jun '14

01 Jun '14

Hi, Now I am learning the kernel code of Fiasco. But as I do not know much about C++, I feel confused about some code. In the file obj_space-virt.cpp, we have such code EXTENSION class Generic_obj_space : Obj_space_virt<Generic_obj_space<SPACE> > And similarly, in the file obj_space-phys.cpp, we have EXTENSION class Generic_obj_space : Obj_space_phys<Generic_obj_space< SPACE > > 1. What's the meaning of these tow line code? Does it mean that the class Generic_obj_space inherit from both class Obj_space_virt and class Obj_space_phys? 2. I note that class Obj_space_virt and Obj_space_phys have some methods with the same name, such as lookup_local method. When such a method is called, how can I know which class is invoked? Thanks a lot.

4 7

page fault on virtual bus
by ba_f 30 May '14

30 May '14

Hello Hackers, i try to access some peripheral on my platform. But i get page faults when writing to the peripheral at 0x41220000: MOE: Hello world MOE: found 505476 KByte free memory MOE: found RAM from 6f000 to 1f000000 MOE: allocated 495 KByte for the page array @0x9f000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [116d000-116d117] [C:503000] periTest.cfg BOOTFS: [116e000-116e1aa] [C:504000] periTest.io BOOTFS: [116f000-1188494] [C:505000] l4re BOOTFS: [1189000-129673c] [C:506000] io BOOTFS: [1100000-1152c0c] [C:507000] ned BOOTFS: [1153000-116c5e4] [C:508000] periTest MOE: cmdline: moe rom/periTest.cfg MOE: Starting: rom/ned rom/periTest.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/periTest.cfg' periTest| L4Re[rm]: unhandled write page fault @41220000 pc=1000294 periTest| L4Re: unhandled exception: pc=0x1000294 Here is my CFG. My io-file looks like the one here https://os.inf.tu-dresden.de/L4Re/doc/io.html ## cfg require("L4"); local loader = L4.default_loader; local io_buses = { FOODEVICE = loader:new_channel(); }; loader:start({ caps ={ FOODEVICE = io_buses.FOODEVICE:svr(), }, }, "rom/periTest rom/periTest.io" ); ## end CFG Thanks for any help.

4 3

Re: kinvoke fonction
by Matthias Lange 28 May '14

28 May '14

On Tue, May 27, 2014 at 03:45:18PM +0000, Bouchra Elouri wrote: > Hi Matthias, > can you explain to me what this fonction do :Scheduler::kinvoke(L4_obj_ref > ref, L4_fpage::Rights rights, Syscall_frame *f, Utcb const *iutcb, Utcb > *outcb) > > L4_obj_ref ref : ?? explication L4_obj_ref is a reference to a kernel object. See src/abi/l4_types.cpp for details. > L4_fpage::Rights rights : ?? These are the access rights for the kernel object. See src/abi/l4_fpage.cpp. > Syscall_frame *f : ?? A Syscall_frame encapsulates the system call data. See src/kern/entry_frame.cpp. > Utcb const *iutcb, Utcb *outcb: ?? The UTCB is used to pass and return data between kernel and user (in case of a system call) or between IPC partners. If you have other questions in the future please use the l4-hackers mailing list! 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

1 0

[Question] How do I do to secure LCD on L4 Linux ?
by Yeongchan 28 May '14

28 May '14

Hi, l4hackers I'm try to securing LCD on L4 Linux using Freescale i.MX6Q SABRESD board. I succeeded in securing Ethernet on L4 Linux. But I don't yet secure LCD on L4 Linux. LCD(HSD100PXN1) is connected by LVDS. I've modified as below.. 1.' .io' I've added LDB control register address to '.io' file. 2. 'mach_setup.c' (l4linux/arch/l4/kernel/arch-arm/mach_setup.c) I've added code for LVDS. Qusetion 1. Did I do wrong modification ? Qusetion 2. Must I do something outside of that ? How do I do to secure LCD on L4 Linux ? If you give a bit hints me, I would appreciate it .

2 1

Re: Doing simple I/O in clntsrv example
by Marcus Hähnel 26 May '14

26 May '14

On 2014-05-22 16:02, Valentin Hauner wrote: > On 05/22/2014 03:41 PM, Marcus Hähnel wrote: >> Sorry. Forgot to reply to the previous mail. Is this for a 64-bit or >> 32-bit system? > No problem. > It's a 32-bit system, I'm compiling into ./bin/x86_586. You need a terminal to do input. fbterminal is one that provides what you need. It does not work from the serial line out of the box as far as I know. Please have a look at the x86-fb.* example in l4/conf/examples and start the client using the same method. This will allow it to receive keyboard input. Instead of the ex_spectrum... example use fbterminal to start with mag using (for example) the following lines: local c = { fb = mag_caps.svc:create(L4.Proto.Goos, "g=800x600"), term = l:new_channel():svr() }; l:start({ caps = c }, "rom/fbterminal"); And then start the clntsrv-client in the terminal using (again, for example): l:startv({ caps = { calc_server = calc_server}, log = c.term:m("ro") }, "rom/ex_clntsrv-client"); Best regards, - Marcus Haehnel

1 0

Where is kernel entry code
by Yuxin Ren 26 May '14

26 May '14

Hi, Where is the code around kernel entry, including both l4Re and kernel? What is the register format of system call in Fiasco? Thanks a lot. Best

3 3

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