I, personally, don't feel comfortable cluttering up our already cluttered
text-mode screen output code with serial-port output calls.
*However* - I am very excited about serial output, so I'm wondering if it is
okay with you if we work into the kernel logging stuff. Perhaps we can
refactor the kernel logging so that it can handle more verbose throughput -
and use parameters to determine whether to print to screen, serial port, or
both?
Anyone else have any thoughts on this?
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
SharpOS-Developers mailing list
SharpOS-Developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sharpos-developers
