diff options
author | Felix Fietkau <nbd@openwrt.org> | 2008-06-15 11:11:28 +0000 |
---|---|---|
committer | Felix Fietkau <nbd@openwrt.org> | 2008-06-15 11:11:28 +0000 |
commit | 567993fa4c6001197e3e25a57a4a0d718c372952 (patch) | |
tree | 628e1de7f62f279d851f47ad1ee6ab63c320c1c8 /include | |
parent | d6b78c826aa67fb04e34c69c1b41eed843462bab (diff) | |
download | master-187ad058-567993fa4c6001197e3e25a57a4a0d718c372952.tar.gz master-187ad058-567993fa4c6001197e3e25a57a4a0d718c372952.tar.bz2 master-187ad058-567993fa4c6001197e3e25a57a4a0d718c372952.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>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@11471 3c298f89-4303-0410-b956-a3cf2f4a3e73
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions