l4-hackers

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

2827 discussions

Trustzone Dual-OS
by meng-qy 12 Nov '12

12 Nov '12

Hi,all： Now,we are trying to make dual-os solution based on fiasco, android and trustzone. Does it already have the stable dual-os soluton in l4-hacker community? If have, how can we get it? we can not find the trustzone-surpport in the latest release of source tree. Thanks and looking forward your response. Best Regards Steven Meng --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient, unauthorized use, forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. ---------------------------------------------------------------------------------------------------

1 0

bootstrapper error
by Ryan Brown 10 Nov '12

10 Nov '12

Hi, I just tried updating to fiasco/l4re from 2012081219, and now I'm getting bootstrapper errors. Previously bootstrap went like this: L4 Bootstrapper Build: #1 Wed Jun 27 14:54:16 PDT 2012, x86-32, 4.4.3 RAM: 0000000000000000 - 000000000009f3ff: 637kB RAM: 0000000000100000 - 0000000012bfcfff: 306164kB Total RAM: 299MB Moving 11 modules to 1100000 with offset f2fc2000 moving module 01 { e13e000, e1b4914 } (ELF) -> { 1100000 - 1176914 } moving module 02 { e1b5000, e1f5a05 } (ELF) -> { 1177000 - 11b7a05 } moving module 03 { e1f6000, e3b92fb } (ELF) -> { 11b8000 - 137b2fb } moving module 04 { e3ba000, e4a8004 } (ELF) -> { 137c000 - 146a004 } moving module 05 { e4a9000, e6a301e } (ELF) -> { 146b000 - 166501e } moving module 06 { 12a71000, 12a71237 } (-- v) -> { 5a33000 - 5a33237 } moving module 07 { e6a4000, ef0f8c7 } (ELF) -> { 1666000 - 1ed18c7 } moving module 08 { ef10000, eff8eba } (ELF) -> { 1ed2000 - 1fbaeba } moving module 09 { 12bcd000, 12bcd3b7 } (# vi) -> { 5b8f000 - 5b8f3b7 } moving module 10 { 12a72000, 12a72106 } (l4li) -> { 5a34000 - 5a34106 } moving module 11 { eff9000, f9280a6 } (ELF) -> { 1fbb000 - 28ea0a6 } => Images moved But now I get this: L4 Bootstrapper Build: #1 Tue Nov 6 15:26:40 PST 2012, x86-32, 4.6.x RAM: 0000000000000000 - 000000000009f3ff: 637kB RAM: 0000000000100000 - 0000000012bfcfff: 306164kB Total RAM: 299MB Moving modules behind 1100000 moving module 00 { e13e000-e163d3f } -> { 12b6c000-12b91d3f } [154944] moving module 01 { e164000-e1c0c6b } -> { 12b92000-12beec6b } [380012] moving module 02 { e1c1000-e41df1f } -> { 12bef000-12e4bf1f } [2477856] ERROR: module target [12bef000-12e4bf1f) overlaps [ 12bfd000, 12bfffff] { 3000} Arch BIOS can not move module Key press reboots... I've tried specifying different modaddrs, but it always starts moving modules to 12b6c000 and runs past the end of RAM. I tried increasing the ram to my virtual machine, but bootstrap just picks a higher address that doesn't work. What am I doing wrong? Also, I noticed now that io is 11mb. Is it normal for it to be this big?

2 1

bug report: compile about l4re
by Wangjintang 06 Nov '12

06 Nov '12

Environment: Linux linux-tilera 2.6.32.12-0.7-default #1 SMP 2010-05-20 11:14:20 +0200 x86_64 x86_64 x86_64 GNU/Linux gcc version 4.3.4 [gcc-4_3-branch revision 152973] (SUSE Linux) packet: l4re-core-2012081219.tar.bz2 step: 1. Create build directory somedir$ cd src/kernel/fiasco somedir/src/kernel/fiasco$ make BUILDDIR=mybuild The make step will generate a build directory called mybuild. 1. Got the build directory somedir/src/kernel/fiasco$ cd mybuild 1. Configure kernel build somedir/src/kernel/fiasco/mybuild$ make config Will launch the configuration menu. This is the time to configure your kernel. The default config will build a uniprocessor IA32 kernel with debugging features enabled. If you're happy with this step you may skip it. 1. Build it somedir/src/kernel/fiasco/mybuild$ make -j4 In file included from /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/kern/kmem_alloc.cpp:3, from /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/boot/bootstrap.cc:18: /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/kern/auto_quota.h:13: error: invalid pure specifier (only `= 0' is allowed) before ';' token /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/kern/auto_quota.h:14: error: invalid pure specifier (only `= 0' is allowed) before ';' token In file included from /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/lib/libk/slist:22, from /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/kern/kmem_alloc.cpp:4, from /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/boot/bootstrap.cc:18: /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/lib/libk/bits/list_basics.h:50: error: invalid pure specifier (only `= 0' is allowed) before ';' token /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/lib/libk/bits/list_basics.h:51: error: invalid pure specifier (only `= 0' is allowed) before ';' token In file included from /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/kern/kmem_alloc.cpp:4, from /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/boot/bootstrap.cc:18: /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/lib/libk/slist:46: error: invalid pure specifier (only `= 0' is allowed) before ';' token /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/lib/libk/slist:47: error: invalid pure specifier (only `= 0' is allowed) before ';' token In file included from /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/boot/bootstrap.cc:18: /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/lib/libk/bits/list_basics.h: In instantiation of 'cxx::Bits::Basic_list<cxx::Bits::Basic_list_policy<Kmem_alloc_reaper, cxx::S_list_item> >': /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/lib/libk/slist:45: instantiated from 'cxx::S_list<Kmem_alloc_reaper, cxx::Bits::Basic_list_policy<Kmem_alloc_reaper, cxx::S_list_item> >' /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/lib/libk/slist:127: instantiated from 'cxx::S_list_bss<Kmem_alloc_reaper>' /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/kern/kmem_alloc.cpp:309: instantiated from here /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/lib/libk/bits/list_basics.h:50: error: initializer specified for non-virtual method 'cxx::Bits::Basic_list<POLICY>::Basic_list(const cxx::Bits::Basic_list<POLICY>&) [with POLICY = cxx::Bits::Basic_list_policy<Kmem_alloc_reaper, cxx::S_list_item>]' /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/lib/libk/bits/list_basics.h:51: error: initializer specified for non-virtual method 'void cxx::Bits::Basic_list<POLICY>::operator=(const cxx::Bits::Basic_list<POLICY>&) [with POLICY = cxx::Bits::Basic_list_policy<Kmem_alloc_reaper, cxx::S_list_item>]' /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/lib/libk/slist: In instantiation of 'cxx::S_list<Kmem_alloc_reaper, cxx::Bits::Basic_list_policy<Kmem_alloc_reaper, cxx::S_list_item> >': /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/lib/libk/slist:127: instantiated from 'cxx::S_list_bss<Kmem_alloc_reaper>' /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/kern/kmem_alloc.cpp:309: instantiated from here /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/lib/libk/slist:46: error: initializer specified for non-virtual method 'cxx::S_list<T, P>::S_list(const cxx::S_list<T, P>&) [with T = Kmem_alloc_reaper, POLICY = cxx::Bits::Basic_list_policy<Kmem_alloc_reaper, cxx::S_list_item>]' /home/L4/L4re/l4re-core-2012081219/src/kernel/fiasco/src/lib/libk/slist:47: error: initializer specified for non-virtual method 'void cxx::S_list<T, P>::operator=(const cxx::S_list<T, P>&) [with T = Kmem_alloc_reaper, POLICY = cxx::Bits::Basic_list_policy<Kmem_alloc_reaper, cxx::S_list_item>]' ... Making __assert_fail.o

2 1

Compiling l4re on ubuntu 12.10
by Ali Nehzat 05 Nov '12

05 Nov '12

Hi, Could someone please let me know what the expected dev environment is and which tool chains I should in fact be using? I'm trying to compile L4Re for a pandaboard on a 32-bit stock standard Ubuntu 12.10 dev machine with gcc-arm-linux-gnueabihf installed on it, however during the "make O=<build-path> config" step, after going through the menu config I get a pile of "bash: arm-linux-gcc: command not found" error. Thanks in advance, Ali

2 1

1G memory for L4Linux on Panda
by Владимир Шилкин 01 Nov '12

01 Nov '12

Hello, When allow L4Linux using more than 512M of memory, user level apps execution can cause ‘Segmentation fault’ or glibc error. For example run 'find' command on fresh booted system. We use PandaBoard. To configure system use 1Gb RAM we set in src/l4/mk/platforms/pandaboard.conf PLATFORM_RAM_SIZE_MB = 1024 Best Regards, Vladimir

2 1

how to get Task
by 朱振 01 Nov '12

01 Nov '12

hi, I want to know the memory size that each Task uses,Is there any API can help me to get this ? Thanks

2 1

Page Fault on real hardware
by Wajidali Whowe 31 Oct '12

31 Oct '12

Dear all, I have been trying to run L4linux on a real hardware (x86 PC). Everything seems fine once I try the image with the qemu, however the following error appears on the real hardware: .. .. .. vmlinuz . | main thread will be 413 vmlinuz . | l4x_register_pointer_section: addr = 005e6000 size 929792 vmlinuz . | section-with-init: virt: 0x5e6000 to 0x6c8fff [908KiB] vmlinuz . | section-with-init: virt: .... .. .. .. vmlinuz . | Loading: rom/ramdiskfs.tar.gz vmlinuz . | INITRD: Size of RAMdisk is 32768KiB vmlinuz . | RAMdisk from 188800000 to 1a800000 [32768KiB] vmlinuz . | Page fault (non-resolved): pfa=0 pc=473569 Die message: Trap: 14 vmlinuz . | panic: going to sleep forever, bye Would you please have an idea or a suggestion for this problem? Best Regards

3 7

get memory size each task uses
by 朱振 30 Oct '12

30 Oct '12

hi, I want to know the memory size that each Task uses,Is there any API that can help me to get this ? Thanks

1 0

Re: FOSDEM 2013 - Microkernels / Component-based OSes devroom
by Stefan Kalkowski 30 Oct '12

30 Oct '12

Hi all, apologies for the high cross-posting traffic. I left out the information on how to subscribe to the devroom's mailing list previously: https://lists.fosdem.org/listinfo/microkernel-devroom Please, limit the discussion regarding the devroom's organization, respectively your proposals to the above list instead of replying to all organizations in this mail-header. Thank you in advance Stefan On 29.10.2012 13:01, Stefan Kalkowski wrote: > FOSDEM 2013 - Microkernels / Component-based OSes devroom > *CALL FOR PARTICIPATION* > http://fosdem.org/2013 > > The developers of several free and open-source component- and/or > microkernel-based operating systems will meet at FOSDEM 2013 in > Brussels, Belgium and will share a developer room. > > The devroom is currently looking for content in the form of talks > related to the area of component- and/or microkernel-based operating > systems. Possible topics include, but are not limited to: > > * OS introduction to developers of other OS > * Subsystems and architecture > * Hardware and device drivers > * Tools and languages > * Release engineering and testing > * Experience and learning from mistakes > * Technical challenges > * Community and life with an OS-project > * Academia and education > > Please send your talk proposal(s) no later than by 2012-12-15 to: > > microkernel-devroom at lists.fosdem.org > > Make sure to include the following in your proposal: > > * title of your talk (will be printed in the FOSDEM booklet) > * your full name (will be printed in the FOSDEM booklet) > * a short abstract > * duration of your talk (please, no longer than 45 minutes) > > The final devroom schedule (along with accepted talks) will be announced > on the above mailing list on 2012-12-22. Moreover, the speakers will be > notified via e-mail. The schedule will be also published on the FOSDEM > web and in the FOSDEM booklet after 2013-01-10. > > If you do not want to give a talk yourself, you may still send > suggestions for what else you would like to see, or do in the devroom. > Please send your suggestions to the above mailing list. > > The devroom is scheduled for Saturday of February 2. The seating > capacity of the room is 74 seats. Any changes will be announced in the > above mailing list. > -- Stefan Kalkowski Genode Labs http://www.genode-labs.com/ · http://genode.org/

1 0

FOSDEM 2013 - Microkernels / Component-based OSes devroom
by Stefan Kalkowski 29 Oct '12

29 Oct '12

FOSDEM 2013 - Microkernels / Component-based OSes devroom *CALL FOR PARTICIPATION* http://fosdem.org/2013 The developers of several free and open-source component- and/or microkernel-based operating systems will meet at FOSDEM 2013 in Brussels, Belgium and will share a developer room. The devroom is currently looking for content in the form of talks related to the area of component- and/or microkernel-based operating systems. Possible topics include, but are not limited to: * OS introduction to developers of other OS * Subsystems and architecture * Hardware and device drivers * Tools and languages * Release engineering and testing * Experience and learning from mistakes * Technical challenges * Community and life with an OS-project * Academia and education Please send your talk proposal(s) no later than by 2012-12-15 to: microkernel-devroom at lists.fosdem.org Make sure to include the following in your proposal: * title of your talk (will be printed in the FOSDEM booklet) * your full name (will be printed in the FOSDEM booklet) * a short abstract * duration of your talk (please, no longer than 45 minutes) The final devroom schedule (along with accepted talks) will be announced on the above mailing list on 2012-12-22. Moreover, the speakers will be notified via e-mail. The schedule will be also published on the FOSDEM web and in the FOSDEM booklet after 2013-01-10. If you do not want to give a talk yourself, you may still send suggestions for what else you would like to see, or do in the devroom. Please send your suggestions to the above mailing list. The devroom is scheduled for Saturday of February 2. The seating capacity of the room is 74 seats. Any changes will be announced in the above mailing list.

1 0

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