l4-hackers

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

2 participants
2880 discussions

doperun
by sbrobson＠fastmail.fm 20 Dec '04

20 Dec '04

Hi Excuse my ignorance, but can anyone please tell me whats happened to doperun. Does it no longer form part of the cvs download? What should I use instead? steve -- sbrobson(a)fastmail.fm

2 1

l4/pkg compile problem
by sbrobson＠fastmail.fm 20 Dec '04

20 Dec '04

Hi all. Using a cvs version downloaded over the weekend (which includes the libc_backends_l4env package), I get the following error when compiling the l4/pkg directory. ... Compiling net/sched/sch_generic.o LD_PRELOAD=/root/DROPS/l4/tool/gendep/libgendep.so GENDEP_TARGET=net/sched/sch_generic.o GENDEP_BINARY=cc1 gcc -c -D__KERNEL__ - DDDE_LINUX -DHZ=100 -DRAM_BASE=0x0 -DSYSTEM_x86_586_l4v2 -DARCH_x86 -DCPUTYPE_586 -DL4API_l4v2 -I../../../../server/lib-linux/include - I../../../../server/include -I../../../../../../include/x86/l4/dde_linux -I/root/DROPS/drops/include/x86/l4/dde_linux -I/root/DROPS/ l4linux-2.4/include -I../../../../idl/OBJ-x86-l4v2 -I../../../../../../include/x86/l4v2 -I/root/DROPS/drops/include/x86/l4v2 - I../../../../../../include/l4v2 -I/root/DROPS/drops/include/l4v2 -I../../../../../../include/x86 -I/root/DROPS/drops/include/x86 - I../../../../../../include -I/root/DROPS/drops/include -nostdinc -DOSKIT -I../../../../../../../oskit10 -I../../../../../../../oskit10/ oskit/c -I/root/DROPS/drops/include/oskit10 -I/root/DROPS/drops/include/oskit10/oskit/c -I/usr/lib/gcc-lib/i486-linux/3.3.4/include - ffunction-sections -gstabs+ -g -O2 -fno-strict-aliasing -march=i586 -Wall -Wstrict-prototypes /root/DROPS/l4linux-2.4/net/sched/ sch_generic.c -o net/sched/sch_generic.o/root/DROPS/l4linux-2.4/net/sched/sch_generic.c: In function `dev_activate': /root/DROPS/l4linux-2.4/net/sched/sch_generic.c:458: warning: passing arg 2 of `list_add_tail' from incompatible pointer type /root/DROPS/l4linux-2.4/net/sched/sch_generic.c: In function `dev_init_scheduler': /root/DROPS/l4linux-2.4/net/sched/sch_generic.c:504: error: request for member `next' in something not a structure or union /root/DROPS/l4linux-2.4/net/sched/sch_generic.c:504: error: request for member `prev' in something not a structure or union /root/DROPS/l4linux-2.4/net/sched/sch_generic.c: In function `dev_shutdown': /root/DROPS/l4linux-2.4/net/sched/sch_generic.c:526: warning: passing arg 1 of `list_empty' from incompatible pointer type make[5]: *** [net/sched/sch_generic.o] Error 1 make[5]: Leaving directory `/root/DROPS/l4/pkg/flips/server/lib-linux/src/OBJ-x86_586-l4v2' make[4]: *** [OBJ-x86_586-l4v2] Error 2 make[4]: Leaving directory `/root/DROPS/l4/pkg/flips/server/lib-linux/src' make[3]: *** [src] Error 2 make[3]: Leaving directory `/root/DROPS/l4/pkg/flips/server/lib-linux' make[2]: *** [lib-linux] Error 2 make[2]: Leaving directory `/root/DROPS/l4/pkg/flips/server' make[1]: *** [server] Error 2 make[1]: Leaving directory `/root/DROPS/l4/pkg/flips' make: *** [flips.bin] Error 2 I am able to compile l4/pkg by removing flips, but thought I would bring it to everyones attention. steve -- sbrobson(a)fastmail.fm

2 1

l4 compile problem
by sbrobson＠fastmail.fm 17 Dec '04

17 Dec '04

Hi all. I downloaded the latest cvs version (wednesday Dec 15), but when I run make in the l4 directory I get the following error: make[5]: Entering directory `/root/DROPS/l4/pkg/l4vfs/lib/libc_backends/io/OBJ-x86_586-l4v2' ... Compiling mmap_normal.o LD_PRELOAD=/root/DROPS/l4/tool/gendep/libgendep.so GENDEP_TARGET=mmap_normal.o GENDEP_BINARY=cc1 gcc -c -DRAM_BASE=0x0 -DSYSTEM_x86_586_l4v2 -DARCH_x86 -DCPUTYPE_586 -DL4API_l4v2 -I../../../../idl/OBJ-x86-l4v2 -I../../../../../../include/x86/l4v2 -I/root/DROPS/drops/include/x86/l4v2 -I../../../../../../include/l4v2 -I/root/DROPS/drops/include/l4v2 -I../../../../../../include/x86 -I/root/DROPS/drops/include/x86 -I../../../../../../include -I/root/DROPS/drops/include -nostdinc -I../../../../../../include/dietlibc -I/root/DROPS/drops/include/dietlibc -I/usr/lib/gcc-lib/i486-linux/3.3.4/include -ffunction-sections -gstabs+ -g -O2 -fno-strict-aliasing -march=i586 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations /root/DROPS/l4/pkg/l4vfs/lib/libc_backends/io/mmap_normal.c -o mmap_normal.o /root/DROPS/l4/pkg/l4vfs/lib/libc_backends/io/mmap_normal.c:24:40: l4/libc_backends/mmap_util.h: No such file or directory /root/DROPS/l4/pkg/l4vfs/lib/libc_backends/io/mmap_normal.c:37: warning: `struct ds2server' declared inside parameter list /root/DROPS/l4/pkg/l4vfs/lib/libc_backends/io/mmap_normal.c:37: warning: its scope is only this definition or declaration, which is probably not what you want /root/DROPS/l4/pkg/l4vfs/lib/libc_backends/io/mmap_normal.c: In function `mmap_normal': /root/DROPS/l4/pkg/l4vfs/lib/libc_backends/io/mmap_normal.c:160: warning: implicit declaration of function `add_ds2server' /root/DROPS/l4/pkg/l4vfs/lib/libc_backends/io/mmap_normal.c: In function `msync': /root/DROPS/l4/pkg/l4vfs/lib/libc_backends/io/mmap_normal.c:189: warning: implicit declaration of function `get_ds2server' /root/DROPS/l4/pkg/l4vfs/lib/libc_backends/io/mmap_normal.c:189: warning: assignment makes pointer from integer without a cast /root/DROPS/l4/pkg/l4vfs/lib/libc_backends/io/mmap_normal.c:198: error: dereferencing pointer to incomplete type /root/DROPS/l4/pkg/l4vfs/lib/libc_backends/io/mmap_normal.c: At top level: /root/DROPS/l4/pkg/l4vfs/lib/libc_backends/io/mmap_normal.c:209: warning: `struct ds2server' declared inside parameter list /root/DROPS/l4/pkg/l4vfs/lib/libc_backends/io/mmap_normal.c:210: error: conflicting types for `munmap_normal' /root/DROPS/l4/pkg/l4vfs/lib/libc_backends/io/mmap_normal.c:37: error: previous declaration of `munmap_normal' /root/DROPS/l4/pkg/l4vfs/lib/libc_backends/io/mmap_normal.c: In function `munmap_normal': /root/DROPS/l4/pkg/l4vfs/lib/libc_backends/io/mmap_normal.c:235: error: dereferencing pointer to incomplete type /root/DROPS/l4/pkg/l4vfs/lib/libc_backends/io/mmap_normal.c:239: warning: implicit declaration of function `del_ds2server' /root/DROPS/l4/pkg/l4vfs/lib/libc_backends/io/mmap_normal.c:239: error: dereferencing pointer to incomplete type make[5]: *** [mmap_normal.o] Error 1 make[5]: Leaving directory `/root/DROPS/l4/pkg/l4vfs/lib/libc_backends/io/OBJ-x86_586-l4v2' make[4]: *** [OBJ-x86_586-l4v2] Error 2 make[4]: Leaving directory `/root/DROPS/l4/pkg/l4vfs/lib/libc_backends/io' make[3]: *** [io] Error 2 make[3]: Leaving directory `/root/DROPS/l4/pkg/l4vfs/lib/libc_backends' make[2]: *** [libc_backends] Error 2 make[2]: Leaving directory `/root/DROPS/l4/pkg/l4vfs/lib' make[1]: *** [lib] Error 2 make[1]: Leaving directory `/root/DROPS/l4/pkg/l4vfs' make: *** [l4vfs.lib] Error 2 It complains that it can't find mmap_util.h, which does't seem to exist anywhere. Any suggestions? Thanx Steve. -- sbrobson(a)fastmail.fm

2 1

L4Linux 2.4 IRQ problem
by Carsten Weinhold 15 Dec '04

15 Dec '04

Hi all! I'm trying to get L4Linux 2.4 running. It starts to boot, but then it runs into trouble attaching to interrupts: -------------------------------- ... l4lx_irq_dev_startup: Starting IRQ thread for IRQ 5. l4lx | l4lx_thread_create: Created thread 0f.11 (IRQ5) l4lx_irq_dev_startup: Starting IRQ thread for IRQ 4. l4lx | l4lx_thread_create: Created thread 0f.12 (IRQ4) l4lx_irq_dev_startup: Starting IRQ thread for IRQ 3. l4lx | l4lx_thread_create: Created thread 0f.13 (IRQ3) l4lx_irq_dev_startup: Starting IRQ thread for IRQ 2. l4lx | l4lx_thread_create: Created thread 0f.14 (IRQ2) hda: ST317221A, ATA DISK drive hda: IRQ probe failed (0xfffc) hdb: IRQ probe failed (0xfffc) hdb: IRQ probe failed (0xfffc) hdc: IRQ probe failed (0xfffc) acquire_irq: Error attaching to IRQ 1 ---------------------------------- After these messages L4Linux enters Fiasco's kernel debugger (thread f.06). There seem to be 2 problems, the first one is that L4Linux has difficulties accessing the IDE controller. The second is related to IRQ 1. This happens on two different machines, so it's probably a configuration issue. However, I don't know where to start in order to fix this. Greetings, Carsten ------------- menu.lst entry used to boot L4Linux --------------- title L4Linux-2.4 on L4Env kernel $(P)/rmgr -sigma0 task modname "L4Linux task" modaddr 0x02000000 module $(P)/main -nowait -nokdb -serial_esc -comspeed 115200 -comport 1 module $(P)/sigma0 module $(P)/names module $(P)/log module $(P)/dm_phys module $(P)/rtc module $(P)/simple_ts -t 300 module $(P)/l4io --noirq #module $(P)/con --l4io module $(P)/tftp -i module $(P)/l4exec module $(P)/loader $(P)/l4linux.l4env #vbeset $(VBE_MODE) ------------- loader config file for L4Linux --------------- task "l4linux.l4env" "l4irqack=linux mem=256M no-scroll root=/dev/hda3 l4env_rd=$(P)/drops.rd" priority 0xA0

1 0

L4 come together at 21C3 in Berlin?
by Michael Engel 10 Dec '04

10 Dec '04

Hi, I just browsed through the 21C3 conference program - http://www.ccc.de/congress/2004/fahrplan-preview/fahrplan.html - and saw that at least some of the people involved in L4 development will be in Berlin (and, the better, give interesting talks). So, this is a good excuse to attend 21C3 (and let the University pay for it :-)) - are there eventually more L4 hackers attending the congress? Perhaps we could organize something like a BoF session... Btw., does anyone have a proposal for an inexpensive place to stay in Berlin from the 27th to the 30th of December? regards, Michael

2 1

Beta release of Kenge, Iguana, Wombat
by Gernot Heiser 29 Nov '04

29 Nov '04

[ Sorry, wrong URLs in original posting, this is what happens if people randomly revoke domain delegations from you... ] National ICT Australia is pleased to announce the release of version 0.4 of the first stage of its Embedded Systems Framework for beta testing. The software is fairly stable and in use in several commercial settings. However, no performance tuning has been done to date. This will be done for the 1.0 release, which is planned for February 2005. The present release consists of the following components: - Kenge, a support environment for L4-based systems LICENSE: OZPLA (BSD-like) URL: http://www.disy.cse.unsw.edu.au/Software/Kenge - Iguana, a lightweight L4-based OS personality for embedded systems, providing basic services, resource and protection management LICENSE: OZPLA (BSD-like) URL: http://www.disy.cse.unsw.edu.au/Software/Iguana - Wombat, an architecture-independent Linux server for L4/Iguana, aimed at embedded systems use LICENSE: GPL URL: http://www.disy.cse.unsw.edu.au/Software/Wombat The software presently runs on x86 and ARM platforms, a beta-version for MIPS will follow shortly and further ports are underway. An experimental version of L4Ka::Pistachio is required to run the software, this is included. Driver support is limited at present, but more will be available soon. ARCHITECTURE-SPECIFIC NOTES: - x86: - runs on PC hardware and Qemu simulator - Wombat runs the Linux Test Project with the exception of system calls using the presently unimplemented valloc functionality. - ARM: - runs on a number of ARM7 and ARM9 platforms as well as the Skyeye simulator -- Gernot Heiser Program Leader Professor of Operating Systems Embedded, Real-Time, and Operating Systems University of New South Wales National ICT Australia (NICTA) http://gernot.web.cse.unsw.edu.au http://nicta.com.au/ertos.html Phone: +61 2 9385 5156 Fax: +61 2 9385 7942

1 0

Beta release of Kenge, Iguana, Wombat
by Gernot Heiser 29 Nov '04

29 Nov '04

National ICT Australia is pleased to announce the release of version 0.4 of the first stage of its Embedded Systems Framework for beta testing. The software is fairly stable and in use in several commercial settings. However, no performance tuning has been done to date. This will be done for the 1.0 release, which is planned for February 2005. The present release consists of the following components: - Kenge, a support environment for L4-based systems LICENSE: OZPLA (BSD-like) URL: http://disy.cse.unsw.edu.au/Software/Kenge - Iguana, a lightweight L4-based OS personality for embedded systems, providing basic services, resource and protection management LICENSE: OZPLA (BSD-like) URL: http://disy.cse.unsw.edu.au/Software/Iguana - Wombat, an architecture-independent Linux server for L4/Iguana, aimed at embedded systems use LICENSE: GPL URL: http://disy.cse.unsw.edu.au/Software/Wombat The software presently runs on x86 and ARM platforms, a beta-version for MIPS will follow shortly and further ports are underway. An experimental version of L4Ka::Pistachio is required to run the software, this is available from http://ertos.nicta.com.au/Software/L4. Driver support is limited at present, but more will be available soon. ARCHITECTURE-SPECIFIC NOTES: - x86: - runs on PC hardware and Qemu simulator - Wombat runs the Linux Test Project with the exception of system calls using the presently unimplemented valloc functionality. - ARM: - runs on a number of ARM7 and ARM9 platforms as well as the Skyeye simulator -- Gernot Heiser Program Leader Professor of Operating Systems Embedded, Real-Time, and Operating Systems University of New South Wales National ICT Australia (NICTA) http://gernot.web.cse.unsw.edu.au http://nicta.com.au/ertos.html Phone: +61 2 9385 5156 Fax: +61 2 9385 7942

1 0

Various questions
by Mattia Belletti 19 Nov '04

19 Nov '04

Hi all - I have some questions; I hope they have not already been posed! - I'm running a bare qemu + pistachio 0.4, and its kickstart + sigma0, with a little root server of my own, on a IA32 architecture. I ask for bootinfo location, and I find it's 0x1000 (that's where kickstart puts it, so it's ok). However, when I try accessing it, I obviously pagefault, but sigma0 refuses to give me that page. Anyway, if I _force_ it it to do (I've tweaked by hand source code), everything works fine - in fact the bootinfo is there, and it is correct. Did I get something wrong? - Little note: looking kickstart, I found this, around user/util/kickstart/mbi-loader.cc:486: if (use_bootinfo) { // Allocate and initialize a bootinfo structure. bi = init_bootinfo (&kip); rec = (L4_BootRec_t *) ((L4_Word_t) bi + bi->size); if (bi) // Record MBI modules rec = record_bootinfo_modules (bi, rec); else use_bootinfo = false; } (I'm referring to CVS version, If I remember well 0.4 version was exactly the same). The "rec = stuff" isn't wrong? If "bi" is set to NULL by the init_bootinfo (in case of OOM, if I remember well), this segfaults - well, don't know what it does exactly, since there's still no kernel around, and I don't remember IA32 defaults ;D - Looking L4 specs (even the latest - by the way, how come the sources theirselves aren't published? I would have found it useful when I did those searches about sigma0 ;D), I have found no satisfying explanation about the kinds of memory descriptors L4 knows about. That is, UndefinedMemoryType, BootLoaderSpecificMemoryType, ArchitectureSpecificMemoryType are obvious, but what are the differences between ConventionalMemoryType and SharedMemoryType? What between ReservedMemoryType and DedicatedMemoryType? What are their exact meanings? Not that I absolutely need to work this out now, but I would like to know this better! :-) - Last: what purpose sigma1 has? I remember reading something about it in the papers about transparent checkouts of kernel state, and stuff like that... Thank you all for the attention! :-) -- Mat/tia Belletti - Undergraduate student @ cs.unibo.it ICQ: 33292311 - email: mbellett(a)cs.unibo.it IRC: RedGlow - site(s): http://mbellett.web.cs.unibo.it/ Jabber: RedGlow - Linux registered user 299762 @ machine 213003

4 3

Stack Pointers for Exception Modes
by Wolfgang Johann BETZ 15 Nov '04

15 Nov '04

Hello, during my study of the bootstrap sequence of the L4/Arm source codes I have come to the following question: On which stacks get the exception handlers for exceptions like "fast interrupt" and "undefined instruction" executed and where in the sources get the (banked) stack pointers for these modes initialized? Thanks, Wolfgang

1 0

Various questions
by Mattia Belletti 11 Nov '04

11 Nov '04

I try to send this message again, since it seems it has not been posted: Hi all - I have some questions; I hope they have not already been posed! - I'm running a bare qemu + pistachio 0.4, and its kickstart + sigma0, with a little root server of my own, on a IA32 architecture. I ask for bootinfo location, and I find it's 0x1000 (that's where kickstart puts it, so it's ok). However, when I try accessing it, I obviously pagefault, but sigma0 refuses to give me that page. Anyway, if I _force_ it it to do (I've tweaked by hand source code), everything works fine - in fact the bootinfo is there, and it is correct. Did I get something wrong? - Little note: looking kickstart, I found this, around user/util/kickstart/mbi-loader.cc:486: if (use_bootinfo) { // Allocate and initialize a bootinfo structure. bi = init_bootinfo (&kip); rec = (L4_BootRec_t *) ((L4_Word_t) bi + bi->size); if (bi) // Record MBI modules rec = record_bootinfo_modules (bi, rec); else use_bootinfo = false; } (I'm referring to CVS version, If I remember well 0.4 version was exactly the same). The "rec = stuff" isn't wrong? If "bi" is set to NULL by the init_bootinfo (in case of OOM, if I remember well), this segfaults - well, don't know what it does exactly, since there's still no kernel around, and I don't remember IA32 defaults ;D - Looking L4 specs (even the latest - by the way, how come the sources theirselves aren't published? I would have found it useful when I did those searches about sigma0 ;D), I have found no satisfying explanation about the kinds of memory descriptors L4 knows about. That is, UndefinedMemoryType, BootLoaderSpecificMemoryType, ArchitectureSpecificMemoryType are obvious, but what are the differences between ConventionalMemoryType and SharedMemoryType? What between ReservedMemoryType and DedicatedMemoryType? What are their exact meanings? Not that I absolutely need to work this out now, but I would like to know this better! :-) - Last: what purpose sigma1 has? I remember reading something about it in the papers about transparent checkouts of kernel state, and stuff like that... Thank you all for the attention! :-) -- Mat/tia Belletti - Undergraduate student @ cs.unibo.it ICQ: 33292311 - email: mbellett(a)cs.unibo.it IRC: RedGlow - site(s): http://mbellett.web.cs.unibo.it/ Jabber: RedGlow - Linux registered user 299762 @ machine 213003

1 0

Jump to page:

2025

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