Hi all,
I'm running L4Linux on the Fiasco V2 microkernel on a Pentium IV. I am also running other L4 applications beside the L4Linux kernel. I would like to be able to print debug messages from those applications to the serial port. Messages print fine until L4Linux boots up. As best as I can determine, the problem is that L4Linux gets control of the serial port, and so no other tasks can use it. There may be a way to get this working using the L4Env setup; however, I am trying to keep a very minimal setup and so do not want to use L4Env. Can anyone provide some pointers on how to best go about restricting L4Linux's access to the serial port?
Thanks!
-Julian
Hi,
On Wed Jan 26, 2005 at 12:00:31 -0500, Julian Grizzard wrote:
I'm running L4Linux on the Fiasco V2 microkernel on a Pentium IV. I am also running other L4 applications beside the L4Linux kernel. I would like to be able to print debug messages from those applications to the serial port. Messages print fine until L4Linux boots up. As best as I can determine, the problem is that L4Linux gets control of the serial port, and so no other tasks can use it. There may be a way to get this working using the L4Env setup; however, I am trying to keep a very minimal setup and so do not want to use L4Env. Can anyone provide some pointers on how to best go about restricting L4Linux's access to the serial port?
Just do not configure it in L4Linux?
Adam
l4-hackers@os.inf.tu-dresden.de
-
Adam Lackorzynski -
Julian Grizzard