[lkml]   [2000]   [Sep]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [DOC] Debugging early kernel hangs
On Sat, 23 Sep 2000, Russell King wrote:

> Keith Owens writes:
> > Something I forgot to mention about debugging using screen writes. If
> > the problem is caused by incorrect compiler output then even printk can
> > fail. Not because the C code is wrong but because the generated
> > assembler is wrong. Writing direct to screen memory is as simple as it
> > gets and gives the compiler little or no chance to get it wrong.
> And I'll try to make the point a second time that everything does not have
> a character-based screen to write to.

So what? For platforms which have a nice easy way to stick ASCII on
screen, use this. For other platforms, find some other approach - if you
have a nice easy serial port handy, try feeding the characters there.

This feature doesn't need to work identically on all platforms. It doesn't
even need to work on all platforms (although that would be nice).


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:38    [W:0.048 / U:9.164 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site