Re: [OpenWrt-Devel] [PATCH 16/30][ WRT1900AC ] mamba mvebu: sysupgrade support for mamba + dual boot
On Friday 09 May 2014 14:11:32 Karl Palsson wrote: > I understand how it works in general, John was nacking the support as it > duplicated existing functionality. I was asking more about this existing > functionality within openwrt for supporting dual firmware images. I wasn't > aware of any existing functionality for this. Check target/linux/ar71xx/base-files/lib/upgrade/openmesh.sh. All OpenMesh boards provide exactly this kind of upgrade behavior. Cheers, Marek ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] brcm47xx: profiles: fix white spaces (s/ $//)
Signed-off-by: Rafał Miłecki --- target/linux/brcm47xx/profiles/100-Broadcom-b43.mk| 4 ++-- target/linux/brcm47xx/profiles/101-Broadcom-wl.mk | 4 ++-- target/linux/brcm47xx/profiles/104-Broadcom-ath5k.mk | 4 ++-- target/linux/brcm47xx/profiles/105-Broadcom-none.mk | 2 +- target/linux/brcm47xx/profiles/200-Broadcom-b44-b43.mk| 4 ++-- target/linux/brcm47xx/profiles/201-Broadcom-b44-wl.mk | 4 ++-- target/linux/brcm47xx/profiles/204-Broadcom-b44-ath5k.mk | 4 ++-- target/linux/brcm47xx/profiles/205-Broadcom-b44-none.mk | 2 +- target/linux/brcm47xx/profiles/211-Broadcom-tg3-wl.mk | 2 +- target/linux/brcm47xx/profiles/220-Broadcom-bgmac-b43.mk | 2 +- target/linux/brcm47xx/profiles/221-Broadcom-bgmac-wl.mk | 4 ++-- target/linux/brcm47xx/profiles/225-Broadcom-bgmac-none.mk | 2 +- 12 files changed, 19 insertions(+), 19 deletions(-) diff --git a/target/linux/brcm47xx/profiles/100-Broadcom-b43.mk b/target/linux/brcm47xx/profiles/100-Broadcom-b43.mk index b50e305..4c420fb 100644 --- a/target/linux/brcm47xx/profiles/100-Broadcom-b43.mk +++ b/target/linux/brcm47xx/profiles/100-Broadcom-b43.mk @@ -11,8 +11,8 @@ define Profile/Broadcom-b43 endef define Profile/Broadcom-b43/Description - Package set compatible with hardware any Broadcom BCM47xx or BCM535x - SoC with Broadcom BCM43xx Wifi cards using the mac80211, b43 and + Package set compatible with hardware any Broadcom BCM47xx or BCM535x + SoC with Broadcom BCM43xx Wifi cards using the mac80211, b43 and b43legacy drivers and b44, tg3 or bgmac Ethernet driver. endef diff --git a/target/linux/brcm47xx/profiles/101-Broadcom-wl.mk b/target/linux/brcm47xx/profiles/101-Broadcom-wl.mk index e06ceb0..21265da 100644 --- a/target/linux/brcm47xx/profiles/101-Broadcom-wl.mk +++ b/target/linux/brcm47xx/profiles/101-Broadcom-wl.mk @@ -11,8 +11,8 @@ define Profile/Broadcom-wl endef define Profile/Broadcom-wl/Description - Package set compatible with hardware any Broadcom BCM47xx or BCM535x - SoC with Broadcom BCM43xx Wifi cards using the proprietary Broadcom + Package set compatible with hardware any Broadcom BCM47xx or BCM535x + SoC with Broadcom BCM43xx Wifi cards using the proprietary Broadcom wireless "wl" driver and b44, tg3 or bgmac Ethernet driver. endef diff --git a/target/linux/brcm47xx/profiles/104-Broadcom-ath5k.mk b/target/linux/brcm47xx/profiles/104-Broadcom-ath5k.mk index cd6b10b..ca5295f 100644 --- a/target/linux/brcm47xx/profiles/104-Broadcom-ath5k.mk +++ b/target/linux/brcm47xx/profiles/104-Broadcom-ath5k.mk @@ -11,8 +11,8 @@ define Profile/Broadcom-ath5k endef define Profile/Broadcom-ath5k/Description - Package set compatible with hardware any Broadcom BCM47xx or BCM535x - SoC with Atheros Wifi cards using the mac80211 and ath5k drivers and + Package set compatible with hardware any Broadcom BCM47xx or BCM535x + SoC with Atheros Wifi cards using the mac80211 and ath5k drivers and b44, tg3 or bgmac Ethernet driver. endef $(eval $(call Profile,Broadcom-ath5k)) diff --git a/target/linux/brcm47xx/profiles/105-Broadcom-none.mk b/target/linux/brcm47xx/profiles/105-Broadcom-none.mk index 7917d35..301d02a 100644 --- a/target/linux/brcm47xx/profiles/105-Broadcom-none.mk +++ b/target/linux/brcm47xx/profiles/105-Broadcom-none.mk @@ -11,7 +11,7 @@ define Profile/Broadcom-none endef define Profile/Broadcom-none/Description - Package set compatible with hardware any Broadcom BCM47xx or BCM535x + Package set compatible with hardware any Broadcom BCM47xx or BCM535x SoC without any Wifi cards and b44, tg3 or bgmac Ethernet driver. endef $(eval $(call Profile,Broadcom-none)) diff --git a/target/linux/brcm47xx/profiles/200-Broadcom-b44-b43.mk b/target/linux/brcm47xx/profiles/200-Broadcom-b44-b43.mk index f246a3a..662a7c8 100644 --- a/target/linux/brcm47xx/profiles/200-Broadcom-b44-b43.mk +++ b/target/linux/brcm47xx/profiles/200-Broadcom-b44-b43.mk @@ -11,8 +11,8 @@ define Profile/Broadcom-b44-b43 endef define Profile/Broadcom-b44-b43/Description - Package set compatible with hardware older Broadcom BCM47xx or BCM535x - SoC with Broadcom BCM43xx Wifi cards using the mac80211, b43 and + Package set compatible with hardware older Broadcom BCM47xx or BCM535x + SoC with Broadcom BCM43xx Wifi cards using the mac80211, b43 and b43legacy drivers and b44 Ethernet driver. endef diff --git a/target/linux/brcm47xx/profiles/201-Broadcom-b44-wl.mk b/target/linux/brcm47xx/profiles/201-Broadcom-b44-wl.mk index 83dd596..f974c00 100644 --- a/target/linux/brcm47xx/profiles/201-Broadcom-b44-wl.mk +++ b/target/linux/brcm47xx/profiles/201-Broadcom-b44-wl.mk @@ -11,8 +11,8 @@ define Profile/Broadcom-b44-wl endef define Profile/Broadcom-b44-wl/Description - Package set compatible with hardware older Broadcom BCM47xx or BCM535x - SoC with Broa
[OpenWrt-Devel] [PATCH 1/2] Added the cryptodev-linux kernel module.
Signed-off-by: Nikos Mavrogiannopoulos --- utils/cryptodev-linux/Makefile | 74 ++ 1 file changed, 74 insertions(+) create mode 100644 utils/cryptodev-linux/Makefile diff --git a/utils/cryptodev-linux/Makefile b/utils/cryptodev-linux/Makefile new file mode 100644 index 000..f559c7e --- /dev/null +++ b/utils/cryptodev-linux/Makefile @@ -0,0 +1,74 @@ +# +# Copyright (C) 2014 OpenWrt.org +# +# This is free software, licensed under the GNU General Public License v2. +# See /LICENSE for more information. +# +# $Id$ + +include $(TOPDIR)/rules.mk +include $(INCLUDE_DIR)/kernel.mk + +PKG_NAME:=cryptodev-linux +PKG_VERSION:=1.6 +PKG_RELEASE:=1 + +PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz +PKG_SOURCE_URL:=http://download.gna.org/cryptodev-linux/ +PKG_MD5SUM:=eade38998313c25fd7934719cdf8a2ea + +PKG_BUILD_DIR:=$(KERNEL_BUILD_DIR)/$(PKG_NAME)-$(PKG_VERSION) + +include $(INCLUDE_DIR)/package.mk + +CRYPTODEV_AUTOLOAD:= \ + cryptodev + +define KernelPackage/cryptodev + SUBMENU:=Cryptographic API modules + DEFAULT:=m if ALL + TITLE:=Driver for cryptographic acceleration + URL:=http://cryptodev-linux.org/ + VERSION:=$(LINUX_VERSION)+$(PKG_VERSION)-$(BOARD)-$(PKG_RELEASE) + DEPENDS:=+kmod-crypto-core +kmod-crypto-authenc +kmod-crypto-hash + FILES:= \ + $(PKG_BUILD_DIR)/cryptodev.$(LINUX_KMOD_SUFFIX) + AUTOLOAD:=$(call AutoLoad,50,$(CRYPTODEV_AUTOLOAD)) +endef + +define KernelPackage/cryptodev/description + This is a driver for that allows to use the Linux kernel supported + hardware ciphers by user-space applications. +endef + +CRYPTODEV_MAKEOPTS= -C $(PKG_BUILD_DIR) \ + PATH="$(TARGET_PATH)" \ + ARCH="$(LINUX_KARCH)" \ + CROSS_COMPILE="$(TARGET_CROSS)" \ + TOOLPREFIX="$(KERNEL_CROSS)" \ + TOOLPATH="$(KERNEL_CROSS)" \ + KERNEL_DIR="$(LINUX_DIR)" \ + LDOPTS=" " \ + DOMULTI=1 + +define Build/Compile/cryptodev + $(MAKE) $(CRYPTODEV_MAKEOPTS) +endef + +define Build/Compile + $(call Build/Compile/cryptodev) +endef + +define Build/InstallDev + $(INSTALL_DIR) $(STAGING_DIR)/usr/include/crypto + $(CP) $(PKG_BUILD_DIR)/crypto/cryptodev.h $(STAGING_DIR)/usr/include/crypto/ +endef + +define KernelPackage/cryptodev/install + $(INSTALL_DIR) $(1)/etc/modules.d + $(INSTALL_DATA) ./files/cryptodev.modules $(1)/etc/modules.d/80-cryptodev + $(INSTALL_DIR) $(1)/lib/modules/$(LINUX_VERSION) + $(INSTALL_DIR) $(1)/usr/sbin +endef + +$(eval $(call KernelPackage,cryptodev)) -- 1.9.2 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 2/2] GNUTLS_CRYPTODEV depends on kmod-cryptodev.
Signed-off-by: Nikos Mavrogiannopoulos --- libs/gnutls/Config.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libs/gnutls/Config.in b/libs/gnutls/Config.in index d55743f..0160cf0 100644 --- a/libs/gnutls/Config.in +++ b/libs/gnutls/Config.in @@ -14,7 +14,7 @@ config GNUTLS_OCSP config GNUTLS_CRYPTODEV bool "enable /dev/crypto support" - depends on BROKEN + depends on PACKAGE_kmod-cryptodev config GNUTLS_HEARTBEAT bool "enable DTLS heartbeat support" -- 1.9.2 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 16/30][ WRT1900AC ] mamba mvebu: sysupgrade support for mamba + dual boot
On 05/10/2014 10:53 AM, Marek Lindner wrote: On Friday 09 May 2014 14:11:32 Karl Palsson wrote: I understand how it works in general, John was nacking the support as it duplicated existing functionality. I was asking more about this existing functionality within openwrt for supporting dual firmware images. I wasn't aware of any existing functionality for this. Check target/linux/ar71xx/base-files/lib/upgrade/openmesh.sh. All OpenMesh boards provide exactly this kind of upgrade behavior. Which of course begs the question why it's buried in openmesh support code :) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 16/30][ WRT1900AC ] mamba mvebu: sysupgrade support for mamba + dual boot
On Saturday 10 May 2014 16:38:42 Karl P wrote: > On 05/10/2014 10:53 AM, Marek Lindner wrote: > > On Friday 09 May 2014 14:11:32 Karl Palsson wrote: > >> I understand how it works in general, John was nacking the support as it > >> duplicated existing functionality. I was asking more about this existing > >> functionality within openwrt for supporting dual firmware images. I > >> wasn't > >> aware of any existing functionality for this. > > > > Check target/linux/ar71xx/base-files/lib/upgrade/openmesh.sh. All OpenMesh > > boards provide exactly this kind of upgrade behavior. > > Which of course begs the question why it's buried in openmesh support code > :) Feel free to 'liberate' the code any way you see fit. I would not know how to abstract this code in a meaningful way, so it could be re-used elsewhere but I am certainly willing to review your patches on that matter. Cheers, Marek ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] mac80211: b43: add more configs (bus choice and LP-PHY support)
This allows users of old hardware to disable BCMA support and users of new hardware to disable LP-PHY support. Signed-off-by: Rafał Miłecki --- package/kernel/mac80211/Makefile | 28 +++- 1 file changed, 27 insertions(+), 1 deletion(-) diff --git a/package/kernel/mac80211/Makefile b/package/kernel/mac80211/Makefile index d1759fd..e5302ed 100644 --- a/package/kernel/mac80211/Makefile +++ b/package/kernel/mac80211/Makefile @@ -1173,6 +1173,20 @@ define KernelPackage/b43/config Example (keep files for G-PHY and N-PHY): G,N + choice + prompt "Supported buses" + default PACKAGE_B43_BUSES_BCMA_AND_SSB + help + This option allows you to select the version of the b43 firmware. + + config PACKAGE_B43_BUSES_BCMA_AND_SSB + bool "BCMA and SSB" + + config PACKAGE_B43_BUSES_SSB + bool "SSB only" + + endchoice + config PACKAGE_B43_DEBUG bool "Enable debug output and debugfs for b43" default n @@ -1203,6 +1217,16 @@ define KernelPackage/b43/config If unsure, say Y. + config PACKAGE_B43_PHY_LP + bool "Enable support for LP-PHYs" + default y + help + Enable support for LP-PHY. This includes support for the following devices: + PCI: BCM4312 + SoC: BCM5354 + + If unsure, say Y. + config PACKAGE_B43_PHY_HT bool "Enable support for HT-PHYs" default y @@ -1412,8 +1436,10 @@ endif config-$(call config_package,carl9170) += CARL9170 config-$(call config_package,b43) += B43 -config-y += B43_SSB B43_BCMA B43_PHY_LP +config-$(CONFIG_PACKAGE_B43_BUSES_BCMA_AND_SSB) += B43_BCMA B43_SSB +config-$(CONFIG_PACKAGE_B43_BUSES_SSB) += B43_SSB config-$(CONFIG_PACKAGE_B43_PHY_N) += B43_PHY_N +config-$(CONFIG_PACKAGE_B43_PHY_LP) += B43_PHY_LP config-$(CONFIG_PACKAGE_B43_PHY_HT) += B43_PHY_HT config-$(CONFIG_PACKAGE_B43_PIO) += B43_PIO config-$(CONFIG_PACKAGE_B43_DEBUG) += B43_DEBUG -- 1.8.4.5 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH V2] mac80211: b43: add more configs (bus choice and LP-PHY support)
This allows users of old hardware to disable BCMA support and users of new hardware to disable LP-PHY support. Signed-off-by: Rafał Miłecki --- V2: Fix copy & paste mistake in choice help --- package/kernel/mac80211/Makefile | 28 +++- 1 file changed, 27 insertions(+), 1 deletion(-) diff --git a/package/kernel/mac80211/Makefile b/package/kernel/mac80211/Makefile index d1759fd..f03a55d 100644 --- a/package/kernel/mac80211/Makefile +++ b/package/kernel/mac80211/Makefile @@ -1173,6 +1173,20 @@ define KernelPackage/b43/config Example (keep files for G-PHY and N-PHY): G,N + choice + prompt "Supported buses" + default PACKAGE_B43_BUSES_BCMA_AND_SSB + help + This allows choosing buses that b43 should support. + + config PACKAGE_B43_BUSES_BCMA_AND_SSB + bool "BCMA and SSB" + + config PACKAGE_B43_BUSES_SSB + bool "SSB only" + + endchoice + config PACKAGE_B43_DEBUG bool "Enable debug output and debugfs for b43" default n @@ -1203,6 +1217,16 @@ define KernelPackage/b43/config If unsure, say Y. + config PACKAGE_B43_PHY_LP + bool "Enable support for LP-PHYs" + default y + help + Enable support for LP-PHY. This includes support for the following devices: + PCI: BCM4312 + SoC: BCM5354 + + If unsure, say Y. + config PACKAGE_B43_PHY_HT bool "Enable support for HT-PHYs" default y @@ -1412,8 +1436,10 @@ endif config-$(call config_package,carl9170) += CARL9170 config-$(call config_package,b43) += B43 -config-y += B43_SSB B43_BCMA B43_PHY_LP +config-$(CONFIG_PACKAGE_B43_BUSES_BCMA_AND_SSB) += B43_BCMA B43_SSB +config-$(CONFIG_PACKAGE_B43_BUSES_SSB) += B43_SSB config-$(CONFIG_PACKAGE_B43_PHY_N) += B43_PHY_N +config-$(CONFIG_PACKAGE_B43_PHY_LP) += B43_PHY_LP config-$(CONFIG_PACKAGE_B43_PHY_HT) += B43_PHY_HT config-$(CONFIG_PACKAGE_B43_PIO) += B43_PIO config-$(CONFIG_PACKAGE_B43_DEBUG) += B43_DEBUG -- 1.8.4.5 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 16/30][ WRT1900AC ] mamba mvebu: sysupgrade support for mamba + dual boot
Hi! On 05/10/2014 06:45 PM, Marek Lindner wrote: > On Saturday 10 May 2014 16:38:42 Karl P wrote: >> On 05/10/2014 10:53 AM, Marek Lindner wrote: >>> On Friday 09 May 2014 14:11:32 Karl Palsson wrote: I understand how it works in general, John was nacking the support as it duplicated existing functionality. I was asking more about this existing functionality within openwrt for supporting dual firmware images. I wasn't aware of any existing functionality for this. >>> >>> Check target/linux/ar71xx/base-files/lib/upgrade/openmesh.sh. All OpenMesh >>> boards provide exactly this kind of upgrade behavior. >> >> Which of course begs the question why it's buried in openmesh support code >> :) > > Feel free to 'liberate' the code any way you see fit. I would not know how to > abstract this code in a meaningful way, so it could be re-used elsewhere but > I > am certainly willing to review your patches on that matter. I also implemented this for the ALL0258N in r28700, later added the necessary abstraction to at least support all the similar Allnet devices within the same script. When I saw the OM2P support was merged, I wasn't that happy to see a 90% copy of an already ugly vendor-specific hack occupying flash-space on *all* ar71xx-based devices... (ugly because the uImage header already got a checksum, and if already start hacking on the bootloader, they could have implemented FIT or alike) Anyway, we are far from having decent U-Boot source coverage on ar71xx to replace the affected bootloaders, so we'll have to deal with it. It should be possible to further generalize the two existing scripts into one. I'd be happy to provide assistance and code review in that matter. However, I do not have time to work on this, nor casual access to testing devices which might end up bricked and need recovery via serial... Cheers Daniel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [RFC][PATCH] brcm47xx: image: respect device flash block size
We should be more careful and don't generate 128K JFFS2 images for devices with flashes using 64K blocks (nor the other way). --- target/linux/brcm47xx/image/Makefile | 44 ++-- 1 file changed, 22 insertions(+), 22 deletions(-) diff --git a/target/linux/brcm47xx/image/Makefile b/target/linux/brcm47xx/image/Makefile index bf7f747..f8f8cd0 100644 --- a/target/linux/brcm47xx/image/Makefile +++ b/target/linux/brcm47xx/image/Makefile @@ -71,6 +71,15 @@ define Image/Build/Huawei cat $(BIN_DIR)/$(IMG_PREFIX)-$(1)-gz.trx >> $(BIN_DIR)/openwrt-$(2)-$(3)-gz.bin endef +# $(1): filesystem type. +# $(2): device model (used for output file). +# $(3): board_id (device specific magic). +# $(4): region. +# $(5): simplified filesystem type (without block size). +define Image/Build/Chk + $(STAGING_DIR_HOST)/bin/mkchkimg -o $(BIN_DIR)/openwrt-$(2)-$(5).chk -k $(BIN_DIR)/$(IMG_PREFIX)-$(1).trx -b $(3) -r $(4) +endef + define trxalign/jffs2-128k -a 0x2 -f $(KDIR)/root.$(1) endef @@ -99,6 +108,16 @@ endef # $(1): filesystem type. define Image/Build/jffs2-64k + $(call Image/Build/Chk,$(1),wgr614_v8,U12H072T00_NETGEAR,2,$(patsubst jffs2-%,jffs2,$(1))) + $(call Image/Build/Chk,$(1),wndr3300_v1,U12H093T00_NETGEAR,2,$(patsubst jffs2-%,jffs2,$(1))) + $(call Image/Build/Chk,$(1),wndr3400_v1,U12H155T00_NETGEAR,2,$(patsubst jffs2-%,jffs2,$(1))) + $(call Image/Build/Chk,$(1),wndr3400_v2,U12H187T00_NETGEAR,2,$(patsubst jffs2-%,jffs2,$(1))) + $(call Image/Build/Chk,$(1),wndr3700_v3,U12H194T00_NETGEAR,2,$(patsubst jffs2-%,jffs2,$(1))) + $(call Image/Build/Chk,$(1),wndr4000,U12H181T00_NETGEAR,2,$(patsubst jffs2-%,jffs2,$(1))) + $(call Image/Build/Chk,$(1),wnr834b_v2,U12H081T00_NETGEAR,2,$(patsubst jffs2-%,jffs2,$(1))) + $(call Image/Build/Chk,$(1),wnr2000v2,U12H114T00_NETGEAR,2,$(patsubst jffs2-%,jffs2,$(1))) + $(call Image/Build/Chk,$(1),wnr3500L,U12H136T99_NETGEAR,2,$(patsubst jffs2-%,jffs2,$(1))) + $(call Image/Build/Chk,$(1),wnr3500v2,U12H127T00_NETGEAR,2,$(patsubst jffs2-%,jffs2,$(1))) $(call Image/Build/CyberTAN,$(1),wrt54g3g,W54F,2.20.1,$(patsubst jffs2-%,jffs2,$(1))) $(call Image/Build/CyberTAN,$(1),wrt54g3g-em,W3GN,2.20.1,$(patsubst jffs2-%,jffs2,$(1))) $(call Image/Build/CyberTAN,$(1),wrt54g,W54G,4.71.1,$(patsubst jffs2-%,jffs2,$(1))) @@ -125,8 +144,11 @@ define Image/Build/jffs2-64k $(call Image/Build/CyberTAN,$(1),e3000_v1,61XN,1.0.3,$(patsubst jffs2-%,jffs2,$(1))) $(call Image/Build/CyberTAN,$(1),e3200_v1,3200,1.0.1,$(patsubst jffs2-%,jffs2,$(1))) $(call Image/Build/CyberTAN,$(1),e4200_v1,4200,1.0.5,$(patsubst jffs2-%,jffs2,$(1))) + $(call Image/Build/Huawei,$(1),e970,$(1)) $(call Image/Build/Motorola,$(1),wa840g,2,$(patsubst jffs2-%,jffs2,$(1))) $(call Image/Build/Motorola,$(1),we800g,3,$(patsubst jffs2-%,jffs2,$(1))) + $(call Image/Build/Motorola,$(1),wr850g,1,$(1)) + $(call Image/Build/USR,$(1),usr5461,$(1)) $(call Image/Build/Edi,$(1),ps1208mfg,$(patsubst jffs2-%,jffs2,$(1))) $(call Image/Build/dwl3150,$(1),$(patsubst jffs2-%,jffs2,$(1))) endef @@ -142,15 +164,6 @@ define Image/Build/Initramfs endef # $(1): filesystem type. -# $(2): device model (used for output file). -# $(3): board_id (device specific magic). -# $(4): region. -# $(5): simplified filesystem type (without block size). -define Image/Build/Chk - $(STAGING_DIR_HOST)/bin/mkchkimg -o $(BIN_DIR)/openwrt-$(2)-$(5).chk -k $(BIN_DIR)/$(IMG_PREFIX)-$(1).trx -b $(3) -r $(4) -endef - -# $(1): filesystem type. define Image/Build $(STAGING_DIR_HOST)/bin/trx -o $(BIN_DIR)/$(IMG_PREFIX)-$(1).trx \ -f $(KDIR)/loader.gz -f $(KDIR)/vmlinux.lzma \ @@ -159,22 +172,9 @@ define Image/Build -f $(KDIR)/vmlinux.gz \ $(call trxalign/$(1),$(1)) $(call Image/Build/$(1),$(1)) - $(call Image/Build/Motorola,$(1),wr850g,1,$(1)) - $(call Image/Build/USR,$(1),usr5461,$(1)) - $(call Image/Build/Huawei,$(1),e970,$(1)) - $(call Image/Build/Chk,$(1),wgr614_v8,U12H072T00_NETGEAR,2,$(patsubst jffs2-%,jffs2,$(1))) # $(call Image/Build/Chk,$(1),wgr614_v9,U12H094T00_NETGEAR,2,$(patsubst jffs2-%,jffs2,$(1))) - $(call Image/Build/Chk,$(1),wndr3300_v1,U12H093T00_NETGEAR,2,$(patsubst jffs2-%,jffs2,$(1))) - $(call Image/Build/Chk,$(1),wndr3400_v1,U12H155T00_NETGEAR,2,$(patsubst jffs2-%,jffs2,$(1))) - $(call Image/Build/Chk,$(1),wndr3400_v2,U12H187T00_NETGEAR,2,$(patsubst jffs2-%,jffs2,$(1))) # $(call Image/Build/Chk,$(1),wndr3400_vcna,U12H155T01_NETGEAR,2,$(patsubst jffs2-%,jffs2,$(1))) - $(call Image/Build/Chk,$(1),wndr3700_v3,U12H194T00_NETGEAR,2,$(patsubst jffs2-%,jffs2,$(1))) - $(call Image/Build/Chk,$(1),wndr4000,U12H181T00_NETGEAR,2,$(patsubst jffs2-%,jffs2,$(1))) - $(call Image/Build/Chk,$(1),wnr834b_v2,U12H0
[OpenWrt-Devel] [PATCH] gpio-button-hotplug: fix (and extend) package description
Signed-off-by: Rafał Miłecki --- package/kernel/gpio-button-hotplug/Makefile | 10 -- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/package/kernel/gpio-button-hotplug/Makefile b/package/kernel/gpio-button-hotplug/Makefile index c947f43..0a2c7c0 100644 --- a/package/kernel/gpio-button-hotplug/Makefile +++ b/package/kernel/gpio-button-hotplug/Makefile @@ -22,8 +22,14 @@ define KernelPackage/gpio-button-hotplug KCONFIG:= endef -define KernelPackage/button-hotplug/description - Kernel module to generate GPIO button hotplug events +define KernelPackage/gpio-button-hotplug/description + This is a replacement for the following in-kernel drivers: + 1) gpio_keys (KEYBOARD_GPIO) + 2) gpio_keys_polled (KEYBOARD_GPIO_POLLED) + + Instead of generating input events (like in-kernel drivers do) it generates + uevent-s and broadcasts them. This allows disabling input subsystem which is + an overkill for OpenWrt simple needs. endef MAKE_OPTS:= \ -- 1.8.4.5 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] button-hotplug: describe module a bit better & mention gpio-button-hotplug
Signed-off-by: Rafał Miłecki --- package/kernel/button-hotplug/Makefile | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/package/kernel/button-hotplug/Makefile b/package/kernel/button-hotplug/Makefile index 10f6723..347544c 100644 --- a/package/kernel/button-hotplug/Makefile +++ b/package/kernel/button-hotplug/Makefile @@ -23,7 +23,8 @@ define KernelPackage/button-hotplug endef define KernelPackage/button-hotplug/description - Kernel module to generate button hotplug events + Kernel module to generate button uevent-s from input subsystem events. + If your device uses GPIO buttons, see gpio-button-hotplug. endef EXTRA_KCONFIG:= \ -- 1.8.4.5 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
