diff options
| author | Felix Fietkau <nbd@openwrt.org> | 2008-06-15 11:11:28 +0000 |
|---|---|---|
| committer | Felix Fietkau <nbd@openwrt.org> | 2008-06-15 11:11:28 +0000 |
| commit | ddd809f9e56e3a30d459d6189a1582808d204821 (patch) | |
| tree | 42452684184365d849557d88c0a7155f32287ad3 /package/broadcom-57xx/Makefile | |
| parent | 20937ce81a7807fb3506728edaaff731cee7e18c (diff) | |
| download | upstream-ddd809f9e56e3a30d459d6189a1582808d204821.tar.gz upstream-ddd809f9e56e3a30d459d6189a1582808d204821.tar.bz2 upstream-ddd809f9e56e3a30d459d6189a1582808d204821.zip | |
(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
Diffstat (limited to 'package/broadcom-57xx/Makefile')
| -rw-r--r-- | package/broadcom-57xx/Makefile | 51 |
1 files changed, 51 insertions, 0 deletions
diff --git a/package/broadcom-57xx/Makefile b/package/broadcom-57xx/Makefile new file mode 100644 index 0000000000..172074ca35 --- /dev/null +++ b/package/broadcom-57xx/Makefile @@ -0,0 +1,51 @@ +# +# Copyright (C) 2006 OpenWrt.org +# +# This is free software, licensed under the GNU General Public License v2. +# See /LICENSE for more information. +# +# $Id: Makefile 8694 2007-09-08 19:55:42Z nbd $ + +include $(TOPDIR)/rules.mk +include $(INCLUDE_DIR)/kernel.mk + +PKG_NAME:=broadcom-57xx +PKG_RELEASE:=1 + +include $(INCLUDE_DIR)/package.mk + +define KernelPackage/brcm-57xx + SUBMENU:=Network Devices + DEPENDS:=@TARGET_brcm_2_4 +kmod-switch + TITLE:=Broadcom 57xx ethernet support + FILES:=$(PKG_BUILD_DIR)/bcm57xx.$(LINUX_KMOD_SUFFIX) + AUTOLOAD:=$(call AutoLoad,30,bcm57xx) +endef + +define Build/Prepare + mkdir -p $(PKG_BUILD_DIR) + $(CP) ./src/* $(PKG_BUILD_DIR)/ +endef + +ifeq ($(BOARD),brcm-2.4) + BUILDFLAGS = -DBCMDRIVER -I$(LINUX_DIR)/arch/mips/bcm947xx/include -I$(STAGING_DIR)/usr/include + BUILDFLAGS += -DDBG=0 -DBCM_PROC_FS=1 -DT3_JUMBO_RCV_RCB_ENTRY_COUNT=256 -DNICE_SUPPORT + BUILDFLAGS += -DPCIX_TARGET_WORKAROUND=1 -DINCLUDE_TBI_SUPPORT=1 -DINCLUDE_5701_AX_FIX=1 +endif + +define Build/Compile + $(MAKE) -C "$(LINUX_DIR)" \ + CROSS_COMPILE="$(TARGET_CROSS)" \ + ARCH="$(LINUX_KARCH)" \ + SUBDIRS="$(PKG_BUILD_DIR)" \ + EXTRA_CFLAGS="$(BUILDFLAGS)" \ + modules +endef + +define KernelPackage/brcm-57xx/install + $(call Package/brcm-57xx/install/Default,$(1)) + #$(INSTALL_DIR) $(1)/etc/modules.d + #echo "bcm57xx activate_gpio=1" > $(1)/etc/modules.d/30-bcm57xx +endef + +$(eval $(call KernelPackage,brcm-57xx)) |