mirror of
git://projects.qi-hardware.com/openwrt-xburst.git
synced 2024-09-12 17:50:14 +03:00
128434cb23
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
18 lines
453 B
Makefile
18 lines
453 B
Makefile
#
|
|
# Broadcom BCM57XX Gigabit Ethernet driver make file.
|
|
#
|
|
# $Id: Makefile,v 1.1.1.4 2006/09/26 02:17:12 michael Exp $
|
|
#
|
|
|
|
O_TARGET = bcm57xx.o
|
|
|
|
EXTRA_CFLAGS += -DDBG=0 -DBCM_PROC_FS=1 -DT3_JUMBO_RCV_RCB_ENTRY_COUNT=256
|
|
EXTRA_CFLAGS += -DPCIX_TARGET_WORKAROUND=1 -DINCLUDE_TBI_SUPPORT=1 -DINCLUDE_5701_AX_FIX=1
|
|
|
|
export-objs :=
|
|
|
|
obj-y := b57um.o tigon3.o autoneg.o 5701rls.o tcp_seg.o hndgige.o bcmrobo.o
|
|
obj-m := $(O_TARGET)
|
|
|
|
include $(TOPDIR)/Rules.make
|