This patch makes it possible to reset and enable writing vlans to recent switchs.
This is based on a patch by jcharest and the Broadcom SDK.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@35585 3c298f89-4303-0410-b956-a3cf2f4a3e73
This patch makes it possible to read and write the vlan config from and to recent switchs.
This is based on a patch by jcharest and the Broadcom SDK.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@35584 3c298f89-4303-0410-b956-a3cf2f4a3e73
This makes it easier to compare this code with the code from the Broadcom SDK.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@35580 3c298f89-4303-0410-b956-a3cf2f4a3e73
Switch to using the B53 switch driver where appropriate.
Use a non-tagged default config where it isn't confirmed to be
working.
Remove the switch configuration in preinit as the switch will now
be configured by the driver to use port isolation to prevent leakage
between lan and wan.
While at it, also provide a switch config for Neufbox 6.
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@35307 3c298f89-4303-0410-b956-a3cf2f4a3e73
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>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@34992 3c298f89-4303-0410-b956-a3cf2f4a3e73
This is in part based on a patch send by Nathan Hintz <nlhintz@hotmail.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@34991 3c298f89-4303-0410-b956-a3cf2f4a3e73
This is the version like it was send for mainline inclusion.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@34988 3c298f89-4303-0410-b956-a3cf2f4a3e73
* remove use_et, all supported drivers are using mii ioctls
* remove robo.phy_addr, phy_addr was always set to ROBO_PHY_ADDR.
* remove support for old kernel versions
* do_ioctl is allways called with buff == NULL
* use if_mii
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33002 3c298f89-4303-0410-b956-a3cf2f4a3e73
Since the removal of the interface coldplug hack the timing changed in such a way that eth0 is not up during switch setup,
leading to an inaccesible device. Bring up the switch interface before configuring it to mitigate the problem.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@30937 3c298f89-4303-0410-b956-a3cf2f4a3e73
eliminate the asterisk from the switch port configuration and set it
automatically on the first vlan, this aligns the broadcom vlan config
with the swconfig format
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@19909 3c298f89-4303-0410-b956-a3cf2f4a3e73
This is completly untested. Only a compile tests with the default config was done!
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@17734 3c298f89-4303-0410-b956-a3cf2f4a3e73
This patch prevents switch-robo.c from attempting robo_probe on a port
that is already registered. robo_probe will adjust kernel reference counts
if it detects a switch on the port. If this patch wasn't applied, the
wrt350n would hang on reboot, waiting for the network driver reference count
to reach zero indefinitely.
Signed-off-by: Ben Pfountz <netprince (at) vt (dot) edu>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@11469 3c298f89-4303-0410-b956-a3cf2f4a3e73