5 Commits (5399ba975151551e37faf709949adb5729ea039a)

Author	SHA1	Message	Date
Felix Fietkau	453c3b8fc0	Added support for identifying the BCM53115 switch found in WRT610N. ... Signed-off-by: Tomas Kopal <Tomas.Kopal@altap.cz> SVN-Revision: 17433	2009-08-28 14:20:37 +00:00
Felix Fietkau	8567c34340	brcm-2.4: nvram_set has been removed, remove some remaining calls to it ... SVN-Revision: 15878	2009-05-16 20:02:17 +00:00
Felix Fietkau	34939cad39	get rid of $Id$ - it has never helped us and it has broken too many patches ;) ... SVN-Revision: 15242	2009-04-17 14:09:46 +00:00
Felix Fietkau	f2e997ac38	remove some unused crap ... SVN-Revision: 11472	2008-06-15 11:15:35 +00:00
Felix Fietkau	ddd809f9e5	(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	2008-06-15 11:11:28 +00:00