- l4-hackers - example.com Site

RE: None
by Volkmar Uhlig 21 May '03

21 May '03

> -----Original Message----- > From: Andreas Rottmann [mailto:a.rottmann@gmx.at] > Sent: Wednesday, May 21, 2003 8:27 PM > > I wonder why Pistachio needs VME, however. Maybe someone can give a > hint? The hint is that it is not needed right now. The check is going to be removed with the next revision. We just wanted to keep track of all the boch users (just kidding...) - Volkmar

1 0

Re: None
by Andreas Rottmann 21 May '03

21 May '03

Farid Hajji <farid.hajji(a)ob.kamp.net> writes: >> Many thanks for your help, I'm sorry if this seems dumb but I really am >> confused with all the different parts of l4ka and l4hurd. As soon as I >> get all of this working, I am going to put together a complete guide to >> setting up bochs with l4ka, combining all of the above resources. That's >> *if* I get it working, and understand why! > > You may want to try running L4Ka::Pistachio/x86 under the most recent > bochs. We're planning to implement l4hurd on top of Pistachio, not > Hazelnut. > I tried that, and FWICT, Pistachio needs the VME processor capapbility (virtual mode extensions, see http://x86.ddj.com/articles/vme1/vme_overview.htm) which bochs doesn't provide. here is the relevant code (pistachio/kernel/src/glue/v4-ia32/init.cc): --------------------- /** * checks the IA32 features (CPUID) to make sure the processor * has all necessary features */ static void SECTION(".init.cpu") check_cpu_features() { u32_t req_features = IA32_FEAT_FPU | IA32_FEAT_VME | IA32_FEAT_PSE; [...] if ((req_features & avail_features) != req_features) { printf("CPU does not support all features (%x) -- halting\n", req_features); ------- I wonder why Pistachio needs VME, however. Maybe someone can give a hint? Regards, Andy -- Andreas Rottmann | Rotty@ICQ | 118634484@ICQ | a.rottmann(a)gmx.at http://www.8ung.at/rotty | GnuPG Key: http://www.8ung.at/rotty/gpg.asc Fingerprint | DFB4 4EB4 78A4 5EEE 6219 F228 F92F CFC5 01FD 5B62 Make free software, not war!

2 1

(no subject)
by Yu Neil 19 May '03

19 May '03

hello: how we identify the sigma0 server in l4_threadid_t format ? ( the sigma0.id.* is what?) Neil Yu _________________________________________________________________ 免费下载 MSN Explorer: http://explorer.msn.com/lccn/

2 1

Re: Re: Neukundenakquise
by Cherry George Mathew 17 May '03

17 May '03

Farid> Whoever stopped this would be the Hero of the Day(TM) ;) And I certainly hope somebody cleans up the archives. Googling can be a pain with all the noise. Regards, Cherry.

1 0

Re: Neukundenakquise
by Farid Hajji 17 May '03

17 May '03

Hi l4-hackers admins: > SIE HABEN DAS PRODUKT - WIR IHRE ZUK\NFTIGEN KUNDEN. > > http://www.Adress-Schmiede.de I'm also getting a lot of SPAM from those people. They seem to misuse a T-Online AG dialin account to spread their stuff: > Received: from os.inf.tu-dresden.de (pD9E8B8C6.dip.t-dialin.net > [217.232.184.198])h4H0DdhF006363 > for <l4-hackers(a)os.inf.tu-dresden.de>; > Sat, 17 May 2003 02:13:39 +0200 (MEST) This looks similar on all SPAMs that I've got on multiple E-Mail addresses. They use different IP addresses from the same pool. You may contact T-Online AG regarding this. I'm pretty sure that this is not in accordance with their (T-Online's) AUP. Whoever stopped this would be the Hero of the Day(TM) ;) > l4-hackers mailing list > l4-hackers(a)os.inf.tu-dresden.de > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers Thanks, -Farid. -- Farid Hajji -- Unix Systems and Network Management. http://www.farid-hajji.net/address.html Quoth the Raven, "Nevermore." --Edgar Allan Poe.

1 0

spamfilter on mailinglist
by Remco Post 16 May '03

16 May '03

Hi all, ok, spmmers found us, unfortunately, could the listowner apply some spamassasin magic to incoming mails? It would be greatly appriciated.... -- Met vriendelijke groeten, Remco Post SARA - Stichting Academisch Rekencentrum Amsterdam http://www.sara.nl High Performance Computing Tel. +31 20 592 8008 Fax. +31 20 668 3167 "I really didn't foresee the Internet. But then, neither did the computer industry. Not that that tells us very much of course - the computer industry didn't even foresee that the century was going to end." -- Douglas Adams

2 1

compiling L4Env with oskit for Fiasco and L4Linux
by Etienne Robillard 06 May '03

06 May '03

Hello everyone, My name is Etienne Robillard and I am studying Art in college. I don't have yet any degree in computers science, whatsoever. What I am attempting to do is to build/boot L4Linux (and on another time The Hurd, while I'm at it...) on a typical x86 machine, Pentium III with 384mb of sdram. oskit = oskit60 (the old version modified for l4 with patches) gcc = crossgcc 2.95.2 (no libgcc2.a) with pthread-elf support, i386/linux emulation os = freebsd4.7-p8 (with libc_r/) make = gmake target = i586-l4-linux (just for fun...) build= i386-unknown-freebsd4.7 binutils = version 2.13.2.1 as root in $(L4DIR); gmake hello : gmake[1]: Entering directory `/home/manoya/build/l4oskit/l4/oskit/flux' gmake[1]: Nothing to be done for `all'. gmake[1]: Leaving directory `/home/manoya/build/l4oskit/l4/oskit/flux' gmake[1]: Entering directory `/home/manoya/build/l4oskit/l4/oskit/libc' i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libc/x86 -I../libc/stdio -I../libc/stdlib -I../libc/string -I../libc/gen -I../libc/malloc -I- -I.. -I.. -I../flux/c -nostdinc -DASSEMBLER -MD ../libc/x86/bcopy.S i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libc/x86 -I../libc/stdio -I../libc/stdlib -I../libc/string -I../libc/gen -I../libc/malloc -I- -I.. -I.. -I../flux/c -nostdinc -DASSEMBLER -MD ../libc/x86/bcopy16.S i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libc/x86 -I../libc/stdio -I../libc/stdlib -I../libc/string -I../libc/gen -I../libc/malloc -I- -I.. -I.. -I../flux/c -nostdinc -DASSEMBLER -MD ../libc/x86/bzero.S i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libc/x86 -I../libc/stdio -I../libc/stdlib -I../libc/string -I../libc/gen -I../libc/malloc -I- -I.. -I.. -I../flux/c -nostdinc -DASSEMBLER -MD ../libc/x86/gcc.S i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libc/x86 -I../libc/stdio -I../libc/stdlib -I../libc/string -I../libc/gen -I../libc/malloc -I- -I.. -I.. -I../flux/c -nostdinc -DASSEMBLER -MD ../libc/x86/i16_bcopy.S i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libc/x86 -I../libc/stdio -I../libc/stdlib -I../libc/string -I../libc/gen -I../libc/malloc -I- -I.. -I.. -I../flux/c -nostdinc -DASSEMBLER -MD ../libc/x86/i16_bzero.S i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libc/x86 -I../libc/stdio -I../libc/stdlib -I../libc/string -I../libc/gen -I../libc/malloc -I- -I.. -I.. -I../flux/c -nostdinc -DASSEMBLER -MD ../libc/x86/memset.S i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libc/x86 -I../libc/stdio -I../libc/stdlib -I../libc/string -I../libc/gen -I../libc/malloc -I- -I.. -I.. -I../flux/c -nostdinc -DASSEMBLER -MD ../libc/x86/ntoh.S i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libc/x86 -I../libc/stdio -I../libc/stdlib -I../libc/string -I../libc/gen -I../libc/malloc -I- -I.. -I.. -I../flux/c -nostdinc -g -O2 -Wall ../libc/x86/proc_reg.c i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libc/x86 -I../libc/stdio -I../libc/stdlib -I../libc/string -I../libc/gen -I../libc/malloc -I- -I.. -I.. -I../flux/c -nostdinc -DASSEMBLER -MD ../libc/x86/setjmp.S ar rv libmc.a bcopy.o bcopy16.o bzero.o gcc.o i16_bcopy.o i16_bzero.o memset.o ntoh.o proc_reg.o setjmp.o r - bcopy.o r - bcopy16.o r - bzero.o r - gcc.o r - i16_bcopy.o r - i16_bzero.o r - memset.o r - ntoh.o r - proc_reg.o r - setjmp.o ranlib libmc.a cp libmc.a ../lib/libmc.a gmake[1]: Leaving directory `/home/manoya/build/l4oskit/l4/oskit/libc' gmake[1]: Entering directory `/home/manoya/build/l4oskit/l4/oskit/liblmm' gmake[1]: Nothing to be done for `all'. gmake[1]: Leaving directory `/home/manoya/build/l4oskit/l4/oskit/liblmm' gmake[1]: Entering directory `/home/manoya/build/l4oskit/l4/oskit/libexec' gmake[1]: Nothing to be done for `all'. gmake[1]: Leaving directory `/home/manoya/build/l4oskit/l4/oskit/libexec' gmake[1]: Entering directory `/home/manoya/build/l4oskit/l4/oskit/libdiskpart' gmake[1]: Nothing to be done for `all'. gmake[1]: Leaving directory `/home/manoya/build/l4oskit/l4/oskit/libdiskpart' gmake[1]: Entering directory `/home/manoya/build/l4oskit/l4/oskit/libkern' i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libkern/x86 -I../libkern/x86/trap -I../libkern/x86/pc -I../libkern -I- -I.. -I.. -I../flux/c -nostdinc -g -O2 -Wall ../libkern/x86/base_critical.c i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libkern/x86 -I../libkern/x86/trap -I../libkern/x86/pc -I../libkern -I- -I.. -I.. -I../flux/c -nostdinc -g -O2 -Wall ../libkern/x86/base_gdt_load.c i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libkern/x86 -I../libkern/x86/trap -I../libkern/x86/pc -I../libkern -I- -I.. -I.. -I../flux/c -nostdinc -g -O2 -Wall ../libkern/x86/base_idt_load.c i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libkern/x86 -I../libkern/x86/trap -I../libkern/x86/pc -I../libkern -I- -I.. -I.. -I../flux/c -nostdinc -g -O2 -Wall ../libkern/x86/base_paging_init.c i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libkern/x86 -I../libkern/x86/trap -I../libkern/x86/pc -I../libkern -I- -I.. -I.. -I../flux/c -nostdinc -DASSEMBLER -MD ../libkern/x86/base_stack.S i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libkern/x86 -I../libkern/x86/trap -I../libkern/x86/pc -I../libkern -I- -I.. -I.. -I../flux/c -nostdinc -DASSEMBLER -MD ../libkern/x86/base_trap_inittab.S i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libkern/x86 -I../libkern/x86/trap -I../libkern/x86/pc -I../libkern -I- -I.. -I.. -I../flux/c -nostdinc -g -O2 -Wall ../libkern/x86/base_tss_init.c i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libkern/x86 -I../libkern/x86/trap -I../libkern/x86/pc -I../libkern -I- -I.. -I.. -I../flux/c -nostdinc -g -O2 -Wall ../libkern/x86/base_tss_load.c i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libkern/x86 -I../libkern/x86/trap -I../libkern/x86/pc -I../libkern -I- -I.. -I.. -I../flux/c -nostdinc -g -O2 -Wall ../libkern/x86/cpuid.c i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libkern/x86 -I../libkern/x86/trap -I../libkern/x86/pc -I../libkern -I- -I.. -I.. -I../flux/c -nostdinc -DASSEMBLER -MD ../libkern/x86/gdb_copy.S i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libkern/x86 -I../libkern/x86/trap -I../libkern/x86/pc -I../libkern -I- -I.. -I.. -I../flux/c -nostdinc -DASSEMBLER -MD ../libkern/x86/pc/gdb_pc_com_intr.S i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libkern/x86 -I../libkern/x86/trap -I../libkern/x86/pc -I../libkern -I- -I.. -I.. -I../flux/c -nostdinc -g -O2 -Wall ../libkern/x86/gdb_trap.c i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libkern/x86 -I../libkern/x86/trap -I../libkern/x86/pc -I../libkern -I- -I.. -I.. -I../flux/c -nostdinc -g -O2 -Wall ../libkern/x86/pdir_dump.c i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libkern/x86 -I../libkern/x86/trap -I../libkern/x86/pc -I../libkern -I- -I.. -I.. -I../flux/c -nostdinc -g -O2 -Wall ../libkern/x86/pdir_map_page.c i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libkern/x86 -I../libkern/x86/trap -I../libkern/x86/pc -I../libkern -I- -I.. -I.. -I../flux/c -nostdinc -g -O2 -Wall ../libkern/x86/pdir_map_range.c i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libkern/x86 -I../libkern/x86/trap -I../libkern/x86/pc -I../libkern -I- -I.. -I.. -I../flux/c -nostdinc -g -O2 -Wall ../libkern/x86/pdir_prot_range.c i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libkern/x86 -I../libkern/x86/trap -I../libkern/x86/pc -I../libkern -I- -I.. -I.. -I../flux/c -nostdinc -g -O2 -Wall ../libkern/x86/pdir_unmap_range.c i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libkern/x86 -I../libkern/x86/trap -I../libkern/x86/pc -I../libkern -I- -I.. -I.. -I../flux/c -nostdinc -g -O2 -Wall ../libkern/x86/pc/pic.c i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libkern/x86 -I../libkern/x86/trap -I../libkern/x86/pc -I../libkern -I- -I.. -I.. -I../flux/c -nostdinc -g -O2 -Wall ../libkern/x86/ptab_alloc.c i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libkern/x86 -I../libkern/x86/trap -I../libkern/x86/pc -I../libkern -I- -I.. -I.. -I../flux/c -nostdinc -g -O2 -Wall ../libkern/x86/ptab_dump.c i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libkern/x86 -I../libkern/x86/trap -I../libkern/x86/pc -I../libkern -I- -I.. -I.. -I../flux/c -nostdinc -g -O2 -Wall ../libkern/x86/ptab_free.c i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libkern/x86 -I../libkern/x86/trap -I../libkern/x86/pc -I../libkern -I- -I.. -I.. -I../flux/c -nostdinc -g -O2 -Wall ../libkern/x86/pc/reset.c i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libkern/x86 -I../libkern/x86/trap -I../libkern/x86/pc -I../libkern -I- -I.. -I.. -I../flux/c -nostdinc -g -O2 -Wall ../libkern/x86/trap_dump.c ar rv libkern.a base_critical.o base_gdt_load.o base_idt_load.o base_paging_init.o base_stack.o base_trap_inittab.o base_tss_init.o base_tss_load.o cpuid.o gdb_copy.o gdb_pc_com_intr.o gdb_trap.o pdir_dump.o pdir_map_page.o pdir_map_range.o pdir_prot_range.o pdir_unmap_range.o pic.o ptab_alloc.o ptab_dump.o ptab_free.o reset.o trap_dump.o r - base_critical.o r - base_gdt_load.o r - base_idt_load.o r - base_paging_init.o r - base_stack.o r - base_trap_inittab.o r - base_tss_init.o r - base_tss_load.o r - cpuid.o r - gdb_copy.o r - gdb_pc_com_intr.o r - gdb_trap.o r - pdir_dump.o r - pdir_map_page.o r - pdir_map_range.o r - pdir_prot_range.o r - pdir_unmap_range.o r - pic.o r - ptab_alloc.o r - ptab_dump.o r - ptab_free.o r - reset.o r - trap_dump.o ranlib libkern.a cp libkern.a ../lib/libkern.a gmake[1]: Leaving directory `/home/manoya/build/l4oskit/l4/oskit/libkern' gmake[1]: Entering directory `/home/manoya/build/l4oskit/l4/oskit/libsmp' i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libsmp/x86 -I- -I.. -I.. -I../flux/c -nostdinc -DASSEMBLER -MD ../libsmp/x86/boot.S i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libsmp/x86 -I- -I.. -I.. -I../flux/c -nostdinc -g -O2 -Wall ../libsmp/x86/critical.c i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libsmp/x86 -I- -I.. -I.. -I../flux/c -nostdinc -g -O2 -Wall ../libsmp/x86/linux-smp.c i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libsmp/x86 -I- -I.. -I.. -I../flux/c -nostdinc -g -O2 -Wall ../libsmp/x86/smp.c ar rv libsmp.a boot.o critical.o linux-smp.o smp.o r - boot.o r - critical.o r - linux-smp.o r - smp.o ranlib libsmp.a cp libsmp.a ../lib/libsmp.a gmake[1]: Leaving directory `/home/manoya/build/l4oskit/l4/oskit/libsmp' gmake[1]: Entering directory `/home/manoya/build/l4oskit/l4/oskit/libmemdebug' gmake[1]: Nothing to be done for `all'. gmake[1]: Leaving directory `/home/manoya/build/l4oskit/l4/oskit/libmemdebug' gmake[1]: Entering directory `/home/manoya/build/l4oskit/l4/oskit/libfdev' i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -DDEBUG -I. -I../libfdev -I- -I.. -I.. -I../flux/c -nostdinc -g -O2 -Wall irq.c irq.c:97: warning: `fdev_intr_enable' declared inline after being called irq.c:103: warning: `fdev_intr_disable' declared inline after being called i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -DDEBUG -I. -I../libfdev -I- -I.. -I.. -I../flux/c -nostdinc -DASSEMBLER -MD irqstubs.S /var/tmp/ccMEqA1O.s: Assembler messages: /var/tmp/ccMEqA1O.s:421: Warning: using `%ecx' instead of `%cx' due to `l' suffix /var/tmp/ccMEqA1O.s:422: Warning: using `%ecx' instead of `%cx' due to `l' suffix /var/tmp/ccMEqA1O.s:423: Warning: using `%ecx' instead of `%cx' due to `l' suffix i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -DDEBUG -I. -I../libfdev -I- -I.. -I.. -I../flux/c -nostdinc -g -O2 -Wall sched.c i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -DDEBUG -I. -I../libfdev -I- -I.. -I.. -I../flux/c -nostdinc -g -O2 -Wall softintr.c i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -DDEBUG -I. -I../libfdev -I- -I.. -I.. -I../flux/c -nostdinc -g -O2 -Wall timer.c ar rv libfdev.a irq.o irqstubs.o sched.o softintr.o timer.o r - irq.o r - irqstubs.o r - sched.o r - softintr.o r - timer.o ranlib libfdev.a cp libfdev.a ../lib/libfdev.a gmake[1]: Leaving directory `/home/manoya/build/l4oskit/l4/oskit/libfdev' gmake[1]: Entering directory `/home/manoya/build/l4oskit/l4/oskit/libfdev_linux' gmake[1]: Leaving directory `/home/manoya/build/l4oskit/l4/oskit/libfdev_linux' gmake[1]: Entering directory `/home/manoya/build/l4oskit/l4/oskit/libfdev_linux' i586-l4-linux-gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -DOSKIT -D__KERNEL__ -DDEBUG -I. -I../libfdev_linux -I../libfdev_linux/net -I../libfdev_linux/block -I../libfdev_linux/pci -I../libfdev_linux/scsi -I- -I../libfdev_linux/include -I.. -I.. -I../flux/c -nostdinc -g -O2 -Wall ../libfdev_linux/scsi/53c7,8xx.c In file included from ../libfdev_linux/include/linux/string.h:40, from ../libfdev_linux/include/asm/termios.h:271, from ../libfdev_linux/include/linux/termios.h:5, from ../libfdev_linux/include/linux/tty.h:10, from ../libfdev_linux/include/linux/sched.h:25, from ../libfdev_linux/scsi/53c7,8xx.c:228: ../libfdev_linux/include/asm/string.h: In function `__constant_memcpy': ../libfdev_linux/include/asm/string.h:408: warning: control reaches end of non-void function ../libfdev_linux/include/asm/string.h: In function `__constant_c_and_count_memset': ../libfdev_linux/include/asm/string.h:557: warning: control reaches end of non-void function In file included from ../libfdev_linux/scsi/53c7,8xx.c:230: ../libfdev_linux/include/linux/bios32.h: At top level: ../libfdev_linux/include/linux/bios32.h:58: warning: type defaults to `int' in declaration of `pcibios_write_config_dword' ../libfdev_linux/scsi/53c7,8xx.c: In function `internal_setup': ../libfdev_linux/include/asm/string.h:105: Invalid `asm' statement: ../libfdev_linux/include/asm/string.h:105: fixed or forbidden register 4 (si) was spilled for class SIREG. ../libfdev_linux/scsi/53c7,8xx.c: In function `NCR53c7x0_init': ../libfdev_linux/include/asm/string.h:402: Invalid `asm' statement: ../libfdev_linux/include/asm/string.h:402: fixed or forbidden register 2 (cx) was spilled for class CREG. ../libfdev_linux/scsi/53c7,8xx.c: In function `normal_init': ../libfdev_linux/include/asm/string.h:495: Invalid `asm' statement: ../libfdev_linux/include/asm/string.h:495: fixed or forbidden register 2 (cx) was spilled for class CREG. ../libfdev_linux/scsi/53c7,8xx.c: In function `NCR53c8x0_init_fixup': ../libfdev_linux/include/asm/string.h:402: Invalid `asm' statement: ../libfdev_linux/include/asm/string.h:402: fixed or forbidden register 2 (cx) was spilled for class CREG. ../libfdev_linux/scsi/53c7,8xx.c: In function `NCR53c8xx_dsa_fixup': ../libfdev_linux/include/asm/string.h:366: Invalid `asm' statement: ../libfdev_linux/include/asm/string.h:366: fixed or forbidden register 2 (cx) was spilled for class CREG. ../libfdev_linux/scsi/53c7,8xx.c: In function `abnormal_finished': ../libfdev_linux/scsi/53c7,8xx.c:2137: warning: suggest explicit braces to avoid ambiguous `else' ../libfdev_linux/scsi/53c7,8xx.c: In function `NCR53c8x0_dstat_sir_intr': ../libfdev_linux/include/asm/string.h:402: Invalid `asm' statement: ../libfdev_linux/include/asm/string.h:402: fixed or forbidden register 2 (cx) was spilled for class CREG. ../libfdev_linux/scsi/53c7,8xx.c: In function `create_cmd': ../libfdev_linux/include/asm/string.h:403: Invalid `asm' statement: ../libfdev_linux/include/asm/string.h:403: fixed or forbidden register 2 (cx) was spilled for class CREG. ../libfdev_linux/include/asm/string.h:403: Invalid `asm' statement: ../libfdev_linux/include/asm/string.h:403: fixed or forbidden register 2 (cx) was spilled for class CREG. ../libfdev_linux/scsi/53c7,8xx.c: In function `intr_scsi': ../libfdev_linux/include/asm/delay.h:43: Invalid `asm' statement: ../libfdev_linux/include/asm/delay.h:43: fixed or forbidden register 0 (ax) was spilled for class AREG. ../libfdev_linux/include/asm/delay.h:20: Invalid `asm' statement: ../libfdev_linux/include/asm/delay.h:20: fixed or forbidden register 0 (ax) was spilled for class AREG. ../libfdev_linux/scsi/53c7,8xx.c: In function `print_insn': ../libfdev_linux/include/asm/string.h:287: Invalid `asm' statement: ../libfdev_linux/include/asm/string.h:287: fixed or forbidden register 5 (di) was spilled for class DIREG. ../libfdev_linux/scsi/53c7,8xx.c: In function `ncr_scsi_reset': ../libfdev_linux/include/asm/delay.h:43: Invalid `asm' statement: ../libfdev_linux/include/asm/delay.h:43: fixed or forbidden register 0 (ax) was spilled for class AREG. ../libfdev_linux/include/asm/delay.h:20: Invalid `asm' statement: ../libfdev_linux/include/asm/delay.h:20: fixed or forbidden register 0 (ax) was spilled for class AREG. ../libfdev_linux/scsi/53c7,8xx.c: In function `ncr_halt': ../libfdev_linux/scsi/53c7,8xx.c:6233: warning: suggest explicit braces to avoid ambiguous `else' ../libfdev_linux/include/asm/delay.h:43: Invalid `asm' statement: ../libfdev_linux/include/asm/delay.h:43: fixed or forbidden register 0 (ax) was spilled for class AREG. ../libfdev_linux/include/asm/delay.h:20: Invalid `asm' statement: ../libfdev_linux/include/asm/delay.h:20: fixed or forbidden register 0 (ax) was spilled for class AREG. ../libfdev_linux/scsi/53c7,8xx.c: In function `dump_events': ../libfdev_linux/include/asm/string.h:402: Invalid `asm' statement: ../libfdev_linux/include/asm/string.h:402: fixed or forbidden register 2 (cx) was spilled for class CREG. ../libfdev_linux/scsi/53c7,8xx.c: At top level: ../libfdev_linux/scsi/53c7,8xx.c:693: warning: `request_synchronous' defined but not used ../libfdev_linux/scsi/53c7,8xx.c:741: warning: `request_disconnect' defined but not used ../libfdev_linux/scsi/53c7,8xx.c:5395: warning: `ncr_state' defined but not used gmake[1]: *** [53c7,8xx.o] Error 1 gmake[1]: Leaving directory `/home/manoya/build/l4oskit/l4/oskit/libfdev_linux' gmake: *** [libfdev_linux/all.MAKE] Error 2 In order to get there, I had to undefined HAVE_CODE16 in $(OSKIT)/flux/config.h. Otherwise, I would have this bug : gmake[1]: Entering directory `/home/manoya/build/l4oskit/l4/oskit/flux' gmake[1]: Nothing to be done for `all'. gmake[1]: Leaving directory `/home/manoya/build/l4oskit/l4/oskit/flux' gmake[1]: Entering directory `/home/manoya/build/l4oskit/l4/oskit/libc' gcc -c -MD -DHAVE_CONFIG_H -DDEBUG -I. -I../libc/x86 -I../libc/stdio -I../libc/stdlib -I../libc/string -I../libc/gen -I../libc/malloc -I- -I.. -I.. -I../flux/c -nostdinc -DASSEMBLER -MD ../libc/x86/i16_bcopy.S /tmp/ccqgmwoi.s: Assembler messages: /tmp/ccqgmwoi.s:235: Error: `8(%ebp)' is not a valid 16 bit base/index expression /tmp/ccqgmwoi.s:236: Error: `12(%ebp)' is not a valid 16 bit base/index expression /tmp/ccqgmwoi.s:238: Error: `16(%ebp)' is not a valid 16 bit base/index expression /tmp/ccqgmwoi.s:239: Error: `(%esi,%edx)' is not a valid 16 bit base/index expression /tmp/ccqgmwoi.s:242: Error: `(%edi,%edx)' is not a valid 16 bit base/index expression /tmp/ccqgmwoi.s:259: Error: `8(%ebp)' is not a valid 16 bit base/index expression /tmp/ccqgmwoi.s:278: Error: `8(%ebp)' is not a valid 16 bit base/index expression /tmp/ccqgmwoi.s:291: Error: `8(%ebp)' is not a valid 16 bit base/index expression /tmp/ccqgmwoi.s:292: Error: `12(%ebp)' is not a valid 16 bit base/index expression gmake[1]: *** [i16_bcopy.o] Error 1 gmake[1]: Leaving directory `/home/manoya/build/l4oskit/l4/oskit/libc' gmake: *** [libc/all.MAKE] Error 2 I dont know if this is a bug 'cause, ain't qualified ;) really... As a result, I am quite lost in space with the asm part. But, I was asking myself if 1) this is due to an improper crosscompiler setup (compiler doesnt have libgcc2.a subroutines... my fault) Will work on that for now on. 2) because I have undef HAVE_CODE16, my i16_bcopy object will fail bit-copying inline functions that need 16 bit index base ? 3) "warning: control reaches end of non-void function" and "fixed or forbidden register 2 (cx) was spilled for class CREG" Yeah. right. Bring it Linda ! Here is for your convenience a sample of the contents of $(OSKIT)/libfdev_linux/include/asm/string.h:408 #define __HAVE_ARCH_MEMCPY #define memcpy(t, f, n) \ (__builtin_constant_p(n) ? \ __constant_memcpy((t),(f),(n)) : \ <------ n=count ? __memcpy((t),(f),(n))) /* I have tried to change (n) to (count) with similar syndromes; but something's telling me that Linus know what he`s doing while I seriously doubt my proefficiency in that domain... */ Also, I dont have an Internet connection at home... Therefore, I got very, very old parts (before 1.0) of the Fiasco �-kernel... At last, this issue in lfdev_linux might be solved already(?), which would be nice, but I haven't found any references to that neither in the 2001 mailing-list or in the 2002. Kind regards, Etienne Robillard Person who say it cannot be done should not interrupt person doing it. --Chinese Proverb ===== iD ______________________________________________________________________ Post your free ad now! http://personals.yahoo.ca

2 1

about l4_thread_ex_regs()
by Yu Neil 05 May '03

05 May '03

hello: i execute the l4_thread_ex_regs(...) systemcall, then the stack been pushed 0x38 byte data (esp -0x38), what`s that ? most serious is if i execute the l4_thread_ex_regs( dest_thread_id, child,... ) systemcall then the |child| running ,but if i execute l4_myself() in |child|, the return value is not equal to dest_thread_id, is that means i can`t specific the dest thread id or it`s unnecessary to spicify the dest thread id in the caller thread, but managed by |child| itself ? Neil Yu _________________________________________________________________ 免费下载 MSN Explorer: http://explorer.msn.com/lccn

1 0

Re: Problems compiling from CVS
by Daniel Koch 04 May '03

04 May '03

> Subject: Re: Problems compiling from CVS > To: l4-hackers(a)os.inf.tu-dresden.de > Message-ID: <20030503220824.GA16869(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > Hi, > > On Sun May 04, 2003 at 00:42:03 +0200, Daniel Koch is going to write: > > when I try to compile the hello world servers with "make hello" from > > your newest cvs version I get the following error: > > > > In file included from ../cfg-parse.y:320: > > <stdout>:23:20: stdint.h: Datei oder Verzeichnis nicht gefunden > > Do you have the libc development package with the header files installed > (something like libc6-dev)? > > > > > > > Adam Hi Adam, the stdint.h file is where it should be: /usr/include/stdint.h skywalker:/usr/include# ls -la stdint.h -rw-r--r-- 1 root root 8545 2003-04-19 20:56 stdint.h skywalker:/usr/include# I tried compiling it as root, but its just the same problem Daniel

2 4

Re:Re: Problems compiling from CVS
by Daniel Koch 04 May '03

04 May '03

>Do you have the libc development package with the header files >installed >(something like libc6-dev)? Yes,libc6-dev 2.3.17. Should I remove this package and use the standard libc6 instead ? Daniel

2 1

Problems compiling from CVS
by Daniel Koch 04 May '03

04 May '03

Hello, when I try to compile the hello world servers with "make hello" from your newest cvs version I get the following error: ... Compiling cfg-parse.o LD_PRELOAD= GENDEP_TARGET=cfg-parse.o GENDEP_BINARY= gcc -c -DSYSTEM_x86_586_l4v2 -DARCH_x86 -DCPUTYPE_586 -DL4API_l4v2 -I../../../server/src -I. -I../../../../../include/x86/l4v2 -I/home/drops/include/x86/l4v2 -I../../../../../include/x86 -I/home/drops/include/x86 -I../../../../../include -I/home/drops/include -nostdinc -I../../../../../../oskit -I../../../../../../oskit/flux/c -I/home/drops/include -I/home/drops/include/flux/c -I/usr/lib/gcc-lib/i386-linux/3.2.3//include -g -O2 -march=i586 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wno-unused -Wno-parentheses cfg-parse.c -o cfg-parse.o In file included from ../cfg-parse.y:320: <stdout>:23:20: stdint.h: Datei oder Verzeichnis nicht gefunden In file included from ../cfg-parse.y:320: <stdout>:2086: warning: no previous prototype for `yyget_lineno' <stdout>:2095: warning: no previous prototype for `yyget_in' <stdout>:2103: warning: no previous prototype for `yyget_out' <stdout>:2111: warning: no previous prototype for `yyget_leng' <stdout>:2120: warning: no previous prototype for `yyget_text' <stdout>:2129: warning: no previous prototype for `yyset_lineno' <stdout>:2141: warning: no previous prototype for `yyset_in' <stdout>:2146: warning: no previous prototype for `yyset_out' <stdout>:2151: warning: no previous prototype for `yyget_debug' <stdout>:2156: warning: no previous prototype for `yyset_debug' <stdout>:2162: warning: no previous prototype for `yylex_destroy' make[4]: *** [cfg-parse.o] Fehler 1 make[4]: Leaving directory `/home/daniel/Projekt/DROPS/l4/pkg/rmgr/server/src/OBJ-x86_586-l4v2' make[3]: *** [all] Fehler 2 make[3]: Leaving directory `/home/daniel/Projekt/DROPS/l4/pkg/rmgr/server/src' make[2]: *** [src] Fehler 2 make[2]: Leaving directory `/home/daniel/Projekt/DROPS/l4/pkg/rmgr/server' make[1]: *** [server] Fehler 2 make[1]: Leaving directory `/home/daniel/Projekt/DROPS/l4/pkg/rmgr' make: *** [hello] Fehler 2 daniel@skywalker:~/Projekt/DROPS/l4$ Im using gcc 3.2.3 on an Athlon system. Any suggestions ? Daniel

2 1

ANNOUNCE: L4Ka::Pistachio version 0.1
by Espen Skoglund 02 May '03

02 May '03

The L4Ka team is happy to announce the first release of the L4Ka::Pistachio microkernel. L4Ka::Pistachio is the latest L4 microkernel developed by the System Architecture Group at the University of Karlsruhe, Germany, in collaboration with the DISY group at the University of New South Wales, Australia. It is the first available kernel implementation of the L4 Version 4 kernel API (currently code-named Version X.2), which is fully 32 and 64 bit clean and provides multiprocessor support. A broad overview of L4Ka::Pistachio and the L4 Version 4 API can be found in: http://l4ka.org/projects/pistachio/pistachio-whitepaper.pdf L4Ka::Pistachio is built from ground up incorporating the research results of the last seven years of microkernel and multi-server research. The code is written in C++ with a strong focus on performance and portability. The first release includes support for many of today's widely used commodity architectures: o Intel IA32 (Pentium and higher) o Intel IA64 (Itanium1) o PowerPC 32bit (IBM 750) o Alpha (21164) o MIPS 64bit (R4000, R5000) The variety of supported architectures makes L4Ka::Pistachio an ideal research and development platform for a wide variety of systems. Additional architectural support for AMD64, ARM, Power4, and UltraSparc is either planned or already in progress. L4Ka::Pistachio is available under the two-clause BSD license. Source and binary distributions, documentation, and other online resources can be found on the L4Ka website: http://l4ka.org/ Within the next few weeks we are going to release L4Linux 2.4.20 which has support for L4Ka::Pistachio/ia32 (besides the old V2 and X.0 APIs). Happy hacking, The L4Ka Development Team

1 0

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 02 Apr '03

02 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

Poblem compiling fiasco-ux: ld: entry.o: bad symbol index: 845556
by Rudolf Weber 23 Mar '03

23 Mar '03

Hello, I tried to compile the current fiasco-ux: make[1]: Entering directory `/home/rw/l4/20030322/l4/kernel/fiasco/build-ux' ==> Linking kernel.image g++ -Wl,--gc-sections,-T../src/kernel.ux.ld -static -o kernel.image boot_info.o boot_info-ux.o cpu-ia32-common.o cpu-ux.o mapdb.o region.o space_context-ia32-ux.o space_context-ux.o space.o space-ia32-ux.o space-ux.o space_index.o space_index_util.o stack.o kmem-ia32-ux.o kmem-ux.o kmem_alloc.o kmem_alloc-ia32-ux.o slab_cache_anon.o kmem_slab_simple.o kmem_slab.o switch_lock.o thread_lock.o helpin g_lock.o cpu_lock.o cpu_lock-generic.o timer.o timer-ia32.o timer-ux.o pic.o pic-ux.o thread_state.o sched.o sched-ia32-ux.o context.o context-ia32-ux.o context-ux.o threadid.o sender.o receiver.o thread.o thread-ia32-ux.o thread-ux.o thread-v2.o thread-syscall.o thread-syscall-v2.o thread-ipc.o thread-msg.o thread-msg-ux.o thread-list.o thread-nolog.o thread-user-ux.o thread-nosmas.o kernel_thread.o kernel_thread-std.o kernel_thread-ux.o thread_util.o kdb_ke.o dirq.o dirq-ia32-ux.o fpu.o fpu-ia32-ux.o fpu-ux.o fpu_alloc.o fpu_state.o map_util.o map_util-ia32-ux.o irq.o irq-ipc.o irq-ux.o globals.o globals-ia32-ux.o main-ia32-ux.o main-ux.o config.o config-ux.o config-ia32-ux.o usermode.o mapped_alloc.o trampoline.o loader.o kern_types.o vmem_alloc.o vmem_alloc-ia32-ux.o vmem_alloc-ux.o panic.o paging.o paging-ia32-ux.o entry_frame.o entry_frame-ia32-common-v2.o startup.o emulation.o hostproc.o task.o task-no-auto-map-kip.o irq_alloc.o libc_support.o long_msg.o long_msg-ux.o entry.o sighandler.o libk.a libamm.a liblmm.a libabi.a libjabi.a libcxx.a libkern.a -lutil /usr/bin/ld: entry.o: bad symbol index: 845556 entry.o: could not read symbols: File format not recognized My System: [rw@fetzi build-ux]$ gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --host=i386-redhat-linux --with-system-zlib --enable-__cxa_atexit Thread model: posix gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7) [rw@fetzi build-ux]$ as -v GNU assembler version 2.13.90.0.2 (i386-redhat-linux) using BFD version 2.13.90.0.2 20020802 [rw@fetzi build-ux]$ ld -v GNU ld version 2.13.90.0.2 20020802 (from Redhat 8.0) Who can fix it ? Greetings Rudolf -- -- --------------------------------------------------------------- Rudolf Weber http://www.infnet.verein.de/~rw E-Mail: rfweber(a)tesionmail.de

3 2

about l4rm
by Yu Neil 22 Mar '03

22 Mar '03

hello every one: where i can find the source code of l4rm ( l4 region maper ) ? and should it work well on x86? Neil Yu _________________________________________________________________ 享用世界上最大的电子邮件系统― MSN Hotmail。 http://www.hotmail.com

2 1

(no subject)
by Yu Neil 20 Mar '03

20 Mar '03

hello every one: where i can find the source code of l4rm ( l4 region maper ) ? and should it work well on x86? Neil Yu _________________________________________________________________ 免费下载 MSN Explorer: http://explorer.msn.com/lccn/

1 0