summaryrefslogtreecommitdiffstats
path: root/c/src/lib/libcpu
diff options
context:
space:
mode:
authorJoel Sherrill <joel.sherrill@OARcorp.com>1998-08-24 16:58:39 +0000
committerJoel Sherrill <joel.sherrill@OARcorp.com>1998-08-24 16:58:39 +0000
commit69036586b5807eaf78f2a9e123d88a54b2338a25 (patch)
tree76e0e53a6b7f6c04adad8cb9214fd3bf08cb190a /c/src/lib/libcpu
parentRegenerated (diff)
downloadrtems-69036586b5807eaf78f2a9e123d88a54b2338a25.tar.bz2
Patch from Eric Valette <valette@crf.canon.fr>:
Celso Labinaz <labinaz@tin.it> pointed to me thatthe console on serial line was not working. After spending quite a time to find the right cable and software, I confirm this. I'm going to debug this in the next days because I want to use the serial line for debugging. In the meantime, in order to be sure that this was a driver initialization/bug, I made printk work on the serial line in order to be sure the receiver part and configuration was OK. Here is the for printk on serial line. BTW, does anyone else use the serial line facilities for PC? printf seems to output nothing (hello.exe output everything that has a printk but application printf seems to be broken).
Diffstat (limited to 'c/src/lib/libcpu')
0 files changed, 0 insertions, 0 deletions