- l4-hackers - example.com Site

Re: Bash-script with l4re-App
by Björn Döbel 20 Jan '15

20 Jan '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Waldo, please send your questions to the l4-hackers(a)os.inf.tu-dresden.de mailing list. On 19.01.2015 20:59, Waldo Paz Rodriguez wrote: > hello l4hacker, I am working with yse5250 card and I need in > implement a driver for a sensor of this card, using L4Re, but I > cant find an example of make this. Can you help me? That is a fairly vague question, so I can only give you a vague answer. In general, device drivers request IO resources (IRQs, IO memory) from a resource manager and then use these resources to manage their device. The interface to request those resources is specified by the IO libraries, which you find either in l4/pkg/libio-direct or l4/pkg/libio-io. Some example drivers can be found in l4/pkg/drivers. If you have more specific questions, please do not hesitate to ask them on the mailing list. Hth, Bjoern - -- Dr.-Ing. Bjoern Doebel Mail: doebel(a)tudos.org TU Dresden, OS Chair Phone: +49 351 463 38 799 Noethnitzer Str. 46 Fax: +49 351 463 38 284 01187 Dresden, Germany WWW: http://www.tudos.org/~doebel - -- "When the seagulls follow the trawler, it's because they think sardines will be thrown into the sea." (Eric Cantona) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlS+GbUACgkQP5ijxgQLUNnVkACeImBFYz/a1sEMWFYz4FJhOhvI uZkAnRuFmsAEzjsK2f73LVfND22kMNnI =XnBR -----END PGP SIGNATURE-----

1 0

Compare security of normal OS and Fiasco.oc with L4re
by Gayathri Nagarajan 19 Jan '15

19 Jan '15

How to show that an application running on l4re with fiasco.oc is more secure than running the same application on normal operating system? Which application can be chosen for proving the security aspects of l4re? Some of which that I know are 1. DMS - Denial of mitigation system 2. IDS - Intrusion Detection system 3. Firewall etc... But I want a very basic and simple application to demonstrate the security when compared with running the same on normal os. Help needed. Gayathri

2 1

build system library path
by teclis High Elf 15 Jan '15

15 Jan '15

If I create a new library is there a library include path in the Fiasco/L4Re build system that I need to add my new library to before I can link to it? thanks

2 1

Source Code of the Monitoring Frameworks FERRET and HAECER
by Karl Steger 13 Jan '15

13 Jan '15

Hi L4 hackers, Would it be possible to make the source code of the monitoring frameworks FERRET [http://os.inf.tu-dresden.de/papers_ps/pohlack-phd.pdf] and HAECER [http://os.inf.tu-dresden.de/papers_ps/haehnel-diplom.pdf] public? I would like to develop a generic monitoring framework with similar capabilities for L4Re. Even if the code was not up to date with the current release or still pertained to L4Env, it would help me greatly. Thanks and regards, Karl

4 3

Problem with running client-server application in l4re
by Gayathri Nagarajan 13 Jan '15

13 Jan '15

I am able to generate "clntsrv.iso" image for the clntsrv application given in l4/pkg/examples directory. But when i execute in qemu, i get * BOOTFS: [1418000-154fef5] [C:503000] l4re* * BOOTFS: [1550000-162e6e6] [C:504000] clntsrv-client* * BOOTFS: [162f000-1714483] [C:505000] clntsrv-server* *No fpage received* *MOE: cmdline: moe --init=rom/clntsrv-server* *MOE: Starting: rom/clntsrv-server * *MOE: loading 'rom/clntsrv-server'* *Could not register my service, is there a 'calc_server' in the caps table?* *MOE: task 1565571 exited with 1* Please help... Gayathri

2 1

PF_RING installation on l4re
by Vidya Lakshmi 07 Jan '15

07 Jan '15

sir, I'm very new to fiasco microkernel. I need assistance for running PF_RING on top of l4re. Please give us guidelines/procedure for the same. Thanks in advance.

2 1

Re: L4Re GPIO
by Erry Pradana Darajati 05 Jan '15

05 Jan '15

>Hi >This piece of code is missing the mapping of the GPIO4's MMIO region. For your >client program to successfully access the GPIO chip you need to create a virtual >device in IO's lua configuration file. Then you attach this device to a virtual bus. In the >startup script you hand IO's capability to that virtual bus to the 'vbus' cap of your >client. Then you client can query its vbus to discover connected devices and their >resources (see documentation of libvbus for reference). Then your client can map the >GPIO's chip MMIO region. > >Best, >Matthias. Thank you for the explanation. I am reading through the libvbus doc right now. I'm still not fully understand but if i conclude the method to access the gpio of omap4460 in Pandaboard is : Define the res.mmio(address) in lua .dev script. Make vbus capabilities in .cfg. Make a program that can access GPIO via vbus with a client-server concept? I'm sorry i'm not fully understand about this, but what is the server of this client i am making. Also, before i your email, i already 'porting' a omap4460-chip driver in io module. and editing the .devs file so it matches with the memory of omap4460 (The two file is attached). Is my step right, and after that what should i do to be able to access it via my main program. When i try to compile the omap44x2.c it give me error like attached below. Is it because i'm not insert all of the virtual function in my program ? because actually i am not really in my goal in the mean time. I really appreciate and say biggest thanks with any of your suggestion and answer P.S : I am attaching my current main program just in case. And i still access it directly. without main2.c : http://pastebin.com/eZKqy1LE omap44x2.c : http://pastebin.com/0hupnnyR arm-omap4.devs : http://pastebin.com/pK6k7F5y error output : http://pastebin.com/s2skR3wu

4 3

L4Android on Pandaboard
by Lin 04 Jan '15

04 Jan '15

Hi hackers, I'm trying to get L4Android working on a PandaBoard ES(OMAP 4460). I managed to run Fiasco and L4Linux successfully, but L4Android give me some error: Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2013 TU Dresden Rev: unknown compiled with gcc 4.7.3 for Pandaboard [] Build: #1 Tue Dec 23 16:44:35 CST 2014 Per_cpu_data_alloc: (orig: 0xf005e290-0xf005ec58) Allocate 2504 bytes (2KB) for CPU[2] local storage (offset=118bd70, 0xf11ea000-0xf11ea9c8) Number of CPUs: 2 Calibrating timer loop... Per_cpu_data_alloc: (orig: 0xf005e290-0xf005ec58) Allocate 2504 bytes (2KB) for CPU[1] local storage (offset=118dd70, 0xf11ec000-0xf11ec9c8) done. FPU1: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl MDB: use page size: 20 Cache config: ON MDB: use page size: 12 ID_PFR[01]: 00001231 00000011S ID_[DA]FR0: 00010444 00000000 IID_MMFR[04]: 00100103 20000000 01230000 00102111 GCPU[1]: goes to idle loop MA0: Hello! KIP @ 80002000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [4:80000000;80000fff] [0:8006f000;8008ffff] [0:80097000;80097fff] [0:8009f000;8013ffff] [4:80140000;8016efff] [0:8016f000;8016ffff] [4:80170000;80186fff] [0:80187000;810fffff] [4:81100000;8451bfff] [0:8451c000;bbffffff] IOMEM:---------------------- [0:0;7fffffff] [0:bd000000;ffffffff] MOE: Hello world MOE: found 928900 KByte free memory MOE: found RAM from 80000000 to bc000000 MOE: allocated 960 KByte for the page array @0x80187000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [81100000-81119458] [C:503000] l4re BOOTFS: [8111a000-8116cc04] [C:504000] ned BOOTFS: [8116d000-812bb454] [C:505000] io BOOTFS: [812bc000-81353c44] [C:506000] mag BOOTFS: [81354000-81375624] [C:507000] fb-drv BOOTFS: [81376000-81376666] [C:508000] l4_gingerbread-arm.cfg BOOTFS: [81377000-81377589] [C:509000] arm-rv-eb-mc.devs BOOTFS: [81378000-8137810a] [C:50a000] l4_android-arm.vbus BOOTFS: [81379000-8177247c] [C:50b000] l4linux.android-arm BOOTFS: [81773000-81873000] [C:50c000] root-arm-ginger.img BOOTFS: [81873000-8451c000] [C:50d000] system-arm-ginger.img MOE: cmdline: moe rom/l4_gingerbread-arm.cfg MOE: Starting: rom/ned rom/l4_gingerbread-arm.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/l4_gingerbread-arm.cfg' io | Io service io | Ready. Waiting for request. mag | Hello from MAG fb | Using LCD driver: ARM AMBA PrimeCell 11x Here is my modules.list file: entry lx_ginger-arm roottask moe rom/l4_gingerbread-arm.cfg kernel fiasco -serial_esc module l4re module ned module io module mag module fb-drv module l4_gingerbread-arm.cfg #from L4Android website module arm-rv-eb-mc.devs #from l4re-snapshot-2014092821/src/l4/pkg/io/config module l4_android-arm.vbus #from l4re-snapshot-2014092821/src/l4/pkg/io/config module l4linux.android-arm module root-arm-ginger.img module system-arm-ginger.img Any ideas on what's going wrong or next steps I can take to diagnose the issue? Thanks! Best regards, Lin

2 1

Re: Iostream and string in L4Re
by Erry Pradana Darajati 04 Jan '15

04 Jan '15

Hi, I already fix the line to this line >> REQUIRES_LIBS += libc_be_file_stdin libstdc++ but it still gave error. But the error is not in the compiler. It's on the linker. My code is like this : char cmd[12] ; printf("Initialization Finished\n"); while(1) { printf("erry@erry-OS : \t"); gets(cmd); if(strcmp(cmd,"clear")==0) { ............. It gives undefined referenced error to gets in main.o (Liunker error not compiler error). Where do i go wrong. And also, how to use getline() in this scope ? >> And also, how to make hello-cfg be able to accept keyboard input. I have >> already include libc_be_file_stdin and include line below in my hello.cfg >> but it still not working : >> >> *L4.default_loader:start({ caps = { log = L4.Env.log,},l4re_dbg = >> L4.Dbg.Warn,log = { "l4linux", "yellow" },}, "rom/hello");* > >That looks ok to me. How are you trying to get the input in your >program? I'm trying to get input using getchar(). But when i load the kernel. It's still skips the input sequence and going into loop (I'm accpeting the keyboard input inside While(1)) Thank you for any help -- *Regards,* *Erry Pradana Darajati | Student of Computer Engineering* *Politeknik Elektronika Negeri Surabaya / EEPIS, Indonesia*

2 1

Re: L4Re GPIO
by Erry Pradana Darajati 28 Dec '14

28 Dec '14

>> 1. I want to QEMU to accept input from keyboard to emulate and study how to >> use an configure of IO. I study this as a part of my main goal to access >> GPIOs of Pandaboard. Well, in my last email i stated that i already include > x86-legacy.devs module in modules.list, and define >> REQUIRES_LIBS=libc_be_file_ >stdin, and using "default-kernel fiasco >> -serial_esc" defined. But, it still not respond to any of my keyboard >> input. So, what did i miss? > >The x86-legacy.devs is for x86-based platforms. The pandaboard is ARM >based, so you do not need that file there. Also, the input here is also >based on the UART that is driven by the kernel, so there's no driver >necessary in user-land here. As already questioned in the other mail, >how are you trying to get the input in your program? Yes, I am testing this scenario in QEMU using x86 Build. The purpose of this testing is to understand how to access and use the IO using L4Re. Because i'm still not fully understand about it. So i'm trying to make a L4RE Build x86, boot it in the QEMU and directly access using keyboard input (not via serial). But i still cannot do that. In Pandaboard ARM. i am already understand and be able to access keyboard via UART3 >> 2. I have modified omap3 driver that included in the package to be used >> with omap4460 registers, but i have a few difficulties. There are few >> missing registers (like Clr_irq_enable1 register that not present in >> OMAP4460) and i am still cannot comprehend the scm_offset table. Because >> when i crossreferencing the source with the OMAP3 TRM the i cannot >> understand the value. My question is. Is it be able to use only some of the >> defined register to do simple IO task, and enable or disable register ? > >I've not written the particular code, but the scm_offset seems to select >a specific gpio block. >For starting to work on a driver I recommend to start with a simple >program and directly work on the MMIO. This helps to understand how the >device is working. When basic things work, such as switching pins >on/off, settings directions, interrupts, etc things can be integrated. I am studying to directly access the GPIO. So if i wrote simple program (let's say main.c program in testGPIO module that i created myself). I don't need to call the .devs and .io or call the driver module ? And also, i already make successful block code to access GPIO but not using L4Re API. But it cannot be implemented in L4Re Block code. It's something like this : http://pastebin.com/TMc9ieBr Thank you, and i really appreciate any answer and helps. -- *Regards,* *Erry Pradana Darajati | Student of Computer Engineering* *Politeknik Elektronika Negeri Surabaya / EEPIS, Indonesia*

2 1