Post #1539650
2026-04-01 16:07 UTC
@samueldr So I'm already reworking this to pick the right index on x86 since they're statically allocated there. You're right that on arm we can't really know for sure. I kept it for now to pick ttyAMA0 if we find a single serial console.
As for the graphical console, you're of course right that this breaks if the uefi firmware can't detect the graphics output. I guess I could make it opt-in to avoid breaking existing use cases.
Replies (1)
-
@samueldr@ap.samueldr.com 2026-04-01 16:34
@daandemeyer not sure if applicable, but you might prefer not relying on tty.*\d identifiers, and instead use either the device paths or the variants with specific addressing: https://github.com/torvalds/linux/blob/9147566d801602c9e7fc7f85e989735735bf38ba/Documentation/admin-guide/kernel-parameters.txt#L959-L991 It would require double-checking whether or not the other earlycon parameter values work for console=, and when lacking console= if earlycon ends-up being preferred when provided. https://github.com/torvalds/linux/blob/9147566d801602c9e7fc7f85e989735735bf38ba/Documentation/admin-guide/kernel-parameters.txt#L1429