Messages in this thread | | | Date | Wed, 27 Mar 2024 15:12:33 +0200 | From | Andy Shevchenko <> | Subject | Re: [PATCH printk v2 08/26] printk: nbcon: Implement processing in port->lock wrapper |
| |
On Wed, Mar 27, 2024 at 10:38:15AM +0106, John Ogness wrote: > On 2024-03-22, Tony Lindgren <tony@atomide.com> wrote: > > * John Ogness <john.ogness@linutronix.de> [240313 09:50]: > >> One nice thing that has risen from this is we are starting to see > >> exactly what the console lock is needed for. At this point I would say > >> its main function is synchronizing boot consoles with real > >> drivers. Which means we will not be able to remove the console lock > >> until we find a real solution to match boot consoles (which circumvent > >> the Linux driver model) with the real drivers. > > > > Would it help if earlycon handles all the boot consoles? > > Then just have the serial driver take over when it probes? > > I think this would be very helpful. And it would also cleanup the boot > arguments. For example, we would no longer need the > architecture-specific arguments/options (such as "early_printk" and > "keep"). These architecture-specific arguments can be really > confusing.
You may not get rid of earlyprintk as it affects *very* early at boot, earlycon is simply not and may not be available at these stages.
-- With Best Regards, Andy Shevchenko
| |