summaryrefslogtreecommitdiff
path: root/scripts/objdiff
diff options
context:
space:
mode:
authorAhmad Fatoum <a.fatoum@pengutronix.de>2026-06-11 20:12:35 +0200
committerAlexandre Torgue <alexandre.torgue@foss.st.com>2026-08-10 10:38:17 +0200
commitdd4c4b1231b4b3ce97f94daa6f3874040b8b8302 (patch)
tree416fb43b5658254e395605883abf58337c9d99a4 /scripts/objdiff
parente78fba2ce1682ed52058fba358840194463ba9a9 (diff)
downloadlinux-next-dd4c4b1231b4b3ce97f94daa6f3874040b8b8302.tar.gz
linux-next-dd4c4b1231b4b3ce97f94daa6f3874040b8b8302.zip
ARM: dts: stm32: fairytux2: change stdout-path baud rate from 9600 to 115200
The default baud rate when none is specified is up to the DT consumer. In the case of the Linux STM32 serial driver, it defaults to 9600 baud, which differs from the 115200 baud that this board's barebox bootloader configured. This went unnoticed, because barebox automatically fixes up a console= command-line option that looks like this on the LXA boards: console=ttySTM0,115200n8 This had precedence over the 9600 fallback baud rate. But when EFI booting a kernel via GRUB, we run into this issue, because the barebox-provided command-line is disregarded by GRUB. Fix this by explicitly setting the baud rate to the correct 115200. Fixes: 8c6d469f5249 ("ARM: dts: stm32: lxa-fairytux2: add Linux Automation GmbH FairyTux 2") Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.kernel.org/r/20260611-lxa-stdout-path-baudrate-v1-3-59b60a5069ff@pengutronix.de Signed-off-by: Alexandre Torgue <alexandre.torgue@foss.st.com>
Diffstat (limited to 'scripts/objdiff')
0 files changed, 0 insertions, 0 deletions