On Sat, 23 Sep 2000 12:42:13 +0200, Benjamin Herrenschmidt <[EMAIL PROTECTED]> wrote: >However, there's still a huge gap between the last progress() message and >availability of the frame buffer device. The simple console has the >advantage of outputing existing printk messages. (basically, it's a >console using prom_printf). 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. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- [DOC] Debugging early kernel hangs Keith Owens
- Re: [DOC] Debugging early kernel hangs Byron Stanoszek
- Re: [DOC] Debugging early kernel hangs Keith Owens
- Re: [DOC] Debugging early kernel hangs Oliver Xymoron
- Re: [DOC] Debugging early kernel hangs Russell King
- Re: [DOC] Debugging early kernel hangs Benjamin Herrenschmidt
- Re: [DOC] Debugging early kernel hangs Daniel Phillips
- Re: [DOC] Debugging early kernel hangs Benjamin Herrenschmidt
- Re: [DOC] Debugging early kernel hangs Keith Owens
- Re: [DOC] Debugging early kernel hangs Russell King
- Re: [DOC] Debugging early kernel h... James Sutherland
- Re: [DOC] Debugging early ker... Russell King
- Re: [DOC] Debugging early... James Sutherland
- Re: [DOC] Debugging early kernel hangs Thorsten Kranzkowski
- Re: [DOC] Debugging early kernel h... Keith Owens
- Re: [DOC] Debugging early kernel h... Pavel Machek
- Re: [DOC] Debugging early kernel hangs Martin J. Bligh