hello;
rtlinux takes over the interrupts from linux.
printk causes an interrupt so it can display
to the console, be output the serial port, and/or
logged to a /var/log/ log file. this causes race
conditions and a catch-22. debugging an interrupt
handler with printks is sort of self-defeating.
that is why there is the rtl_printf.
On Thu, 16 Nov 2000, Pfistner wrote:
>Hi folks,
>Maybe I just missed something:
>Upgrading from rtl2.0 to rtl2.2 I got the problem that my printk commands
>within the thread of rtl2.2 seemed to freeze my machine.
>
>Well, now I use rtl_printf within my thread (it took some time to track this
>down ...) and everything is fine now.
>
>
>Now I'm curios :-?
>I didn't find any hints in the docs.
>
>Any explanations?
>
>ThanX,
>Norbert
>
--
Terry L. Ridder
Blue Danube Software (Blaue Donau Software)
"We do not write software, we compose it."
digging deep, i feel my conscience burn
i need to know who and what i am
this hunger jolts me from complacency
rocks me, makes me meet myself
----kendall payne---closer to myself---
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
---
For more information on Real-Time Linux see:
http://www.rtlinux.org/rtlinux/
