summaryrefslogtreecommitdiff
path: root/target/linux/lantiq/image/eva.dummy.squashfs
diff options
context:
space:
mode:
authorHauke Mehrtens <hauke@hauke-m.de>2013-01-03 01:58:01 +0000
committerHauke Mehrtens <hauke@hauke-m.de>2013-01-03 01:58:01 +0000
commitd8f1fa1e382050139006e0f03000275e639d09fe (patch)
tree3a6b684b039b93682bbe7159bbd7df61cb06300b /target/linux/lantiq/image/eva.dummy.squashfs
parent63ec34612cec4b0357d9baff3745825d3c5d544b (diff)
downloadmtk-20170518-d8f1fa1e382050139006e0f03000275e639d09fe.zip
mtk-20170518-d8f1fa1e382050139006e0f03000275e639d09fe.tar.gz
mtk-20170518-d8f1fa1e382050139006e0f03000275e639d09fe.tar.bz2
switch: ROBO Switch Gigabit MII Support
I wrote this patch some time ago because I had a need for one of the Gigabit ports (Linksys E3000) to be forced to 100FD. This is based on the robocfg sources included w/ the RT-N16 sources from ASUS. Since work is progressing on a BGMAC driver that could be included in OpenWRT, this may be useful to someone else. In testing, forcing the speed to 10/100 or 1000 worked fine; however, when trying to force full-duplex mode, the result was always half-duplex. I was not able to isolate the source of the problem (this patch, driver or H/W limitation). The only way I could get it to work was to set the port to Auto, but then only advertise 100FD (not included in this patch). I have a modified version of the robocfg package as well, I'd have to clean it up a little first (remove the full-duplex hack) before submitting it if there is interest. Signed-off-by: Nathan Hintz <nlhintz@hotmail.com> SVN-Revision: 34992
Diffstat (limited to 'target/linux/lantiq/image/eva.dummy.squashfs')
0 files changed, 0 insertions, 0 deletions