l4-hackers

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

2827 discussions

Start a nNew thread

Static_object in fiasco kernel
by 水镜 23 Apr '15

23 Apr '15

hi, what is the Static_object in fiasco kernel used for?

2 1

How L4Linux Linked the header file?
by Youren Shen 23 Apr '15

23 Apr '15

Hi, I'm trying to port L4Linux 3.14 to Linux Kernel 3.4. But when I complied the kernel, this error happened: /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/kernel/main.c: In function 'cpu0_startup': /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/kernel/main.c:2124:2: error: implicit declaration of function 'set_my_cpu_offset' [-Werror=implicit-function-declaration] I checked main.c file: #include <asm/unistd.h> #include <asm/percpu.h> #include <asm/generic/l4lib.h> So I add one percpu.h file with definition of 'set_my_cpu_offset' in /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/include/asm/arch-arm/, however this error still happened. Then I add the definition of this function to /home/shenyouren/workspace/kernel/kernel_exynos5250/include/linux/percpu.h, then the error message will not show. Also, discard the change in $(src)/include/linux/percpu.h, then I change the main.c file to include absolute path of percpu.h. #include <asm/unistd.h> #include </home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/include/asm/arch-arm/percpu.h> #include <asm/generic/l4lib.h> It passed the complied to. So that is say, the #include <asm/percpu.h> is reference to src/include/linux/percpu.h. That really strange. I do not change the Makefile in arch/l4, and I really confused about this error. Now this problem occurs to me again, when complied the arch/l4/kernel/timer.c file, this error happened: /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/kernel/timer.c:153:35: warning: 'struct clock_event_device' declared inside parameter list [enabled by default] /home/shenyouren/workspace/kernel/kernel_exynos5250/arch/l4/kernel/timer.c:153:35: warning: its scope is only this definition or declaration, which is probably not what you want [enabled by default] but the definition of this to file should be defined in clockchips.h which is include in timer.c: #include <linux/timex.h> #include <linux/clockchips.h> #include <linux/irq.h> Thank you for your reading, I just want to know what's the rule of L4Linux header file linking, and solve this problem. I'd be so appreciated if anyone can give me some help! -- Best Regards. Youren Shen.

2 1

How to compile the fiasco kernel test directory?
by Liu Xiaodong 23 Apr '15

23 Apr '15

Hi,I got a tar ball(l4re-snapshot-2014092821.tar.bz2) from fiasco website. I see a directory for test under the fiasco kernel source path: /l4re-snapshot-2014092821/src/kernel/fiasco/src/test/. But I can't compile them in the normal way, such as that you discrbed in the website http://os.inf.tu-dresden.de/fiasco/build.html. I really want to do some kernel tests on fiaso. If you can tell me how to compile the fiasco kernel test directory, it will be very helpful, and I will appreciate it. By the way, the test source code seems to not be included completely. Such as /l4re-snapshot-2014092821/src/kernel/fiasco/src/test/space/space.t.cc #include <iostream> #include <iomanip> #include <cassert> using namespace std; #include <flux/page.h> #include "space.h" int main() { // // Make task 4 the chief of task 5 // assert (space_index_t (5).lookup () == 0); assert (space_index_t (5).chief () == 0); assert (space_index_t (5).set_chief (space_index_t(0), space_index_t(4))); assert (space_index_t (5).lookup () == 0); assert (space_index_t (5).chief () == 4); ...... } I can't find headfile "space.h" in the tar ball, and there is no define about "space_index_t" too. can you tell me why? thanks again! -------------------------------------------------------- ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.

2 3

How to do quickly in order to starting fiasco with a console shell?
by zhou.li9＠zte.com.cn 23 Apr '15

23 Apr '15

How to do quickly in order to starting fiasco with a console shell? After copying src/l4/conf/examples/x86-fb.list to src/l4/conf/modules.list,I use QEMU to boot,the boot process appears to be normal: ....... fbdrv | Starting server loop mag | mapped frame buffer at 0x200000 mag | View::Info: mag | flags: 0 mag | size: 1280x1024 pos: 0, 0 mag | bytes_per_line: 2560 mag | buffer_offset: 0 mag | RGBA(2): 5(11):6(5):5(0):0(0) mag | memory 200000-600000 mag | Plugin: Mag_client service started mag | Plugin: Frame-buffer service started mag | L4INPUT native mode activated mag | L4INPUT: !!! W A R N I N G !!! mag | L4INPUT: Please, do not use Fiasco's "-esc" with L4INPUT. mag | L4INPUT: !!! W A R N I N G !!! mag | serio: i8042 AUX port at 0x60,0x64 irq 12 mag | serio: i8042 KBD port at 0x60,0x64 irq 1 mag | input: ImExPS/2 Generic Explorer Mouse on isa0060/serio1 mag | input: AT Translated Set 2 keyboard on isa0060/serio0 mag | connect "ImExPS/2 Generic Explorer Mouse", isa0060/serio1/input0 mag | connect "AT Translated Set 2 keyboard", isa0060/serio0/input0 spectrum| x:640 y:480 bit/pixel:16 bytes/line:1280 But How can I input some shell command? -------------------------------------------------------- ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.

3 4

Re: Using a second UART to control a serial device
by Pflaum, Clemens 20 Apr '15

20 Apr '15

Thank you for your fast response, I've adapted your code to my needs (using the uart_pxa driver in drivers-frst). It compiles and starts up fine on the BananaPi but sadly I'm not getting any response on the uart3 pins... It seems to have a problem in the l4\pkg\drivers-frst\uart\src\uart_pxa.cc when calling the Uart_16550::startup(regs). I get a few wierd boxlike characters on the console and then "failed to startup uart regs". This is my init() : #define IRQ_NUM 86 #define UART_BASE 0x01C28C00 . . . bool Maestro_server::init() { l4_addr_t virt_base = 0; if (l4io_request_iomem((l4_addr_t)UART_BASE, 0x1000, L4IO_MEM_NONCACHED, &virt_base)) { printf("maestro-drv: request io-memory from l4io failed.\n"); return false; } printf("maestro-drv: virtual base at:%lx\n", virt_base); L4::Io_register_block_mmio *regs = new L4::Io_register_block_mmio(virt_base); _uart = new (malloc(sizeof(L4::Uart_16550))) L4::Uart_16550((unsigned long) 115200); if(!(_uart->startup(regs))){ printf("failed to startup uart regs!"); } if(!(_uart->change_mode(0x00 | 0x03 | 0x00, 115200))){ printf("failed to change uart mode!"); } the rest of it is equal to the serial-drv example. Any idea what i couldve done wrong? regard, Clemens

1 0

Using multiple NICs within one application
by Stark, Josef 19 Apr '15

19 Apr '15

Hello, is it possible to use more than one network card in one L4Re-application and how would I do that? I would guess from the example lwip lua-script that I had to create a separate shm-area and/or communication channel (for ankh-sessions) for each device that my app wants to access, but I don't know how I would supply these additional channels to ankh and if this would be enough to enable multi-NIC networking. Any help would be appreciated. Regards, Josef

1 0

Re: Using a second UART to control a serial device
by Reinier Millo Sánchez 18 Apr '15

18 Apr '15

Hi Clemens I have been testing something similar in other board (YSE5250-Exynos5). First you must guarantee that the UART device driver is compatible with the hardware or you must write an specific device driver. I have tried to make a GPS device driver using the S3C2410 UART based on the serial-drv package. To connect the uart on the user land with my server i have configured the HW.Device in a vbus with the IO server using this configuration: -- File: yse5250.devs local Hw = Io.Hw local Res = Io.Res Io.hw_add_devices { UART3 = Hw.Device { hid = "UART3"; Res.irq(86); Res.mmio(0x12C30000, 0x12C3ffff); } } To create the vbus, i have created the file yse5250.io: -- File: yse5250.io Io.add_vbusses { -- Create a virtual bus for a client and give access to UART3 uart03 = Io.Vi.System_bus(function () dev = wrap(Io.system_bus():match("UART3")); end); } To run my server using the UART3 on the vbus have used this configuration -- gps-drv.cfg -- Run GPS Driver for YSE5250 (Exynos 5250) require("L4"); -- Shortcuts local ld = L4.default_loader; local vbus_uart03 = ld:new_channel(); local platform_ctl = ld:new_channel(); local gps_srv = ld:new_channel(); -- Start the IO Server ld:start( { caps = { sigma0 = L4.cast(L4.Proto.Factory, L4.Env.sigma0):create(L4.Proto.Sigma0); icu = L4.Env.icu; platform_ctl = platform_ctl:svr(); uart03 = vbus_uart03:svr(); }, log = { "IO Server", "green" }, l4re_dbg = L4.Dbg.Warn, }, "rom/io rom/yse5250.devs rom/yse5250.io"); -- Start the GPS Driver Server conected to UART3 ld:start( { caps = { gps_srv = gps_srv:svr(); vbus = vbus_uart03; }, log = {"GPS Driver","blue"} }, "rom/gps_drv"); The server code is very similar to: /pkg/serial-drv/server/src/main.cc But in my case i have adjusted the UART to use the S3C2410 uart. Best regards On 04/18/2015 06:00 AM, l4-hackers-request(a)os.inf.tu-dresden.de wrote: > Message: 1 > Date: Fri, 17 Apr 2015 12:03:46 +0200 > From: "Pflaum, Clemens"<clemens.pflaum(a)mytum.de> > To:l4-hackers@os.inf.tu-dresden.de > Subject: Using a second UART to control a serial device > Message-ID:<4a79357eec3b3359e8b09e16a3fe0994(a)roundcube.lrz.de> > Content-Type: text/plain; charset=US-ASCII; format=flowed > > Hi L4 Hackers, > Im currently running Fiasco.OC with L4Re on my BananaPi. I'm trying to > control a serial device (Pololu Servo Controller) by sending a small > series of Bytes over a second UART ( not UART 0 since im getting the > console from there ). Via documentation I've found out that UART 3 is at > 0x01C28C00 and is a U6_16550A, so I'm hoping the driver in > /pkg/drivers-frst/uart/src/uart_pxa.cc will be compatible with that. > Where and how would I have to go about initiating my UART 3? By writing > a new platform for BPi in /pkg/bootstrap/server/src/platform? The > function set_stdio_uart(&_uart); made me think its only the "console" > UART. Or do I have to instantiate some kind of Hw.Device like the gpio > in /pkg/io/config/arm-omap3.devs and put it on a new vBus like in > /pkg/io/doc/example.io ? > > Or am I thinking way too complicated and it is as simple as editing the > /pkg/serial-drv/server/src/main.cc : > > bool > Serial_drv::init() > { > int irq_num = 37; > // How can i find out what this number refers to/do i have to > change it at all? > l4_addr_t phys_base = 0x1000a000; > // change to 0x01C28C00 > #if 0 > int irq_num = 74; > l4_addr_t phys_base = 0x49020000; > #endif > l4_addr_t virt_base = 0; > > if (l4io_request_iomem(phys_base, 0x1000, L4IO_MEM_NONCACHED, > &virt_base)) > { > printf("serial-drv: request io-memory from l4io failed.\n"); > return false; > } > printf("serial-drv: virtual base at:%lx\n", virt_base); > > L4::Io_register_block_mmio *regs = new > L4::Io_register_block_mmio(virt_base); > _uart = new (malloc(sizeof(L4::Uart_pl011))) L4::Uart_pl011(24019200); > //change to L4::Uart_pxa(what does this number mean?) > _uart->startup(regs); > > > Thanks for any answers in advance. > > Regards, > Clemensc...(a)mytum.de -- Lic. Reinier Millo Sánchez Centro de Estudios de Informática Universidad Central "Marta Abreu" de Las Villas Carretera a Camajuaní Km 5 1/2 Santa Clara, Villa Clara, Cuba CP 54830 "antes de discutir ... respira; antes de hablar ... escucha; antes de escribir ... piensa; antes de herir ... siente; antes de rendirte ... intenta; antes de morir ... vive"

1 0

Using a second UART to control a serial device
by Pflaum, Clemens 17 Apr '15

17 Apr '15

Hi L4 Hackers, Im currently running Fiasco.OC with L4Re on my BananaPi. I'm trying to control a serial device (Pololu Servo Controller) by sending a small series of Bytes over a second UART ( not UART 0 since im getting the console from there ). Via documentation I've found out that UART 3 is at 0x01C28C00 and is a U6_16550A, so I'm hoping the driver in /pkg/drivers-frst/uart/src/uart_pxa.cc will be compatible with that. Where and how would I have to go about initiating my UART 3? By writing a new platform for BPi in /pkg/bootstrap/server/src/platform? The function set_stdio_uart(&_uart); made me think its only the "console" UART. Or do I have to instantiate some kind of Hw.Device like the gpio in /pkg/io/config/arm-omap3.devs and put it on a new vBus like in /pkg/io/doc/example.io ? Or am I thinking way too complicated and it is as simple as editing the /pkg/serial-drv/server/src/main.cc : bool Serial_drv::init() { int irq_num = 37; // How can i find out what this number refers to/do i have to change it at all? l4_addr_t phys_base = 0x1000a000; // change to 0x01C28C00 #if 0 int irq_num = 74; l4_addr_t phys_base = 0x49020000; #endif l4_addr_t virt_base = 0; if (l4io_request_iomem(phys_base, 0x1000, L4IO_MEM_NONCACHED, &virt_base)) { printf("serial-drv: request io-memory from l4io failed.\n"); return false; } printf("serial-drv: virtual base at:%lx\n", virt_base); L4::Io_register_block_mmio *regs = new L4::Io_register_block_mmio(virt_base); _uart = new (malloc(sizeof(L4::Uart_pl011))) L4::Uart_pl011(24019200); //change to L4::Uart_pxa(what does this number mean?) _uart->startup(regs); Thanks for any answers in advance. Regards, Clemens c...(a)mytum.de

1 0

the kernel's output
by 水镜 17 Apr '15

17 Apr '15

hi , there're a lot of printf in fiasco kernel, but i can not seen any output on the screen. how could i turn these things on?

2 1

the ldscripts of L4Re
by 水镜 16 Apr '15

16 Apr '15

hi, the L4Re has three ldscripts: main_dyn.ld main.rel.ld main.stat.ld what are the differences?

2 1

Jump to page:

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