summaryrefslogtreecommitdiff
path: root/package/broadcom-57xx/Makefile
Commit message (Collapse)AuthorAgeFilesLines
* remove broadcom-57xx (only used on linux 2.4)Felix Fietkau2010-06-261-51/+0
| | | | SVN-Revision: 21953
* bump some revisions and update copyrightsAndy Boyett2009-09-101-3/+3
| | | | SVN-Revision: 17554
* get rid of $Id$ - it has never helped us and it has broken too many patches ;)Felix Fietkau2009-04-171-1/+0
| | | | SVN-Revision: 15242
* replace some -I & -L flags with $(TARGET_CPPFLAGS) & $(TARGET_LDFLAGS) when ↵Nicolas Thill2009-02-241-3/+4
| | | | | | appropriate SVN-Revision: 14651
* (6/6) bcm57xx: packageFelix Fietkau2008-06-151-0/+51
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