l4-hackers November 2011

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

15 participants
17 discussions

Using different serial port for 2 linux instances
by Julien SIMONE 10 Nov '11

10 Nov '11

Hello, I have 2 linux running on top of Fiasco.OC and I would like them to use a different serial port. I found out there is "bootstrap -comport=<com#>" but I don't know how to use it..Maybe it's not the only solution and not the best one... Can someone share some experiences? Thank you. Best regards, Julien.

2 1

Booting multiple instances of L4 Linux
by Julien SIMONE 08 Nov '11

08 Nov '11

Hello, I'm trying to boot 2 instances of L4 linux on top of Fiasco.OC micro kernel but I get an error during the checksum verification. I tried to boot a L4Linux and a hello, it was ok but not with 2 L4Linux. I would like to boot 2 l4Linux on a Beagleboard emulated by QEMU (The error is not from QEMU) The output is: " Verifying Checksum ... Bad Data CRC ERROR: Can't get kernel image!" Is it an error from my module.list file? My config file?..Any ideas? Thank you, Best regards. Julien.

2 1

Problem booting L4 on Sheevaplug
by Julian Vetter 08 Nov '11

08 Nov '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everybody, its me again =) I have a problem booting L4 on the Sheevaplug. I have built L4re, Fiasco and also L4Linux for arm platform and built an uimage by calling "make image E=L4Linux-arm BOOTSTRAP_DO_UIMAGE=y SUPPORT_CC_armkirkwood=y MODULE_SEARCH_PATH=/opt/arm/fiasco:/opt/src/l4/conf/examples:/opt/arm/l4linux:/tmp" Everything worked fine. Than I copied the image to my usb stick and tried to boot it on the Sheevaplug with UBoot. I got the following output: Marvell>> usb start Marvell>> fatload usb 0:1 0x00800000 /bootstrap_l4linux-arm.uimage Marvell>> bootm 0x00800000 ## Booting image at 00800000 ... Image Name: L4 Image #11 Created: 2011-11-08 10:20:15 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 8028328 Bytes = 7.7 MB Load Address: 01000000 Entry Point: 01000000 Verifying Checksum ... OK OK Starting kernel ... And then nothing happens after that. I also tried the simple 'Hello'-Example without L4Linux, and it also didn't work. Or at least I get nothing to see... I think the problem is the serial console. But how can I tell L4 that the output should be send to this same console? (I'm connected to the Sheevaplug via MiniUsb->Usb 'screen /dev/ttyUSB0 115200'). I hope someone can help me. Thanks in advance. Cheers, Julian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOuQcTAAoJEOpGAeJlWp7qygMIALNgU5q0PLFJTtqe31jZwWX0 V8SYxtYuaX/SSowRElRhg7fTHF3FzFKdnGzhmZrRQDc0OGTH2LVpiZR2a6OBhfKX pvq4CjOwNXYSYFz2EtwODie0Z37YH7ywWoO5ojUTJz8XyMkD8mgLlqLqUj9kAL7A RHP5yROXKTc7tvcYiGpqpWAtBs6Em/P/KwynVHZCBeHkgH9UlOvK7ycCbYCTLOBA mqts0mY7NOnNAXG5se5+JuNQXE422lQN66r7PX43Pm5WPumrW/9SJuhH9qyea9FF JCtO9F828pmRK3a98kGc+Nf/TzJjr4EkvsDZKKUQ6zYAWgAVDjVc8OCp1D+kRPk= =0Cgd -----END PGP SIGNATURE-----

2 1

L4CON with client
by Peter Hanzel 08 Nov '11

08 Nov '11

Hello. I am trying L4Re with Fiasco.OC. I have successfuly build l4re-snapshot. Now I am trying to run examples. I am always building iso images with make grub2iso. Now I am editing .cfgs and .list files. I am trying to get working L4CON. The L4Con runs okay, saying: con | Running. Video mode is 800x600@16. con | Ready. Waiting for clients Now I suppose I need some client to work with L4CON. I have tried fbterminal, but it doesn't work. (Or i am missing something in .cfgs) I have added fbterminal to run after "con", but in logs it runs earlier ang log says: fbdrv | Starting server loop mmag | mapped frame buffer at 0x400000 fbtermin| Could not bind event IRQ How can I achive to get some console with for example dash running? Attached are .cfg, .list Thanks.

2 4

Disko UI Framework porting
by Ivan Loskutov 05 Nov '11

05 Nov '11

Hi all! I executed porting of Disko (http://www.diskohq.com/ ) to use in L4Re. Archive with dependencies and patches http://dl.dropbox.com/u/8558928/disko.tar.bz2 1. Differences of Disko original source code I changed *.cpp files name extension to *.cc. I didn’t build a library from *.cpp files. I added files enabling working with framebuffer (mmsgui/fb/mmsfbl4re.cc) and L4Re input subsystem (mmsinput/mmsinputl4rehandler.cc). Virtual file system(VFS) added (mmstool/vfswrapper.cc) for implementation of access at application resources (image, xml form files). Libwhefs library was used for it (http://code.google.com/p/whefs/). 2. Known issues The input system link handler has has only the functions I needed. The touchscreen calibration function was added to mmsinputl4rehandler.cc, but it’s not the best solution. The best solution would be a separate server for the input subsystem that routes handled events to other applications. To simplify the touchscreen handler coding I added a patch to input. See input.patch. L4Re video API function bits_per_pixel returned incorrect pixel size because it was calculated as a sum of R, G, B and A fields sizes. I have used RGB32 format with A field length equal to 0 bits. That’s why the returned total length was 24 bits instead of 32 bits. See video.patch The realloc sometimes malfunctions. But I couldn’t recreate conditions to make this malfunctions repeat. Shared library libdisko.so not building. 3. Comments For application compilation the following utilities are required: taff (from disko tools), whefs-mkfs and whefs-cp (from libwhefs). It was used for creating VFS-image (see examples). You must to build this utilities manually and add they to PATH. For example, to build disko/examples/tutorial/01 vfs-image you need to execute cd disko/examples and run ./convert.sh tutorial/01 I use Gumstix Overo platform with lcd 4.3" and ads7846 touchscreen, drivers added to archive. modules.list and configs added to disko/examples For correct work on ARM you must apply patch from Adam for pthread ( http://os.inf.tu-dresden.de/pipermail/l4-hackers/2011/004992.html ). Some screenshots: http://dl.dropbox.com/u/8558928/disko-04-arm.jpg http://dl.dropbox.com/u/8558928/disko-04-qemu.jpg http://dl.dropbox.com/u/8558928/disko-05-qemu.jpg

2 1

gcc: symbol lookup error: ...libgendep.so: undefined symbol: dlsym
by Wesley Miaw 03 Nov '11

03 Nov '11

Hi, I saw someone ran into this same problem a couple of years ago but I didn't see a solution posted. I just updated my OS to Ubuntu 11 and all of a sudden I am hitting this error when I run make setup and target either x86 or ARM. gcc: symbol lookup error: ...libgendep.so: undefined symbol: dlsym I see -ldl on the gcc line when building libgendep.so, but when I ldd libgendep.so it only prints linux-gate.so.1, libc.so.6, and /lib/ld-linux.so.2. libdl.so.2 exists and is in my ld cache. I am using gcc (Ubuntu/Linaro) 4.6.1. Thanks, -- Wesley Miaw wesley(a)wesman.net

2 1

omap3 usb platform and other
by Vasily Sartakov 02 Nov '11

02 Nov '11

Hello. I would like to discuss with you platforms supported in l4linux. l4linux good working on "vanilla" arm platform, but when we try to use a board specific devices - for example USB, we have some problem with full device support in sources. For example, USB gadget need musb, witch need twl4030, which need i2c, which need clock and power domain initialisation, and all of this part placed in arch/arm/omap. In next mail attachment you can find the our kernel, which support usb on Overo Gumstix platform. We copied sources from arch/arm/omap to arch/l4/kernel/arch-arm/ and made it work. Most of them serious changed, but we tried to save structure. I don't thing what its good solution, but it real working and someone who ask USB support on arm can use it. So, what you think about full board/platform supporting? any idea? Can this solution may be pushed to SVN? I understand that this code should be more clear, and I think it would be better if he would be on the Internet. Incidentally, this is the second version, we have previously done this for kernel 2.6.xx, and it is very difficult to keep a local copy and make regular merge. The other thing which i would like discuss is configuration management for l4re build. With a time, count of a package will be increased, and, like now, the compiling of l4re take a long time. Do you plan in this direction some work? For example, you could make small configuration files for compiling only requirements, similar to Control -- Sartakov A. Vasily

3 4

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 November 2011