summaryrefslogtreecommitdiffstats
path: root/package/broadcom-57xx/src/bcmrobo.c
Commit message (Collapse)AuthorAgeFilesLines
* brcm-2.4: nvram_set has been removed, remove some remaining calls to itnbd2009-05-161-7/+0
| | | | git-svn-id: svn://svn.openwrt.org/openwrt/trunk@15878 3c298f89-4303-0410-b956-a3cf2f4a3e73
* (6/6) bcm57xx: packagenbd2008-06-151-0/+1329
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