Re: IOLog on serial port? Or to use kprintf?
Re: IOLog on serial port? Or to use kprintf?
- Subject: Re: IOLog on serial port? Or to use kprintf?
- From: David Gatwood <email@hidden>
- Date: Mon, 24 Jan 2005 13:45:48 -0800
On Jan 24, 2005, at 12:38 PM, Justin Walker wrote:
Currently I see my IOLog() messages in to the
/var/log/system.log file.
Can I redirect it to my serial port?
My Sytem is MAC OS X 10.3.7 on Power MAC G5.
If yes, Do I have to set do nvram
boot-args="debug=0x08" ?
(DB_KPRT)
I learned from Kernel Programming.pdf .
I tried it, but I still get IOLog() messages in the
same file.
I believe this should work, if you have a serial port.
About the USB thing that some folks have mentioned, that won't work.
The kprintf requires a serial chip that is directly addressable because
it uses polled I/O (so that it can work with interrupts disabled).
That pretty much means that without a complete rewrite, you're pretty
much limited to the serial hardware on the main logic board, unless you
find a PCI card with a Zilog 8530 (in which case you'd probably still
need to hack the PCI drivers up a bit to guarantee that the device
didn't get remapped or anything...).
There are stealth cards for the first generation G5s available from
GeeThree.
If you have a second generation G5 (after the 2.5 GHz speed
bump), well... the stealth cards reportedly won't fit. I don't know
if they'll be doing a redesign for those or not (or even if it's
possible---you'd have to ask someone at GeeThree).
David
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden