On 31 Jan 2025, at 07:25, Mikko Rapeli <mikko.rap...@linaro.org> wrote: > ACK, we have also found that systemd and udev handle serial consoles > correctly when supporting multiple devices like rockpi4b, synquacer, > AMD KV260, zcu102, AVA, qemu etc from a single build.
The challenge is doing the same for sysvinit… Sharing for the wider community: genericarm64 defines SERIAL_CONSOLES to hvc0 (if its inside a qemu), ttyAMA0 (hardware using the Arm PL011 uart), and ttyS[0-2] (other hardware using serial ports). It has to be the first three serial ports because hardware is different: specifically the BeaglePlay has the Linux console on ttyS2 as two internal uarts that connect to the expansion port are 0 and 1. However, throwing a getty on ttyS1 doesn’t go well, but there doesn’t appear to be a good way to know that from userspace. My current best idea is to replicate the logic in systemd inside syvinit somehow, but that’s… not trivial. Possibly a shell wrapper that init starts and it forks off gettys, respawning them as needed? It’s almost easier to extend sysvinit so that it can start inittab lines dynamically. Ross
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#210490): https://lists.openembedded.org/g/openembedded-core/message/210490 Mute This Topic: https://lists.openembedded.org/mt/110901815/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
