aboutsummaryrefslogtreecommitdiffstats
path: root/package/libs/lzo
diff options
context:
space:
mode:
authorNick Hainke <vincent@systemli.org>2020-10-25 15:25:01 +0100
committerAdrian Schmutzler <freifunk@adrianschmutzler.de>2020-11-03 18:34:04 +0100
commit50a76208bcce98977615d8048f7655aa2f49cf38 (patch)
treeab2043744be40ca8dcf3e70787f57146c5622bd9 /package/libs/lzo
parentf5772d71a41914d40fec21f6111c1b39eea32d4c (diff)
downloadupstream-50a76208bcce98977615d8048f7655aa2f49cf38.tar.gz
upstream-50a76208bcce98977615d8048f7655aa2f49cf38.tar.bz2
upstream-50a76208bcce98977615d8048f7655aa2f49cf38.zip
ath79: fix nanobeam ac ethernet interface
In 4.14 the delays were not cleared, so setting "rgmii" as phy-mode did not affect delays set by the bootloader. With 5.4 kernel the situation changed and the ethernet interface stopped working. "rgmii" requires rx and tx delays depending on the hardware circuit and wiring. The mac or the phy can add these delays. - "rgmii": delays are controlled by the mac - "rgmii-id": delays are controlled by the phy More Information in Linux Kernel Tree: Documentation/devicetree/bindings/net/ethernet-controller.yaml "rgmii" should be the preferred mode, which allows the mac layer to turn off the dealys completely if they are not needed. However, the delays are not set correctly, which causes the ethernet interface to be broken. Just taking the ethernetpart from the litebeam ac gen2 will fix the issue. Explained-by: David Bauer <mail@david-bauer.net> Signed-off-by: Nick Hainke <vincent@systemli.org>
Diffstat (limited to 'package/libs/lzo')
0 files changed, 0 insertions, 0 deletions