[OpenWrt-Devel] [PATCH v2] [ar71xx] Add support for TL-WA830RE v1
Added support for the TP-LINK TL-WA830RE v1 Range Extender. Based on the
WA901ND v1 support. Hardware IDs checked against original firmware. Patch was
successfully tested on hardware.
Signed-off-by: Ronald Hecht ronald.he...@gmx.de
Index: target/linux/ar71xx/image/Makefile
===
--- target/linux/ar71xx/image/Makefile (revision 35759)
+++ target/linux/ar71xx/image/Makefile (working copy)
@@ -900,6 +900,7 @@
$(eval $(call
SingleProfile,TPLINK,$(fs_64kraw),TLWA701,tl-wa701n-v1,TL-WA901ND,ttyS0,115200,0x07010001,1,4M))
$(eval $(call
SingleProfile,TPLINK,$(fs_64kraw),TLWA7510NV1,tl-wa7510n,TL-WA7510N,ttyS0,115200,0x7511,1,4M))
$(eval $(call
SingleProfile,TPLINK,$(fs_64kraw),TLWA801NV1,tl-wa801nd-v1,TL-WA901ND,ttyS0,115200,0x08010001,1,4M))
+$(eval $(call
SingleProfile,TPLINK,$(fs_64kraw),TLWA830RV1,tl-wa830re-v1,TL-WA901ND,ttyS0,115200,0x08300010,1,4M))
$(eval $(call
SingleProfile,TPLINK,$(fs_64kraw),TLWA901NV1,tl-wa901nd-v1,TL-WA901ND,ttyS0,115200,0x09010001,1,4M))
$(eval $(call
SingleProfile,TPLINK,$(fs_64kraw),TLWA901NV2,tl-wa901nd-v2,TL-WA901ND-v2,ttyS0,115200,0x09010002,1,4M))
$(eval $(call
SingleProfile,TPLINK,$(fs_64kraw),TLWR740NV1,tl-wr740n-v1,TL-WR741ND,ttyS0,115200,0x0741,1,4M))
@@ -972,6 +973,7 @@
$(eval $(call MultiProfile,TEW652BRP,TEW652BRP_FW TEW652BRP_RECOVERY))
$(eval $(call MultiProfile,TLMR3220,TLMR3220V1 TLMR3220V2))
$(eval $(call MultiProfile,TLWA801,TLWA801NV1))
+$(eval $(call MultiProfile,TLWA830,TLWA830RV1))
$(eval $(call MultiProfile,TLWA901,TLWA901NV1 TLWA901NV2))
$(eval $(call MultiProfile,TLWA7510,TLWA7510NV1))
$(eval $(call MultiProfile,TLWR740,TLWR740NV1 TLWR740NV3 TLWR740NV4))
Index: target/linux/ar71xx/base-files/lib/ar71xx.sh
===
--- target/linux/ar71xx/base-files/lib/ar71xx.sh(revision 35759)
+++ target/linux/ar71xx/base-files/lib/ar71xx.sh(working copy)
@@ -90,6 +90,9 @@
080100*)
model=TP-Link TL-WA801N/ND
;;
+ 083000*)
+ model=TP-Link TL-WA830RE
+ ;;
084100*)
model=TP-Link TL-WR841N/ND
;;
Index: target/linux/ar71xx/generic/profiles/tp-link.mk
===
--- target/linux/ar71xx/generic/profiles/tp-link.mk (revision 35759)
+++ target/linux/ar71xx/generic/profiles/tp-link.mk (working copy)
@@ -102,7 +102,17 @@
endef
$(eval $(call Profile,TLWA801))
+define Profile/TLWA830
+ NAME:=TP-LINK TL-WA830RE
+ PACKAGES:=
+endef
+define Profile/TLWA830/Description
+ Package set optimized for the TP-LINK TL-WA830RE.
+endef
+$(eval $(call Profile,TLWA830))
+
+
define Profile/TLWA901
NAME:=TP-LINK TL-WA901N/ND
PACKAGES:=
Index: tools/firmware-utils/src/mktplinkfw.c
===
--- tools/firmware-utils/src/mktplinkfw.c (revision 35759)
+++ tools/firmware-utils/src/mktplinkfw.c (working copy)
@@ -37,6 +37,8 @@
#define HWID_TL_WA701N_V1 0x07010001
#define HWID_TL_WA7510N_V1 0x7511
#define HWID_TL_WA801ND_V1 0x08010001
+#define HWID_TL_WA830RE_V1 0x08300010
+#define HWID_TL_WA830RE_V2 0x0832
#define HWID_TL_WA901ND_V1 0x09010001
#define HWID_TL_WA901ND_V2 0x09010002
#define HWID_TL_WDR4900_V1 0x4901
@@ -224,6 +226,16 @@
.hw_rev = 1,
.layout_id = 4M,
}, {
+ .id = TL-WA830REv1,
+ .hw_id = HWID_TL_WA830RE_V1,
+ .hw_rev = 1,
+ .layout_id = 4M,
+ }, {
+ .id = TL-WA830REv2,
+ .hw_id = HWID_TL_WA830RE_V2,
+ .hw_rev = 1,
+ .layout_id = 4M,
+ }, {
.id = TL-WA901NDv1,
.hw_id = HWID_TL_WA901ND_V1,
.hw_rev = 1,
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Adding new cdc-mbim driver to package_kernel_modules_usb.mk
Hello! This patch adds CDC MBIM driver coming in kernel 3.8 for high speed mobile broadband modem devices. The Mobile Interface Broadband Model (MBIM) is a new standard developed by the USB Implementers Forum. Index: package/kernel/modules/usb.mk === --- a/package/kernel/modules/usb.mk (version 35627) +++ b/package/kernel/modules/usb.mk (working copy) @@ -842,6 +842,22 @@ $(eval $(call KernelPackage,usb-net-rndis)) +define KernelPackage/usb-net-cdc-mbim + SUBMENU:=$(USB_MENU) + TITLE:=Kernel module for MBIM Devices + KCONFIG:=CONFIG_USB_NET_CDC_MBIM + FILES:= \ + $(LINUX_DIR)/drivers/$(USBNET_DIR)/cdc_mbim.ko + AUTOLOAD:=$(call AutoLoad,61,cdc_mbim) + $(call AddDepends/usb-net,+kmod-usb-wdm,+kmod-usb-net-cdc-ncm) +endef + +define KernelPackage/usb-net-cdc-mbim/description + Kernel module for Option USB High Speed Mobile Devices +endef + +$(eval $(call KernelPackage,usb-net-cdc-mbim)) + define KernelPackage/usb-net-cdc-ncm TITLE:=Support for CDC NCM connections KCONFIG:=CONFIG_USB_NET_CDC_NCM ___ Best Regards! Rusink ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] [ramips] rt305x: add profile for tenda w150m board
From: Chi Zhang zhangchi...@gmail.com
This patch makes it possible for OpenWRT to run on a version of w150m that has
4MB parallel flash.
Signed-off-by: Chi Zhang zhangchi...@gmail.com
---
In addtion I would like to point out that 3G300M, 3G150M, W300M, W150M and
W150M+ 's board are the same, except that 3G models have USB sockets populated,
and there are a few differences in LED labeling between 3G models and W models.
xx300M uses RT3052F which has 2T2R MIMO while xx150M uses RT3050F.
Stock firmware indicates that all of the above models can have either SPI or
parallel NOR flash. 3G models have 4MB flash and 16M x 16bit SDRAM, while most
W models come with 2MB flash and 8M x 16bit SDRAM. But there are special cases
that some W150M (at least those customized by Hewlett-Packard ) have 4MB flash,
which is enough for OpenWRT.
It is still hard to squeeze OpenWRT into the common 2MB version of W150M, and
the versions with SPI flash can use 3G300M profile instead, but with wrong LED
definations.
I did not include rt305x_register_usb() call in my patch, though some people
could get the USB socket on W150M populated or even upgrade the memories making
it identical to 3G models.
Finally, what we need is actually 4 target profiles: 3G150M/3G300M, 3G150M
SPI/3G300M SPI, W150M/W300M, W150M SPI/W300M SPI ( stock firmware adds _SPI
after firmware version for SPI flash hardware version).
Internal photos and boot information for Hewlett-Packard customized version of
W150M can be found on my site at http://blog.dword1511.info/?p=3781 ( in
Chinese ).
diff --git a/target/linux/ramips/base-files/etc/diag.sh
b/target/linux/ramips/base-files/etc/diag.sh
index 102ff27..cbae14a 100755
--- a/target/linux/ramips/base-files/etc/diag.sh
+++ b/target/linux/ramips/base-files/etc/diag.sh
@@ -9,7 +9,7 @@ get_status_led() {
3g-6200n)
status_led=edimax:green:power
;;
- 3g300m)
+ 3g300m | w150m)
status_led=tenda:blue:ap
;;
argus-atp52b)
diff --git
a/target/linux/ramips/base-files/etc/hotplug.d/firmware/10-rt2x00-eeprom
b/target/linux/ramips/base-files/etc/hotplug.d/firmware/10-rt2x00-eeprom
index 43121e1..8fa1de9 100644
--- a/target/linux/ramips/base-files/etc/hotplug.d/firmware/10-rt2x00-eeprom
+++ b/target/linux/ramips/base-files/etc/hotplug.d/firmware/10-rt2x00-eeprom
@@ -83,6 +83,7 @@ case $FIRMWARE in
v11st-fe | \
v22rw-2x2 | \
w306r-v20 | \
+ w150m | \
w502u | \
wcr-150gn | \
whr-g300n | \
diff --git a/target/linux/ramips/base-files/etc/uci-defaults/02_network
b/target/linux/ramips/base-files/etc/uci-defaults/02_network
index 5fb52bb..448a453 100755
--- a/target/linux/ramips/base-files/etc/uci-defaults/02_network
+++ b/target/linux/ramips/base-files/etc/uci-defaults/02_network
@@ -38,6 +38,7 @@ ramips_setup_interfaces()
case $board in
3g300m | \
+ w150m | \
all0256n | \
all5002 | \
broadway)
@@ -147,6 +148,7 @@ ramips_setup_macs()
;;
3g-6200n | \
3g300m | \
+ w150m | \
air3gii | \
argus-atp52b | \
bc2 | \
diff --git a/target/linux/ramips/base-files/lib/preinit/06_set_iface_mac
b/target/linux/ramips/base-files/lib/preinit/06_set_iface_mac
index fcfb86b..30eaf28 100644
--- a/target/linux/ramips/base-files/lib/preinit/06_set_iface_mac
+++ b/target/linux/ramips/base-files/lib/preinit/06_set_iface_mac
@@ -11,6 +11,7 @@ preinit_set_mac_address() {
case $(ramips_board_name) in
3g-6200n |\
3g300m | \
+ w150m | \
mzk-w300nh2 |\
wl-330n |\
wl-330n3g)
diff --git a/target/linux/ramips/base-files/lib/ramips.sh
b/target/linux/ramips/base-files/lib/ramips.sh
index 5d24abc..461b43d 100755
--- a/target/linux/ramips/base-files/lib/ramips.sh
+++ b/target/linux/ramips/base-files/lib/ramips.sh
@@ -157,6 +157,9 @@ ramips_board_name() {
*Tenda W306R V2.0)
name=w306r-v20
;;
+ *Tenda W150M)
+ name=w150m
+ ;;
*TEW-691GR)
name=tew-691gr
;;
diff --git a/target/linux/ramips/base-files/lib/upgrade/platform.sh
b/target/linux/ramips/base-files/lib/upgrade/platform.sh
index 1b358c1..728cb8a 100755
--- a/target/linux/ramips/base-files/lib/upgrade/platform.sh
+++ b/target/linux/ramips/base-files/lib/upgrade/platform.sh
@@ -16,6 +16,7 @@ platform_check_image() {
case $board in
3g-6200n | \
3g300m | \
+ w150m | \
air3gii | \
all0239-3g | \
all0256n | \
diff --git
a/target/linux/ramips/files/arch/mips/include/asm/mach-ralink/machine.h
b/target/linux/ramips/files/arch/mips/include/asm/mach-ralink/machine.h
index b3903fc..d503941 100644
--- a/target/linux/ramips/files/arch/mips/include/asm/mach-ralink/machine.h
+++
Re: [OpenWrt-Devel] About IGMP snooping support
Hi, On 24 February 2013 06:18, hayate hayate...@gmail.com wrote: My router hardware has a AR8327 switch which is supposed to support hardware IGMP snooping, but it seems it doesn't work on my OpenWrt of trunk. I noted that in target/linux/generic/files/drivers/net/phy/ar8216.h there is a AR8327_FWD_CTRL1_IGMP defined but not used anywhere. And there is a config option CONFIG_BRIDGE_IGMP_SNOOPING in kernel config. Does these two affect this feature? How can I enable IGMP snooping in OpenWrt on my router IGMP snooping for switches has a slightly different meaning than IGMP snooing support in linux. For switches (also for AR8xxx) IGMP snooping means that any JOINS/LEAVES are redirected to the CPU port, so the CPU can setup/update the appropriate forwarding entries in the switch. So for this feature to work it requires a daemon capable of that, which currently doesn't exist. The IGMP snooping from linux does something like that already, but only for bridge interface members. That means that is able to prevent multicast traffic from leaking to wlan, but it does not have any influence to the individual switch ports. Jonas ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] About IGMP snooping support
Thank you Jonas, If I understand correctly, 1. If that kind of daemons exist, it can prevent multicast flood in the switch by setting proper rules 2. We can infer that if two switches are connected together, unless both of them support IGMP snooping, at least one of them would suffer multicast flood right? On Sun, Feb 24, 2013 at 7:42 PM, Jonas Gorski j...@openwrt.org wrote: Hi, On 24 February 2013 06:18, hayate hayate...@gmail.com wrote: My router hardware has a AR8327 switch which is supposed to support hardware IGMP snooping, but it seems it doesn't work on my OpenWrt of trunk. I noted that in target/linux/generic/files/drivers/net/phy/ar8216.h there is a AR8327_FWD_CTRL1_IGMP defined but not used anywhere. And there is a config option CONFIG_BRIDGE_IGMP_SNOOPING in kernel config. Does these two affect this feature? How can I enable IGMP snooping in OpenWrt on my router IGMP snooping for switches has a slightly different meaning than IGMP snooing support in linux. For switches (also for AR8xxx) IGMP snooping means that any JOINS/LEAVES are redirected to the CPU port, so the CPU can setup/update the appropriate forwarding entries in the switch. So for this feature to work it requires a daemon capable of that, which currently doesn't exist. The IGMP snooping from linux does something like that already, but only for bridge interface members. That means that is able to prevent multicast traffic from leaking to wlan, but it does not have any influence to the individual switch ports. Jonas ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] About IGMP snooping support
On 24 February 2013 12:55, hayate hayate...@gmail.com wrote: Thank you Jonas, If I understand correctly, 1. If that kind of daemons exist, it can prevent multicast flood in the switch by setting proper rules 2. We can infer that if two switches are connected together, unless both of them support IGMP snooping, at least one of them would suffer multicast flood right? Yes, and yes. Also please don't top post. Jonas ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] [packages] php4: add compatibility fix for gmp
gmp modified some if it's internal constants, in particular __GMP_BITS_PER_MP_LIMB. Added a patch to substitute GMP_LIMB_BITS. Also bumped release number and copyright date. Signed-off-by: Russell Senior russ...@personaltelco.net --- lang/php4/Makefile |4 ++-- lang/php4/patches/120-gmp-compat.patch | 11 +++ 2 files changed, 13 insertions(+), 2 deletions(-) create mode 100644 lang/php4/patches/120-gmp-compat.patch diff --git a/lang/php4/Makefile b/lang/php4/Makefile index 2ba1bf3..78c1c50 100644 --- a/lang/php4/Makefile +++ b/lang/php4/Makefile @@ -1,5 +1,5 @@ # -# Copyright (C) 2006-2010 OpenWrt.org +# Copyright (C) 2006-2013 OpenWrt.org # # This is free software, licensed under the GNU General Public License v2. # See /LICENSE for more information. @@ -9,7 +9,7 @@ include $(TOPDIR)/rules.mk PKG_NAME:=php4 PKG_VERSION:=4.4.9 -PKG_RELEASE:=1 +PKG_RELEASE:=2 PKG_SOURCE:=php-$(PKG_VERSION).tar.bz2 PKG_SOURCE_URL:=http://www.php.net/distributions/ diff --git a/lang/php4/patches/120-gmp-compat.patch b/lang/php4/patches/120-gmp-compat.patch new file mode 100644 index 000..76672c3 --- /dev/null +++ b/lang/php4/patches/120-gmp-compat.patch @@ -0,0 +1,11 @@ +--- a/ext/gmp/gmp.c b/ext/gmp/gmp.c +@@ -1159,7 +1159,7 @@ ZEND_FUNCTION(gmp_random) + + GMPG(rand_initialized) = 1; + } +- mpz_urandomb(*gmpnum_result, GMPG(rand_state), GMP_ABS (limiter) * __GMP_BITS_PER_MP_LIMB); ++ mpz_urandomb(*gmpnum_result, GMPG(rand_state), GMP_ABS (limiter) * GMP_LIMB_BITS); + + ZEND_REGISTER_RESOURCE(return_value, gmpnum_result, le_gmp); + } -- 1.7.10.4 -- Russell Senior, President russ...@personaltelco.net ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [Patch] [packages] broadcom-diag : Detection of WNDR3400v1
On 02/23/2013 12:34 PM, Dirk Neukirchen wrote: Hi, first time commit. nvram variable boardtype is unique for now. - button gpio were taken from nvram. - led information was taken from dd-wrt ( http://svn.dd-wrt.com/browser/src/router/libutils/utils.c ) I hope that I changed the values correctly. Signed-off-by: Dirk Neukirchen dirkneukirc...@web.de Thank you for your patch. it was committed with a small change in r35765. Next time please send a plain text mail. Hauke ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] broadcom-diag: add support for e3200 v1
On 02/21/2013 04:57 PM, Tijs Van Buggenhout wrote: Hex values in nvram seem to be uppercase on my e3200 device. Define one power led and two buttons (reset/wps). Signed-off-by: Tijs Van Buggenhout t...@able.be Thank you for your patch, it was committed in r35766. Next time please send a plain text mail. Hauke ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Clean up kmod-diag for Linksys E3000v1 / WRT610Nv2
On 01/06/2013 12:19 AM, Nathan Hintz wrote:
Special handling for Linksys E3000v1 is no longer required. WRT610Nv2 uses
the same H/W and should be the same.
Only tested on E3000v1.
Signed-off-by: Nathan Hintz nlhi...@hotmail.com
Index: package/broadcom-diag/src/diag.c
===
--- package/broadcom-diag/src/diag.c (revision 35017)
+++ package/broadcom-diag/src/diag.c (working copy)
@@ -1130,19 +1130,6 @@
return platforms[WRT600N];
}
- /*
- * Normally, these would go inside the CFE based - newer hardware
block below; however, during early init, the
- * pmon_ver variable is not available on the E3000v1 (and probably
the WRT610Nv2 also). Until this is figured out,
- * these will need to remain here in order for platform detection to
work.
- */
- if (!strcmp(boardnum, 42)) { /* Linksys */
- if (!strcmp(boardtype, 0x04cf)
!strcmp(getvar(boot_hw_model), E300) !strcmp(getvar(boot_hw_ver),
1.0))
- return platforms[E3000V1];
-
- if (!strcmp(boardtype, 0x04cf)
!strcmp(getvar(boot_hw_model), WRT610N) !strcmp(getvar(boot_hw_ver),
2.0))
- return platforms[WRT610NV2];
- }
-
if (startswith(getvar(pmon_ver), CFE)) {
/* CFE based - newer hardware */
if (!strcmp(boardnum, 42)) { /* Linksys */
@@ -1183,6 +1170,17 @@
}
}
+ if (!strcmp(boardtype, 0x04cf)) {
+ if (!strcmp(getvar(boot_hw_model), E300)) {
+ if (!strcmp(getvar(boot_hw_ver),
1.0))
+ return platforms[E3000V1];
+ }
+ else if (!strcmp(getvar(boot_hw_model),
WRT610N)) {
+ if (!strcmp(getvar(boot_hw_ver),
2.0))
+ return platforms[WRT610NV2];
+ }
+ }
+
/* default to WRT54G */
return platforms[WRT54G];
}
I will drop this patch because now the kernel is asked to detect these
devices, see r35764.
Hauke
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Fix Board Name for Linksys E1000/E3000
On 02/05/2013 07:32 AM, Nathan Hintz wrote:
Signed-off-by: Nathan Hintz nlhi...@hotmail.com
Index:
target/linux/brcm47xx/patches-3.6/260-MIPS-BCM47XX-add-board-detection.patch
===
---
target/linux/brcm47xx/patches-3.6/260-MIPS-BCM47XX-add-board-detection.patch
(revision 35492)
+++
target/linux/brcm47xx/patches-3.6/260-MIPS-BCM47XX-add-board-detection.patch
(working copy)
@@ -89,10 +89,10 @@
+static const struct bcm47xx_board_type_list bcm47xx_board_list_boot_hw[] = {
+{{BCM47XX_BOARD_CISCO_M10V1, Cisco M10}, M10, 1.0}, /* like
WRT160N v3.0 */
+{{BCM47XX_BOARD_CISCO_M20V1, Cisco M20}, M20, 1.0}, /* like
WRT310N v2.0 */
-+{{BCM47XX_BOARD_LINKSYS_E1000V1, Linksys E100}, E100, 1.0}, /*
like WRT160N v3.0 */
++{{BCM47XX_BOARD_LINKSYS_E1000V1, Linksys E1000}, E100, 1.0}, /*
like WRT160N v3.0 */
+{{BCM47XX_BOARD_LINKSYS_E1000V2, Linksys E1000}, E1000, 2.0},
+{{BCM47XX_BOARD_LINKSYS_E2000V1, Linksys E2000}, Linksys E2000,
1.0},
-+{{BCM47XX_BOARD_LINKSYS_E3000V1, Linksys E300}, E300, 1.0}, /*
like WRT610N v2.0 */
++{{BCM47XX_BOARD_LINKSYS_E3000V1, Linksys E3000}, E300, 1.0}, /*
like WRT610N v2.0 */
+{{BCM47XX_BOARD_LINKSYS_E3200V1, Linksys E3200}, E3200, 1.0},
+{{BCM47XX_BOARD_LINKSYS_E4200V1, Linksys E4200}, E4200, 1.0},
+{{BCM47XX_BOARD_LINKSYS_WRT150NV11, Linksys WRT150N}, WRT150N,
1.1},
Thank you for the patch, this was applied some time ago.
Hauke
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] [packages] broadcom-diag: Properly implement WRT610N (v1) detection
On 02/15/2013 11:41 AM, Christian Lachner wrote: Hello, the original code in diag.c does not detect my WRT610N because it checks for the nvram variable wsc_modelname which does not exist on my device. Several CFE-Revisions exist which might be the cause that some models may have wsc_modelname and others don't. It is also possible that the original linksys-firmware creates that variable. However, I know for fact that on CFE 4.175.64.16, a cleaned nvram does definitely not have that variable. As a result, I added a check which works similar to the one of the WRT300N. Also, I did double-check if pmon_ver actually is available during early init. This patch is tested by me and works for trunk. Signed-off-by: Christian Lachner gladiac_at_gmail.com Hi, Could you please test a recent trunk version, and check if your device gets detected without this extra patch? I changed the detection for many boards including this. Hauke ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 001/001] [package] ddns-scripts: add dy.fi service and add [HTTPAUTH] to description
From: Sami Olmari s...@olmari.fi Add dy.fi ddns provider into ddns-scripts services file and add [HTTPAUTH] into description in top of the services file, the functionality has been added long ago, just description is missing. Signed-off-by: Sami Olmari s...@olmari.fi Tested-by: Sami Olmari s...@olmari.fi --- --- package/feeds/packages/ddns-scripts/files/usr/lib/ddns/services.orig 2013-02-08 22:42:48.628443832 +0200 +++ package/feeds/packages/ddns-scripts/files/usr/lib/ddns/services 2013-02-24 21:12:54.618384332 +0200 @@ -1,12 +1,13 @@ # This file contains the update urls for various dynamic dns services. # Column one contains the service name, column two contains the update url. -# within the update url there are 4 variables you can use: [USERNAME], -# [PASSWORD], [DOMAIN] and [IP]. These are substituted for the username, -# password, and domain name specified in the /etc/config/ddns file when an -# update is performed. The IP is substituted for the current ip address of the -# router. These variables are case sensitive, while urls generally are not, so -# if you need to enter the same text in the url (which seems very unlikely) put -# that text in lowercase, while the variables should remain in uppercase +# within the update url there are 5 variables you can use: [USERNAME], +# [PASSWORD], [HTTPAUTH], [DOMAIN] and [IP]. These are substituted for the +# username, password, and domain name specified in the /etc/config/ddns file +# when an update is performed. The IP is substituted for the current ip +# address of the router. These variables are case sensitive, while urls +# generally are not, so if you need to enter the same text in the url +# (which seems very unlikely) put that text in lowercase, while the variables +# should remain in uppercase dyndns.org http://[USERNAME]:[PASSWORD]@members.dyndns.org/nic/update?hostname=[DOMAIN]myip=[IP]; changeip.com http://[USERNAME]:[PASSWORD]@nic.changeip.com/nic/update?u=[USERNAME]p=[PASSWORD]cmd=updatehostname=[DOMAIN]ip=[IP]; @@ -57,3 +58,6 @@ # easydns.com dynamic DNS easydns.com http://[USERNAME]:[PASSWORD]@api.cp.easydns.com/dyn/tomato.php?hostname=[DOMAIN]myip=[IP]; + +# dy.fi Dynamic DNS for finnish users +dy.fi http://[HTTPAUTH]@www.dy.fi/nic/update?hostname=[DOMAIN]; ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [Patch] board detection WNDR3400v2
WNDR3400v2 is based on BCM53xx . Image that is created breaks the router
somehow therefore #.
CFE and NVRAM contain different vars - example:
CFE line original: Device eth0: hwaddr 74-44-01-37-C6-69, ipaddr
192.168.1.1, mask 255.255.255.0
CFE after openwrt: Device eth0: hwaddr 00-FF-FF-FF-FF-FF, ipaddr
192.168.1.1, mask 255.255.255.0
Logs were posted earlier on this mailing list:
https://lists.openwrt.org/pipermail/openwrt-devel/2012-July/016174.html
Different logs with factory firmware are in the wiki:
http://wiki.openwrt.org/toh/netgear/wndr3400#wndr3400v2
(and on wikidevi for example)
Signed off by: Dirk Neukirchen dirkneukirc...@web.de
diff --git a/target/linux/brcm47xx/image/Makefile
b/target/linux/brcm47xx/image/Makefile
index ffb5e7c..f9afa79 100644
--- a/target/linux/brcm47xx/image/Makefile
+++ b/target/linux/brcm47xx/image/Makefile
@@ -124,6 +124,7 @@ define Image/Build
#$(call
Image/Build/Chk,$(1),wgr614_v9,U12H094T00_NETGEAR,2,$(patsubst
jffs2-%,jffs2,$(1)))
#$(call
Image/Build/Chk,$(1),wndr3300,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),wndr4000,U12H181T00_NETGEAR,2,$(patsubst
jffs2-%,jffs2,$(1)))
$(call
Image/Build/Chk,$(1),wnr834b_v2,U12H081T00_NETGEAR,2,$(patsubst
jffs2-%,jffs2,$(1)))
diff --git
a/target/linux/brcm47xx/patches-3.6/260-MIPS-BCM47XX-add-board-detection.patch
b/target/linux/brcm47xx/patches-3.6/260-MIPS-BCM47XX-add-board-detection.patch
index 6edbaed..711b0ec 100644
---
a/target/linux/brcm47xx/patches-3.6/260-MIPS-BCM47XX-add-board-detection.patch
+++
b/target/linux/brcm47xx/patches-3.6/260-MIPS-BCM47XX-add-board-detection.patch
@@ -112,6 +112,7 @@
+{{BCM47XX_BOARD_NETGEAR_WGR614V9, Netgear WGR614 V9},
U12H094T00_NETGEAR,},
+{{BCM47XX_BOARD_NETGEAR_WNDR3300, Netgear WNDR3300},
U12H093T00_NETGEAR,},
+{{BCM47XX_BOARD_NETGEAR_WNDR3400V1, Netgear WNDR3400 V1},
U12H155T00_NETGEAR,},
++ {{BCM47XX_BOARD_NETGEAR_WNDR3400V2, Netgear WNDR3400 V2},
U12H187T00_NETGEAR,},
+{{BCM47XX_BOARD_NETGEAR_WNDR3400VCNA, Netgear WNDR3400 Vcna},
U12H155T01_NETGEAR,},
+{{BCM47XX_BOARD_NETGEAR_WNDR3700V3, Netgear WNDR3700 V3},
U12H194T00_NETGEAR,},
+{{BCM47XX_BOARD_NETGEAR_WNDR4000, Netgear WNDR4000},
U12H181T00_NETGEAR,},
@@ -298,6 +299,7 @@
+BCM47XX_BOARD_NETGEAR_WGR614V9,
+BCM47XX_BOARD_NETGEAR_WNDR3300,
+BCM47XX_BOARD_NETGEAR_WNDR3400V1,
++BCM47XX_BOARD_NETGEAR_WNDR3400V2,
+BCM47XX_BOARD_NETGEAR_WNDR3400VCNA,
+BCM47XX_BOARD_NETGEAR_WNDR3700V3,
+BCM47XX_BOARD_NETGEAR_WNDR4000,
diff --git
a/target/linux/brcm47xx/patches-3.8/260-MIPS-BCM47XX-add-board-detection.patch
b/target/linux/brcm47xx/patches-3.8/260-MIPS-BCM47XX-add-board-detection.patch
index 6edbaed..acf550c 100644
---
a/target/linux/brcm47xx/patches-3.8/260-MIPS-BCM47XX-add-board-detection.patch
+++
b/target/linux/brcm47xx/patches-3.8/260-MIPS-BCM47XX-add-board-detection.patch
@@ -112,6 +112,7 @@
+{{BCM47XX_BOARD_NETGEAR_WGR614V9, Netgear WGR614 V9},
U12H094T00_NETGEAR,},
+{{BCM47XX_BOARD_NETGEAR_WNDR3300, Netgear WNDR3300},
U12H093T00_NETGEAR,},
+{{BCM47XX_BOARD_NETGEAR_WNDR3400V1, Netgear WNDR3400 V1},
U12H155T00_NETGEAR,},
++{{BCM47XX_BOARD_NETGEAR_WNDR3400V2, Netgear WNDR3400 V2},
U12H187T00_NETGEAR,},
+{{BCM47XX_BOARD_NETGEAR_WNDR3400VCNA, Netgear WNDR3400 Vcna},
U12H155T01_NETGEAR,},
+{{BCM47XX_BOARD_NETGEAR_WNDR3700V3, Netgear WNDR3700 V3},
U12H194T00_NETGEAR,},
+{{BCM47XX_BOARD_NETGEAR_WNDR4000, Netgear WNDR4000},
U12H181T00_NETGEAR,},
@@ -298,6 +299,7 @@
+BCM47XX_BOARD_NETGEAR_WGR614V9,
+BCM47XX_BOARD_NETGEAR_WNDR3300,
+BCM47XX_BOARD_NETGEAR_WNDR3400V1,
++BCM47XX_BOARD_NETGEAR_WNDR3400V2,
+BCM47XX_BOARD_NETGEAR_WNDR3400VCNA,
+BCM47XX_BOARD_NETGEAR_WNDR3700V3,
+BCM47XX_BOARD_NETGEAR_WNDR4000,
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] lldpd: upgrade to 0.7.1
Signed-off-by: Stijn Tintel st...@linux-ipv6.be --- package/network/services/lldpd/Makefile | 8 +--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/package/network/services/lldpd/Makefile b/package/network/services/lldpd/Makefile index f0983f7..024116c 100644 --- a/package/network/services/lldpd/Makefile +++ b/package/network/services/lldpd/Makefile @@ -8,18 +8,20 @@ include $(TOPDIR)/rules.mk PKG_NAME:=lldpd -PKG_VERSION:=0.6.1 -PKG_RELEASE:=2 +PKG_VERSION:=0.7.1 +PKG_RELEASE:=1 PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz PKG_SOURCE_URL:=http://media.luffy.cx/files/lldpd -PKG_MD5SUM:=d2f9ae67e0bcce0206a3a501a81d0738 +PKG_MD5SUM:=cee0e2ae7d4b8bf25ae234d9536052b8 PKG_MAINTAINER:=Jo-Philipp Wich j...@openwrt.org PKG_FIXUP:=autoreconf PKG_INSTALL:=1 +TARGET_CFLAGS+=--std=c99 + include $(INCLUDE_DIR)/package.mk define Package/lldpd -- 1.7.12.4 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
