Re: [microblaze-uclinux] early printk support for microblaze

[John Williams <jwilliams@xxxxxxxxxxxxxx>]

Yasushi SHOJI wrote:
> 
> if you apply the patch it produce boot log like the above. note that
> the top part of boot log is duplicated. The reason I said was that I
> misunderstood what CON_PRINTBUFFER is for.
> 
> it might be better to redirect early printk's out put to debug uart if
> the platform has one.  what do you think?

OK, i'm slowly catching up!  Sorry, I'd never heard of early printk 
before - but a google search suggests it's a capability to use printk() 
before the kernel calls console_init(), is that right?

What I don't understand, is why it is necessary?  Any printk() output 
that is sent before calling console_init() gets buffered, and is output 
eventually.

Or should pre-console_init() printk's be output immediately, in case the 
kernel hangs/crashes before console_init()?

Thanks,

John


___________________________
microblaze-uclinux mailing list
microblaze-uclinux@itee.uq.edu.au
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/