l4-hackers

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

2827 discussions

[L4LINUX] Is there a loop in revision 32 ?
by Clermont, Nicolas 05 Jul '07

05 Jul '07

Hi everybody, I got a problem with L4Linux but really don't know from where it comes, if I forgot to do something or if there is like a bug in L4Linux..... I have updated my l4 repositories yesterday, switching to L4Linux revision 32 and tudos revision 127. When booting L4Linux with TCP/IP enabled, it blocks after printing "Registered protocol 2". When disabling TCP/IP, it blocks after IDE probe. I have observed the same behavior with revision 31, but didn't have the time at this time to investigate. This time I have tried to find the reason of this loop. I have disabled TCP/IP and tried to see where L4Linux hangs. After IDE probe, L4Linux goes through wait_for_completion(), which calls schedule(), and then loops as need_resched label is always re-invocated. The last thing displayed is the creation of the idler thread... The problem with TCP/IP support enabled is different but maybe related to the same source. the schedule() function is also called, but it completes and so schedule. Then the idler thread is created and noting goes on. I have tried with different configurations, especially with protected I/O and unprotected, but I get always the same behavior. This is the output I get trough the serial line with TCP/IP disabled (l4linux also print on serial) : l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.21-l4 (clermont@L4-dev <mailto:clermont@L4-dev> ) (gcc version 3.4.4 (Gentoo l4lx : 3.4.4-r1, ssp-3.4.4-1.0, pie-8.7.8)) #59 Tue Jul 3 19:21:07 Local tim l4lx : e zone must be set--see zic manu l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (5 args): console=ttyLv0 earlyprintk=yes mem=128M l4lx : root=/dev/hda1 video=l4fb:refreshsleep:200 l4lx | Image: 00400000 - 00681000 [2564 KiB]. l4lx | Areas: Text: 00400000 - 005e6000 [1944kB] (a bit longer) l4lx | Data: 005e6000 - 005f9f7c [79kB] l4lx | Initdata: 005fc000 - 00618260 [112kB] l4lx | BSS: 0061a000 - 0067e840 [402kB] names | 12.02: server_names_register(12.03 -> "l4lx.tamer") l4lx | l4lx_thread_create: Created thread 12.03 (tamer) l4lx | Using tamed mode. ROOT: Sending all ports (for cli/sti) to task #0d l4lx | Got 65536 out of 65536 I/O ports names | 12.02: server_names_register(12.04 -> "l4lx.server") l4lx | l4lx_thread_create: Created thread 12.04 (server) l4lx | main thread will be 12.04 l4lx | l4env_register_pointer_section: addr = 005e6000 size = 634880 l4lx | sec-w-init: virt: 0x005e6000 to 0x00680fff [620 KiB] l4lx | sec-w-init: Number of physical regions: 1, 634880 Bytes l4lx | sec-w-init: 1: Phys: 0x01185000 to 0x01220000, Size: 634880 l4lx | l4env_linux_startup thread 4. l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 128MB l4lx | Got 2048kB of ISA DMA memory. l4lx | ISA DMA memory: virt: 0x00800000 to 0x009fffff [2048 KiB] l4lx | ISA DMA memory: Number of physical regions: 1, 2097152 Bytes l4lx | ISA DMA memory: 1: Phys: 0x0043a000 to 0x0063a000, Size: 2097152 l4lx | Main memory: virt: 0x00c00000 to 0x08bfffff [131072 KiB] l4lx | Main memory: Number of physical regions: 1, 134217728 Bytes l4lx | Main memory: 1: Phys: 0x14400000 to 0x1c400000, Size: 134217728 l4lx | Filling lower ptabs... l4lx | Done (1883 entries). Linux version 2.6.21-l4 (clermont@L4-dev <mailto:clermont@L4-dev> ) (gcc version 3.4.4 (Gentoo 3.4.4-r1, s sp-3.4.4-1.0, pie-8.7.8)) #59 Tue Jul 3 19:21:07 Local time zone must be set--se e zic manu CPU: Vendor unknown, using generic init. CPU: Your system may be unstable. dm_phys: 0000000000c00000 - 0000000008c00000 (usable) dm_phys: 0000000000800000 - 0000000000a00000 (usable) 132MB memory available. Zone PFN ranges: DMA 0 -> 2560 Normal 2560 -> 35840 early_node_map[1] active PFN ranges 0: 0 -> 35840 Allocating PCI resources starting at 10000000 (gap: 00a00000:ff600000) Built 1 zonelists. Total pages: 35560 Kernel command line: console=ttyLv0 earlyprintk=yes mem=128M root=/dev/hda1 vide o=l4fb:refreshsleep:200 Initializing CPU#0 PID hash table entries: 1024 (order: 10, 4096 bytes) Detected 2800.514 MHz processor. Console: colour dummy device 80x25 l4ser_init_ports l4ser: input not enabled! Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Memory: 131700k/143360k available (1539k kernel code, 1344k reserved, 484k data, 112k init, 0k highmem) virtual kernel memory layout: fixmap : 0xffffc000 - 0xfffff000 ( 12 kB) vmalloc : 0x10000000 - 0x18000000 ( 128 MB) lowmem : 0x00000000 - 0x08c00000 ( 140 MB) .init : 0x005fc000 - 0x00618260 ( 112 kB) .data : 0x00580cc4 - 0x005f9f7c ( 484 kB) .text : 0x00400000 - 0x00580cc4 (1539 kB) l4lx_irq_timer_startup(0) names | 12.04: server_names_register(12.05 -> "l4lx.timer.i0") l4lx | l4lx_thread_create: Created thread 12.05 (timer.i0) timer_irq_thread: Starting timer IRQ thread. Calibrating delay using timer specific routine.. 5603.19 BogoMIPS (lpj=28015972) Mount-cache hash table entries: 512 Compat vDSO mapped to 0040e000. CPU: GenuineIntel Intel(R) Pentium(R) 4 CPU 2.80GHz stepping 09 NET: Registered protocol family 16 PCI: Using configuration type 1 Setting up standard PCI resources SCSI subsystem initialized PCI: Probing PCI hardware PCI quirk: region 0400-047f claimed by ICH4 ACPI/GPIO/TCO PCI quirk: region 0480-04bf claimed by ICH4 GPIO PCI: Transparent bridge - 0000:00:1e.0 PCI: Ignore bogus resource 6 [0:0] of 0000:00:02.0 PCI: Bridge: 0000:00:03.0 IO window: a000-afff MEM window: fa000000-fa0fffff PREFETCH window: disabled. PCI: Bridge: 0000:00:1e.0 IO window: b000-bfff MEM window: f8000000-f9ffffff PREFETCH window: 10000000-100fffff io scheduler noop registered Time: tsc clocksource has been installed. io scheduler anticipatory registered (default) io scheduler deadline registered io scheduler cfq registered __ioremap: Requested region at fa180000 [0x400 Bytes] __ioremap: Mapping physaddr fa180000 [0x400 Bytes, fa180000+000400] to 08c00000+ 000000 l4lx | Starting L4FB via DOpE names | 12.04: server_names_register(12.06 -> "l4lx.listener") l4dope | SharedMem(alloc): hl.raw=100000, id=a1, size=96000 l4dope | SharedMem(get_adr): address = 0x200000 names | 12.04: server_names_register(12.07 -> "l4lx.DOpE refre") l4lx | l4lx_thread_create: Created thread 12.07 (DOpE refresher) names | 12.04: server_names_register(12.08 -> "l4lx.L4DOpEinpu") l4lx | l4lx_thread_create: Created thread 12.08 (L4DOpEinput) input: l4input key as /class/input/input0 input: l4input mouse as /class/input/input1 l4fb: DOpE framebuffer at 0x08c05000, size 600k l4fb: mode is 640x480x16, linelength=1280, pages=0 l4fb: directcolor: size=0:5:6:5, shift=0:11:5:0 Console: switching to colour frame buffer device 80x30 l4fb0: l4fb L4 frame buffer device (refresh: 200ms) L4 serial driver l4ser_init_ports l4ser: input not enabled! ttyLv0 at MMIO 0x1 (irq = 0) is a L4 Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx names | 12.04: server_names_register(12.09 -> "l4lx.Idler") l4lx | l4lx_thread_create: Created thread 12.09 (Idler) l4dope | SharedMem(alloc): hl.raw=100000, id=aa, size=280000 l4dope | SharedMem(get_adr): address = 0x800000 Does somebody have a running L4Linux revision 32 ? Is it a known problem, or could it be specific to my configuration, etc ... ? Thanks. -- Nico

2 1

mk/tmpl/inst
by Neal H. Walfield 04 Jul '07

04 Jul '07

mk/tmpl/inst correctly excludes CVS files, however, it does not exclude .svn files, which it ought since the code is now managed under svn. The attached patch corrects this deficiency. Neal Index: mk/tmpl/inst =================================================================== --- mk/tmpl/inst (revision 74) +++ mk/tmpl/inst (working copy) @@ -10,4 +10,4 @@ TARGETDIR="`pwd`" TOINSTALL="MAINTAINER Makefile idl include lib server examples doc ptest" -tar c -C $SRCDIR -f- --exclude=CVS $TOINSTALL | tar xvf - +tar c -C $SRCDIR -f- --exclude=CVS --exclude=.svn $TOINSTALL | tar xvf -

2 1

segment problem
by junioraozhi＠sina.com 03 Jul '07

03 Jul '07

Hi  all I have get the source code of fiasco,l4env,l4linux-2.6.21 via SVN ,and  compiled them succesfully. but when boot the l4linux , it says "the running kernel does not have the segments", "kernel feature missing "and went to jdb console. All my work is under the l4 document Why? thanks ------------------------------------------------------------------- 7月11日《变形金刚》首映电影票开抢了！( http://d1.sina.com.cn/sina/limeng3/mail_zhuiyu/2007/mail_zhuiyu_20070702.ht… ) =================================================================== 注册新浪2G免费邮箱（ http://mail.sina.com.cn/chooseMode.html ）

2 1

Re: l4 on mips
by Antoine.Amirault＠esial.uhp-nancy.fr 02 Jul '07

02 Jul '07

HI. Thanks for your answer. I answer you from another addresse because I'm currently in china and sometimes, gmail is not working well here. I hope you won't receive my 10 previous try ;). If i do that, the error is gone but unfortunately I experience another problem. Is it strange because it seems like syntax errors. It looks like that : make[1]: Entering directory `/home/antoine/Desktop/pistachio-build' ===> src/glue/v4-mips64/asmsyms.cc cd src/glue/v4-mips64/ && /home/antoine/Desktop/NICTA/bin/mips64-elf-gcc -nostdinc -I/home/antoine/Desktop/pistachio-build/include -I/home/antoine/Desktop/pistachio/kernel/include -I/home/antoine/Desktop/NICTA/bin/../lib/gcc/mips64-elf/3.4.4/include -Umips64 -Uvr4181 -Uvr41xx -Uv4 -D__ARCH__=mips64 -D__CPU__=vr4181 -D__PLATFORM__=vr41xx -D__API__=v4 -imacros /home/antoine/Desktop/pistachio-build/config/config.h -imacros /home/antoine/Desktop/pistachio/kernel/include/macros.h -include /home/antoine/Desktop/pistachio/kernel/include/config.h -include /home/antoine/Desktop/pistachio/kernel/include/types.h -fno-rtti -fno-builtin -fomit-frame-pointer -fno-exceptions -Wall -Wno-non-virtual-dtor -Wno-format -Wconversion -O3 -G 0 -mlong64 -mno-abicalls -non_shared -msplit-addresses -EL -march=r4100 -mips3 -mabi=64 -Wa,-mabi=o64 -c /home/antoine/Desktop/pistachio/kernel/src/glue/v4-mips64/asmsyms.cc In file included from /home/antoine/Desktop/pistachio/kernel/include/glue/v4-mips64/space.h:42, from /home/antoine/Desktop/pistachio/kernel/include/api/v4/space.h:36, from /home/antoine/Desktop/pistachio/kernel/include/api/v4/tcb.h:41, from /home/antoine/Desktop/pistachio/kernel/src/glue/v4-mips64/asmsyms.cc:34: /home/antoine/Desktop/pistachio/kernel/include/arch/mips64/pgent.h:277: error: expected unqualified-id before '{' token /home/antoine/Desktop/pistachio/kernel/include/arch/mips64/pgent.h: In member function `void pgent_t::set_entry(space_t*, pgent_t::pgsize_e, void*, word_t, word_t, bool)': /home/antoine/Desktop/pistachio/kernel/include/arch/mips64/pgent.h:293: error: `readable' undeclared (first use this function) /home/antoine/Desktop/pistachio/kernel/include/arch/mips64/pgent.h:293: error: (Each undeclared identifier is reported only once for each function it appears in.) /home/antoine/Desktop/pistachio/kernel/include/arch/mips64/pgent.h:293: error: `writable' undeclared (first use this function) In file included from /home/antoine/Desktop/pistachio/kernel/include/api/v4/tcb.h:674, from /home/antoine/Desktop/pistachio/kernel/src/glue/v4-mips64/asmsyms.cc:34: /home/antoine/Desktop/pistachio/kernel/include/glue/v4-mips64/tcb.h: In member function `void tcb_t::notify(void (*)())': /home/antoine/Desktop/pistachio/kernel/include/glue/v4-mips64/tcb.h:393: error: ISO C++ forbids cast to non-reference type used as lvalue /home/antoine/Desktop/pistachio/kernel/include/glue/v4-mips64/tcb.h: In member function `void tcb_t::notify(void (*)(word_t), word_t)': /home/antoine/Desktop/pistachio/kernel/include/glue/v4-mips64/tcb.h:410: error: ISO C++ forbids cast to non-reference type used as lvalue /home/antoine/Desktop/pistachio/kernel/include/glue/v4-mips64/tcb.h: In member function `void tcb_t::notify(void (*)(word_t, word_t), word_t, word_t)': /home/antoine/Desktop/pistachio/kernel/include/glue/v4-mips64/tcb.h:430: error: ISO C++ forbids cast to non-reference type used as lvalue /home/antoine/Desktop/pistachio/kernel/src/glue/v4-mips64/asmsyms.cc: At global scope: /home/antoine/Desktop/pistachio/kernel/src/glue/v4-mips64/asmsyms.cc:41: warning: invalid access to non-static data member `utcb_t::mr' of NULL object /home/antoine/Desktop/pistachio/kernel/src/glue/v4-mips64/asmsyms.cc:41: warning: (perhaps the `offsetof' macro was used incorrectly) /home/antoine/Desktop/pistachio/kernel/src/glue/v4-mips64/asmsyms.cc:41: warning: invalid access to non-static data member `utcb_t::mr' of NULL object This two warnings are repeated a lot of times, and after ===> src/generic/kmemory.cc cd src/generic/ && /home/antoine/Desktop/NICTA/bin/mips64-elf-gcc -nostdinc -I/home/antoine/Desktop/pistachio-build/include -I/home/antoine/Desktop/pistachio/kernel/include -I/home/antoine/Desktop/NICTA/bin/../lib/gcc/mips64-elf/3.4.4/include -Umips64 -Uvr4181 -Uvr41xx -Uv4 -D__ARCH__=mips64 -D__CPU__=vr4181 -D__PLATFORM__=vr41xx -D__API__=v4 -imacros /home/antoine/Desktop/pistachio-build/config/config.h -imacros /home/antoine/Desktop/pistachio/kernel/include/macros.h -include /home/antoine/Desktop/pistachio/kernel/include/config.h -include /home/antoine/Desktop/pistachio/kernel/include/types.h -fno-rtti -fno-builtin -fomit-frame-pointer -fno-exceptions -Wall -Wno-non-virtual-dtor -Wno-format -Wconversion -O3 -G 0 -mlong64 -mno-abicalls -non_shared -msplit-addresses -EL -march=r4100 -mips3 -mabi=64 -Wa,-mabi=o64 -c /home/antoine/Desktop/pistachio/kernel/src/generic/kmemory.cc In file included from /home/antoine/Desktop/pistachio/kernel/include/arch/mips64/cache.h:38, from /home/antoine/Desktop/pistachio/kernel/include/platform/vr41xx/cache.h:36, from /home/antoine/Desktop/pistachio/kernel/src/generic/kmemory.cc:38: /home/antoine/Desktop/pistachio/kernel/include/arch/mips64/pgent.h:277: error: expected unqualified-id before '{' token /home/antoine/Desktop/pistachio/kernel/include/arch/mips64/pgent.h: In member function `void pgent_t::set_entry(space_t*, pgent_t::pgsize_e, void*, word_t, word_t, bool)': /home/antoine/Desktop/pistachio/kernel/include/arch/mips64/pgent.h:293: error: `readable' undeclared (first use this function) /home/antoine/Desktop/pistachio/kernel/include/arch/mips64/pgent.h:293: error: (Each undeclared identifier is reported only once for each function it appears in.) /home/antoine/Desktop/pistachio/kernel/include/arch/mips64/pgent.h:293: error: `writable' undeclared (first use this function) make[1]: *** [src/generic/kmemory.o] Error 1 make[1]: Leaving directory `/home/antoine/Desktop/pistachio-build' make: *** [all] Error 2 I hope you could help me. I use the CVS Version and a cross compiler taken from the NICTA SIte 2007/7/2, Daniel Potts < danielp(a)ok-labs.com>: Hi Antoine, Sorry for the late reply, I hope you've made progress on this. We believe this is a problem with compiler flags changing in our compiler tools release, compared to those expected by the build system in Pistachio 0.4. Try editing kernel/Mk/Makeconf.mips and change mcpu=r4100 to march=4100, or something similar. Good luck, Daniel On 21/06/2007, at 4:36 PM, Antoine Amirault wrote: > Hi, > I'm student at ESIAL (a French engineering school) currently > doing an internship in Beijing. I have to simulate l4 on a mips > platform with qemu. > > I have downloaded pistachio and mips64-elf-3.4.4 from > http://ertos.nicta.com.au/software/prebuilt/binaries.pml > > When i compile the kernel i obtain the following messages : > > antoine@liama-desktop:~/Desktop/pistachio-0.4-aos/build$ make > make[1]: Entering directory `/home/antoine/Desktop/pistachio- > 0.4-aos/build' > ===> src/glue/v4-mips64/asmsyms.cc > cd src/glue/v4-mips64/ && > /opt/nicta/tools/gcc-3.4.4-glibc-2.3.5/mips64-elf/bin/mips64-elf-gcc > -nostdinc -I/home/antoine/Desktop/pistachio-0.4-aos/build/include > -I/home/antoine/Desktop/pistachio- 0.4-aos/kernel/include > -I/opt/nicta/tools/gcc-3.4.4-glibc-2.3.5/mips64-elf/bin/../lib/gcc/mips64-elf/3.4.4/include -Umips64 -Uvr4181 -Uvr41xx -Uv4 -D__ARCH__=mips64 -D__CPU__=vr4181 -D__PLATFORM__=vr41xx -D__API__=v4 -imacros /home/antoine/Desktop/pistachio- 0.4-aos/build/config/config.h -imacros /home/antoine/Desktop/pistachio-0.4-aos/kernel/include/macros.h -include /home/antoine/Desktop/pistachio-0.4-aos/kernel/include/config.h -include /home/antoine/Desktop/pistachio-0.4-aos /kernel/include/types.h -fno-builtin -fomit-frame-pointer -fno-exceptions -Wall -Wno-format -Wconversion -O3 -G 0 -mlong64 -mno-abicalls -non_shared -msplit-addresses -EL -mcpu=r4100 -mips3 -mabi=64 -Wa,-mabi=o64 -c /home/antoine/Desktop/pistachio- > 0.4-aos/kernel/src/glue/v4-mips64/asmsyms.cc > cc1plus: error: invalid option `cpu=r4100' > ===> src/api/v4/exregs.cc > cd src/api/v4/ && > /opt/nicta/tools/gcc-3.4.4-glibc-2.3.5/mips64-elf/bin/mips64-elf-gcc > -nostdinc -I/home/antoine/Desktop/pistachio- 0.4-aos/build/include > -I/home/antoine/Desktop/pistachio-0.4-aos/kernel/include > -I/opt/nicta/tools/gcc-3.4.4-glibc-2.3.5/mips64-elf/bin/../lib/gcc/mips64-elf/3.4.4/include -Umips64 -Uvr4181 -Uvr41xx -Uv4 -D__ARCH__=mips64 -D__CPU__=vr4181 -D__PLATFORM__=vr41xx -D__API__=v4 -imacros /home/antoine/Desktop/pistachio- 0.4-aos/build/config/config.h -imacros /home/antoine/Desktop/pistachio-0.4-aos/kernel/include/macros.h -include /home/antoine/Desktop/pistachio-0.4-aos/kernel/include/config.h -include /home/antoine/Desktop/pistachio-0.4-aos /kernel/include/types.h -fno-builtin -fomit-frame-pointer -fno-exceptions -Wall -Wno-format -Wconversion -O3 -G 0 -mlong64 -mno-abicalls -non_shared -msplit-addresses -EL -mcpu=r4100 -mips3 -mabi=64 -Wa,-mabi=o64 -c /home/antoine/Desktop/pistachio- > 0.4-aos/kernel/src/api/v4/exregs.cc > cc1plus: error: invalid option `cpu=r4100' > make[1]: *** [src/api/v4/exregs.o] Error 1 > make[1]: Leaving directory > `/home/antoine/Desktop/pistachio-0.4-aos/build' > make: *** [all] Error 2 > > Do you know how to solve this ? > Maybe i should use another compiler. > Thanks for your help > Antoine > > _______________________________________________ > l4-hackers mailing list > l4-hackers(a)os.inf.tu-dresden.de > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

1 0

l4 on mips
by Antoine Amirault 02 Jul '07

02 Jul '07

Hi, I'm student at ESIAL (a French engineering school) currently doing an internship in Beijing. I have to simulate l4 on a mips platform with qemu. I have downloaded pistachio and mips64-elf-3.4.4 from http://ertos.nicta.com.au/software/prebuilt/binaries.pml When i compile the kernel i obtain the following messages : antoine@liama-desktop:~/Desktop/pistachio-0.4-aos/build$ make make[1]: Entering directory `/home/antoine/Desktop/pistachio-0.4-aos/build' ===> src/glue/v4-mips64/asmsyms.cc cd src/glue/v4-mips64/ && /opt/nicta/tools/gcc-3.4.4-glibc-2.3.5/mips64-elf/bin/mips64-elf-gcc -nostdinc -I/home/antoine/Desktop/pistachio-0.4-aos/build/include -I/home/antoine/Desktop/pistachio-0.4-aos/kernel/include -I/opt/nicta/tools/gcc-3.4.4-glibc-2.3.5/mips64-elf/bin/../lib/gcc/mips64-elf/3.4.4/include -Umips64 -Uvr4181 -Uvr41xx -Uv4 -D__ARCH__=mips64 -D__CPU__=vr4181 -D__PLATFORM__=vr41xx -D__API__=v4 -imacros /home/antoine/Desktop/pistachio- 0.4-aos/build/config/config.h -imacros /home/antoine/Desktop/pistachio- 0.4-aos/kernel/include/macros.h -include /home/antoine/Desktop/pistachio- 0.4-aos/kernel/include/config.h -include /home/antoine/Desktop/pistachio- 0.4-aos/kernel/include/types.h -fno-builtin -fomit-frame-pointer -fno-exceptions -Wall -Wno-format -Wconversion -O3 -G 0 -mlong64 -mno-abicalls -non_shared -msplit-addresses -EL -mcpu=r4100 -mips3 -mabi=64 -Wa,-mabi=o64 -c /home/antoine/Desktop/pistachio-0.4-aos /kernel/src/glue/v4-mips64/asmsyms.cc cc1plus: error: invalid option `cpu=r4100' ===> src/api/v4/exregs.cc cd src/api/v4/ && /opt/nicta/tools/gcc-3.4.4-glibc-2.3.5/mips64-elf/bin/mips64-elf-gcc -nostdinc -I/home/antoine/Desktop/pistachio-0.4-aos/build/include -I/home/antoine/Desktop/pistachio-0.4-aos/kernel/include -I/opt/nicta/tools/gcc-3.4.4-glibc-2.3.5/mips64-elf/bin/../lib/gcc/mips64-elf/3.4.4/include -Umips64 -Uvr4181 -Uvr41xx -Uv4 -D__ARCH__=mips64 -D__CPU__=vr4181 -D__PLATFORM__=vr41xx -D__API__=v4 -imacros /home/antoine/Desktop/pistachio- 0.4-aos/build/config/config.h -imacros /home/antoine/Desktop/pistachio- 0.4-aos/kernel/include/macros.h -include /home/antoine/Desktop/pistachio- 0.4-aos/kernel/include/config.h -include /home/antoine/Desktop/pistachio- 0.4-aos/kernel/include/types.h -fno-builtin -fomit-frame-pointer -fno-exceptions -Wall -Wno-format -Wconversion -O3 -G 0 -mlong64 -mno-abicalls -non_shared -msplit-addresses -EL -mcpu=r4100 -mips3 -mabi=64 -Wa,-mabi=o64 -c /home/antoine/Desktop/pistachio-0.4-aos /kernel/src/api/v4/exregs.cc cc1plus: error: invalid option `cpu=r4100' make[1]: *** [src/api/v4/exregs.o] Error 1 make[1]: Leaving directory `/home/antoine/Desktop/pistachio-0.4-aos/build' make: *** [all] Error 2 Do you know how to solve this ? Maybe i should use another compiler. Thanks for your help Antoine

2 1

Fiasco@ARM - supported hardware
by Daniel Vandersee 01 Jul '07

01 Jul '07

Hello, how do you test L4 on an ARM platform? Do you have specific hardware for that purpose? You mentioned that you use ARM Integrator boards. As there are several integrator boards available: which one exactly do you use? Do you use other boards as well? I'm asking because I plan to buy an ARM board which is supported out of the box without the need to modify drivers. Do you additionally use software simulators to test L4? If so, which one do you use? I tried Skyeye to simulate an ARM integrator board as well as a SA1100-board but didn't get any output over the serial line. Qemu doesn't work either and terminates with the following error: "qemu: uncaught target signal 11 (Segmentation fault) - exiting". Kind regards, Daniel

2 5

Installing Generated Header Files
by Neal H. Walfield 01 Jul '07

01 Jul '07

Hi, I'm using BID and generating header files at compile time. I looked at the include role, however, as far as I can tell, it only installs files from the source tree, not from the object tree. The attached patch improves the include role-file to allow this mode of operation. The patch consists of two changes. First, before listing the directory, we change to $(INCSRC_DIR). (This also requires evaluating TARGET_CMD lazily, i.e., using a recursive variable, not a simple one, as INCSRC_DIR may be set later.) Second, an additional target has been added, headers, which can depend on generated header files. I also updated the documentation. The current patch doesn't allow installing header files from both the source directory and the object directory. This might be useful, however, it appears to require modifying the perl code, which I have done my best to forget. Thanks, Neal Index: mk/include.mk =================================================================== --- mk/include.mk (revision 74) +++ mk/include.mk (working copy) @@ -27,9 +27,9 @@ ifeq ($(origin TARGET),undefined) # use POSIX -print here -TARGET_CMD := find . -name '*.[ih]' -print +TARGET_CMD = (cd $(INCSRC_DIR); find . -name '*.[ih]' -print) else -TARGET_CMD := echo $(TARGET) +TARGET_CMD = echo $(TARGET) endif INSTALL_INC_PREFIX ?= l4/$(PKGNAME) INCSRC_DIR ?= $(SRC_DIR) @@ -64,7 +64,9 @@ } \ }' -all:: +headers:: + +all:: headers @$(TARGET_CMD) | $(call installscript,1) install:: Index: doc/bid-spec/spec.tex =================================================================== --- doc/bid-spec/spec.tex (revision 73) +++ doc/bid-spec/spec.tex (working copy) @@ -2274,22 +2274,32 @@ \subsubsection{Purpose} -The purpose of the include role is to install the local include-files -into the local install-tree or into the drops install-tree. The -role-file achieves two goals when managing include-files: +The purpose of the include role is to install all .h and .i under +INCSRC_DIR into the local install-tree or into the drops +install-tree. This role facilitates two goals with respect to managing +include-files: + \begin{enumerate} -\item The path where the include-files are to be found in is entirely +\item The path where the include-files are found is entirely defined by the package name and the target system of the include-files. -\item Once written, the makefile needs not to be modified, even if new - include files are added or old include files are removed from the package. +\item Once written, the make file need not be modified, even when new + include files are added or old include files are removed from the + package. \end{enumerate} The target system of an include file is determined by putting it into -a specific subdirectory. The role-file will install it accordingly -then. The following table defines the subdirectories depending on the -target systems. +a specific subdirectory. The role-file will then install it +accordingly. By default, INCSRC_DIR points is set to the source +directory. To install generated header files, set INCSRC_DIR to +§OBJ_DIR. There is currently no mechanism to exclude header files. +When generating header files, add them to the headers target (which +all depends on). + +The following table defines the subdirectories depending on the target +systems. + \begin{center} \begin{tabular}{|l|l|} \hline

2 1

memory overflow
by Antoine Amirault 29 Jun '07

29 Jun '07

Hi all! I'm trying to run l4 on qemu. I've successfully build the kernel and the user level code. I have followed the guide from l4ka : http://l4ka.org/projects/pistachio/ia32/gettingstarted.php and everything is running well except some little thing but i think it doesn't matter (like problem when unmounting,...). but whem i run qemu with qemu -fda fdimage.img, i got this message : Memory descriptor overflow (max=200, n=200) --- "KD# memdesc overflow" --- ---------------------------------------------9eip=f0102358, esp=f010ee400 --- then everything is locked> Do you know how i can solve that? Thanks. Antoine

1 0

How can Minix 3 be so small
by Hendrik Tews 27 Jun '07

27 Jun '07

Hi, I just noticed that the Minix 3 kernel is under 4000 lines. I couldn't easily find numbers for Pistachio, but I guess it is comparable to Fiasco, which is about 15.000 lines (without the kernel debugger). Could anybody explain why Fiasco is so big in comparison with Minix 3? From the difference in size I would expect that there is an essential difference in the feature set between Minix 3 and Fiasco. Or are the Minix lines just four times longer on average? Bye, Hendrik

8 8

RE: How can Minix 3 be so small
by Clermont, Nicolas 26 Jun '07

26 Jun '07

I have noticed that Minix3 only support one architecture (x86), and doesn't offers something like a HAL. Maybe this is one reason. -----Message d'origine----- De : l4-hackers-bounces(a)os.inf.tu-dresden.de [mailto:l4-hackers-bounces@os.inf.tu-dresden.de] De la part de Hendrik Tews Envoyé : mardi 26 juin 2007 17:13 À : l4-hackers(a)os.inf.tu-dresden.de Objet : How can Minix 3 be so small Hi, I just noticed that the Minix 3 kernel is under 4000 lines. I couldn't easily find numbers for Pistachio, but I guess it is comparable to Fiasco, which is about 15.000 lines (without the kernel debugger). Could anybody explain why Fiasco is so big in comparison with Minix 3? From the difference in size I would expect that there is an essential difference in the feature set between Minix 3 and Fiasco. Or are the Minix lines just four times longer on average? Bye, Hendrik _______________________________________________ l4-hackers mailing list l4-hackers(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

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