Re: [OpenWrt-Devel] ramips dwc_otg DEVICE_ONLY mode build failed
Hi, I can't find try_wake_up() definition in kernel 3.10 and 3.9. Which openwrt version you compile it successfully? zhenjun_...@icloudaegis.com From: John Crispin Date: 2014-06-04 23:10 To: openwrt-devel Subject: Re: [OpenWrt-Devel] ramips dwc_otg DEVICE_ONLY mode build failed On 04/06/2014 16:47, zhenjun_...@icloudaegis.com wrote: I doubt that the base addr of udc is base: 0x1012_ in datasheet but 0xB012 in source. 0x1012_ == KSEG1(0xB012) i did not test. as i said i only compile tested for 7620 but have no HW to test with... ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-develel‘ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] hotplug / micro-optimization
i have a router here with 400 vlan-interfaces. i'am still not happy, that an hotplug-event triggers a lot of unneccesary action. i see at least 3 possibilities reduce the load: (beside the upcoming procd-interface job) 1) each script implements something like: #!/bin/sh /etc/init.d/$daemon enabled || exit 0 case $ACTION in ifup) ... ;; esac the part '/etc/init.d/$daemon enabled' is expensive, so we can instead call: . /etc/rc.common /etc/init.d/$daemon enabled || return 0 this saves _some_ cycles (2 seconds here for 400 hotplug-scripts, not much) 2) simply dont call a script when the corresponding daemon is not enabled. i'am not sure, if each hotplug-script has a coressponding /etc/init.d/$daemon script, if so - so would be fine (and easy to do) 3) during bootup or '/etc/init.d/$daemon enable' we build a directory for enabled scripts. while we are at it, we can e.g. call 'ifup'/$ACTION if the daemon supports/implements it, otherwise ignore what will be the best approach? bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] ramips dwc_otg DEVICE_ONLY mode build failed
Hi, I modify some code to correct compilation errors. But the board halt on boot. _ Is any one familiar with usb willing to help me? zhenjun_...@icloudaegis.com From: zhenjun_...@icloudaegis.com Date: 2014-06-05 16:16 To: john; openwrt-devel Subject: Re: Re: [OpenWrt-Devel] ramips dwc_otg DEVICE_ONLY mode build failed Hi, I can't find try_wake_up() definition in kernel 3.10 and 3.9. Which openwrt version you compile it successfully? zhenjun_...@icloudaegis.com From: John Crispin Date: 2014-06-04 23:10 To: openwrt-devel Subject: Re: [OpenWrt-Devel] ramips dwc_otg DEVICE_ONLY mode build failed On 04/06/2014 16:47, zhenjun_...@icloudaegis.com wrote: I doubt that the base addr of udc is base: 0x1012_ in datasheet but 0xB012 in source. 0x1012_ == KSEG1(0xB012) i did not test. as i said i only compile tested for 7620 but have no HW to test with... ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-develel‘ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] hostapd: move reading of rsn_preauth out of auth_type=eap context
On 2014-06-04 17:57, Reiner Herrmann wrote: rsn_preauth is used outside of case $auth_type, so if it is set for an EAP-enabled SSID, it would also be set for the following non-EAP-enabled SSIDs, because it would not be read again. Signed-off-by: Reiner Herrmann rei...@reiner-h.de Committed in r41012, thanks. - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Kirkwood kernel version
Hi, I am cleaning up my port for a kirkwood-based router, D-Link DIR-665. I see there are now some patches for 3.14, and a new 'router' subtarget. I reworked the port to use the new subtarget. Should I also rework it to use the newer kernel before I submit it? I should note it builds (after a minor dts patch) and boots, but crashes fairly quickly with the newer kernel. Thanks. -Claudio ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] openssl: version bump
Hello, today appeared another serious vulnerability in openssl. More info is here http://ccsinjection.lepidum.co.jp. Users are advised to update to openssl 1.0.1h. Signed-off-by: Martin Strbacka martin.strba...@nic.cz --- diff --git a/package/libs/openssl/Makefile b/package/libs/openssl/Makefile index 26833a3..fff260b 100644 --- a/package/libs/openssl/Makefile +++ b/package/libs/openssl/Makefile @@ -8,7 +8,7 @@ include $(TOPDIR)/rules.mk PKG_NAME:=openssl -PKG_VERSION:=1.0.1g +PKG_VERSION:=1.0.1h PKG_RELEASE:=1 PKG_USE_MIPS16:=0 @@ -18,7 +18,7 @@ PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz PKG_SOURCE_URL:=http://www.openssl.org/source/ \ ftp://ftp.funet.fi/pub/crypt/mirrors/ftp.openssl.org/source \ ftp://ftp.sunet.se/pub/security/tools/net/openssl/source/ -PKG_MD5SUM:=de62b43dfcd858e66a74bee1c834e959 +PKG_MD5SUM:=8d6d684a9430d5cc98a62a5d8fbda8cf PKG_LICENSE:=SSLEAY OPENSSL PKG_LICENSE_FILES:=LICENSE ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Fixed wpa_supplicant locking hostapd to 20MHz (#12720)
On 2014-06-04 11:51, Lance Chaney wrote: Fixed wpa_supplicant when the radio is in 40MHz mode so that it no longer restarts hostapd with the second channel disableed. Signed-off-by: Lance Chaney furryf...@gmail.com Applied in r41019, thanks! - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] brcm47xx: add mips74k subtarget for newer devices
All new devices (with MIPS 74K CPU) are based on BCMA SoC and have Ethernet core supported by bgmac. Create a new subtarget to generate optimized builds. This is just a beginning, further tweaks (like kernel configuration) are still possible. This decreases default root.squashfs by ~128 kB. Signed-off-by: Rafał Miłecki zaj...@gmail.com --- This patch depends on [PATCH V2] brcm47xx: move current target to generic subtarget --- target/linux/brcm47xx/Makefile| 2 +- .../brcm47xx/mips74k/profiles/100-Broadcom-b43.mk | 19 +++ .../brcm47xx/mips74k/profiles/101-Broadcom-brcsmac.mk | 19 +++ .../brcm47xx/mips74k/profiles/102-Broadcom-wl.mk | 19 +++ .../brcm47xx/mips74k/profiles/103-Broadcom-none.mk| 18 ++ target/linux/brcm47xx/mips74k/target.mk | 6 ++ 6 files changed, 82 insertions(+), 1 deletion(-) create mode 100644 target/linux/brcm47xx/mips74k/profiles/100-Broadcom-b43.mk create mode 100644 target/linux/brcm47xx/mips74k/profiles/101-Broadcom-brcsmac.mk create mode 100644 target/linux/brcm47xx/mips74k/profiles/102-Broadcom-wl.mk create mode 100644 target/linux/brcm47xx/mips74k/profiles/103-Broadcom-none.mk create mode 100644 target/linux/brcm47xx/mips74k/target.mk diff --git a/target/linux/brcm47xx/Makefile b/target/linux/brcm47xx/Makefile index fa5d21b..17a9e31 100644 --- a/target/linux/brcm47xx/Makefile +++ b/target/linux/brcm47xx/Makefile @@ -10,7 +10,7 @@ ARCH:=mipsel BOARD:=brcm47xx BOARDNAME:=Broadcom BCM47xx/53xx (MIPS) FEATURES:=squashfs usb pcmcia low_mem -SUBTARGETS:=generic +SUBTARGETS:=generic mips74k MAINTAINER:=Hauke Mehrtens ha...@hauke-m.de LINUX_VERSION:=3.10.36 diff --git a/target/linux/brcm47xx/mips74k/profiles/100-Broadcom-b43.mk b/target/linux/brcm47xx/mips74k/profiles/100-Broadcom-b43.mk new file mode 100644 index 000..7d3c6a7 --- /dev/null +++ b/target/linux/brcm47xx/mips74k/profiles/100-Broadcom-b43.mk @@ -0,0 +1,19 @@ +# +# Copyright (C) 2014 OpenWrt.org +# +# This is free software, licensed under the GNU General Public License v2. +# See /LICENSE for more information. +# + +define Profile/Broadcom-mips74k-b43 + NAME:=Broadcom SoC, BCM43xx WiFi (b43) + PACKAGES:=kmod-bgmac kmod-b43 +endef + +define Profile/Broadcom-mips74k-b43/Description + Package set for devices with BCM43xx WiFi including mac80211 and b43 + driver. +endef + +$(eval $(call Profile,Broadcom-mips74k-b43)) + diff --git a/target/linux/brcm47xx/mips74k/profiles/101-Broadcom-brcsmac.mk b/target/linux/brcm47xx/mips74k/profiles/101-Broadcom-brcsmac.mk new file mode 100644 index 000..2d09cd2 --- /dev/null +++ b/target/linux/brcm47xx/mips74k/profiles/101-Broadcom-brcsmac.mk @@ -0,0 +1,19 @@ +# +# Copyright (C) 2014 OpenWrt.org +# +# This is free software, licensed under the GNU General Public License v2. +# See /LICENSE for more information. +# + +define Profile/Broadcom-mips74k-brcmsmac + NAME:=Broadcom SoC, BCM43xx WiFi (brcmsmac) + PACKAGES:=kmod-bgmac kmod-brcmsmac +endef + +define Profile/Broadcom-mips74k-brcmsmac/Description + Package set for devices with BCM43xx WiFi including mac80211 and + brcmsmac driver. +endef + +$(eval $(call Profile,Broadcom-mips74k-brcmsmac)) + diff --git a/target/linux/brcm47xx/mips74k/profiles/102-Broadcom-wl.mk b/target/linux/brcm47xx/mips74k/profiles/102-Broadcom-wl.mk new file mode 100644 index 000..37063ac --- /dev/null +++ b/target/linux/brcm47xx/mips74k/profiles/102-Broadcom-wl.mk @@ -0,0 +1,19 @@ +# +# Copyright (C) 2014 OpenWrt.org +# +# This is free software, licensed under the GNU General Public License v2. +# See /LICENSE for more information. +# + +define Profile/Broadcom-mips74k-wl + NAME:=Broadcom SoC, BCM43xx WiFi (proprietary wl) + PACKAGES:=kmod-bgmac -wpad-mini kmod-brcm-wl wlc nas +endef + +define Profile/Broadcom-mips74k-wl/Description + Package set for devices with BCM43xx WiFi including proprietary (and + closed source) driver wl. +endef + +$(eval $(call Profile,Broadcom-mips74k-wl)) + diff --git a/target/linux/brcm47xx/mips74k/profiles/103-Broadcom-none.mk b/target/linux/brcm47xx/mips74k/profiles/103-Broadcom-none.mk new file mode 100644 index 000..bfe3719 --- /dev/null +++ b/target/linux/brcm47xx/mips74k/profiles/103-Broadcom-none.mk @@ -0,0 +1,18 @@ +# +# Copyright (C) 2014 OpenWrt.org +# +# This is free software, licensed under the GNU General Public License v2. +# See /LICENSE for more information. +# + +define Profile/Broadcom-mips74k-none + NAME:=Broadcom SoC, No WiFi + PACKAGES:=kmod-bgmac -wpad-mini +endef + +define Profile/Broadcom-mips74k-none/Description + Package set for devices without a WiFi. +endef + +$(eval $(call Profile,Broadcom-mips74k-none)) + diff --git a/target/linux/brcm47xx/mips74k/target.mk b/target/linux/brcm47xx/mips74k/target.mk new file mode 100644 index 000..ab7af28 --- /dev/null +++ b/target/linux/brcm47xx/mips74k/target.mk @@
[OpenWrt-Devel] WRT54GS v1.0 GPIO definitions in r41004
Hi,
I've got a WRT54GS v1.0 and trying to run r41004 on it. I'm having
trouble with assignment of GPIOs.
The model number on the case, serial no, MAC and FCC ID all match a
WRT54GS v1.0 according to:
https://wikidevi.com/wiki/Linksys_WRT54GS_v1.0
But my nvram has these board parameters:
boardtype=0x0101
boardnum=42
boardrev=0x10
(full nvram dump: http://pastebin.com/FVkddFSi)
which in arch/mips/bcm47xx/board.c gets mapped to:
{{BCM47XX_BOARD_LINKSYS_WRT54G, Linksys WRT54G/GS/GL}, 0x0101,
42, 0x10},
with these LED definitions:
bcm47xx_leds_linksys_wrt54gsv1[] __initconst = {
BCM47XX_GPIO_LED(0, unk, dmz, 1, LEDS_GPIO_DEFSTATE_OFF),
BCM47XX_GPIO_LED(1, unk, power, 0, LEDS_GPIO_DEFSTATE_ON),
BCM47XX_GPIO_LED(5, white, wps, 1, LEDS_GPIO_DEFSTATE_OFF),
BCM47XX_GPIO_LED(7, orange, wps, 1, LEDS_GPIO_DEFSTATE_OFF),
};
I have DMZ and power LEDs, but they're on different GPIOs, and I don't
have a WPS LED (front panel looks like this:
http://www.rootdir.de/linksys_wrt54gs/wrt54gs_rev1.1_5.jpg).
I did some experimentation and this is my GPIO layout:
GPIOs 0-15, ssb_chipco_gpio:
gpio-0 (sysfs ) out hi WLAN LED active high
gpio-1 (sysfs ) out lo PWR LED 0=blink 1=on
gpio-2 (adm_eecs) in lo
gpio-3 (adm_eesk) in lo
gpio-4 (sysfs ) in hi
gpio-5 (adm_eedi) in lo
gpio-6 (adm_eerc) in hi RESET BTN active low
gpio-7 (sysfs ) in hi DMZ LED active low
gpio-8 (sysfs ) in lo
gpio-9 (sysfs ) in lo
gpio-10 (sysfs ) in lo
gpio-11 (sysfs ) in lo
gpio-12 (sysfs ) in lo
gpio-13 (sysfs ) in lo
gpio-14 (sysfs ) in lo
gpio-15 (sysfs ) in lo
which most closely matches WRTSL54GS (except no WPS LED).
The ADM pins also might be wrong (despite definitions in the nvram
that point to those pins). My switch gets detected but when I do
swconfig switch0 show my system reboots.
It feels like I have a WRT54GS v1.0 hardware with WRT54G NVRAM. Does
anyone have a WRT54GS v1.0 nvram dump to compare? WRTSL54GS dump would
also be nice.
Catalin
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] WRT54GS v1.0 GPIO definitions in r41004
Here is dmesg also:
http://pastebin.com/ZHXdd3PK
Note:
[ 12.58] gpio-keys gpio-keys.0: unable to claim gpio 6, err=-16
[ 12.66] gpio-keys: probe of gpio-keys.0 failed with error -16
[ 12.90] leds-gpio: probe of leds-gpio failed with error -16
I also have trouble with sysupgrade. I can load a new firmware image
using TFTP to the bootloader, but if I try a OpenWrt-OpenWrt upgrade
using sysupgrade, the system never reboots and gets stuck in the
bootloader when I powercycle. I can then flash the same image using
TFTP and it works (so I think the image is OK, but some issue with
sysupgrade).
On Thu, Jun 5, 2014 at 1:12 PM, Catalin Patulea c...@vv.carleton.ca wrote:
Hi,
I've got a WRT54GS v1.0 and trying to run r41004 on it. I'm having
trouble with assignment of GPIOs.
The model number on the case, serial no, MAC and FCC ID all match a
WRT54GS v1.0 according to:
https://wikidevi.com/wiki/Linksys_WRT54GS_v1.0
But my nvram has these board parameters:
boardtype=0x0101
boardnum=42
boardrev=0x10
(full nvram dump: http://pastebin.com/FVkddFSi)
which in arch/mips/bcm47xx/board.c gets mapped to:
{{BCM47XX_BOARD_LINKSYS_WRT54G, Linksys WRT54G/GS/GL}, 0x0101,
42, 0x10},
with these LED definitions:
bcm47xx_leds_linksys_wrt54gsv1[] __initconst = {
BCM47XX_GPIO_LED(0, unk, dmz, 1, LEDS_GPIO_DEFSTATE_OFF),
BCM47XX_GPIO_LED(1, unk, power, 0, LEDS_GPIO_DEFSTATE_ON),
BCM47XX_GPIO_LED(5, white, wps, 1, LEDS_GPIO_DEFSTATE_OFF),
BCM47XX_GPIO_LED(7, orange, wps, 1, LEDS_GPIO_DEFSTATE_OFF),
};
I have DMZ and power LEDs, but they're on different GPIOs, and I don't
have a WPS LED (front panel looks like this:
http://www.rootdir.de/linksys_wrt54gs/wrt54gs_rev1.1_5.jpg).
I did some experimentation and this is my GPIO layout:
GPIOs 0-15, ssb_chipco_gpio:
gpio-0 (sysfs ) out hi WLAN LED active high
gpio-1 (sysfs ) out lo PWR LED 0=blink 1=on
gpio-2 (adm_eecs) in lo
gpio-3 (adm_eesk) in lo
gpio-4 (sysfs ) in hi
gpio-5 (adm_eedi) in lo
gpio-6 (adm_eerc) in hi RESET BTN active low
gpio-7 (sysfs ) in hi DMZ LED active low
gpio-8 (sysfs ) in lo
gpio-9 (sysfs ) in lo
gpio-10 (sysfs ) in lo
gpio-11 (sysfs ) in lo
gpio-12 (sysfs ) in lo
gpio-13 (sysfs ) in lo
gpio-14 (sysfs ) in lo
gpio-15 (sysfs ) in lo
which most closely matches WRTSL54GS (except no WPS LED).
The ADM pins also might be wrong (despite definitions in the nvram
that point to those pins). My switch gets detected but when I do
swconfig switch0 show my system reboots.
It feels like I have a WRT54GS v1.0 hardware with WRT54G NVRAM. Does
anyone have a WRT54GS v1.0 nvram dump to compare? WRTSL54GS dump would
also be nice.
Catalin
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] WRT54GS v1.0 GPIO definitions in r41004
On 5 June 2014 19:12, Catalin Patulea c...@vv.carleton.ca wrote:
Hi,
I've got a WRT54GS v1.0 and trying to run r41004 on it. I'm having
trouble with assignment of GPIOs.
The model number on the case, serial no, MAC and FCC ID all match a
WRT54GS v1.0 according to:
https://wikidevi.com/wiki/Linksys_WRT54GS_v1.0
But my nvram has these board parameters:
boardtype=0x0101
boardnum=42
boardrev=0x10
(full nvram dump: http://pastebin.com/FVkddFSi)
which in arch/mips/bcm47xx/board.c gets mapped to:
{{BCM47XX_BOARD_LINKSYS_WRT54G, Linksys WRT54G/GS/GL}, 0x0101,
42, 0x10},
with these LED definitions:
bcm47xx_leds_linksys_wrt54gsv1[] __initconst = {
BCM47XX_GPIO_LED(0, unk, dmz, 1, LEDS_GPIO_DEFSTATE_OFF),
BCM47XX_GPIO_LED(1, unk, power, 0, LEDS_GPIO_DEFSTATE_ON),
BCM47XX_GPIO_LED(5, white, wps, 1, LEDS_GPIO_DEFSTATE_OFF),
BCM47XX_GPIO_LED(7, orange, wps, 1, LEDS_GPIO_DEFSTATE_OFF),
};
I have DMZ and power LEDs, but they're on different GPIOs, and I don't
have a WPS LED (front panel looks like this:
http://www.rootdir.de/linksys_wrt54gs/wrt54gs_rev1.1_5.jpg).
I did some experimentation and this is my GPIO layout:
GPIOs 0-15, ssb_chipco_gpio:
gpio-0 (sysfs ) out hi WLAN LED active high
gpio-1 (sysfs ) out lo PWR LED 0=blink 1=on
gpio-2 (adm_eecs) in lo
gpio-3 (adm_eesk) in lo
gpio-4 (sysfs ) in hi
gpio-5 (adm_eedi) in lo
gpio-6 (adm_eerc) in hi RESET BTN active low
gpio-7 (sysfs ) in hi DMZ LED active low
gpio-8 (sysfs ) in lo
gpio-9 (sysfs ) in lo
gpio-10 (sysfs ) in lo
gpio-11 (sysfs ) in lo
gpio-12 (sysfs ) in lo
gpio-13 (sysfs ) in lo
gpio-14 (sysfs ) in lo
gpio-15 (sysfs ) in lo
which most closely matches WRTSL54GS (except no WPS LED).
The ADM pins also might be wrong (despite definitions in the nvram
that point to those pins). My switch gets detected but when I do
swconfig switch0 show my system reboots.
It feels like I have a WRT54GS v1.0 hardware with WRT54G NVRAM. Does
anyone have a WRT54GS v1.0 nvram dump to compare? WRTSL54GS dump would
also be nice.
Catalin
--
Rafał
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] WRT54GS v1.0 GPIO definitions in r41004
On 5 June 2014 19:12, Catalin Patulea c...@vv.carleton.ca wrote: It feels like I have a WRT54GS v1.0 hardware with WRT54G NVRAM. Does anyone have a WRT54GS v1.0 nvram dump to compare? WRTSL54GS dump would also be nice. See attached file (I've just added your case to it). 0x0101/42/0x10 seems correct for WRT54GS V1.0 (I found it in 2 other places too). As you noticed, it's also the same for WRT54G V2. It seems we need to split this set of WRT54G* a bit. -- Rafał DEVICE VER eou_device_id type/num/revboardflags other source WRT54G V2 0x0101/42/0x10 0x0188 https://forum.openwrt.org/viewtopic.php?id=9220 WRT54G V2 HDIVKKAS0x0708/42/0x10 0x0118 https://forum.openwrt.org/viewtopic.php?id=2469 WRT54G V2.2HDIVKKAS0x0708/42/0x10 0x0118 https://forum.openwrt.org/viewtopic.php?id=2469 WRT54G V2.2K4TRV2ON0x0708/42/0x10 0x0118 ftp://ftp.ens-cachan.fr/pub/OpenWRT/openwrt.org/forum/viewtopic.php%3Fid=1065 WRT54G V2.2CXLVVGWQ0x0708/42/0x10 0x0118 router_name=WRT54G https://freewrt.org/scm/viewvc.php/trunk/freewrt/docs/hardware/linksys/wrt54g_v22/nvram.txt?pathrev=1root=freewrtview=diffr1=1r2=1diff_format=s WRT54G V3 S344KOPU0x0708/ /0x10 0x0118 https://forum.openwrt.org/viewtopic.php?id=21189 WRT54G V3.1ZXLDPXAY0x0708/42/0x10 0x0118 router_name=WRT54G https://forum.openwrt.org/viewtopic.php?id=19553 WRT54G V3.1LOYJFJFB0x0708/42/0x10 0x0118 router_name=funkstar-ac https://forum.openwrt.org/viewtopic.php?id=2297 WRT54G V4 UVOZES9I0x0467/42/0x10 0x2558 https://forum.openwrt.org/viewtopic.php?id=4660 WRT54GS V1 0x0101/42/0x10 0x0388 MIPS: BCM47XX: add board detection for Linksys WRT54GS V1 WRT54GS V1 0x0101/42/0x10 0x0388 https://forum.openwrt.org/viewtopic.php?id=8107 WRT54GS V1 0x0101/42/0x10 0x0388 https://lists.openwrt.org/pipermail/openwrt-devel/2014-June/025865.html WRT54GS V1.1MLTOWWH20x0708/42/0x10 0x0318 https://forum.openwrt.org/viewtopic.php?id=8632 WRT54GS V1.1F7QVRQQK0x0708/42/0x10 0x0318 https://freewrt.org/scm/viewvc.php/trunk/freewrt/docs/hardware/linksys/wrt54gs_v11/nvram.txt?pathrev=1root=freewrtview=diffr1=1r2=1diff_format=s WRT54GS V1.1*HIDDEN*0x0708/42/0x10 0x0318 https://forum.openwrt.org/viewtopic.php?id=1750 WRT54GS V1.1F7QVRQQK0x0708/42/0x10 0x0318 https://dev.openwrt.org/browser/trunk/openwrt/docs/hardware/linksys/wrt54gs_v11/nvram.txt?rev=988 WRT54GS V2.1RJXXM7QF0x0708/42/0x10 0x0318 https://forum.openwrt.org/viewtopic.php?id=4776 WRT54GS V3 E49LQUHI0x0467/42/0x10 0x2758 https://forum.openwrt.org/viewtopic.php?id=4938 WRT54GS V4 KMJACURU0x0467/42/0x10 0x2758 gnu...@no-log.org WRT54GS V4 RD3FEIIC0x0467/42/0x10 0x2758 https://forum.openwrt.org/viewtopic.php?id=3158 WRT54GL V1.1OQZN5CA90x0467/42/0x10 0x2558 https://forum.openwrt.org/viewtopic.php?id=8253 WRT54GL V1.1YA4PZDZC0x0467/42/0x10 0x2558 https://forum.openwrt.org/viewtopic.php?id=6332 WRTSL54GS 0x042f/42/0x10 0x0018 machine_comment=WRTSL54GS machine_name=WRTSL54GS router_name=WRTSL54GS https://dev.openwrt.org/ticket/13319 WTR54GS 0x456/56/0x10 http://svn.dd-wrt.com/changeset/12225 WRT54G3G V2 0x042f/42/0x10 0x0018 boot_hw_model=WRT54G3GV2-VF https://dev.openwrt.org/ticket/11674 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Kirkwood kernel version
Hi Claudio, On Thu, Jun 05, 2014 at 08:22:13AM -0400, Claudio Leite wrote: I am cleaning up my port for a kirkwood-based router, D-Link DIR-665. I see there are now some patches for 3.14, and a new 'router' subtarget. I reworked the port to use the new subtarget. Should I also rework it to use the newer kernel before I submit it? Please add support for 3.14 as well. It would be good that you add support for uboot-kirkwood and uboot-envtools package. I should note it builds (after a minor dts patch) and boots, but crashes fairly quickly with the newer kernel. Please fix that ;) I don't have that board so you are pretty much on your own there. If you are unsure about your patches you can post them as [RFC] so we can take a look... Luka ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] brcm47xx: add mips74k subtarget for newer devices
On 06/05/2014 05:34 PM, Rafał Miłecki wrote: All new devices (with MIPS 74K CPU) are based on BCMA SoC and have Ethernet core supported by bgmac. Create a new subtarget to generate optimized builds. This is just a beginning, further tweaks (like kernel configuration) are still possible. This decreases default root.squashfs by ~128 kB. Signed-off-by: Rafał Miłecki zaj...@gmail.com --- This patch depends on [PATCH V2] brcm47xx: move current target to generic subtarget --- target/linux/brcm47xx/Makefile| 2 +- .../brcm47xx/mips74k/profiles/100-Broadcom-b43.mk | 19 +++ .../brcm47xx/mips74k/profiles/101-Broadcom-brcsmac.mk | 19 +++ .../brcm47xx/mips74k/profiles/102-Broadcom-wl.mk | 19 +++ .../brcm47xx/mips74k/profiles/103-Broadcom-none.mk| 18 ++ target/linux/brcm47xx/mips74k/target.mk | 6 ++ 6 files changed, 82 insertions(+), 1 deletion(-) create mode 100644 target/linux/brcm47xx/mips74k/profiles/100-Broadcom-b43.mk create mode 100644 target/linux/brcm47xx/mips74k/profiles/101-Broadcom-brcsmac.mk create mode 100644 target/linux/brcm47xx/mips74k/profiles/102-Broadcom-wl.mk create mode 100644 target/linux/brcm47xx/mips74k/profiles/103-Broadcom-none.mk create mode 100644 target/linux/brcm47xx/mips74k/target.mk Thank you for your patch, it was committed in r41025. Hauke ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH V2] brcm47xx: move current target to generic subtarget
On 06/02/2014 11:34 PM, Rafał Miłecki wrote: This allows creating more subtargets and optimize builds per family. Signed-off-by: Rafał Miłecki zaj...@gmail.com --- V2: Rebase to apply after brcm47xx: enable the low-memory feature flag --- target/linux/brcm47xx/Makefile | 7 ++- .../brcm47xx/generic/profiles/100-Broadcom-b43.mk| 20 .../brcm47xx/generic/profiles/101-Broadcom-wl.mk | 20 .../brcm47xx/generic/profiles/104-Broadcom-ath5k.mk | 19 +++ .../brcm47xx/generic/profiles/105-Broadcom-none.mk | 18 ++ .../generic/profiles/200-Broadcom-b44-b43.mk | 20 .../brcm47xx/generic/profiles/201-Broadcom-b44-wl.mk | 20 .../generic/profiles/204-Broadcom-b44-ath5k.mk | 19 +++ .../generic/profiles/205-Broadcom-b44-none.mk| 18 ++ .../generic/profiles/210-Broadcom-tg3-b43.mk | 20 .../brcm47xx/generic/profiles/211-Broadcom-tg3-wl.mk | 20 .../generic/profiles/215-Broadcom-tg3-none.mk| 18 ++ .../generic/profiles/220-Broadcom-bgmac-b43.mk | 20 .../generic/profiles/221-Broadcom-bgmac-wl.mk| 20 .../generic/profiles/225-Broadcom-bgmac-none.mk | 18 ++ .../generic/profiles/226-Broadcom-bgmac-brcsmac.mk | 20 target/linux/brcm47xx/generic/profiles/PS-1208MFG.mk | 18 ++ target/linux/brcm47xx/generic/profiles/WGT634U.mk| 17 + .../linux/brcm47xx/generic/profiles/WL500GPv1-ATH.mk | 16 target/linux/brcm47xx/generic/profiles/WRT350Nv1.mk | 16 target/linux/brcm47xx/generic/profiles/WRTSL54GS.mk | 17 + target/linux/brcm47xx/generic/target.mk | 6 ++ target/linux/brcm47xx/image/Makefile | 20 ++-- target/linux/brcm47xx/profiles/100-Broadcom-b43.mk | 20 target/linux/brcm47xx/profiles/101-Broadcom-wl.mk| 20 target/linux/brcm47xx/profiles/104-Broadcom-ath5k.mk | 19 --- target/linux/brcm47xx/profiles/105-Broadcom-none.mk | 18 -- .../linux/brcm47xx/profiles/200-Broadcom-b44-b43.mk | 20 .../linux/brcm47xx/profiles/201-Broadcom-b44-wl.mk | 20 .../brcm47xx/profiles/204-Broadcom-b44-ath5k.mk | 19 --- .../linux/brcm47xx/profiles/205-Broadcom-b44-none.mk | 18 -- .../linux/brcm47xx/profiles/210-Broadcom-tg3-b43.mk | 20 .../linux/brcm47xx/profiles/211-Broadcom-tg3-wl.mk | 20 .../linux/brcm47xx/profiles/215-Broadcom-tg3-none.mk | 18 -- .../brcm47xx/profiles/220-Broadcom-bgmac-b43.mk | 20 .../linux/brcm47xx/profiles/221-Broadcom-bgmac-wl.mk | 20 .../brcm47xx/profiles/225-Broadcom-bgmac-none.mk | 18 -- .../brcm47xx/profiles/226-Broadcom-bgmac-brcsmac.mk | 20 target/linux/brcm47xx/profiles/PS-1208MFG.mk | 18 -- target/linux/brcm47xx/profiles/WGT634U.mk| 17 - target/linux/brcm47xx/profiles/WL500GPv1-ATH.mk | 16 target/linux/brcm47xx/profiles/WRT350Nv1.mk | 16 target/linux/brcm47xx/profiles/WRTSL54GS.mk | 17 - 43 files changed, 396 insertions(+), 385 deletions(-) create mode 100644 target/linux/brcm47xx/generic/profiles/100-Broadcom-b43.mk create mode 100644 target/linux/brcm47xx/generic/profiles/101-Broadcom-wl.mk create mode 100644 target/linux/brcm47xx/generic/profiles/104-Broadcom-ath5k.mk create mode 100644 target/linux/brcm47xx/generic/profiles/105-Broadcom-none.mk create mode 100644 target/linux/brcm47xx/generic/profiles/200-Broadcom-b44-b43.mk create mode 100644 target/linux/brcm47xx/generic/profiles/201-Broadcom-b44-wl.mk create mode 100644 target/linux/brcm47xx/generic/profiles/204-Broadcom-b44-ath5k.mk create mode 100644 target/linux/brcm47xx/generic/profiles/205-Broadcom-b44-none.mk create mode 100644 target/linux/brcm47xx/generic/profiles/210-Broadcom-tg3-b43.mk create mode 100644 target/linux/brcm47xx/generic/profiles/211-Broadcom-tg3-wl.mk create mode 100644 target/linux/brcm47xx/generic/profiles/215-Broadcom-tg3-none.mk create mode 100644 target/linux/brcm47xx/generic/profiles/220-Broadcom-bgmac-b43.mk create mode 100644 target/linux/brcm47xx/generic/profiles/221-Broadcom-bgmac-wl.mk create mode 100644 target/linux/brcm47xx/generic/profiles/225-Broadcom-bgmac-none.mk create mode 100644
Re: [OpenWrt-Devel] [PATCH] openssl: version bump
On 06/05/2014 03:13 PM, Martin Strbačka wrote: Hello, today appeared another serious vulnerability in openssl. More info is here http://ccsinjection.lepidum.co.jp. Users are advised to update to openssl 1.0.1h. Signed-off-by: Martin Strbacka martin.strba...@nic.cz --- Thank you for your patch, it was committed in r41026 and 41027. Hauke ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] openssl: version bump
today appeared another serious vulnerability in openssl. More info is here http://ccsinjection.lepidum.co.jp. Users are advised to update to openssl 1.0.1h. Thank you for your patch, it was committed in r41026 and 41027. Will there be a backport to AA 12.09? best regards -- Joerg Jungermann ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] WRT54GS v1.0 GPIO definitions in r41004
On Jun 5, 2014 4:13 PM, Rafał Miłecki zaj...@gmail.com wrote: See attached file (I've just added your case to it). 0x0101/42/0x10 seems correct for WRT54GS V1.0 (I found it in 2 other places too). As you noticed, it's also the same for WRT54G V2. Thanks for this. Do you know if the GPIO layout is the same for WRT54GS V1.0 and WRT54G V2? It seems we need to split this set of WRT54G* a bit. I suspect that you are implying that the GPIO layouts are *not* the same and we will need to split by boardflags, is that correct? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] openssl: version bump
On Jun 5, 2014 2:54 PM, joerg jungermann j...@borkum.net wrote: today appeared another serious vulnerability in openssl. More info is here http://ccsinjection.lepidum.co.jp. Users are advised to update to openssl 1.0.1h. Thank you for your patch, it was committed in r41026 and 41027. Will there be a backport to AA 12.09? There has been one just applied in r41027 best regards -- Joerg Jungermann ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] WRT54GS v1.0 GPIO definitions in r41004
Also seems package/broadcom-diag/src/diag.c's legacy detection default WRT54G layout is correct for my board. But I guess nowadays diag.c uses board.c information first. On Thu, Jun 5, 2014 at 6:38 PM, Catalin Patulea c...@vv.carleton.ca wrote: On Jun 5, 2014 4:13 PM, Rafał Miłecki zaj...@gmail.com wrote: See attached file (I've just added your case to it). 0x0101/42/0x10 seems correct for WRT54GS V1.0 (I found it in 2 other places too). As you noticed, it's also the same for WRT54G V2. Thanks for this. Do you know if the GPIO layout is the same for WRT54GS V1.0 and WRT54G V2? It seems we need to split this set of WRT54G* a bit. I suspect that you are implying that the GPIO layouts are *not* the same and we will need to split by boardflags, is that correct? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] hotplug / micro-optimization
On 5 Jun 2014 04:19, Bastian Bittorf bitt...@bluebottle.com wrote: 3) during bootup or '/etc/init.d/$daemon enable' we build a directory for enabled scripts. while we are at it, we can e.g. call 'ifup'/$ACTION if the daemon supports/implements it, otherwise ignore You mean the symlinks in /etc/rcS/? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
