On Fri, 2020-02-28 at 17:59 +0300, Alper Nebi Yasak wrote: > On 27/02/2020 02:10, Ben Hutchings wrote: > > A device that is intended to be used with keyboard and video display > > should not have this in the device tree for production units. If we > > ship the device tree then we can correct that. If not, then the boot > > loader should be configured to override it, and the installer could do > > that by default. > > I'm using rk3399-gru-kevin.dtb from the Debian package. The stdout-path > property comes from arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi in the > kernel tree. Setting a serial console this way seems to be ordinary, a > lot of other devices have it too. I think most devices for which the kernel provides the device tree are development boards, so a serial console is a fairly sensible default for them. It sounds like this should be changed for the "kevin" board. > For the bootloader (part of the firmware), I don't know if there is a > way to make it change that property in the device-tree file. Yes, it is normal for the boot loader to modify the device tree after loading it. For example, to set the kernel command line or memory size. > Meanwhile > I've added "console=tty0" to the default cmdline my bootloader-handler > project uses, so everything should be fine for now. > > > I don't think it makes sense for initramfs-tools to do this, as the > > wrong default console will still affect other software. > > I intended to say that maybe initramfs-tools should correct the default > console to the virtual console not just for itself but for the entire > userspace. (I don't even know if that's possible.) Right, but I don't think it is possible. Ben. -- Ben Hutchings If more than one person is responsible for a bug, no one is at fault.
Attachment:
signature.asc
Description: This is a digitally signed message part