aboutsummaryrefslogtreecommitdiffstats
path: root/include
diff options
context:
space:
mode:
authorFelix Fietkau <nbd@openwrt.org>2008-06-15 11:11:28 +0000
committerFelix Fietkau <nbd@openwrt.org>2008-06-15 11:11:28 +0000
commitddd809f9e56e3a30d459d6189a1582808d204821 (patch)
tree42452684184365d849557d88c0a7155f32287ad3 /include
parent20937ce81a7807fb3506728edaaff731cee7e18c (diff)
downloadupstream-ddd809f9e56e3a30d459d6189a1582808d204821.tar.gz
upstream-ddd809f9e56e3a30d459d6189a1582808d204821.tar.bz2
upstream-ddd809f9e56e3a30d459d6189a1582808d204821.zip
(6/6) bcm57xx: package
This is the bcm57xx package. I have tested default vlan functions, but I dont have the equipment to test more advanced setups. The default vlan setup seems to be working fine. I also added the activate_gpio parameter which will make the driver activate the switch via gpio before probing for it. I'm not sure which method is best for autoload. For the wrt350n, I need the activate_gpio parameter. But its probably not a good idea to add that to the autoload file. On a system without a bcm57xx switch, isn't it a bad idea to mess with the gpios looking for the switch? Ideally, wouldn't it be best to load the bcm57xx module from broadcom-diag, after it has determined which router its on? I tried using 'request_module' from there, but had no success. For now, I am relying on preinit to load the bcm57xx module with activate_gpio param, after it has failed to load switch_robo and switch_adm. Signed-off-by: Ben Pfountz <netprince (at) vt (dot) edu> SVN-Revision: 11471
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions