On Wed, 2016-07-20 at 18:16 -0700, Andy Lutomirski wrote:
> If we do all this stuff, can we also try to clean up earlyprintk a
> bit?  The whole earlyconsole mechanism is a mess, and switching over
> to the non-early console is only somewhat functional.  I'd love to see
> this all simplified: before there's any console at all available, just
> buffer messages.  Then, when a console shows up, write the buffer out.
> Then earlyprintk can work just like regular printk.

That's exactly what we already do. Look at the CON_PRINTBUFFER flag.

I never did understand why "earlyprintk" was introduced as such a nasty
special-case hack in the first place. There were various minor excuses
for doing so, but nothing insurmountable IIRC.

I would *love* to kill it completely and simplify the whole thing.

-- 
David Woodhouse                            Open Source Technology Centre
David.Woodhouse@intel.com                              Intel Corporation