l4-hackers October 1999

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

8 participants
19 discussions

Re: Question about IO-fpages
by Christian Stueble 14 Oct '99

14 Oct '99

Am Wed, 13 Oct 1999 schrieben Sie: > Hello, > > the L4 reference manual mentions IO-fpages. Has a L4 task its own > IO address space containing IO-fpages, or maps L4 the IO-fpages > into the user memory? Ok, I found the answer at the RMGR manpage :-) > It is said that always the complete IO space should be specified as > receive fpage, why? ? Christian -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Christian Stueble............stueble(a)ls6.cs.uni-dortmund.de PubKey[BF7104F5].......fp=8678C5D3CAD9CD8C F1DDB8EC202F116A To be or not to be is true... (apocrypha of George Boole) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- ------------------------------------------------------- -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Christian Stueble............stueble(a)ls6.cs.uni-dortmund.de PubKey[BF7104F5].......fp=8678C5D3CAD9CD8C F1DDB8EC202F116A To be or not to be is true... (apocrypha of George Boole) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

1 0

Question about IO-fpages
by Christian Stueble 13 Oct '99

13 Oct '99

Hello, the L4 reference manual mentions IO-fpages. Has a L4 task its own IO address space containing IO-fpages, or maps L4 the IO-fpages into the user memory? It is said that always the complete IO space should be specified as receive fpage, why? Thanks, Christian -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Christian Stueble............stueble(a)ls6.cs.uni-dortmund.de PubKey[BF7104F5].......fp=8678C5D3CAD9CD8C F1DDB8EC202F116A To be or not to be is true... (apocrypha of George Boole) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

1 0

L4 user manual
by Christian Stueble 12 Oct '99

12 Oct '99

Hallo again, I was very enjoyed to find a L4 user manual at http://www.cse.unsw.edu.au/~disy Did I look over the link at the fiasco/L4 homepage? Chris -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Christian Stueble............stueble(a)ls6.cs.uni-dortmund.de PubKey[BF7104F5].......fp=8678C5D3CAD9CD8C F1DDB8EC202F116A To be or not to be is true... (apocrypha of George Boole) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

1 0

Re: Driver available?
by Michael Hohmuth 12 Oct '99

12 Oct '99

Christian Stueble <stueble(a)amaunet.cs.uni-dortmund.de> writes: > Mehnert96 and Stange96 both describe an environment to use Linux-drivers > together with L3. Is something similar available to L4/Fiasco? If yes, > where can the example implementations be found? Yes, similar frameworks have been created for a number of drivers (SCSI and ATM networking drivers come to my mind). These frameworks are more of a hackish ad-hoc nature and are in no way meant as a generic device-driver framework. These drivers (and their frameworks) have not been released publicly yet, and I don't know if there are plans to release them; I guess it would be a bit embarrasing for their authors to release them because they contain a lot of write-only, proof-of-concept code written for various research projects -- code they don't want anyone to see. ;-) Maybe these authors or my boss will bite and clarify what their stance on releasing this code is. However, and probably much more interesting to you, there is now a port of Utah university's OSKit (current snapshot 990722) to the L4/x86 and Fiasco interface. The OSKit comes with a lot of Linux and FreeBSD drivers, filesystems, and a complete IP stack that, with the help of a glue library the ``port'' consists of, just run on top of L4/x86 and Fiasco. There is a piece of news at <URL:http://os.inf.tu-dresden.de/fiasco/> about the port (look for liboskit10_support). It also tells you where to download the stuff. > Does L4-Linux directly access hardware ports? Yes, the drivers contained in L4Linux directly access I/O ports. > If yes, is it possible to prevent this behavior, e.g. by inserting a > new "virtual hardware layer"? I don't understand what you mean by ``virtual hardware layer'' and what exactly you want to do, but the answer to your question probably is yes. :) Do you want L4Linux to use drivers running in separate tasks so that it becomes possible to run L4Linux without any special hardware-access privileges? Yes, that is doable. In fact, I have been dreaming about such a setup on and off; this would make it possible to run and debug L4Linux under L4Linux. Michael -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

2 1

Re: Driver available?
by Michael Hohmuth 11 Oct '99

11 Oct '99

Frank Mehnert <fm3(a)os.inf.tu-dresden.de> writes: > Unfortunately in German there is a paper that describes > an environment to port the Linux SCSI driver to L4: > > http://os.inf.tu-dresden.de/papers_ps/l4scsi.ps > > The source may be found at our CVS server. Nope, the SCSI package currently is not exported via our anonymous-CVS server... But if you want to release it, there probably is no problem. Michael -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

1 0

Driver available?
by Christian Stueble 11 Oct '99

11 Oct '99

Hello, 1) Mehnert96 and Stange96 both describe an environment to use Linux-drivers together with L3. Is something similar available to L4/Fiasco? If yes, where can the example implementations be found? 2) Does L4-Linux directly access hardware ports? If yes, is it possible to prevent this behavior, e.g. by inserting a new "virtual hardware layer"? Ciao, Christian -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Christian Stueble............stueble(a)ls6.cs.uni-dortmund.de PubKey[BF7104F5].......fp=8678C5D3CAD9CD8C F1DDB8EC202F116A To be or not to be is true... (apocrypha of George Boole) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

2 1

Re: Error compiling linux22
by vhandel＠chem.vu.nl 09 Oct '99

09 Oct '99

>gcc: Internal compiler error: program cc1 got fatal signal 11 Are you overclocking ? Otherwise, you probably have a bad SIMM. You should read the GCC-SIG11 FAQ that comes with every linux distro. Ramon

3 2

Re: Error compiling linux22
by Jean Wolter 08 Oct '99

08 Oct '99

Christian Stueble <stueble(a)amaunet.cs.uni-dortmund.de> writes: > > Hello, > > I tried to compile linux22 (8.10.99) and get the following error message: > > --------------- > gcc -D__KERNEL__ -I/usr/home/stueble/DA/Data/sb/linux22/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -pipe -fno-strength-reduce -I/usr/home/stueble/DA/Data/sb/linux22/../l4/include -I/home/drops/include -DLINUX_ON_L4 -g -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=586 -c -o svc.o svc.c > gcc: Internal compiler error: program cc1 got fatal signal 11 [...] > Is this a compiler specific problem? This sounds either like a hardware problem (a kernel make is a good test for the memory subsystem) or a compiler problem. Does it happen every time you try to compile this particular file? Or do you get random segmentation faults (signal 11)? Jean -- Mr. Johnson has learned the first rule of not being seen. However, he has chosen a very obvious piece of covah! Kablooey!

1 0

Error compiling linux22
by Christian Stueble 08 Oct '99

08 Oct '99

Hello, I tried to compile linux22 (8.10.99) and get the following error message: --------------- gcc -D__KERNEL__ -I/usr/home/stueble/DA/Data/sb/linux22/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -pipe -fno-strength-reduce -I/usr/home/stueble/DA/Data/sb/linux22/../l4/include -I/home/drops/include -DLINUX_ON_L4 -g -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=586 -c -o svc.o svc.c gcc: Internal compiler error: program cc1 got fatal signal 11 make[3]: *** [svc.o] Error 1 make[3]: Leaving directory `/usr/home/stueble/DA/Data/sb/linux22/fs/lockd' make[2]: *** [first_rule] Error 2 make[2]: Leaving directory `/usr/home/stueble/DA/Data/sb/linux22/fs/lockd' make[1]: *** [_subdir_lockd] Error 2 make[1]: Leaving directory `/usr/home/stueble/DA/Data/sb/linux22/fs' make: *** [_dir_fs] Error 2 stueble@rum:/usr/home/stueble/DA/Data/sb/linux22 > cpp: output pipe has been closed {standard input}: Assembler messages: {standard input}:1398: Warning: end of file not at end of a line; newline inserted {standard input}:1745: Warning: .stabs: Missing comma ---------------- System: gcc version egcs-2.91.60 19981201 (egcs-1.1.1 release) GNU ld version 2.9.1 (with BFD 2.9.1.0.15) Pentium 133, SuSE 6.0 Is this a compiler specific problem? -Chris- -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Christian Stueble............stueble(a)ls6.cs.uni-dortmund.de PubKey[BF7104F5].......fp=8678C5D3CAD9CD8C F1DDB8EC202F116A To be or not to be is true... (apocrypha of George Boole) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

1 0

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 October 1999