aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux
diff options
context:
space:
mode:
authorChristian Lamparter <chunkeey@gmail.com>2018-10-15 20:00:07 +0200
committerHauke Mehrtens <hauke@hauke-m.de>2018-10-20 16:13:39 +0200
commit9ca82c2374e008f288c90066a7f2c2581c584c7e (patch)
tree3cbd26633fb9e66fdde1ca7a5a9e54a76318646c /target/linux
parent68bb91018df1c3d9474041a4d55e1cfd66022522 (diff)
downloadupstream-9ca82c2374e008f288c90066a7f2c2581c584c7e.tar.gz
upstream-9ca82c2374e008f288c90066a7f2c2581c584c7e.tar.bz2
upstream-9ca82c2374e008f288c90066a7f2c2581c584c7e.zip
apm821xx: force WNDR4700 console to 115200n8
With the upcoming 4.19 release, the serial console on the Netgear WNDR4700 would no longer work as it is never really set and always relied on the kernel's serial code not to change the baud rate. On the stock firmware, Netgear forced the console setting through a custom CONFIG_CMDLINE in their kernel to 115200. Normally, they should have done it in a different way and just passed the baudrate through a "console=..." kernel parameter via the bootargs in the "/chosen" dt node. But in their default u-boot bootcmd setting, they somehow forgot to add the "run addtty", so there's no easy way to pass the baudrate from u-boot to the kernel. So it has to be forced as otherwise it ends up as 9600 baud. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
Diffstat (limited to 'target/linux')
-rw-r--r--target/linux/apm821xx/dts/netgear-wndr4700.dts2
1 files changed, 1 insertions, 1 deletions
diff --git a/target/linux/apm821xx/dts/netgear-wndr4700.dts b/target/linux/apm821xx/dts/netgear-wndr4700.dts
index 171b7e34d6..a8f73e8a04 100644
--- a/target/linux/apm821xx/dts/netgear-wndr4700.dts
+++ b/target/linux/apm821xx/dts/netgear-wndr4700.dts
@@ -26,7 +26,7 @@
};
chosen {
- stdout-path = "/plb/opb/serial@ef600300";
+ stdout-path = "/plb/opb/serial@ef600300:115200n8";
};
thermal-zones {