- l4-hackers - example.com Site

doxygen?!
by Flonai＠gmx.de 18 Apr '03

18 Apr '03

when i try to compile the the hello server by typing make hello in the l4 building dir, i got an error because i haven't installed doxygen. the problem is that i want to compile fiasco from an linux from scratch system and then using the l4linux microkernel. but doxygen needs xfree and some other progs and i do not want to compile it at this time course i am in an chroot environment with no other linux kernel. i heard doxygen is only need to build documantation files and i do not need them. so is there a way to change one/some makefiles to exclude doxygen. i used the cvs-reposetory (l4,oskit,and then linux22) modules from April 02. -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage!

2 1

Problem compiling Logserver
by Rudolf Weber 18 Apr '03

18 Apr '03

Hello, I miss a l4/env/errno.h when I try to compile the logserver in l4/pkg/log. I'm using the l4v2-API on i586 May this different on the remote cvs ? Greeting Rudolf Weber ... Compiling logserver.o LD_PRELOAD= GENDEP_TARGET=logserver.o GENDEP_BINARY=cpp0 gcc -c -D__USE_L4WQLOCKS__ -D__L4__ -DSYSTEM_x86_586_l4v2 -DARCH_x86 -DCPUTYPE_586 -DL4API_l4v2 -I../../../server/include -I../../../lib/include -I../../../../../include/x86/l4v2 -I/home/rw/l4/current/include/x86/l4v2 -I../../../../../include/x86 -I/home/rw/l4/current/include/x86 -I../../../../../include -I/home/rw/l4/current/include -nostdinc -I../../../../../../oskit10 -I../../../../../../oskit10/oskit/c -I/home/rw/l4/current/include -I/home/rw/l4/current/include/oskit/c -I/usr/lib/gcc-lib/i386-redhat-linux/3.2//include -g -O2 -march=i586 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations ../../../lib/src/logserver.c -o logserver.o ../../../lib/src/logserver.c:17:26: l4/env/errno.h: No such file or directory ../../../lib/src/logserver.c: In function `LOG_channel_open': ../../../lib/src/logserver.c:161: `L4_ENOMEM' undeclared (first use in this function) ../../../lib/src/logserver.c:161: (Each undeclared identifier is reported only once ../../../lib/src/logserver.c:161: for each function it appears in.) ../../../lib/src/logserver.c:162: `L4_ENOTFOUND' undeclared (first use in this function) ../../../lib/src/logserver.c: In function `LOG_channel_write': ../../../lib/src/logserver.c:204: `L4_EIPC' undeclared (first use in this function) ../../../lib/src/logserver.c: In function `LOG_channel_flush': ../../../lib/src/logserver.c:230: `L4_EIPC' undeclared (first use in this function) ../../../lib/src/logserver.c: In function `LOG_channel_close': ../../../lib/src/logserver.c:256: `L4_EIPC' undeclared (first use in this function) -- -- --------------------------------------------------------------- Rudolf Weber http://www.infnet.verein.de/~rw E-Mail: rfweber(a)tesionmail.de

3 2

x2
by Igor Shmukler 08 Apr '03

08 Apr '03

on page 57. lipc conditions - use when it's clear that destination thread runs on the same CPU. does this mean scheduler will traverse the per CPU queue and look for idle destination thread?

1 0

RE: L4 on iPAQ
by Volkmar Uhlig 04 Apr '03

04 Apr '03

> I'm trying to install L4 on the iPAQ (3870). > So far, my iPAQ has the "bootldr" bootloader and Linux installed. > I tried to load the precompiled hazelnut rc2 evaluation suite > for the brutus > evaluation board over serial cable to ram (to address > 0xC1000000) und jumped > to this address (as Volkmar described in nov 2002 on this list). > This didn't work. The iPAQ wrote some digits on the serial > line and crashed. > Has anyone who sucessfully installed L4 on the iPAQ some hints for me? > Must I compile my own custom L4 for the iPAQ? > Or must I use angelboot (I didn't find docs about it in google)? You have to compile your own version of Hazelnut specifically for the iPaq. The Brutus board is not compatible (the memory layout is different). - Volkmar

2 1

L4 on iPAQ
by Dominik Gummel 02 Apr '03

02 Apr '03

Hello, I'm trying to install L4 on the iPAQ (3870). So far, my iPAQ has the "bootldr" bootloader and Linux installed. I tried to load the precompiled hazelnut rc2 evaluation suite for the brutus evaluation board over serial cable to ram (to address 0xC1000000) und jumped to this address (as Volkmar described in nov 2002 on this list). This didn't work. The iPAQ wrote some digits on the serial line and crashed. Has anyone who sucessfully installed L4 on the iPAQ some hints for me? Must I compile my own custom L4 for the iPAQ? Or must I use angelboot (I didn't find docs about it in google)? We need L4 on the iPAQ because we are going to port PERSEUS to it. My part will be the port of Linux 2.4 to L4/ARM (it will be my master thesis). Thanks & Regards, Dominik -- Universität des Saarlandes Department for Computer Science, Cryptography and Security Dominik Gummel email: bofh(a)krypt.cs.uni-sb.de Building 45, Room 536 Im Stadtwald,D-66123 Saarbrücken Tel.: +49(681)302-5608 Fax.: +49(681)302 4631 Fu 0172-6916265 public key http://www-krypt.cs.uni-sb.de/~bofh Fingerprint 5057 7FD9 A0DB 5B92 F1A2 46C1 0070 6200 AAE1 98A9

1 0

Fiasco 1.0 released
by Udo A. Steinberg 01 Apr '03

01 Apr '03

Hello L4 hackers, The Fiasco Team is pleased to announce Fiasco version 1.0, the first official release of the Fiasco L4 microkernel developed at the University of Technology, Dresden. Fiasco currently supports Intel and AMD IA-32 processors (i486 and higher) and implements both version 2 and version X.0 of the L4 interface, as well as several other features such as I/O flexpages and small address spaces. Also included in this release are JDB, the powerful Fiasco kernel debugger, and Fiasco-UX, a user-mode port of Fiasco to the Linux system call interface. For further information please visit the Fiasco homepage at: http://os.inf.tu-dresden.de/fiasco/ Udo Steinberg Operating Systems Group University of Technology Dresden, Germany

1 0

Re: problems running hello in fiasco
by Fabian Sturm 01 Apr '03

01 Apr '03

Hello! Thanks for the reply and sorry that I have to write from a different account but my link to the host in germany seems to be down since two days now. > On Wed Mar 26, 2003 at 07:38:33 +0100, Fabian Sturm wrote: > > > When I then boot into it I see some messages of the RMGR but > > then the system is frozen. > > > > Maybe someone knows what I should try next to track this down? > > Which version of GRUB are you using? Is it "our" version from CVS? Hmm I just took the newest from apha.gnu.org 0.93. I read that you have an own but I thought that is only needed if you have overlapping modules. > How did you configure Fiasco? Could you supply your configuration > (globalconfig.out)!? Sure. I followed the manual and did a make menuconfig in the build directory. I now also tried with the assertions compiled in but none gets triggered so far. Thansk a lot, Fabian # # Automatically generated, don't edit # # Generated on: californium # At: Wed, 26 Mar 2003 02:30:06 +0000 # Linux version 2.4.20 (root@californium) (gcc version 2.95.4 20011002 (Debian p rerelease)) #13 Thu Dec 5 19:48:30 EST 2002 # # Main menu # # # Compiler # CONFIG_USE_GCC=y CONFIG_USE_GCC_3_X=n # # Target Architectures # # # Target platform # CONFIG_IA32=y CONFIG_IA64=n CONFIG_ARM=n CONFIG_UX=n # # Kernel ABI Version # CONFIG_ABI_V2=y CONFIG_ABI_X0=n # # Target processor # CONFIG_IA32_586=y CONFIG_IA32_686=n CONFIG_IA32_K6=n CONFIG_IA32_K6_2=n CONFIG_IA32_K6_3=n CONFIG_ASSEMBLER_IPC_SHORTCUT=y CONFIG_SCHED_RTC=y CONFIG_SLOW_RTC=n CONFIG_DECEIT_BIT_DISABLES_SWITCH=n CONFIG_DISABLE_AUTO_SWITCH=n CONFIG_APIC_MASK=n CONFIG_POWERSAVE_GETCHAR=y CONFIG_X2_LIKE_SYS_CALLS=n CONFIG_SYNC_TSC=n CONFIG_SMALL_SPACES=n # # Kernel Debugging # CONFIG_INLINE=y CONFIG_NDEBUG=y CONFIG_PROFILE=n CONFIG_NO_FRAME_PTR=n CONFIG_KDB=y CONFIG_JDB=y CONFIG_JDB_LOGGING=n CONFIG_MAINTAINER_MODE=n # # Derived symbols # CONFIG_ABI="v2" CONFIG_IA32_TARGET="Intel Pentium" CONFIG_XARCH="ia32" CONFIG_SCHED_PIT=n # # That's all, folks!

4 8

DROPS Konsole
by Daniel Koch 31 Mar '03

31 Mar '03

Hi, finally I managed to get l4linux running without overlapping modules, thanks for the help ! Now I d like to install a Drops console with a con_server, but I don t know where I can download the necessary files. Im also interested in DOpE... id appreciate it if anyone can tell me where to download the files. Daniel

2 1

problems running hello in fiasco
by Fabian Sturm 26 Mar '03

26 Mar '03

Hello! I have a problem running the hello world example on fiasco. I downloaded the latest CVS version from 25.4 of fiasco and compiled it like it is described on the web. Except that the sigma0/rmgr binaries were in l4/bin/x86_586/l4v2 and not directly in l4/bin as described. I then created the following grub entry: title Fiasco, hello world root (hd0,4) kernel=/fiasco/rmgr -sigma0 module=/fiasco/main -nokdb module=/fiasco/sigma0 module=/fiasco/hello When I then boot into it I see some messages of the RMGR but then the system is frozen. Maybe someone knows what I should try next to track this down? Thanks a lot, Fabian Sturm My system is a P3 800Mhz 256MB ram notebook with the Intel i815 chipset. (Vaio vx88) The build environment was Debian Linux 3.0 with gcc 2.95.4. The boot messages were: RMGR: Loading /fiasco/sigma0 RMGR: Loading Kernel fiasco main -nokdb RMGR: check_l4_version 0x00300000 to 0x0044a244 RMGR: detected new_style DD-L4(v2)/Fiasco RMGR: configuring s0: (0x00070000, 0x00096000), start: 0x00070000 RMGR: reserve modules memory range: 0x00200000 to 0x0021053c RMGR: starting kernel /fiasco/main -nokdb proto=0x101ba0 @ 0x00300220 Booting kernel image at 0x302000 entry 0xf0001000 Enabling fully serial nested mode for pic Using the RTC on IRQ 8 (1khz) for scheduling (I hope I don't have introduced errors while copying that down)

2 1

Re: Problem compiling fiasco-ux: ld: entry.o: bad symbol index: 845556
by Udo A. Steinberg 24 Mar '03

24 Mar '03

On 24 Mar 2003 20:58:50 +0100 Rudolf Weber (RW) wrote: RW> Thank you very much, RW> anbei der readelf-output 4udo und das erzeugte entry.o für die echten RW> Programmierer ... RW> Relocation section '.rel.text' at offset 0x10d0 contains 13 entries: RW> Offset Info Type Sym.Value Sym. Name RW> 0000011b 00004101 R_386_32 00000000 base_trap_handler RW> 00000141 00004202 R_386_PC32 00000000 trap_dump_panic RW> 00000150 00004301 R_386_32 00000000 PAGE_FAULT_ADDR RW> 00000179 00004402 R_386_PC32 00000000 thread_page_fault RW> 000001cc 00004502 R_386_PC32 00000000 thread_handle_fputrap RW> 000001e7 00004702 R_386_PC32 00000000 thread_timer_interrupt RW> 000001f7 00004902 R_386_PC32 00000000 thread_timer_interrupt RW> 00000207 00004b02 R_386_PC32 00000000 thread_timer_interrupt RW> 00000211 00004c02 R_386_PC32 00000000 irq_interrupt RW> 00000324 00004d02 R_386_PC32 00000000 dispatch_syscall RW> 00000356 00004f02 R_386_PC32 00000000 call_ipc_short_cut RW> 00000360 0ce6f401 R_386_32 bad symbol index: 000ce6f4 RW> 00000374 00004d02 R_386_PC32 00000000 dispatch_syscall Hallo, Siehe vorletzte gequotete Zeile. Der generierte Code ist kaputt. Ich habe das Problem hier soeben mit gcc 2.95 und gcc 3.2 reproduziert. Bis ich genaueres weiß bzw. einen Patch habe, bitte "Assembler IPC Shortcut" in "make menuconfig" anschalten - dann funktioniert's. -Udo.

1 1