mtk-20170518 - MTK 20170518 : Mediatek SDK based on OpenWRT Barrier Breaker

	Commit message (Collapse)	Author	Age	Files	Lines
*	bump some revisions and update copyrights	Andy Boyett	2009-09-10	1	-3/+3
\| \| \| \|	SVN-Revision: 17554
*	Added support for identifying the BCM53115 switch found in WRT610N.	Felix Fietkau	2009-08-28	1	-2/+4
\| \| \| \| \| \|	Signed-off-by: Tomas Kopal <Tomas.Kopal@altap.cz> SVN-Revision: 17433
*	brcm-2.4: nvram_set has been removed, remove some remaining calls to it	Felix Fietkau	2009-05-16	1	-7/+0
\| \| \| \|	SVN-Revision: 15878
*	get rid of $Id$ - it has never helped us and it has broken too many patches ;)	Felix Fietkau	2009-04-17	15	-15/+0
\| \| \| \|	SVN-Revision: 15242
*	replace some -I & -L flags with $(TARGET_CPPFLAGS) & $(TARGET_LDFLAGS) when ↵	Nicolas Thill	2009-02-24	1	-3/+4
\| \| \| \| \| \|	appropriate SVN-Revision: 14651
*	remove some unused crap	Felix Fietkau	2008-06-15	12	-2361/+0
\| \| \| \|	SVN-Revision: 11472
*	(6/6) bcm57xx: package	Felix Fietkau	2008-06-15	40	-0/+27527
	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