Messages in this thread | | | From | John Ogness <> | Subject | Re: [PATCH printk v2 08/26] printk: nbcon: Implement processing in port->lock wrapper | Date | Wed, 13 Mar 2024 10:55:47 +0106 |
| |
On 2024-03-11, John Ogness <john.ogness@linutronix.de> wrote: > And I think you identified a bug relating to the setup() callback.
Actually this bug was recently fixed by Peter Collingbourne:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/kernel/printk/printk.c?h=next-20240313&id=801410b26a0e8b8a16f7915b2b55c9528b69ca87
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.
John
| |