I was wondering if any experienced kernel hackers could give me an opinion
on this: I turned on the serial port echo so that kernel messages get
echoed to the serial port, and this seems (to my untrained eyes) like a
real quick-and-dirty hack because (a) There are now two independent pieces
of code talking to the serial port hardware, possibly simultaneously, that
have no knowledge of each other, and (b) it's not a true serial console;
after the kernel has booted a getty needs to be run on the serial port
port, not the console.
I was just wondering, what would be the _correct_ way to implement this?
(a serial port console that actually _replaces_ the regular console)
Would it be possible to have console.c replace the keyboard/display code
with serial port code? How could this be done so that the existing serial
port code could be used, but without a catch-22 due to the fact that the
kernel has messages to output before the serial driver is normally
initialized?
Thanks folks....
Eric Seppanen / [EMAIL PROTECTED]
