summaryrefslogtreecommitdiff
path: root/target/linux/lantiq
diff options
context:
space:
mode:
authorJohn Crispin <john@openwrt.org>2013-11-20 16:56:50 +0000
committerJohn Crispin <john@openwrt.org>2013-11-20 16:56:50 +0000
commit6c690bf15d5b2d29990be952ad3ac0bf06f7dd2a (patch)
tree39b1f97efad830537ff82b5c81649baef5177353 /target/linux/lantiq
parent1b3a423ad58a07b4173c0efbfc8f2b61277c26de (diff)
downloadmtk-20170518-6c690bf15d5b2d29990be952ad3ac0bf06f7dd2a.zip
mtk-20170518-6c690bf15d5b2d29990be952ad3ac0bf06f7dd2a.tar.gz
mtk-20170518-6c690bf15d5b2d29990be952ad3ac0bf06f7dd2a.tar.bz2
lantiq: fix etop registers
As first reported more than a year ago (https://lists.openwrt.org/pipermail/openwrt-devel/2012-August/016240.html and https://lists.openwrt.org/pipermail/openwrt-devel/2012-August/016241.html), some of the register definitions of the lantiq etop driver are incorrect. When OpenWrt is booted with a bootloader which doesn't do proper network initialization of its own (e.g. brnboot), ethernet won't work. The patch below changes the register names and addresses to match the lantiq etop driver included with the recent U-Boot. At the moment the MII/RMII setting in the lantiq .dts-files has no effect, since wrong registers are written. Once this patch is applied, it is necessary to make sure that the MII/RMII setting in the .dts-file is correct. v2: fix mangled whitespaces Signed-off-by: Matti Laakso <malaakso@elisanet.fi> SVN-Revision: 38880
Diffstat (limited to 'target/linux/lantiq')
0 files changed, 0 insertions, 0 deletions