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@ls6.cs.uni-dortmund.de PubKey[BF7104F5].......fp=8678C5D3CAD9CD8C F1DDB8EC202F116A To be or not to be is true... (apocrypha of George Boole) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Christian Stueble wrote:
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?
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.
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"?
In DROPS there is a Resource Manager (RMGR) that should control all hardware resources needed by L4 tasks (physical memory, hardware interrupts, I/O-ports). Until now I/O ports are not implemented yet. Frank -- Frank Mehnert ## Dept. of Computer Science, TU-Dresden, Germany ## ## email: fm3@os.inf.tu-dresden.de ##
participants (2)
-
Christian Stueble -
Frank Mehnert