Re: [OpenWrt-Devel] [PATCH] fix typo in netifd.sh
On 20/01/2015 18:44, Cezary Jackiewicz wrote:
$ht variable is not passed. $htmode is.
With this, wpa_supplicant-phy0.conf contains htmode line if htmode is set in
config.
Signed-off-by: Cezary Jackiewicz cezary.jackiew...@gmail.com
---
diff --git a/package/network/services/hostapd/files/netifd.sh
b/package/network/services/hostapd/files/netifd.sh
index d625709..436eee3 100644
--- a/package/network/services/hostapd/files/netifd.sh
+++ b/package/network/services/hostapd/files/netifd.sh
@@ -595,8 +595,7 @@ wpa_supplicant_add_network() {
append network_data mcast_rate=$mc_rate $N$T
}
- local ht_str
- [ -n $ht ] append network_data htmode=$ht $N$T
+ [ -n $htmode ] append network_data htmode=$htmode $N$T
this patch is wrong for the following reasons
* the htmode values inside netifd-wireless.sh are not the same values
that wpa_supplicant expects
* wpa_supplicant should automagically detect the channel (and the HT40
ext chan)
this leads me to wonder why you need this and an option would be 2 adhoc
clients.
can you explain your wifi setup so that we can figure out how to
properly fix this ?
cat $_config EOF
network={
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] fix typo in netifd.sh
On 23/01/2015 18:27, Cezary Jackiewicz wrote:
Dnia 2015-01-22, o godz. 14:41:33
John Crispin blo...@openwrt.org napisał(a):
can you explain your wifi setup so that we can figure out how to
properly fix this ?
config wifi-device 'radio1'
option type 'mac80211'
option hwmode '11a'
option path 'pci:00/:00:00.0'
option disabled '0'
option htmode 'HT20'
option channel '48'
config wifi-iface
option device 'radio1'
option encryption 'psk2'
option key '1234567890'
option network 'wlan'
option mode 'adhoc'
option ssid 'link-5g'
Without patch I've got
root@OpenWrt:~# cat /var/run/wpa_supplicant-wlan1.conf
ap_scan=2
network={
scan_ssid=0
ssid=link-5g
key_mgmt=WPA-PSK
mode=1
fixed_freq=1
frequency=5240
mode=1
psk=1234567890
proto=RSN
}
iw wlan1 info shows only 20 MHz (no HT) and iw wlan1 station dump - tx/rx
54MBit
With patch:
root@OpenWrt:~# cat /var/run/wpa_supplicant-wlan1.conf
ap_scan=2
network={
scan_ssid=0
ssid=link-5g
key_mgmt=WPA-PSK
mode=1
fixed_freq=1
frequency=5240
mode=1
psk=1234567890
proto=RSN
htmode=HT20
}
iw wlan1 info shows channel 48 (5240 MHz), width: 20 MHz, center1: 5240 MHz
(width: 40 MHz with channel 36 and HT40+); iw wlan1 station dump shows
bitrate
rx bitrate: 115.6 MBit/s MCS 13 short GI
tx bitrate: 57.8 MBit/s MCS 5 short GI
rx bitrate: 86.7 MBit/s MCS 12 short GI
etc.
ok, so it is adhoc mode. in this case the feature does make sense. the
problem is that the values provided by netifd-wireless.sh cannot
directly be translated to wpa_supplicant values. additionally yor patch
should ensure that values are only applied for adhoc networks. i will
put this on my list and investigate a bit further.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ramips:Fix mt7612 support for Xiaomi Mini.
On 04/02/2015 17:08, Roger Pueyo Centelles wrote: Hi, 2015-02-04 12:44 GMT+01:00 Chuanhong Guo gch981...@gmail.com mailto:gch981...@gmail.com: From: 郭传鈜 gch981...@gmail.com mailto:gch981...@gmail.com 2ghz should be disabled on this router. You're right. This should be patched. And I think 'mediatek,mtd-eeprom' should be defined asfactory 32768 instead of factory 0x8000 according to WHR-1166D.dts Actually I didn't have this router.But I think this is the reason that the MT7612E radio always gets a random MAC address on this router. Both definitions are the same, since 0x8000 hex == 32768 dec. try 0x8004 as 0x8000 holds the chip id and right after that is where the mac is located BTW,Roger,could you please test if this patch can fix the MAC address problem you told in your mail? I tried both, with equal results. ___ 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] [PATCH] ramips: delete unused file
On 04/02/2015 07:04, John Crispin wrote: On 04/02/2015 07:02, Cezary Jackiewicz wrote: These file is not used by system. erm, how is that unused ? people use it for hooking stuff into the motion detection of the belkin webcams. if at all, move it into the matching driver package moving it wont work as the matching kernel patch is currently inside the ralink folder Signed-off-by: Cezary Jackiewicz cezary.jackiew...@gmail.com --- diff --git a/target/linux/ramips/base-files/etc/hotplug.d/usb/10-motion b/target/linux/ramips/base-files/etc/hotplug.d/usb/10-motion deleted file mode 100644 index e96acc8..000 --- a/target/linux/ramips/base-files/etc/hotplug.d/usb/10-motion +++ /dev/null @@ -1 +0,0 @@ -[ $ACTION = motion ] logger webcam motion event ___ 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] [PATCH] ramips: delete unused file
On 04/02/2015 07:02, Cezary Jackiewicz wrote: These file is not used by system. erm, how is that unused ? people use it for hooking stuff into the motion detection of the belkin webcams. if at all, move it into the matching driver package Signed-off-by: Cezary Jackiewicz cezary.jackiew...@gmail.com --- diff --git a/target/linux/ramips/base-files/etc/hotplug.d/usb/10-motion b/target/linux/ramips/base-files/etc/hotplug.d/usb/10-motion deleted file mode 100644 index e96acc8..000 --- a/target/linux/ramips/base-files/etc/hotplug.d/usb/10-motion +++ /dev/null @@ -1 +0,0 @@ -[ $ACTION = motion ] logger webcam motion event ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ramips:Fix mt7612 support for Xiaomi Mini.
On 04/02/2015 20:18, Roger Pueyo Centelles wrote: Hi, I tried with 0x8004 and I also got a random IP address. Actually, I changed this block in in eeprom.c (line 571) [1]: can you do a hexdump -C /dev/mtd2 and paste the output please ? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ramips:Fix mt7612 support for Xiaomi Mini.
On 04/02/2015 22:11, Roger Pueyo Centelles wrote:
root@OpenWrt:/# hexdump -C /dev/mtd2
20 76 05 01 64 09 80 01 66 5d ff ff ff ff ff ff |
v..d...f]..|
0010 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
||
0020 ff ff ff ff ff ff ff ff 64 09 80 01 66 5c 00 d0
|d...f\..|
0030 59 60 00 04 22 0c 04 04 ff ff 15 01 55 77 a8 aa
|Y`.Uw..|
0040 8c 88 ff ff 0d 00 00 00 00 00 00 00 00 00 ff ff
||
0050 ff ff 10 10 10 10 10 10 11 11 11 11 11 11 12 12
||
0060 12 12 12 12 12 12 13 13 13 14 14 14 15 15 80 ff
||
0070 ff ff 80 ff ff ff 00 f4 ff ff ff ff ff ff ff ff
||
0080 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
||
*
00d0 1e 00 ff ff ff ff ff ff ff ff ff ff ff ff 08 08
||
00e0 06 06 04 00 06 06 04 00 06 06 04 00 06 06 04 00
||
00f0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
||
*
8000 62 76 00 00 64 09 80 01 66 5e 62 76 c3 14 00 00
^^ that is the mac at 0x8004
|bv..d...f^bv|
8010 00 00 62 76 c3 14 00 00 00 00 ff ff ff ff ff ff
|..bv|
8020 ff ff 37 d8 9d 00 60 7f fd 9b ff ff ff ff ff ff
|..7...`.|
8030 ff ff ff ff 22 ff 00 20 ff ff 9b 01 00 00 00 00 |..
|
8040 00 00 ff df 00 82 00 00 00 81 00 00 00 00 e0 01
||
8050 00 00 00 00 00 00 84 0a 1a 00 00 00 83 0b 1a 00
||
8060 00 00 7a 06 22 82 82 7a 06 22 82 82 78 08 22 82
|..z...z...x..|
8070 82 7e 02 22 82 82 76 16 22 82 82 75 1c 22 82 82
|.~...v...u...|
8080 79 0a 22 82 82 79 0a 22 82 82 7b 06 22 82 82 77
|y...y...{...w|
8090 14 22 82 82 7e 05 22 82 82 79 11 22 82 82 00 1b
|...~...y.|
80a0 c3 c3 c3 c3 00 00 c4 c4 c2 82 c4 c4 c2 82 00 00
||
80b0 00 00 c4 c4 c2 00 00 00 00 00 c2 c2 82 82 86 00
||
80c0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
||
*
80f0 ff ff ff ff ff ff ff ff 22 ff ff ff ff ff ff ff
|...|
8100 0f ca 74 c5 e8 07 30 3d 01 b0 08 26 00 0e 04 15
|..t...0=...|
8110 00 8a 00 40 00 00 00 08 00 9d 08 00 12 c0 00 00
|...@|
8120 08 20 04 2a 90 00 00 24 01 04 54 08 d0 a0 28 20 |.
.*...$..T...( |
8130 ff ff ff ff ff ff ff 08 ff ff ff ff ff ff 00 00
||
8140 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
||
*
81e0 c0 81 82 c3 04 45 46 07 08 09 ff ff ff ff ff ff
|.EF.|
81f0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
||
*
0001
The MACs are there, at 0x4, 0x28 and 0x8004.
2015-02-04 20:29 GMT+01:00 John Crispin blo...@openwrt.org
mailto:blo...@openwrt.org:
On 04/02/2015 20:18, Roger Pueyo Centelles wrote:
Hi,
I tried with 0x8004 and I also got a random IP address. Actually,
I changed this block in in eeprom.c (line 571) [1]:
can you do a hexdump -C /dev/mtd2 and paste the output please ?
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] How to fix the unknown in the IWINFO
On 05/02/2015 04:56, INYO L wrote: Hi, How can I read the TX power, Signal, and others root@WirelessRouter:/etc# iwinfo wlan0 ESSID: wifi Access Point: 00:0F:02:70:3C:20 Mode: Master Channel: 11 (2.462 GHz) Tx-Power: 20 dBm Link Quality: unknown/70 Signal: unknown Noise: unknown Bit Rate: unknown Encryption: none Type: nl80211 HW Mode(s): 802.11bgn Hardware: unknown [Generic MAC80211] TX power offset: unknown Frequency offset: unknown Supports VAPs: yes PHY name: phy0 Thank you ! which hardware / driver are you using ? ___ 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] AsiaRF AWM002 (ramips) USB and reboot broken at r44044
On 03/02/2015 09:01, Christian Lamparter wrote:
On Tue, Feb 3, 2015 at 8:43 AM, John Crispin blo...@openwrt.org
wrote:
On 03/02/2015 08:36, Christian Lamparter wrote:
Thing is: ralink-phy.c can use some more work!
elaborate on what needs work
Link to github-source:
https://github.com/openwrt-mirror/openwrt/blob/master/target/linux/ramips/patches-3.14/0037-USB-phy-add-ralink-SoC-driver.patch#L102
if (OTG_STATE_B_HOST) { rt_sysc_m32(0, RT_SYSCFG1_USB0_HOST_MODE,
RT_SYSC_REG_SYSCFG1); if (!IS_ERR(rsthost))
reset_control_deassert(rsthost); } else { ...
rt_sysc_m32(RT_SYSCFG1_USB0_HOST_MODE, 0, RT_SYSC_REG_SYSCFG1);
if (!IS_ERR(rstdev)) reset_control_deassert(rstdev); }
What about OTG, Is it not supported? The constant
(OTG_STATE_B_HOST) will always evaluate to true.
OTG is not supported and never has until now due to missing drivers.
try to make a statement rather than encapsulating what you are trying
to say in a question please, because i still don't get what
you mean with needs work
Note: For the M2M, the vendor disabled the USB DEV (by setting the
reset signal in the boot loader). They did this probably to save
power (this unit has a battery). And unfortunately: if the USB DEV
reset bit is not cleared, then the connected USB device on the USB
HOST (of the ramips) is not detected.
Regards, Christian ___
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] [PATCH] [scripts] feeds: search packages by license
On 19/12/2014 23:47, Eric Schultz wrote: Currently, the feeds scripts provides no way to filter by packages by license or no license. This patch adds a search feature to feeds which can be used to search packages by license or by no license. Signed-off-by: Eric Schultz eschu...@prplfoundation.org --- scripts/feeds | 90 ++- 1 file changed, 77 insertions(+), 13 deletions(-) [...] @@ -642,6 +704,8 @@ Commands: search [options] substring: Search for a package Options: -r feedname: Only search in this feed + -l license: Include packages with this license + -n: Include packages without a license tag if i read this correctly the current behavior is changed which will inevitably lead to a trillion tickets with package XYZ is missing can you change the option to Only include packages with a license tag uninstall -a|package: Uninstall a package Options: ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v3] add support for TL-WA701ND v2
On 19/01/2015 13:40, Luigi Tarenga wrote:
Signed-off-by: Luigi Tarenga luigi.tare...@gmail.com
---
version 3. sent with git send-email to avoid tabs conversion from gmail
webmail.
crossing fingers :)
Luigi
looks good however ...
---
target/linux/ar71xx/base-files/etc/diag.sh | 1 +
.../ar71xx/base-files/etc/uci-defaults/01_leds | 5 +
.../ar71xx/base-files/etc/uci-defaults/02_network | 1 +
target/linux/ar71xx/base-files/lib/ar71xx.sh | 3 +
.../ar71xx/base-files/lib/upgrade/platform.sh | 1 +
target/linux/ar71xx/config-3.10| 1 +
this is for BB i assume ... can you also send a version based on trunk ?
.../files/arch/mips/ath79/mach-tl-wa701nd-v2.c | 116
+
target/linux/ar71xx/image/Makefile | 4 +-
.../729-MIPS-ath79-add-TL-WA701NDv2-support.patch | 45
tools/firmware-utils/src/mktplinkfw.c | 6 ++
10 files changed, 182 insertions(+), 1 deletion(-)
create mode 100644
target/linux/ar71xx/files/arch/mips/ath79/mach-tl-wa701nd-v2.c
create mode 100644
target/linux/ar71xx/patches-3.10/729-MIPS-ath79-add-TL-WA701NDv2-support.patch
diff --git a/target/linux/ar71xx/base-files/etc/diag.sh
b/target/linux/ar71xx/base-files/etc/diag.sh
index fa07f39..eb96338 100755
--- a/target/linux/ar71xx/base-files/etc/diag.sh
+++ b/target/linux/ar71xx/base-files/etc/diag.sh
@@ -195,6 +195,7 @@ get_status_led() {
tl-mr3220-v2 | \
tl-mr3420 | \
tl-mr3420-v2 | \
+ tl-wa701nd-v2 | \
tl-wa801nd-v2 | \
tl-wa901nd | \
tl-wa901nd-v2 | \
diff --git a/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds
b/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds
index 5b9dbe7..0d085be 100755
--- a/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds
+++ b/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds
@@ -275,6 +275,11 @@ tl-wa850re)
ucidef_set_led_rssi rssihigh RSSIHIGH tp-link:blue:signal5
wlan0 80 100 -79 13
;;
+tl-wa701nd-v2)
+ ucidef_set_led_netdev lan LAN tp-link:green:lan eth0
+ ucidef_set_led_wlan wlan WLAN tp-link:green:wlan phy0tpt
+ ;;
+
tl-wa860re)
ucidef_set_led_netdev lan LAN tp-link:green:lan eth0
ucidef_set_led_wlan wlan WLAN tp-link:green:wlan phy0tpt
diff --git a/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
b/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
index c5cfd67..4be30b8 100755
--- a/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
+++ b/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
@@ -301,6 +301,7 @@ tl-mr13u |\
tl-mr3020 |\
tl-mr3040 |\
tl-mr3040-v2 |\
+tl-wa701nd-v2 |\
tl-wa750re |\
tl-wa850re |\
tl-wa830re-v2 |\
diff --git a/target/linux/ar71xx/base-files/lib/ar71xx.sh
b/target/linux/ar71xx/base-files/lib/ar71xx.sh
index 1e96b6d..df35775 100755
--- a/target/linux/ar71xx/base-files/lib/ar71xx.sh
+++ b/target/linux/ar71xx/base-files/lib/ar71xx.sh
@@ -571,6 +571,9 @@ ar71xx_board_detect() {
*TL-MR3420 v2)
name=tl-mr3420-v2
;;
+ *TL-WA701ND v2)
+ name=tl-wa701nd-v2
+ ;;
*TL-WA750RE)
name=tl-wa750re
;;
diff --git a/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
b/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
index 846954c..eeaac6a 100755
--- a/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
+++ b/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
@@ -269,6 +269,7 @@ platform_check_image() {
tl-mr3220-v2 | \
tl-mr3420 | \
tl-mr3420-v2 | \
+ tl-wa701nd-v2 | \
tl-wa7510n | \
tl-wa750re | \
tl-wa850re | \
diff --git a/target/linux/ar71xx/config-3.10 b/target/linux/ar71xx/config-3.10
index 9a8378a..482914a 100644
--- a/target/linux/ar71xx/config-3.10
+++ b/target/linux/ar71xx/config-3.10
@@ -88,6 +88,7 @@ CONFIG_ATH79_MACH_TL_MR11U=y
CONFIG_ATH79_MACH_TL_MR13U=y
CONFIG_ATH79_MACH_TL_MR3020=y
CONFIG_ATH79_MACH_TL_MR3X20=y
+CONFIG_ATH79_MACH_TL_WA701ND_V2=y
CONFIG_ATH79_MACH_TL_WA830RE_V2=y
CONFIG_ATH79_MACH_TL_WA901ND=y
CONFIG_ATH79_MACH_TL_WA901ND_V2=y
diff --git a/target/linux/ar71xx/files/arch/mips/ath79/mach-tl-wa701nd-v2.c
b/target/linux/ar71xx/files/arch/mips/ath79/mach-tl-wa701nd-v2.c
new file mode 100644
index 000..aab92b3
--- /dev/null
+++ b/target/linux/ar71xx/files/arch/mips/ath79/mach-tl-wa701nd-v2.c
@@ -0,0 +1,116 @@
+/*
+ * TP-LINK TL-WA701ND v2 board support
+ *
+ * Copyright (C) 2015 Luigi Tarenga luigi.tare...@gmail.com
+ *
+ * This program is free software; you can redistribute it and/or modify it
+ * under the terms of the GNU General Public License version 2 as published
+ * by the Free Software Foundation.
+ */
+
+#include linux/gpio.h
+
+#include asm/mach-ath79/ath79.h
+
+#include dev-eth.h
+#include
Re: [OpenWrt-Devel] [PATCH v2] procd: delay inittab workers until the tty exists.
On 20/01/2015 01:21, Owen Kirby wrote:
Add hotplug support for tty devices in /etc/inittab that are specified
by the askfirst
keyword so that terminals attached after boot time get console processes
started.
This was tested on an AT91 target using the gadget serial subsystem and
on an WNDR3800
with a USB serial adapter. One possible weirdness I encountered was that
the baud rates
and control modes sometimes need adjusting with a hotplug script after
reconnecting
the adapter. This is also only implemented for askfirst, but it might
also make sense
to do the same thing for respawn and askconsole.
i think it would be a lot simpler if you ...
* add a new cmd_handler inside hotplug/json_script called console or
spawn_console
* add a 2nd parameter to procd_inittab_run called char *tty that can be
NULL or act as a filter
* call procd_inittab_run with the 2nd parameter set from the new
json_script handler
* add a new if clause to package/system/procd/files/hotplug.json
Signed-off-by: Owen Kirby o...@exegin.com
---
inittab.c | 35 ---
plug/hotplug.c | 40 +++-
plug/hotplug.h | 15 +++
3 files changed, 82 insertions(+), 8 deletions(-)
diff --git a/inittab.c b/inittab.c
index 623103d..c9310e5 100644
--- a/inittab.c
+++ b/inittab.c
@@ -26,6 +26,7 @@
#include libubox/utils.h
#include libubox/list.h
+#include plug/hotplug.h
#include utils/utils.h
#include procd.h
#include rcS.h
@@ -55,6 +56,7 @@ struct init_action {
struct init_handler *handler;
struct uloop_process proc;
+struct hotplug_event event;
int respawn;
struct uloop_timeout tout;
@@ -90,6 +92,29 @@ static int dev_exist(const char *dev)
return (res != -1);
}
+static void dev_hotplug(struct hotplug_event *event, struct blob_attr
*msg)
+{
+struct init_action *a = container_of(event, struct init_action,
event);
+char *action = hotplug_msg_find_var(msg, ACTION);
+char *subsystem = hotplug_msg_find_var(msg, SUBSYSTEM);
+char *devname = hotplug_msg_find_var(msg, DEVNAME);
+
+if (!action || !subsystem || !devname)
+return;
+if (strcmp(subsystem, tty) || strcmp(devname, a-id))
+return;
+
+DEBUG(4, inittab hotplug: ACTION=\%s\, SUBSYSTEM=\%s\,
DEVNAME=\%s\\n,
+action, subsystem, devname);
+if (!strcmp(action, add)) {
+uloop_timeout_set(a-tout, a-respawn);
+}
+else if (!strcmp(action, remove)) {
+uloop_process_delete(a-proc);
+uloop_timeout_cancel(a-tout);
+}
+}
+
static void fork_worker(struct init_action *a)
{
int fd;
@@ -130,7 +155,7 @@ static void child_exit(struct uloop_process *proc,
int ret)
struct init_action *a = container_of(proc, struct init_action, proc);
DEBUG(4, pid:%d\n, proc-pid);
-uloop_timeout_set(a-tout, a-respawn);
+uloop_timeout_set(a-tout, a-respawn);
}
static void respawn(struct uloop_timeout *tout)
@@ -157,7 +182,7 @@ static void askfirst(struct init_action *a)
{
int i;
-if (!dev_exist(a-id) || (console !strcmp(console, a-id))) {
+if (console !strcmp(console, a-id)) {
DEBUG(4, Skipping %s\n, a-id);
return;
}
@@ -168,8 +193,12 @@ static void askfirst(struct init_action *a)
a-argv[0] = ask;
a-respawn = 500;
+a-event.cb = dev_hotplug;
+hotplug_event_add(a-event);
+
a-proc.cb = child_exit;
-fork_worker(a);
+if (dev_exist(a-id))
+fork_worker(a);
}
static void askconsole(struct init_action *a)
diff --git a/plug/hotplug.c b/plug/hotplug.c
index 061833a..3aa87c0 100644
--- a/plug/hotplug.c
+++ b/plug/hotplug.c
@@ -44,13 +44,14 @@ struct cmd_queue {
};
static LIST_HEAD(cmd_queue);
+static LIST_HEAD(events);
static struct uloop_process queue_proc;
static struct uloop_timeout last_event;
static struct blob_buf b;
static char *rule_file;
static struct blob_buf script;
-static char *hotplug_msg_find_var(struct blob_attr *msg, const char *name)
+char *hotplug_msg_find_var(struct blob_attr *msg, const char *name)
{
struct blob_attr *cur;
int rem;
@@ -393,24 +394,30 @@ static struct json_script_ctx jctx = {
.handle_file = rule_handle_file,
};
-static void hotplug_handler_debug(struct blob_attr *data)
+static void hotplug_handler_debug(struct hotplug_event *e, struct
blob_attr *msg)
{
char *str;
if (debug 3)
return;
-str = blobmsg_format_json(data, true);
+str = blobmsg_format_json(msg, true);
DEBUG(3, %s\n, str);
free(str);
}
+static void hotplug_handler_script(struct hotplug_event *e, struct
blob_attr *msg)
+{
+json_script_run(jctx, rule_file, msg);
+}
+
static void hotplug_handler(struct uloop_fd *u, unsigned int ev)
{
int i = 0;
static char buf[4096];
Re: [OpenWrt-Devel] [PATCH] ralink: add support for firewrt
Hi,
thanks for the patch --
https://dev.openwrt.org/changeset/44055
also big thanks to Mingyu for spending so much time in fixing the
ethernet driver !
John
On 20/01/2015 07:07, wengbj wrote:
---
.../linux/ramips/base-files/etc/board.d/02_network |1 +
target/linux/ramips/base-files/lib/ramips.sh |3 +
.../ramips/base-files/lib/upgrade/platform.sh |1 +
target/linux/ramips/dts/FIREWRT.dts| 81
target/linux/ramips/image/Makefile |7 +-
target/linux/ramips/mt7621/profiles/firefly.mk | 24 ++
6 files changed, 116 insertions(+), 1 deletion(-)
create mode 100644 target/linux/ramips/dts/FIREWRT.dts
create mode 100644 target/linux/ramips/mt7621/profiles/firefly.mk
diff --git a/target/linux/ramips/base-files/etc/board.d/02_network
b/target/linux/ramips/base-files/etc/board.d/02_network
index b440fb3..a8ed0b4 100755
--- a/target/linux/ramips/base-files/etc/board.d/02_network
+++ b/target/linux/ramips/base-files/etc/board.d/02_network
@@ -118,6 +118,7 @@ ramips_setup_interfaces()
dir-300-b7 | \
dir-320-b1 | \
dir-615-h1 | \
+ firewrt | \
hlk-rm04 | \
mt7621 | \
mt7628 | \
diff --git a/target/linux/ramips/base-files/lib/ramips.sh
b/target/linux/ramips/base-files/lib/ramips.sh
index 720b137..bb815da 100755
--- a/target/linux/ramips/base-files/lib/ramips.sh
+++ b/target/linux/ramips/base-files/lib/ramips.sh
@@ -91,6 +91,9 @@ ramips_board_detect() {
*Buffalo WSR-1166DHP)
name=wsr-1166
;;
+ *Firefly FireWRT)
+ name=firewrt
+ ;;
*CY-SWR1100)
name=cy-swr1100
;;
diff --git a/target/linux/ramips/base-files/lib/upgrade/platform.sh
b/target/linux/ramips/base-files/lib/upgrade/platform.sh
index 7c17211..ff7126a 100755
--- a/target/linux/ramips/base-files/lib/upgrade/platform.sh
+++ b/target/linux/ramips/base-files/lib/upgrade/platform.sh
@@ -50,6 +50,7 @@ platform_check_image() {
f7c027 | \
fonera20n | \
freestation5 | \
+ firewrt |\
hg255d | \
hlk-rm04 | \
ht-tm02 | \
diff --git a/target/linux/ramips/dts/FIREWRT.dts
b/target/linux/ramips/dts/FIREWRT.dts
new file mode 100644
index 000..2e5d26b
--- /dev/null
+++ b/target/linux/ramips/dts/FIREWRT.dts
@@ -0,0 +1,81 @@
+/dts-v1/;
+
+/include/ mt7621.dtsi
+
+/ {
+ compatible = mediatek,mt7621-eval-board, mediatek,mt7621-soc;
+ model = Firefly FireWRT;
+
+ memory@0 {
+ reg = 0x0 0x1000;
+ };
+
+ chosen {
+ bootargs = console=ttyS0,57600;
+ };
+
+ sdhci@1013 {
+ status = okay;
+ };
+
+ palmbus@1E00 {
+ spi@b00 {
+ status = okay;
+
+ m25p80@0 {
+ #address-cells = 1;
+ #size-cells = 1;
+ compatible = mx25l12805d;
+ reg = 0 0;
+ linux,modalias = m25p80;
+ spi-max-frequency = 1000;
+
+ partition@0 {
+ label = u-boot;
+ reg = 0x0 0x3;
+ read-only;
+ };
+
+ partition@3 {
+ label = u-boot-env;
+ reg = 0x3 0x1;
+ read-only;
+ };
+
+ factory: partition@4 {
+ label = factory;
+ reg = 0x4 0x1;
+ read-only;
+ };
+
+ partition@5 {
+ label = firmware;
+ reg = 0x5 0x7b;
+ };
+
+ };
+ };
+ };
+
+ pcie@1e14 {
+ status = okay;
+
+ pcie0 {
+ mt76@0,0 {
+ reg = 0x 0 0 0 0;
+ device_type = pci;
+ mediatek,mtd-eeprom = factory 0x8000;
+ mediatek,2ghz = 0;
+ };
+ };
+
+ pcie1 {
+ mt76@1,0 {
+ reg = 0x 0 0 0 0;
+ device_type = pci;
+ mediatek,mtd-eeprom = factory 0x;
+ mediatek,5ghz = 0;
+ };
+ };
+ };
+};
diff
Re: [OpenWrt-Devel] [PATCH 1/2] target: kirkwood: fix leds defaults config
r44000 r44007 ?? On 20/01/2015 14:19, drEagle wrote: Hi Luka, Is this patch missed or lost ? I do not find any trace at patchworks. Do you need that I resubmit it ? Regards, Gérald Le 20/12/2014 03:51, Gerald Kerma a écrit : Fix missing parameters in 01_leds Signed-off-by: Gerald Kerma drea...@doukki.net --- .../kirkwood/base-files/etc/uci-defaults/01_leds | 22 +++--- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/target/linux/kirkwood/base-files/etc/uci-defaults/01_leds b/target/linux/kirkwood/base-files/etc/uci-defaults/01_leds index 51fb4d8..ba4d569 100644 --- a/target/linux/kirkwood/base-files/etc/uci-defaults/01_leds +++ b/target/linux/kirkwood/base-files/etc/uci-defaults/01_leds @@ -10,30 +10,30 @@ board=$(kirkwood_board_name) case $board in dockstar) - ucidef_set_led_default health status:green:health 1 - ucidef_set_led_default fault status:orange:fault 1 + ucidef_set_led_default health health status:green:health 1 + ucidef_set_led_default fault fault status:orange:fault 1 ;; ea3500) - ucidef_set_led_default power ea3500:green:power 1 + ucidef_set_led_default power power ea3500:green:power 1 ;; ea4500) - ucidef_set_led_default health ea4500:white:health 1 - ucidef_set_led_default pulse ea4500:white:pulse 1 + ucidef_set_led_default health health ea4500:white:health 1 + ucidef_set_led_default pulse pulse ea4500:white:pulse 1 ;; ib62x0) - ucidef_set_led_default health ib62x0:green:os 1 - ucidef_set_led_default fault ib62x0:red:os 1 + ucidef_set_led_default health health ib62x0:green:os 1 + ucidef_set_led_default fault fault ib62x0:red:os 1 ;; pogo_e02) -ucidef_set_led_default health status:green:health 1 - ucidef_set_led_default fault status:orange:fault 1 + ucidef_set_led_default health health status:green:health 1 + ucidef_set_led_default fault fault status:orange:fault 1 ;; guruplug-server-plus) -ucidef_set_led_timer health guruplug:red:health 200 800 + ucidef_set_led_timer health health guruplug:red:health 200 800 ;; sheevaplug | \ sheevaplug-esata) -ucidef_set_led_timer health sheevaplug:blue:health 200 800 + ucidef_set_led_timer health health sheevaplug:blue:health 200 800 ;; *) ;; ___ 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] [PATCH v4] add support for TL-WA701ND v2
I pushed the patch to BB and trunk and added the missing ar71xx: prefix to the subject. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Adding support for 6LoWPAN over Bluetooth Low Energy in kernel 3.18.
On 21/01/2015 13:53, Duda, Lukasz wrote: + DEPENDS:=+kmod-bluetooth @!LINUX_3_3 @!LINUX_3_8 @!LINUX_3_10 +@!LINUX_3_13 @!LINUX_3_14 this is also wrong, @!(LINUX_3_3||LINUX_3_8||..)) is the correct syntax. please resend a fixed version ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] lantiq: correct value for fpi clock on ar9
On 21/01/2015 10:35, Ben Mulvihill wrote: Hello, This is a patch to go in target/linux/lantiq/patches-3.14/ please send a patch that adds the file instead of just sending the file It corrects the fpi clock value on lantiq ar9. See this discussion for further details: https://lists.openwrt.org/pipermail/openwrt-devel/2015-January/030688.html --- a/arch/mips/lantiq/xway/clk.c 2015-01-21 10:15:44.0 +0100 +++ b/arch/mips/lantiq/xway/clk.c 2015-01-21 10:17:29.0 +0100 @@ -104,8 +104,9 @@ unsigned long ltq_ar9_fpi_hz(void) unsigned long sys = ltq_ar9_sys_hz(); if (ltq_cgu_r32(CGU_SYS) BIT(0)) - return sys; - return sys 1; + return sys / 3; + else + return sys / 2; } unsigned long ltq_ar9_cpu_hz(void) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] [packages_extra] snort: add missing libuuid dependency
On 21/01/2015 23:13, daniel wrote: The current version of snort fails to build because the libuuid pkg dependency is missing. This little patch fixes the issue, please apply. Signed-off-by: Daniel Danzberger dan...@dd-wrt.com please send a pull request via github for packages inside the feed. the mailing list is for trunk related patches ___ 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] [PATCH] Adding support for 6LoWPAN over Bluetooth Low Energy in kernel 3.18.
This patch was not tested prior to sending it ... see inline On 21/01/2015 13:53, Duda, Lukasz wrote: Adding support 6LoWPAN over Bluetooth Low Energy in kernel 3.18. Creating new bluetooth_6lowpan group with COFNIG_6LOWPAN and CONFIG_BT_6LOWPAN. Adding kernel object dependencies for 6LoWPAN over Bluetooth Low Energy. Signed-off-by: Lukasz Duda lukasz.duda at nordicsemi.no --- Index: package/kernel/linux/modules/other.mk === --- package/kernel/linux/modules/other.mk (revision 44059) +++ package/kernel/linux/modules/other.mk (working copy) @@ -70,6 +70,26 @@ $(eval $(call KernelPackage,bluetooth)) +define KernelPackage/bluetooth_6lowpan + SUBMENU:=$(OTHER_MENU) + TITLE:=Bluetooth 6LoWPAN support + DEPENDS:=+kmod-bluetooth @!LINUX_3_3 @!LINUX_3_8 @!LINUX_3_10 +@!LINUX_3_13 @!LINUX_3_14 + KCONFIG:= \ + CONFIG_6LOWPAN=m \ + CONFIG_BT_6LOWPAN=m + FILES:= \ + $(LINUX_DIR)/net/bluetooth/bluetooth_6lowpan.ko \ + $(LINUX_DIR)/net/6lowpan/6lowpan.ko + AUTOLOAD:=$(call AutoProbe,bluetooth) +endef + +define KernelPackage/bluetooth_6lowpan/description + Kernel support for 6LoWPAN over Bluetooth Low Energy devices endef + endef is missing, please test the patches that you send +$(eval $(call KernelPackage,bluetooth_6lowpan)) + + define KernelPackage/bluetooth-hci-h4p SUBMENU:=$(OTHER_MENU) TITLE:=HCI driver with H4 Nokia extensions --- ___ 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] [PATCH, v2] feeds: search packages by license
On 20/01/2015 23:20, Eric Schultz wrote: Currently, the feeds scripts provides no way to filter by packages by license or no license. This patch adds a search feature to feeds which can be used to search packages by license or by no license. Calls to script/feeds which do not use the new -l or -n options should work the same as before. Signed-off-by: Eric Schultz eschu...@prplfoundation.org --- [...] @@ -642,6 +704,8 @@ Commands: search [options] substring: Search for a package Options: -r feedname: Only search in this feed + -l license: Only include packages with this license + -n:Only include packages without a license tag i think there parameters are still sub optimal How about these 2 -l Only include packages with a license -n List all packages that have no license (developer use) additionally your text editor seems to be wonky and uses leading spaces instead of tabs. please make sure you use tabs. I also spotted 2-3 whitespace fixes, these should be in a seperate patch and not intermingled with the actual feature patch uninstall -a|package: Uninstall a package Options: ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v2] build: allow openwrt.git packages to be replaced by feeds
On 22/01/2015 03:55, Mathieu Olivari wrote:
Currently, replacing a package available in openwrt.git requires
modifications in openwrt.git, or requires duplicating the package
in a feed but with a different name, which causes all kind of
problems related to dependencies (all packages selecting it would
have to be modified accordingly to select the new package).
With this change, if a package with the same name is present both
in feeds/ and package/ folders, the one in feeds/ can override the
one in package/, both in the menuconfig and during the build, by
passing the -f option to ./scripts/feeds install
This mechanism is particularly useful for vendor tree, or in
general for application which needs to replace one particular
package which exists within openwrt.git by a custom/newer version.
Signed-off-by: Mathieu Olivari math...@qca.qualcomm.com
Hi Mathieu,
this looks much better. i think we should also add some info in
/etc/openwrt_release in the field DISTRIB_TAINTS='no-all' indicating
that the build uses out of tree vendor packages.
i will merge this patch as is, but could you put the openwrt_release
patch onto your todo list and send it in the nearish future please
John
--- v2: *fix an issue when trying to override packages which
include a dependency in the core packages. (ex: lua depends on
liblua, which exists in the core, which ended-up in the package not
being overridden properly). *address John's concerns about core
OpenWrt packages being overriden without notice and control.
Override is now disable by default, and -f needs to be passed to
./scripts/feeds install to allow it. --- include/scan.awk | 17
+ include/scan.mk |2 +- scripts/feeds|
25 ++--- 3 files changed, 36 insertions(+), 8
deletions(-) create mode 100644 include/scan.awk
diff --git a/include/scan.awk b/include/scan.awk new file mode
100644 index 000..39b2977 --- /dev/null +++ b/include/scan.awk
@@ -0,0 +1,17 @@ +BEGIN { FS=/ } +$1 ~ /^feeds/ { FEEDS[$NF]=$0
} +$1 !~ /^feeds/ { PKGS[$NF]=$0 } +END { + # Filter-out OpenWrt
packages which have a feeds equivalent + for (pkg in PKGS) +
if
(pkg in FEEDS) + delete PKGS[pkg] + n = asort(PKGS)
+ for (i=1; i
= n; i++) { +print PKGS[i] + } + n = asort(FEEDS) +
for (i=1; i
= n; i++){ + print FEEDS[i] +} +} diff --git
a/include/scan.mk
b/include/scan.mk index 0998333..138707d 100644 ---
a/include/scan.mk +++ b/include/scan.mk @@ -43,7 +43,7 @@ endef
$(FILELIST): rm -f $(TMP_DIR)/info/.files-$(SCAN_TARGET)-* - $(call
FIND_L, $(SCAN_DIR)) $(SCAN_EXTRA) -mindepth 1 $(if
$(SCAN_DEPTH),-maxdepth $(SCAN_DEPTH)) -name Makefile | xargs grep
-HE 'call (Build/DefaultTargets|Build(Package|Target)|.+Package)' |
sed -e 's#^$(SCAN_DIR)/##' -e 's#/Makefile:.*##' | uniq $@ +
$(call FIND_L, $(SCAN_DIR)) $(SCAN_EXTRA) -mindepth 1 $(if
$(SCAN_DEPTH),-maxdepth $(SCAN_DEPTH)) -name Makefile | xargs grep
-HE 'call (Build/DefaultTargets|Build(Package|Target)|.+Package)' |
sed -e 's#^$(SCAN_DIR)/##' -e 's#/Makefile:.*##' | uniq | awk -f
include/scan.awk $@
$(TMP_DIR)/info/.files-$(SCAN_TARGET).mk: $(FILELIST) ( \ diff
--git a/scripts/feeds b/scripts/feeds index 31ad544..6c03375
100755 --- a/scripts/feeds +++ b/scripts/feeds @@ -358,6 +358,7 @@
sub is_core_package($) { sub install_package { my $feed = shift; my
$name = shift; + my $force = shift; my $ret = 0;
$feed = lookup_package($feed, $name); @@ -383,13 +384,22 @@ sub
install_package { $src or $src = $name;
# previously installed packages set the runtime package - # newly
installed packages set the source package - $installed{$src} and
return 0; + # newly installed packages set the source package to 1
+ $installed{$src} and $installed{$src} == 1 and return 0; + +#
we'll trigger the override only with the 3 conditions below: +# -
override is allowed by command line (-f) +# - a package with the
same src exists in the core packages list + # - the package
previously installed is not from a feed + my $override = 1 if
($force and is_core_package($src) and !$installed{$src}-{feed});
# check previously installed packages - $installed{$name} and
return 0; + $installed{$name} and !$override and return 0;
$installed{$src} = 1; - warn Installing package '$src'\n; + +
$override == 1 + and warn Overriding package '$src'\n +
or warn
Installing package '$src'\n;
$install_method{$type} or do { warn Unknown installation method:
'$type'\n; @@ -436,7 +446,7 @@ sub install { my $feed; my $ret =
0;
- getopts('ap:d:h', \%opts); +getopts('ap:d:fh', \%opts);
if ($opts{h}) { usage(); @@ -462,7 +472,7 @@ sub install { my $p =
$feed_package-{$name}; next if $p-{vdepends}; if( $p-{name} ) {
-
Re: [OpenWrt-Devel] [PATCH v2] Adding support for 6LoWPAN over Bluetooth Low Energy in kernel 3.18.
On 22/01/2015 09:48, Duda, Lukasz wrote: Adding support 6LoWPAN over Bluetooth Low Energy in kernel 3.18. Creating new bluetooth_6lowpan group with CONFIG_6LOWPAN and CONFIG_BT_6LOWPAN. Adding kernel object dependencies for 6LoWPAN over Bluetooth Low Energy. the mail contains a html version of the patch and a whitespace broken text version please resend using the method you use for v1. i assume you used copypaste and a mail client for v2 Signed-off-by: Lukasz Duda lukasz.duda...@nordicsemi.com mailto:lukasz.duda...@nordicsemi.com --- v2: *fix an issue with the mail formatting as mail client removed line breaks. --- Index: package/kernel/linux/modules/other.mk === --- package/kernel/linux/modules/other.mk (revision 44059) +++ package/kernel/linux/modules/other.mk (working copy) @@ -70,6 +70,26 @@ $(eval $(call KernelPackage,bluetooth)) +define KernelPackage/bluetooth_6lowpan + SUBMENU:=$(OTHER_MENU) + TITLE:=Bluetooth 6LoWPAN support + DEPENDS:=+kmod-bluetooth @!(LINUX_3_3||LINUX_3_8||LINUX_3_10||LINUX_3_13||LINUX_3_14) + KCONFIG:= \ + CONFIG_6LOWPAN=m \ + CONFIG_BT_6LOWPAN=m + FILES:= \ + $(LINUX_DIR)/net/bluetooth/bluetooth_6lowpan.ko \ + $(LINUX_DIR)/net/6lowpan/6lowpan.ko + AUTOLOAD:=$(call AutoProbe,bluetooth) +endef + +define KernelPackage/bluetooth_6lowpan/description + Kernel support for 6LoWPAN over Bluetooth Low Energy devices +endef + +$(eval $(call KernelPackage,bluetooth_6lowpan)) + + define KernelPackage/bluetooth-hci-h4p SUBMENU:=$(OTHER_MENU) TITLE:=HCI driver with H4 Nokia extensions --- ___ 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] uboot-lantiq cgu settings for ramboot image
is this patch correct and should be merged or is it a RFC ? http://patchwork.ozlabs.org/patch/431024/ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] lantiq: correct value for fpi clock on ar9
On 22/01/2015 10:11, Ben Mulvihill wrote: On Thu, 2015-01-22 at 08:34 +0100, John Crispin wrote: On 21/01/2015 10:35, Ben Mulvihill wrote: Hello, This is a patch to go in target/linux/lantiq/patches-3.14/ please send a patch that adds the file instead of just sending the file Sure, will do. I would have done, but I remembered you replying to someone else a little while ago that you preferred to roll your own. Ben not sure which mail you mean but i guess it was related to the time when we moved some of the code from patches/ to files/ ___ 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] [PATCH v3] Adding support for 6LoWPAN over Bluetooth Low Energy in kernel 3.18.
On 22/01/2015 10:16, Duda, Lukasz wrote: Signed-off-by: Lukasz Duda lukasz.duda...@nordicsemi.com is this email addr valid ? it is not the one you used for sending the patch ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Archer C7, leds and led trigger for ath10k
On 17/01/2015 19:19, Gianluca Anzolin wrote: Il 17/01/2015 13:53, John Crispin ha scritto: On 17/01/2015 08:42, Gianluca Anzolin wrote: Il 17/01/2015 07:41, John Crispin ha scritto: There is also a bugreport in the bug tracking system pointing at this issue: https://dev.openwrt.org/ticket/18188 I looked at the ath9k implementation and I've come up with the attached patch. Do you think a patch like this is acceptable? it is not do you care to elaborate? what's wrong with it? Gianluca _ imho fixing target/linux/ar71xx/base-files/etc/uci-defaults/01_leds is enough nd not driver patch is required I don't get it, how do you create a throughput trigger by changing a script? ok, i misread your patch. the first half says the leds are swapped so i pointed you at the code that sets up the leds. i will talk to felix about the patch Gianluca ___ 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] [PATCH] ar71xx: add support for the UniFi AP Outdoor Plus
On 30/12/2014 06:01, Matthias Schiffer wrote:
I had read the mails regarding the issue and I've asked about it
in #openwrt-devel (but didn't get an answer yet). I didn't try
changing the channel though as I'm in a very noisy environment
(WLAN-wise) at the moment, so I can't really do any proper
testing.
If it's only a GPIO issue, I could look at it, but I don't know
enough about ath9k to do more complex fixes. Unfortunately, I don't
have the device anymore, so I can't perform further tests myself.
can this wrong / missing GPIO cause permanent damage the SoC/wmac ?
On 12/30/2014 05:42 AM, David Hutchison wrote:
Does the new kernel / ath9k address the RF Filter on this board?
I came up with an old patch for this board, but whenever I
changed the channel inside OpenWRT the signal would just
disappear. The RF Filter has to be toggled somehow ( I assume
it's a GPIO of some sort ). I am just curious on how it was
fixed, or if it's still an issue.
-- Davey
On Mon, Dec 29, 2014 at 8:01 PM, Matthias Schiffer
mschif...@universe-factory.net wrote:
Signed-off-by: Matthias Schiffer
mschif...@universe-factory.net ---
target/linux/ar71xx/base-files/etc/diag.sh | 3 ++
target/linux/ar71xx/base-files/lib/ar71xx.sh | 3 ++
.../ar71xx/base-files/lib/upgrade/platform.sh | 2 +
target/linux/ar71xx/image/Makefile | 3 +-
.../610-MIPS-ath79-openwrt-machines.patch | 3 +-
.../patches-3.14/616-MIPS-ath79-ubnt-xw.patch | 61
+- 6 files changed, 72 insertions(+), 3
deletions(-)
diff --git a/target/linux/ar71xx/base-files/etc/diag.sh
b/target/linux/ar71xx/base-files/etc/diag.sh index
06b96a3..30e4aeb 100755 ---
a/target/linux/ar71xx/base-files/etc/diag.sh +++
b/target/linux/ar71xx/base-files/etc/diag.sh @@ -254,6 +254,9
@@ get_status_led() { uap-pro) status_led=ubnt:white:dome ;;
+ unifi-outdoor-plus) +
status_led=ubnt:white:front + ;; airgateway)
status_led=ubnt:white:status ;; diff --git
a/target/linux/ar71xx/base-files/lib/ar71xx.sh
b/target/linux/ar71xx/base-files/lib/ar71xx.sh index
9b056e9..a12101a 100755 ---
a/target/linux/ar71xx/base-files/lib/ar71xx.sh +++
b/target/linux/ar71xx/base-files/lib/ar71xx.sh @@ -732,6 +732,9
@@ ar71xx_board_detect() { *UniFiAP Outdoor)
name=unifi-outdoor ;; + *UniFiAP Outdoor+) +
name=unifi-outdoor-plus + ;; *WP543)
name=wp543 ;; diff --git
a/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
b/target/linux/ar71xx/base-files/lib/upgrade/platform.sh index
6dabf4e..2752729 100755 ---
a/target/linux/ar71xx/base-files/lib/upgrade/platform.sh +++
b/target/linux/ar71xx/base-files/lib/upgrade/platform.sh @@
-368,6 +368,7 @@ platform_check_image() { return 1 ;;
+ unifi-outdoor-plus | \ uap-pro) [ $magic_long !=
19852003 ] { echo Invalid image type. @@ -483,6 +484,7
@@ platform_do_upgrade() { om5p) platform_do_upgrade_openmesh
$ARGV ;; + unifi-outdoor-plus | \ uap-pro)
MTD_CONFIG_ARGS=-s 0x18 default_do_upgrade $ARGV diff
--git a/target/linux/ar71xx/image/Makefile
b/target/linux/ar71xx/image/Makefile index 18c9637..3eb2f07
100644 --- a/target/linux/ar71xx/image/Makefile +++
b/target/linux/ar71xx/image/Makefile @@ -1333,6 +1333,7 @@
$(eval $(call
SingleProfile,TPLINK-LZMA,64kraw,SMART-300,smart-300,SMART-300,tty
$(eval $(call
SingleProfile,TPLINK-LZMA,64kraw,OOLITE,oolite,GS-OOLITE,ttyATH0,115200,0x3C000101,1,16Mlzma))
$(eval $(call
SingleProfile,UAPPRO,64k,UAPPRO,ubnt-uap-pro,UAP-PRO,ttyS0,115200,BZ,BZ,ar934x))
+$(eval $(call
SingleProfile,UAPPRO,64k,UBNTUNIFIOUTDOORPLUS,ubnt-unifi-outdoor-plus,UBNT-UOP,ttyS0,115200,BZ,BZ,ar7240))
$(eval $(call
SingleProfile,UBDEV,64kraw,UBDEV01,ubdev01,UBNT-UF,ttyS0,115200,XM,XM,ar7240))
@@ -1396,7 +1397,7 @@ $(eval $(call MultiProfile,TLWR941,TLWR941NV2
TLWR941NV3 TLWR941NV4 TLWR941NV6))
$(eval $(call MultiProfile,TLWR1043,TLWR1043V1 TLWR1043V2))
$(eval $(call MultiProfile,TLWDR4300,TLWDR3500V1 TLWDR3600V1
TLWDR4300V1 TLWDR4300V1IL TLWDR4310V1 MW4530RV1)) $(eval $(call
MultiProfile,TUBE2H,TUBE2H8M TUBE2H16M)) -$(eval $(call
MultiProfile,UBNT,UBNTAIRROUTER UBNTRS UBNTRSPRO UBNTLSSR71
UBNTBULLETM UBNTROCKETM UBNTNANOM UBNTNANOMXW UBNTLOCOXW
UBNTUNIFI UBNTUNIFIOUTDOOR UAPPRO UBNTAIRGW)) +$(eval $(call
MultiProfile,UBNT,UBNTAIRROUTER UBNTRS UBNTRSPRO UBNTLSSR71
UBNTBULLETM UBNTROCKETM UBNTNANOM UBNTNANOMXW UBNTLOCOXW
UBNTUNIFI UBNTUNIFIOUTDOOR UBNTUNIFIOUTDOORPLUS UAPPRO
UBNTAIRGW)) $(eval $(call MultiProfile,WNDR3700,WNDR3700V1
WNDR3700V2 WNDR3800 WNDR3800CH WNDRMAC WNDRMACV2)) $(eval
$(call MultiProfile,WNR612V2,REALWNR612V2 N150R)) $(eval $(call
MultiProfile,WP543,WP543_2M WP543_4M WP543_8M WP543_16M)) diff
--git
a/target/linux/ar71xx/patches-3.14/610-MIPS-ath79-openwrt-machines.patch
b/target/linux/ar71xx/patches-3.14/610-MIPS-ath79-openwrt-machines.patch
index 4ce9268..b01c5de 100644
---
Re: [OpenWrt-Devel] procd button handling
On 19/01/2015 18:05, beeronice wrote: John Crispin blo...@openwrt.org wrote: On 19/01/2015 16:54, Karl Palsson wrote: The wiki page for http://wiki.openwrt.org/doc/howto/hardware.button refers to https://dev.openwrt.org/changeset/37336 procd: make old button hotplug rules work until all packages are migrated Which imply that procd took over hotplug buttons, and that there's a proper way that packages should migrate to a new form. Is there any example of what this new form is? Existing hotplug scripts are just working as is, but are they going to go away? have a look at /etc/rc.button/* Ok, thanks, hadn't seen those. Are these then syntactically the same as hotplug scripts? Same environment variable names, just in /etc/rc.button instead of /etc/hotplug.d/button ? Is there any other change or new features that can be used? this is the json_script rule for the button handler - [ if, [ and, [ has, BUTTON ], [ eq, SUBSYSTEM, button ], ], [ exec, /etc/rc.button/%BUTTON% ] ], it will pass the same env to the script as it would to the hotplug handler. ___ 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] (no subject)
On 19/01/2015 16:54, Karl Palsson wrote: Hi, The wiki page for http://wiki.openwrt.org/doc/howto/hardware.button refers to https://dev.openwrt.org/changeset/37336 procd: make old button hotplug rules work until all packages are migrated Which imply that procd took over hotplug buttons, and that there's a proper way that packages should migrate to a new form. Is there any example of what this new form is? Existing hotplug scripts are just working as is, but are they going to go away? have a look at /etc/rc.button/* Sincerely, Karl Palsson ___ 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] [PATCH] procd: delay inittab workers until the tty exists.
nack, using magic delays is a no go
On 16/01/2015 04:15, Owen Kirby wrote:
If a process with a tty is specified in inittab, delay the worker
process until the tty exists.
This allows starting consoles with terminals that get delayed until
after procd is reads inittab,
and it also allows hotplugging USB-to-serial adapters attached long
after booting.
Signed-off-by: Owen Kirby o...@exegin.com
---
inittab.c | 14 ++
1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/inittab.c b/inittab.c
index 623103d..73c113f 100644
--- a/inittab.c
+++ b/inittab.c
@@ -99,9 +99,15 @@ static void fork_worker(struct init_action *a)
if (!a-proc.pid) {
p = setsid();
-fd = dev_open(a-id);
-if (fd != -1)
-{
+if (a-id) {
+struct timespec tm;
+tm.tv_sec = a-respawn / 1000;
+tm.tv_nsec = (a-respawn % 1000) * 100;
+
+while ((fd = dev_open(a-id)) == -1)
+if (nanosleep(tm, NULL) == -1)
+exit(-1);
+
dup2(fd, STDIN_FILENO);
dup2(fd, STDOUT_FILENO);
dup2(fd, STDERR_FILENO);
@@ -157,7 +163,7 @@ static void askfirst(struct init_action *a)
{
int i;
-if (!dev_exist(a-id) || (console !strcmp(console, a-id))) {
+if (console !strcmp(console, a-id)) {
DEBUG(4, Skipping %s\n, a-id);
return;
}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] procd: delay inittab workers until the tty exists.
On 16/01/2015 21:19, Owen Kirby wrote:
Okay, I'll rewrite it.
However: Is it polling for the existence of the tty device that is
unacceptable (would a solution using uloop_timeout_set() be okay?),
or would I need to process hotplug events from the kernel?
use hotplug events please
Thanks, Owen
On 15-01-15 10:31 PM, John Crispin wrote:
nack, using magic delays is a no go
On 16/01/2015 04:15, Owen Kirby wrote:
If a process with a tty is specified in inittab, delay the
worker process until the tty exists.
This allows starting consoles with terminals that get delayed
until after procd is reads inittab, and it also allows
hotplugging USB-to-serial adapters attached long after
booting.
Signed-off-by: Owen Kirby o...@exegin.com --- inittab.c | 14
++ 1 file changed, 10 insertions(+), 4
deletions(-)
diff --git a/inittab.c b/inittab.c index 623103d..73c113f
100644 --- a/inittab.c +++ b/inittab.c @@ -99,9 +99,15 @@
static void fork_worker(struct init_action *a) if
(!a-proc.pid) { p = setsid(); -fd = dev_open(a-id); -
if (fd != -1) -{ +if (a-id) { +
struct timespec tm; +tm.tv_sec = a-respawn /
1000; +tm.tv_nsec = (a-respawn % 1000) * 100;
+ +while ((fd = dev_open(a-id)) == -1) +
if (nanosleep(tm, NULL) == -1) +exit(-1);
+ dup2(fd, STDIN_FILENO); dup2(fd, STDOUT_FILENO); dup2(fd,
STDERR_FILENO); @@ -157,7 +163,7 @@ static void askfirst(struct
init_action *a) { int i; -if (!dev_exist(a-id) || (console
!strcmp(console, a-id))) { +if (console
!strcmp(console, a-id)) { DEBUG(4, Skipping %s\n, a-id);
return; }
___ 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] [PATCH] build: allow openwrt.git packages to be replaced by feeds
On 16/01/2015 22:45, Mathieu Olivari wrote:
Currently, replacing a package available in openwrt.git requires
modifications in openwrt.git, or requires duplicating the package
in a feed but with a different name, which causes all kind of
problems related to dependencies (all packages selecting it would
have to be modified accordingly to select the new package).
With this change, if a package with the same name is present both
in feeds/ and package/ folders, the one in feeds/ will override the
one in package/, both in the menuconfig and during the build.
This mechanism is particularly useful for vendor tree, or in
general for application which needs to replace one particular
package which exists within openwrt.git by a custom/newer version.
i think this is a bad solution. this is like overriding files in /sbin
with ones in ~/sbin. it will cause lots of side effects and bogus bug
reports. how about you simply upstream your magic feature and have it
added to packages.git ? your patch seems to work around qca not
upstreaming its work properly.
Signed-off-by: Mathieu Olivari math...@qca.qualcomm.com ---
include/scan.awk | 17 + include/scan.mk |2
+- scripts/feeds|9 ++--- 3 files changed, 24
insertions(+), 4 deletions(-) create mode 100644 include/scan.awk
diff --git a/include/scan.awk b/include/scan.awk new file mode
100644 index 000..39b2977 --- /dev/null +++ b/include/scan.awk
@@ -0,0 +1,17 @@ +BEGIN { FS=/ } +$1 ~ /^feeds/ { FEEDS[$NF]=$0
} +$1 !~ /^feeds/ { PKGS[$NF]=$0 } +END { + # Filter-out OpenWrt
packages which have a feeds equivalent + for (pkg in PKGS) +
if
(pkg in FEEDS) + delete PKGS[pkg] + n = asort(PKGS)
+ for (i=1; i
= n; i++) { +print PKGS[i] + } + n = asort(FEEDS) +
for (i=1; i
= n; i++){ + print FEEDS[i] +} +} diff --git
a/include/scan.mk
b/include/scan.mk index 0998333..138707d 100644 ---
a/include/scan.mk +++ b/include/scan.mk @@ -43,7 +43,7 @@ endef
$(FILELIST): rm -f $(TMP_DIR)/info/.files-$(SCAN_TARGET)-* - $(call
FIND_L, $(SCAN_DIR)) $(SCAN_EXTRA) -mindepth 1 $(if
$(SCAN_DEPTH),-maxdepth $(SCAN_DEPTH)) -name Makefile | xargs grep
-HE 'call (Build/DefaultTargets|Build(Package|Target)|.+Package)' |
sed -e 's#^$(SCAN_DIR)/##' -e 's#/Makefile:.*##' | uniq $@ +
$(call FIND_L, $(SCAN_DIR)) $(SCAN_EXTRA) -mindepth 1 $(if
$(SCAN_DEPTH),-maxdepth $(SCAN_DEPTH)) -name Makefile | xargs grep
-HE 'call (Build/DefaultTargets|Build(Package|Target)|.+Package)' |
sed -e 's#^$(SCAN_DIR)/##' -e 's#/Makefile:.*##' | uniq | awk -f
include/scan.awk $@
$(TMP_DIR)/info/.files-$(SCAN_TARGET).mk: $(FILELIST) ( \ diff
--git a/scripts/feeds b/scripts/feeds index 31ad544..01d9041
100755 --- a/scripts/feeds +++ b/scripts/feeds @@ -384,12 +384,15
@@ sub install_package {
# previously installed packages set the runtime package # newly
installed packages set the source package - $installed{$src} and
return 0; + $installed{$src} and !is_core_package($src) and return
0;
# check previously installed packages - $installed{$name} and
return 0; + $installed{$name} and !is_core_package($name) and
return 0; $installed{$src} = 1; - warn Installing package
'$src'\n; + +is_core_package($src) + and warn Overriding
package '$src'\n + or warn Installing package '$src'\n;
$install_method{$type} or do { warn Unknown installation method:
'$type'\n;
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Archer C7, leds and led trigger for ath10k
On 16/01/2015 19:57, Gianluca Anzolin wrote: Hi, I noticed that on Archer C7 the 2.4Ghz and 5Ghz leds are swapped: this is the relevant section of /etc/config/system config led 'led_wlan2g' option name 'WLAN2G' option sysfs 'tp-link:blue:wlan2g' option trigger 'phy0tpt' config led 'led_wlan5g' option name 'WLAN5G' option sysfs 'tp-link:blue:wlan5g' option trigger 'phy1tpt' However on Archer C7 the 5G interface is on phy0 and 2.4G is on phy1. I've yet to find where (and how) this section is autogenerated but I noticed that the phy0pt trigger doesn't even exist on my system. look at target/linux/ar71xx/base-files/etc/uci-defaults/01_leds There is also a bugreport in the bug tracking system pointing at this issue: https://dev.openwrt.org/ticket/18188 I looked at the ath9k implementation and I've come up with the attached patch. Do you think a patch like this is acceptable? it is not Thank you, Gianluca ___ 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] [PATCH] ar71xx: add support for TP-LINK TL-WA701ND v2
On 16/01/2015 13:04, Luigi Tarenga wrote:
Signed-off-by: Luigi Tarenga luigi.tare...@gmail.com
---
I send the patch again, maybe it was not formatted correctly.
please let me know if there is any problem in how i send it.
regards
Luigi
---
package/libs/openssl/Makefile | 6 +++---
package/libs/openssl/patches/150-no_engines.patch | 18 +-
package/libs/openssl/patches/200-parallel_build.patch | 8
package/network/ipv6/map/Makefile | 7 ---
package/network/ipv6/map/files/map.sh | 3 +++
package/network/ipv6/map/src/mapcalc.c| 6 --
6 files changed, 27 insertions(+), 21 deletions(-)
the diffstat is from a different patch
diff --git a/target/linux/ar71xx/base-files/etc/diag.sh
b/target/linux/ar71xx/base-files/etc/diag.sh
index fa07f39..eb96338 100755
--- a/target/linux/ar71xx/base-files/etc/diag.sh
+++ b/target/linux/ar71xx/base-files/etc/diag.sh
@@ -195,6 +195,7 @@ get_status_led() {
tl-mr3220-v2 | \
tl-mr3420 | \
tl-mr3420-v2 | \
+tl-wa701nd-v2 | \
tl-wa801nd-v2 | \
tl-wa901nd | \
tl-wa901nd-v2 | \
diff --git a/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds
b/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds
index 5b9dbe7..51c2bca 100755
--- a/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds
+++ b/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds
@@ -275,7 +275,11 @@ tl-wa850re)
ucidef_set_led_rssi rssihigh RSSIHIGH tp-link:blue:signal5
wlan0 80 100 -79 13
;;
-tl-wa860re)
+tl-wa701nd-v2 | \
+tl-wa830re-v2 | \
+tl-wa860re | \
+tl-wa801nd-v2 | \
+tl-wa901nd-v3)
ucidef_set_led_netdev lan LAN tp-link:green:lan eth0
ucidef_set_led_wlan wlan WLAN tp-link:green:wlan phy0tpt
;;
@@ -333,11 +337,6 @@ tl-wr841n-v8)
ucidef_set_led_wlan wlan WLAN tp-link:green:wlan phy0tpt
;;
-tl-wa830re-v2)
-ucidef_set_led_netdev lan LAN tp-link:green:lan eth0
-ucidef_set_led_wlan wlan WLAN tp-link:green:wlan phy0tpt
-;;
-
tl-wr841n-v9)
ucidef_set_led_netdev wan WAN tp-link:green:wan eth1
ucidef_set_led_switch lan1 LAN1 tp-link:green:lan1 switch0 0x10
@@ -357,12 +356,6 @@ tl-wr842n-v2)
ucidef_set_led_usbdev usb USB tp-link:green:3g 1-1
;;
-tl-wa801nd-v2 | \
-tl-wa901nd-v3)
-ucidef_set_led_netdev lan LAN tp-link:green:lan eth0
-ucidef_set_led_wlan wlan WLAN tp-link:green:wlan phy0tpt
-;;
-
this refactoring should be in a separate patch.
tl-wr941nd | \
tl-wr1041n-v2)
ucidef_set_led_wlan wlan WLAN tp-link:green:wlan phy0tpt
diff --git a/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
b/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
index c5cfd67..4be30b8 100755
--- a/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
+++ b/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
@@ -301,6 +301,7 @@ tl-mr13u |\
tl-mr3020 |\
tl-mr3040 |\
tl-mr3040-v2 |\
+tl-wa701nd-v2 |\
tl-wa750re |\
tl-wa850re |\
tl-wa830re-v2 |\
diff --git a/target/linux/ar71xx/base-files/lib/ar71xx.sh
b/target/linux/ar71xx/base-files/lib/ar71xx.sh
index 1e96b6d..df35775 100755
--- a/target/linux/ar71xx/base-files/lib/ar71xx.sh
+++ b/target/linux/ar71xx/base-files/lib/ar71xx.sh
@@ -571,6 +571,9 @@ ar71xx_board_detect() {
*TL-MR3420 v2)
name=tl-mr3420-v2
;;
+*TL-WA701ND v2)
+name=tl-wa701nd-v2
+;;
*TL-WA750RE)
name=tl-wa750re
;;
diff --git a/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
b/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
index 846954c..eeaac6a 100755
--- a/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
+++ b/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
@@ -269,6 +269,7 @@ platform_check_image() {
tl-mr3220-v2 | \
tl-mr3420 | \
tl-mr3420-v2 | \
+tl-wa701nd-v2 | \
tl-wa7510n | \
tl-wa750re | \
tl-wa850re | \
diff --git a/target/linux/ar71xx/config-3.10 b/target/linux/ar71xx/config-3.10
index 9a8378a..482914a 100644
--- a/target/linux/ar71xx/config-3.10
+++ b/target/linux/ar71xx/config-3.10
@@ -88,6 +88,7 @@ CONFIG_ATH79_MACH_TL_MR11U=y
CONFIG_ATH79_MACH_TL_MR13U=y
CONFIG_ATH79_MACH_TL_MR3020=y
CONFIG_ATH79_MACH_TL_MR3X20=y
+CONFIG_ATH79_MACH_TL_WA701ND_V2=y
CONFIG_ATH79_MACH_TL_WA830RE_V2=y
CONFIG_ATH79_MACH_TL_WA901ND=y
CONFIG_ATH79_MACH_TL_WA901ND_V2=y
diff --git a/target/linux/ar71xx/files/arch/mips/ath79/mach-tl-wa701nd-v2.c
b/target/linux/ar71xx/files/arch/mips/ath79/mach-tl-wa701nd-v2.c
new file mode 100644
index 000..aab92b3
--- /dev/null
+++ b/target/linux/ar71xx/files/arch/mips/ath79/mach-tl-wa701nd-v2.c
@@ -0,0 +1,116 @@
+/*
+ * TP-LINK TL-WA701ND v2 board support
+ *
+ * Copyright (C) 2015 Luigi Tarenga luigi.tare...@gmail.com
+ *
+ * This program is
Re: [OpenWrt-Devel] [PATCH] ramips: add support for Intenso Memory 2 Move USB 3.0
On 15/01/2015 22:47, Christian Lamparter wrote: This adds support for a rt5350-based portable nas solution from Intenso. The board comes with 32M RAM and 8M Flash, the built-in HDD is connected/accessible via a usb3.0-sata bridge VLI VL701. [] diff --git a/target/linux/ramips/rt305x/profiles/m2m.mk b/target/linux/ramips/rt305x/profiles/m2m.mk new file mode 100644 index 000..e5cb6b8 --- /dev/null +++ b/target/linux/ramips/rt305x/profiles/m2m.mk @@ -0,0 +1,20 @@ +# +# Copyright (C) 2015 OpenWrt.org +# +# This is free software, licensed under the GNU General Public License v2. +# See /LICENSE for more information. +# + +define Profile/M2M + NAME:=Intenso Memory 2 Move + PACKAGES:=\ + kmod-ledtrig-netdev kmod-ledtrig-timer kmod-leds-gpio \ + kmod-usb-core kmod-usb2 kmod-usb-storage kmod-scsi-core \ + kmod-fs-ext4 kmod-fs-vfat block-mount +endef + not sure about the filesystem selection. what filesystem is on the disc when it is shipped ? +define Profile/M2M/Description + Package set for Intenso Memory 2 Move USB 3.0 +endef + +$(eval $(call Profile,M2M)) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] [ar71xx] Add support for MERCURY MAC1200R
On 11/01/2015 12:48, open...@rogerpueyo.com wrote:
From: Roger Pueyo Centelles roger.pu...@guifi.net
description and SoB are missing
---
target/linux/ar71xx/base-files/etc/diag.sh | 3 +
.../ar71xx/base-files/etc/uci-defaults/01_leds | 5 +
.../ar71xx/base-files/etc/uci-defaults/02_network | 1 +
target/linux/ar71xx/base-files/lib/ar71xx.sh | 6 +
.../ar71xx/base-files/lib/upgrade/platform.sh | 1 +
target/linux/ar71xx/config-3.14| 1 +
.../files/arch/mips/ath79/mach-mc-mac1200r.c | 157
+
target/linux/ar71xx/generic/profiles/mercury.mk| 17 +++
target/linux/ar71xx/image/Makefile | 1 +
.../736-MIPS-ath79-add-MC-MAC1200R-support.patch | 39 +
10 files changed, 231 insertions(+)
create mode 100644
target/linux/ar71xx/files/arch/mips/ath79/mach-mc-mac1200r.c
create mode 100644 target/linux/ar71xx/generic/profiles/mercury.mk
create mode 100644
target/linux/ar71xx/patches-3.14/736-MIPS-ath79-add-MC-MAC1200R-support.patch
diff --git a/target/linux/ar71xx/base-files/etc/diag.sh
b/target/linux/ar71xx/base-files/etc/diag.sh
index 06b96a3..388727f 100755
--- a/target/linux/ar71xx/base-files/etc/diag.sh
+++ b/target/linux/ar71xx/base-files/etc/diag.sh
@@ -105,6 +105,9 @@ get_status_led() {
ls-sr71)
status_led=ubnt:green:d22
;;
+ mc-mac1200r)
+ status_led=mercury:green:system
+ ;;
mr600)
status_led=mr600:orange:power
;;
diff --git a/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds
b/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds
index 296ea57..dc5dfa1 100755
--- a/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds
+++ b/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds
@@ -166,6 +166,11 @@ hornet-ub)
ucidef_set_led_usbdev usb USB alfa:blue:usb 1-1
;;
+mc-mac1200r)
+ ucidef_set_led_wlan wlan2g WLAN2G mercury:green:wlan2g phy1tpt
+ ucidef_set_led_wlan wlan5g WLAN5G mercury:green:wlan5g phy0tpt
+ ;;
+
mr600)
ucidef_set_led_wlan wlan58 WLAN58 mr600:green:wlan58 phy0tpt
;;
diff --git a/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
b/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
index b4b6cb3..8151470 100755
--- a/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
+++ b/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
@@ -367,6 +367,7 @@ dir-615-e1 |\
dir-615-e4 |\
hiwifi-hc6361 |\
ja76pf |\
+mc-mac1200r|\
mynet-n600 |\
oolite |\
qihoo-c301 |\
diff --git a/target/linux/ar71xx/base-files/lib/ar71xx.sh
b/target/linux/ar71xx/base-files/lib/ar71xx.sh
index 9b056e9..3ce63aa 100755
--- a/target/linux/ar71xx/base-files/lib/ar71xx.sh
+++ b/target/linux/ar71xx/base-files/lib/ar71xx.sh
@@ -97,6 +97,9 @@ tplink_board_detect() {
015300*)
model=EasyLink EL-MINI
;;
+ 12*)
+ model=MERCURY MAC1200R
+ ;;
3C0001*)
model=OOLITE
;;
@@ -432,6 +435,9 @@ ar71xx_board_detect() {
*LS-SR71)
name=ls-sr71
;;
+ *MAC1200R)
+ name=mc-mac1200r
+ ;;
*MR600v2)
name=mr600v2
;;
diff --git a/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
b/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
index 6dabf4e..7153614 100755
--- a/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
+++ b/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
@@ -297,6 +297,7 @@ platform_check_image() {
el-m150 | \
el-mini | \
gl-inet | \
+ mc-mac1200r | \
oolite | \
smart-300 | \
tl-mr10u | \
diff --git a/target/linux/ar71xx/config-3.14 b/target/linux/ar71xx/config-3.14
index b6fa4ab..a99c082 100644
--- a/target/linux/ar71xx/config-3.14
+++ b/target/linux/ar71xx/config-3.14
@@ -64,6 +64,7 @@ CONFIG_ATH79_MACH_HIWIFI_HC6361=y
CONFIG_ATH79_MACH_HORNET_UB=y
CONFIG_ATH79_MACH_JA76PF=y
CONFIG_ATH79_MACH_JWAP003=y
+CONFIG_ATH79_MACH_MC_MAC1200R=y
CONFIG_ATH79_MACH_MR600=y
CONFIG_ATH79_MACH_MR900=y
CONFIG_ATH79_MACH_MYNET_N600=y
diff --git a/target/linux/ar71xx/files/arch/mips/ath79/mach-mc-mac1200r.c
b/target/linux/ar71xx/files/arch/mips/ath79/mach-mc-mac1200r.c
new file mode 100644
index 000..6b92b9c
--- /dev/null
+++ b/target/linux/ar71xx/files/arch/mips/ath79/mach-mc-mac1200r.c
@@ -0,0 +1,157 @@
+/*
+ * MERCURY MAC1200R board support
+ *
+ * Copyright (C) 2012 Gabor Juhos juh...@openwrt.org
+ * Copyright (C) 2013 Gui Iribarren g...@altermundi.net
+ *
+ * This program is free software; you can redistribute it and/or modify it
+ * under the terms of the GNU General Public License version 2 as published
+ * by the Free Software Foundation.
+ */
+
Re: [OpenWrt-Devel] [PATCH] comgt: Allow using non-TTY devices
On 13/01/2015 18:00, Matti Laakso wrote:
Some Huawei mobile broadband sticks utilizing the NCM protocol expose
the control channel as a cdc-wdm device node instead of a virtual TTY.
This device node does not support the terminal ioctls. This patch
adds a check whether the provided device is a TTY or not and does not
attempt to use the terminal ioctls if they are not supported.
Signed-off-by: Matti Laakso malaa...@elisanet.fi
---
diff --git a/package/network/utils/comgt/patches/004-check_tty.patch
b/package/network/utils/comgt/patches/004-check_tty.patch
new file mode 100644
index 000..d269bce
--- /dev/null
+++ b/package/network/utils/comgt/patches/004-check_tty.patch
@@ -0,0 +1,177 @@
+--- a/comgt.c
b/comgt.c
+@@ -91,6 +91,7 @@ unsigned long hstart,hset;
+ char NullString[]={ };
+ BOOL lastcharnl=1; /* Indicate that last char printed from getonebyte
+was a nl, so no new one is needed */
++BOOL tty=1;
+
+
+ //open com \/dev/modem\\nset com 38400n81\nset senddelay 0.05\nsend
\ATi^m\\nget 2 \ ^m\ $s\nprint \Response : \,$s,\\\n\\nget 2 \ ^m\
$s\nprint \Response :\,$s,\\\n\\nget 2 \ ^m\ $s\nprint \Response :
\,$s,\\\n\\n\n;
+@@ -918,10 +919,12 @@ BOOL getonoroff(void) {
+ }
+
+ void setcom(void) {
+- stbuf.c_cflag = ~(CBAUD | CSIZE | CSTOPB | CLOCAL | PARENB);
+- stbuf.c_cflag |= (speed | bits | CREAD | clocal | parity | stopbits );
+- if (ioctl(comfd, TCSETA, stbuf) 0) {
+-serror(Can't ioctl set device,1);
++ if (tty) {
++stbuf.c_cflag = ~(CBAUD | CSIZE | CSTOPB | CLOCAL | PARENB);
++stbuf.c_cflag |= (speed | bits | CREAD | clocal | parity | stopbits );
++if (ioctl(comfd, TCSETA, stbuf) 0) {
++ serror(Can't ioctl set device,1);
++}
+ }
+ }
+
+@@ -1224,9 +1227,11 @@ void doclose(void) {
+ if(strcmp(token,hardcom)==0) {
+ if(comfd== -1) serror(Com device not open,1);
+ vmsg(Closing device);
+-if (ioctl(comfd, TCSETA, svbuf) 0) {
+- sprintf(msg,Can't ioctl set device %s.\n,device);
+- serror(msg,1);
++if (tty) {
++ if (ioctl(comfd, TCSETA, svbuf) 0) {
++sprintf(msg,Can't ioctl set device %s.\n,device);
++serror(msg,1);
++ }
+ }
if (tty (ioctl(comfd, TCSETA, svbuf) 0)) .
i think this pattern would drastically reduce the diffstat
+ close(comfd);
+ comfd= -1;
+@@ -1266,26 +1271,32 @@ void opengt(void) {
+ ext(1);
+ }
+ }
+- if (ioctl (comfd, TCGETA, svbuf) 0) {
+-sprintf(msg,Can't control %s, please try again.\n,device);
+-serror(msg,1);
++ if (isatty (comfd))
++tty=1;
++ else
++tty=0;
++ if (tty) {
++if (ioctl (comfd, TCGETA, svbuf) 0) {
++ sprintf(msg,Can't control %s, please try again.\n,device);
++ serror(msg,1);
++}
++ioctl(comfd, TCGETA, stbuf);
++speed=stbuf.c_cflag CBAUD;
++if (high_speed == 0) strcpy(cspeed,115200);
++else strcpy(cspeed,57600);
++bits=stbuf.c_cflag CSIZE;
++clocal=stbuf.c_cflag CLOCAL;
++stopbits=stbuf.c_cflag CSTOPB;
++parity=stbuf.c_cflag (PARENB | PARODD);
++stbuf.c_iflag = ~(IGNCR | ICRNL | IUCLC | INPCK | IXON | IXANY |
IGNPAR );
++stbuf.c_oflag = ~(OPOST | OLCUC | OCRNL | ONLCR | ONLRET);
++stbuf.c_lflag = ~(ICANON | ECHO | ECHOE | ECHONL);
++stbuf.c_lflag = ~(ECHO | ECHOE);
++stbuf.c_cc[VMIN] = 1;
++stbuf.c_cc[VTIME] = 0;
++stbuf.c_cc[VEOF] = 1;
+ }
+ setenv(COMGTDEVICE,device,1);
+- ioctl(comfd, TCGETA, stbuf);
+- speed=stbuf.c_cflag CBAUD;
+- if (high_speed == 0) strcpy(cspeed,115200);
+- else strcpy(cspeed,57600);
+- bits=stbuf.c_cflag CSIZE;
+- clocal=stbuf.c_cflag CLOCAL;
+- stopbits=stbuf.c_cflag CSTOPB;
+- parity=stbuf.c_cflag (PARENB | PARODD);
+- stbuf.c_iflag = ~(IGNCR | ICRNL | IUCLC | INPCK | IXON | IXANY | IGNPAR
);
+- stbuf.c_oflag = ~(OPOST | OLCUC | OCRNL | ONLCR | ONLRET);
+- stbuf.c_lflag = ~(ICANON | ECHO | ECHOE | ECHONL);
+- stbuf.c_lflag = ~(ECHO | ECHOE);
+- stbuf.c_cc[VMIN] = 1;
+- stbuf.c_cc[VTIME] = 0;
+- stbuf.c_cc[VEOF] = 1;
+ setcom();
+ dormir(20); /* Wait a bit (DTR raise) */
+ sprintf(msg,Opened %s as FD %d,device,comfd);
+@@ -1302,45 +1313,50 @@ void opendevice(void) {
+ }
+ }
+ else comfd=0;
+-
+- if (ioctl (comfd, TCGETA, svbuf) 0) {
+-sprintf(msg,Can't ioctl get device %s.\n,device);
+-serror(msg,1);
+- }
+- ioctl(comfd, TCGETA, stbuf);
+- speed=stbuf.c_cflag CBAUD;
+- switch(speed) {
+-case B0: strcpy(cspeed,0);break;
+-case B50: strcpy(cspeed,50);break;
+-case B75: strcpy(cspeed,75);break;
+-case B110: strcpy(cspeed,110);break;
+-case B300: strcpy(cspeed,300);break;
+-case B600: strcpy(cspeed,600);break;
+-case B1200: strcpy(cspeed,1200);break;
+-case B2400: strcpy(cspeed,2400);break;
+-case B4800: strcpy(cspeed,4800);break;
+-case
Re: [OpenWrt-Devel] Archer C7, leds and led trigger for ath10k
On 17/01/2015 08:42, Gianluca Anzolin wrote: Il 17/01/2015 07:41, John Crispin ha scritto: There is also a bugreport in the bug tracking system pointing at this issue: https://dev.openwrt.org/ticket/18188 I looked at the ath9k implementation and I've come up with the attached patch. Do you think a patch like this is acceptable? it is not do you care to elaborate? what's wrong with it? Gianluca _ imho fixing target/linux/ar71xx/base-files/etc/uci-defaults/01_leds is enough nd not driver patch is required __ 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] [PATCH] ramips: revert failsafe switch workaround for RT5350 introduced in r42179.
On 25/12/2014 02:29, Vittorio G (VittGam) wrote:
It is not needed anymore as TCP packets get passed correctly now
even when VLAN is disabled.
are you sure this is the case for all rt3x5x, rt5350 and mt7628 units ?
This piece of code also broke routers where the LAN port is not
wired to port 0 of the internal switch.
Signed-off-by: Vittorio Gambaletta open...@vittgam.net
diff --git
a/target/linux/ramips/base-files/lib/preinit/07_set_preinit_iface_ramips
b/target/linux/ramips/base-files/lib/preinit/07_set_preinit_iface_ramips
index cae6396..386b527 100644
---
a/target/linux/ramips/base-files/lib/preinit/07_set_preinit_iface_ramips
+++ b/target/linux/ramips/base-files/lib/preinit/07_set_preinit_iface_ramips
@@ -11,24 +11,7 @@ ramips_set_preinit_iface() { swconfig dev rt305x
set reset 1 fi
- if echo $RT3X5X | egrep -q (RT5350|MT7628); then -# This
is a
dirty hack to get by while the switch - # problem is
investigated.
When VLAN is disabled, ICMP - # pings work as expected, but TCP
connections time -# out, so telnetting in failsafe is impossible.
The - # likely reason is TCP checksumming hardware getting -
#
disabled: - #
https://www.mail-archive.com/openwrt-devel@lists.openwrt.org/msg19870.html
- swconfig dev rt305x set enable_vlan 1
- swconfig dev rt305x vlan 1 set ports 0 6 -
swconfig dev
rt305x port 6 set untag 0 - swconfig dev rt305x set apply 1 -
vconfig add eth0 1 - ifconfig eth0 up - ifname=eth0.1 -
else -
ifname=eth0 - fi +ifname=eth0 }
boot_hook_add preinit_main ramips_set_preinit_iface
___ 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] [PATCH] ramips: add support for Intenso Memory 2 Move USB 3.0
On 17/01/2015 14:49, Christian Lamparter wrote: On Saturday, January 17, 2015 07:48:24 AM John Crispin wrote: On 15/01/2015 22:47, Christian Lamparter wrote: This adds support for a rt5350-based portable nas solution from Intenso. The board comes with 32M RAM and 8M Flash, the built-in HDD is connected/accessible via a usb3.0-sata bridge VLI VL701. BTW: In the meantime, I was able to find the Chinese distributor for this product. The devices seem to be sold by IOVST and they call it the UIS700HD [0]. However, this might not be the hardware vendor. The RT2860.bin in the rootfs has ApCliSsid set to Tenda_501500. But I haven't found anything remotely close on Tenda's product website. my question is: should I rename the profile (and the files) to: UIS700HD then? I would like to keep the Intenso name, because they provided me/us/anyone with at least a (partially very useful) GPL source for their product on their website [1]. feel free to leave it as intenso, just make sure to add a wiki page and list the alternative SKUs there. The HDD was originally formatted with a single 500GB (size of the HDD) vfat[FAT32] partition. The original firmware supports vfat, exfat (via fuse), ntfs (via tuxera tntfs module) and ext2 (ext2 is used exclusively for updating the device firmware. It might be only available for the ramdisk uimage?! see notes about upfs [2]). The rootfs has a few traces of additional support [i.e.: they are listed in scripts or have installed fstools] for hfsplus and xfs. But as far as I can tell, they won't work. BTW: I would like to generate a ramdisk image by default too (I was thinking of adding FEATURES+=ramdisk). The reason is that this would make flashing the device easier (load the ramdisk image via tftp and then use sysupgrade with the squashfs-sysupgrade image). feel free to send a patch. applied your patch as r44001 However, this would of course cause all other rt305x devices to build the ramdisk too! [which is probably not ideal. So, is there another way?]. Regards, Christian [0] http://www.iovst.com/product/article-41.html [1] http://www.intenso.de/downloads.php?kategorie=29produkt=1357297608 [2] http://hckohwnotes.blogspot.de/2014/05/debian-on-intenso-memory-2-move-intenso.html ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 0/6] ar8216: patch series for AR8327/AR8337
On 12/01/2015 20:16, Heiner Kallweit wrote: Patches 1-3 are improvements w/o functional change. merged 1-3 4-6 will need a bit more time and a closer look Patches 4 allows to control EEE PHY sleep mode per port via swconfig. Motivation is that as workaround for issues with certain link partners EEE was disabled in general. Still the default is to initially disable EEE on all ports, however the brave now have the option to enable EEE on selected ports. Patch 5 displays autonegotiated EEE capabilities as part of the get_link attribute. Note that enabling/disabling PHY EEE sleep mode is independent of autonegotiated EEE capabilities. Even if PHY EEE sleep mode is disabled the switch advertises EEE capabilities to the link partner. This might still allow the link partner to sleep if network is inactive. Patch 6 displays autonegotiated rx/tx flow control as part of the get_link attribute. So far this was the case in forced mode only. Heiner Kallweit (6): ar8216: define all switch_addr structs as const ar8216: replace ar8xxx_rmw with ar8xxx_reg_set where appropriate ar8216: introduce ar8xxx_reg_clear complementing ar8xxx_reg_set ar8216: introduce enable_eee swconfig attribute to control 802.3az EEE per port ar8216: add 802.3az EEE info to swconfig get_link attribute ar8216: display flow control info in swconfig get_link in case of autonegatiation too .../linux/generic/files/drivers/net/phy/ar8216.c | 60 --- .../linux/generic/files/drivers/net/phy/ar8216.h | 18 +++ .../linux/generic/files/drivers/net/phy/ar8327.c | 175 ++--- .../linux/generic/files/drivers/net/phy/ar8327.h | 5 + .../linux/generic/files/drivers/net/phy/swconfig.c | 4 +- target/linux/generic/files/include/linux/switch.h | 2 + 6 files changed, 216 insertions(+), 48 deletions(-) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] uclient libubox: handling SIGPIPE / EPIPE
On 21/01/2015 11:32, Rafał Miłecki wrote: I'm trying to use uclient to monitor my home network servers querying http://ip/status . So far I was using bash + curl, but I'm trying to learn libubox now. So today I accidentally queried some unknown machine (random IP) and my app crashed. What has happened: 1) When I first called uclient_request, uclient opened socket and wrote GET /status HTTP/1.1 Host: 192.168.0.136 Inside the ustream_fd_write, write returned -1 and errno was EAGAIN. 2) After handling control back to uloop there was another try of sending GET /status HTTP/1.1 Host: 192.168.0.136 but this time it has failed badly during the write call. There was SIGPIPE that wasn't handled and my app has been terminated. Should we somehow handle SIGPIPE in uclient or disable it using SO_NOSIGPIPE? services like procd do - signal(SIGPIPE, SIG_IGN); this should really be changed to work with 464e05e3 from libubox.git unless i missed something it might be a good idea to add PIP to uloop_setup_signals() ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] hostapd: backport BSSID black/whitelists
On 11/02/2015 15:42, Stefan Tomanek wrote: Dies schrieb Stefan Tomanek (stefan.tomanek+open...@wertarbyte.de): Any feedback regarding this backported feature? this patch is fine, the log file one scares me though as there is no log rotate logic. What kind of log rotate logic do you mean? That can be implemented externally if needed: just move the old logfile away and send SIGHUP to the hostapd process, to make it reopen (and recreate) the file. Any more feedback regarding both patches? still on my todo, sorry for the delay it'll take a few more days till i can go over all the hostapd patches in the queue. ___ 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] [PATCH netifd] bridge: allow enabling or disabling the multicast querier independently of IGMP snooping
On 17/02/2015 18:16, Matthias Schiffer wrote: On 01/28/2015 11:00 PM, John Crispin wrote: On 28/01/2015 21:31, Matthias Schiffer wrote: On 01/28/2015 11:54 AM, John Crispin wrote: [...] this should not break anything with multiple ubus calls. the default behavior also wont change as we set cfg-multicast_querier = true; Please make those changes to the patch and resend it. I just re-read the whole function and noticed why I made my change like this in the first place: all values in bridge_config are always reset to their defaults at the top of bridge_apply_settings() anyways, not regarding if the blobmsg contains a new value for the options or not. yep, i will cook up a patch tomorrow ... Hi, any news on this? i did make a patch, apparently i never pushed it. will go searching during the day ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH RFT] kernel: mtdsplit_uimage: debug buf/header sizes
yep, fixes the problem. please push it :)
On 12/02/2015 12:47, Rafał Miłecki wrote:
---
John can you give it a try, please?
---
.../generic/files/drivers/mtd/mtdsplit/mtdsplit_uimage.c | 15
++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git
a/target/linux/generic/files/drivers/mtd/mtdsplit/mtdsplit_uimage.c
b/target/linux/generic/files/drivers/mtd/mtdsplit/mtdsplit_uimage.c
index 2bb5e9a..4abc4be 100644
--- a/target/linux/generic/files/drivers/mtd/mtdsplit/mtdsplit_uimage.c
+++ b/target/linux/generic/files/drivers/mtd/mtdsplit/mtdsplit_uimage.c
@@ -20,6 +20,8 @@
#include mtdsplit.h
+static int first_try = 1;
+
/*
* uimage_header itself is only 64B, but it may be prepended with another
data.
* Currently the biggest size is for Edimax devices: 20B + 64B
@@ -60,6 +62,8 @@ read_uimage_header(struct mtd_info *mtd, size_t offset,
u_char *buf,
size_t retlen;
int ret;
+ if (first_try)
+ pr_info([%s] buf:%p header_len:%zu\n, __FUNCTION__, buf,
header_len);
ret = mtd_read(mtd, offset, header_len, retlen, buf);
if (ret) {
pr_debug(read error in \%s\\n, mtd-name);
@@ -106,11 +110,15 @@ static int __mtdsplit_parse_uimage(struct mtd_info
*master,
ret = -ENOMEM;
goto err_free_parts;
}
+ if (first_try)
+ pr_info([%s] buf:%p sizeof(*buf):%u\n, __FUNCTION__, buf,
sizeof(*buf));
/* find uImage on erase block boundaries */
for (offset = 0; offset master-size; offset += master-erasesize) {
struct uimage_header *header;
+ if (first_try)
+ pr_info([%s] sizeof(*header):%u\n, __FUNCTION__,
sizeof(*header));
uimage_size = 0;
ret = read_uimage_header(master, offset, buf, sizeof(*buf));
@@ -308,8 +316,13 @@ static ssize_t uimage_find_edimax(u_char *buf, size_t
len)
{
struct uimage_header *header;
+ if (first_try)
+ pr_info([%s] buf:%p len:%zu FW_EDIMAX_OFFSET +
sizeof(*header):%u\n, __FUNCTION__, buf, len, FW_EDIMAX_OFFSET +
sizeof(*header));
+
if (len FW_EDIMAX_OFFSET + sizeof(*header)) {
- pr_err(Buffer too small for checking Edimax header\n);
+ if (first_try)
+ pr_err(Buffer too small for checking Edimax header\n);
+ first_try = 0;
return -ENOSPC;
}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH RFT] kernel: mtdsplit_uimage: debug buf/header sizes
[0.564000] Creating 4 MTD partitions on spi32766.0:
[0.568000] 0x-0x0001 : uboot
[0.572000] 0x0001-0x0002 : uboot-env
[0.58] 0x0002-0x0003 : calibration
[0.584000] 0x0005-0x00ff : firmware
[0.596000] mtdsplit_uimage: [__mtdsplit_parse_uimage] buf:c0049000
sizeof(*buf):1
[0.60] mtdsplit_uimage: [__mtdsplit_parse_uimage] sizeof(*header):64
[0.608000] mtdsplit_uimage: [read_uimage_header] buf:c0049000
header_len:1
[0.616000] mtdsplit_uimage: [uimage_find_edimax] buf:c0049000 len:1
FW_EDIMAX_OFFSET + sizeof(*header):84
[0.624000] mtdsplit_uimage: Buffer too small for checking Edimax header
[0.784000] Dedicated partitioner didn't split firmware partition,
please fill a bug report!
[0.788000] 0x00172108-0x00ff : rootfs
[0.796000] mtd: partition rootfs must either start or end on erase
block boundary or be smaller than an erase block -- forcing read-only
[0.808000] mtd: device 4 (rootfs) set to be root filesystem
[0.812000] 1 squashfs-split partitions found on MTD device rootfs
[0.82] 0x0034-0x00ff : rootfs_data
[1.916000] Realtek RTL8366RB ethernet switch driver version 0.2.4
[1.924000] rtl8366rb rtl8366rb: using GPIO pins 491 (SDA) and 493 (SCK)
[1.928000] rtl8366rb rtl8366rb: RTL5937 ver. 3 chip found
On 12/02/2015 12:47, Rafał Miłecki wrote:
---
John can you give it a try, please?
---
.../generic/files/drivers/mtd/mtdsplit/mtdsplit_uimage.c | 15
++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git
a/target/linux/generic/files/drivers/mtd/mtdsplit/mtdsplit_uimage.c
b/target/linux/generic/files/drivers/mtd/mtdsplit/mtdsplit_uimage.c
index 2bb5e9a..4abc4be 100644
--- a/target/linux/generic/files/drivers/mtd/mtdsplit/mtdsplit_uimage.c
+++ b/target/linux/generic/files/drivers/mtd/mtdsplit/mtdsplit_uimage.c
@@ -20,6 +20,8 @@
#include mtdsplit.h
+static int first_try = 1;
+
/*
* uimage_header itself is only 64B, but it may be prepended with another
data.
* Currently the biggest size is for Edimax devices: 20B + 64B
@@ -60,6 +62,8 @@ read_uimage_header(struct mtd_info *mtd, size_t offset,
u_char *buf,
size_t retlen;
int ret;
+ if (first_try)
+ pr_info([%s] buf:%p header_len:%zu\n, __FUNCTION__, buf,
header_len);
ret = mtd_read(mtd, offset, header_len, retlen, buf);
if (ret) {
pr_debug(read error in \%s\\n, mtd-name);
@@ -106,11 +110,15 @@ static int __mtdsplit_parse_uimage(struct mtd_info
*master,
ret = -ENOMEM;
goto err_free_parts;
}
+ if (first_try)
+ pr_info([%s] buf:%p sizeof(*buf):%u\n, __FUNCTION__, buf,
sizeof(*buf));
/* find uImage on erase block boundaries */
for (offset = 0; offset master-size; offset += master-erasesize) {
struct uimage_header *header;
+ if (first_try)
+ pr_info([%s] sizeof(*header):%u\n, __FUNCTION__,
sizeof(*header));
uimage_size = 0;
ret = read_uimage_header(master, offset, buf, sizeof(*buf));
@@ -308,8 +316,13 @@ static ssize_t uimage_find_edimax(u_char *buf, size_t
len)
{
struct uimage_header *header;
+ if (first_try)
+ pr_info([%s] buf:%p len:%zu FW_EDIMAX_OFFSET +
sizeof(*header):%u\n, __FUNCTION__, buf, len, FW_EDIMAX_OFFSET +
sizeof(*header));
+
if (len FW_EDIMAX_OFFSET + sizeof(*header)) {
- pr_err(Buffer too small for checking Edimax header\n);
+ if (first_try)
+ pr_err(Buffer too small for checking Edimax header\n);
+ first_try = 0;
return -ENOSPC;
}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH RFT] kernel: mtdsplit_uimage: debug buf/header sizes
On 12/02/2015 21:18, Rafał Miłecki wrote: On 12 February 2015 at 21:04, John Crispin blo...@openwrt.org wrote: [0.564000] Creating 4 MTD partitions on spi32766.0: [0.568000] 0x-0x0001 : uboot [0.572000] 0x0001-0x0002 : uboot-env [0.58] 0x0002-0x0003 : calibration [0.584000] 0x0005-0x00ff : firmware [0.596000] mtdsplit_uimage: [__mtdsplit_parse_uimage] buf:c0049000 sizeof(*buf):1 [0.60] mtdsplit_uimage: [__mtdsplit_parse_uimage] sizeof(*header):64 [0.608000] mtdsplit_uimage: [read_uimage_header] buf:c0049000 header_len:1 [0.616000] mtdsplit_uimage: [uimage_find_edimax] buf:c0049000 len:1 FW_EDIMAX_OFFSET + sizeof(*header):84 [0.624000] mtdsplit_uimage: Buffer too small for checking Edimax header [0.784000] Dedicated partitioner didn't split firmware partition, please fill a bug report! [0.788000] 0x00172108-0x00ff : rootfs [0.796000] mtd: partition rootfs must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only [0.808000] mtd: device 4 (rootfs) set to be root filesystem [0.812000] 1 squashfs-split partitions found on MTD device rootfs [0.82] 0x0034-0x00ff : rootfs_data [1.916000] Realtek RTL8366RB ethernet switch driver version 0.2.4 [1.924000] rtl8366rb rtl8366rb: using GPIO pins 491 (SDA) and 493 (SCK) [1.928000] rtl8366rb rtl8366rb: RTL5937 ver. 3 chip found Thank you! My obvious bug was fixed in https://dev.openwrt.org/changeset/44424/ they tend to be the hardest to find ;) Please note that if you still get Dedicated partitioner didn't split firmware partition, please fill a bug report! with 44424, it means that there is something wrong in target/linux/generic/files/drivers/mtd/mtdsplit/mtdsplit_uimage.c and we/you should look for a working reference code in 405-mtd-old-firmware-uimage-splitter.patch ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] looking for a tl-wdr4900 tester
Hi, just bumped the kernel for the tl-wdr4900. i don't actually have the unit. anyone around that feels like testing the images before i push the series to trunk ? John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lantiq v3.18
On 10/02/2015 10:40, Daniel Gimpelevich wrote: Is there a patchset I could try? try r44421 or newer On Mon, 2015-02-09 at 12:44 -0800, Daniel Gimpelevich wrote: On Mon, 2015-02-09 at 21:27 +0100, John Crispin wrote: bootlog please On 09/02/2015 21:25, Daniel Gimpelevich wrote: On Mon, 2015-02-09 at 19:18 +0100, John Crispin wrote: try r44366 or newer please SPI flash is not detected, bricking the device. [0.00] Linux version 3.18.6 (danielg4@chimera) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r43982) ) #3 Mon Feb 9 115 [0.00] SoC: AR9 rev 1.2 [0.00] bootconsole [early0] enabled [0.00] CPU0 revision is: 0001954c (MIPS 34Kc) [0.00] MIPS: machine is DGN3500 - Netgear DGN3500 [0.00] Determined physical RAM map: [0.00] memory: 0400 @ (usable) [0.00] User-defined physical RAM map: [0.00] memory: 0400 @ (usable) [0.00] Initrd not found or empty - disabling initrd [0.00] Zone ranges: [0.00] Normal [mem 0x-0x03ff] [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x-0x03ff] [0.00] Initmem setup node 0 [mem 0x-0x03ff] [0.00] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes. [0.00] Primary data cache 16kB, 4-way, VIPT, no aliases, linesize 32 bytes [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256 [0.00] Kernel command line: root=/dev/mtdblock0 ip=192.168.1.1:192.168.1.15eth0:on console=ttyS1,115200 ethaddr=30:46:90 [0.00] PID hash table entries: 256 (order: -2, 1024 bytes) [0.00] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) [0.00] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) [0.00] Writing ErrCtl register=5880 [0.00] Readback ErrCtl register=5880 [0.00] Memory: 60404K/65536K available (3312K kernel code, 147K rwdata, 664K rodata, 144K init, 194K bss, 5132K reserved) [0.00] NR_IRQS:256 [0.00] CPU Clock: 333MHz [0.00] Calibrating delay loop... 221.18 BogoMIPS (lpj=442368) [0.036000] pid_max: default: 32768 minimum: 301 [0.04] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [0.044000] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [0.052000] pinctrl core: initialized pinctrl subsystem [0.056000] NET: Registered protocol family 16 [0.064000] pinctrl-xway 1e100b10.pinmux: Init done [0.068000] dma-xway 1e104100.dma: Init done - hw rev: 6, ports: 5, channels: 20 [0.076000] PCI host bridge /fpi@1000/pci@E105400 ranges: [0.08] MEM 0x1800..0x19ff [0.084000] IO 0x1ae0..0x1aff [0.088000] ath9k,eeprom ath9k_eep: failed to load eeprom address [0.10] usbcore: registered new interface driver usbfs [0.104000] usbcore: registered new interface driver hub [0.108000] usbcore: registered new device driver usb [0.112000] PCI host bridge to bus :00 [0.116000] pci_bus :00: root bus resource [mem 0x1800-0x19ff] [0.12] pci_bus :00: root bus resource [io 0x] [0.124000] pci_bus :00: No busn resource found for root bus, will use [bus 00-ff] [0.128000] pci :00:0e.0: BAR 0: assigned [mem 0x1800-0x1800] [0.132000] Switched to clocksource MIPS [0.136000] NET: Registered protocol family 2 [0.144000] TCP established hash table entries: 1024 (order: 0, 4096 bytes) [0.148000] TCP bind hash table entries: 1024 (order: 0, 4096 bytes) [0.156000] TCP: Hash tables configured (established 1024 bind 1024) [0.164000] TCP: reno registered [0.164000] UDP hash table entries: 256 (order: 0, 4096 bytes) [0.172000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) [0.18] NET: Registered protocol family 1 [0.184000] gptu: totally 6 16-bit timers/counters [0.188000] gptu: misc_register on minor 63 [0.192000] gptu: succeeded to request irq 126 [0.196000] gptu: succeeded to request irq 127 [0.20] gptu: succeeded to request irq 128 [0.204000] gptu: succeeded to request irq 129 [0.212000] gptu: succeeded to request irq 130 [0.216000] gptu: succeeded to request irq 131 [0.22] futex hash table entries: 256 (order: -1, 3072 bytes) [0.228000] squashfs: version 4.0 (2009/01/31) Phillip Lougher [0.236000] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc. [0.248000] msgmni has been set to 117 [0.252000] io scheduler noop registered [0.256000] io scheduler deadline registered (default) [0.26] 1e100c00.serial: ttyLTQ0 at MMIO 0x1e100c00 (irq = 112
Re: [OpenWrt-Devel] looking for a tl-wdr4900 tester
Hi Philipp, On 12/02/2015 12:41, Philipp Borgers wrote: I can test if you provide me with an image or an *easy* way to compile. i will mail you an initramfs and a flashable image after i had lunch Is there any testing procedure I should follow? Do we have some kind of tests I don't know of? i wish i had. best if you flash the image, see if wifi and ethernet work, thats the best we can do right now i guess :-) thanks, John Regards Philipp On Thu, Feb 12, 2015 at 12:31:07PM +0100, John Crispin wrote: Hi, just bumped the kernel for the tl-wdr4900. i don't actually have the unit. anyone around that feels like testing the images before i push the series to trunk ? John ___ 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 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Request for testing mtdsplit_uimage
On 12/02/2015 08:55, Rafał Miłecki wrote: As you could notice I've improved mtdsplit_uimage a bit: https://dev.openwrt.org/changeset/44412/ https://dev.openwrt.org/changeset/44413/ https://dev.openwrt.org/changeset/44414/ https://dev.openwrt.org/changeset/44415/ This should add support for Edimax devices, but... could also break something. Please try it and let me know if anything went wrong for you. Hi, [0.596000] m25p80 spi32766.0: mx25l12805d (16384 Kbytes) [0.60] 4 ofpart partitions found on MTD device spi32766.0 [0.604000] Creating 4 MTD partitions on spi32766.0: [0.612000] 0x-0x0001 : uboot [0.616000] 0x0001-0x0002 : uboot-env [0.624000] 0x0002-0x0003 : calibration [0.628000] 0x0005-0x00ff : firmware [0.64] mtdsplit_uimage: Buffer too small for checking Edimax header [0.644000] mtdsplit_uimage: Buffer too small for checking Edimax header [0.652000] mtdsplit_uimage: Buffer too small for checking Edimax header [0.656000] mtdsplit_uimage: Buffer too small for checking Edimax header [0.664000] mtdsplit_uimage: Buffer too small for checking Edimax header [0.672000] mtdsplit_uimage: Buffer too small for checking Edimax header [0.676000] mtdsplit_uimage: Buffer too small for checking Edimax header [0.684000] mtdsplit_uimage: Buffer too small for checking Edimax header [0.692000] mtdsplit_uimage: Buffer too small for checking Edimax header [0.696000] mtdsplit_uimage: Buffer too small for checking Edimax header [0.704000] mtdsplit_uimage: Buffer too small for checking Edimax header [0.712000] mtdsplit_uimage: Buffer too small for checking Edimax header [0.716000] mtdsplit_uimage: Buffer too small for checking Edimax header [0.724000] mtdsplit_uimage: Buffer too small for checking Edimax header [0.732000] mtdsplit_uimage: Buffer too small for checking Edimax header [0.736000] mtdsplit_uimage: Buffer too small for checking Edimax header [0.744000] mtdsplit_uimage: Buffer too small for checking Edimax header [0.752000] mtdsplit_uimage: Buffer too small for checking Edimax header [0.756000] mtdsplit_uimage: Buffer too small for checking Edimax header [0.764000] mtdsplit_uimage: Buffer too small for checking Edimax header [0.772000] mtdsplit_uimage: Buffer too small for checking Edimax header [0.776000] mtdsplit_uimage: Buffer too small for checking Edimax header [0.784000] mtdsplit_uimage: Buffer too small for checking Edimax header and about 200 more lines of same error. i can test a patch that fixes the issue if you send it to me. unit boots successfully after the msg flood. John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 3/5] generic: improve kexec support of MIPS.
Hi,
found something while merging the patches. see below ...
On 10/02/2015 13:10, Yousong Zhou wrote:
- Allow --command-line parameters of kexec-tools be parsed and used by
the kernel.
- For malta machine, mark kernel code and kernel data segments as
System RAM instead of reserved in /proc/iomem, otherwise
kexec-tools will complain that program segments in ELF kernel file
are invalid.
Signed-off-by: Yousong Zhou yszhou4t...@gmail.com
[...]
diff --git
a/target/linux/generic/patches-3.19/330-MIPS-Malta-Mark-kernel-code-and-kernel-data-segments.patch
b/target/linux/generic/patches-3.19/330-MIPS-Malta-Mark-kernel-code-and-kernel-data-segments.patch
new file mode 100644
index 000..4457d75
--- /dev/null
+++
b/target/linux/generic/patches-3.19/330-MIPS-Malta-Mark-kernel-code-and-kernel-data-segments.patch
@@ -0,0 +1,39 @@
+From 79c7301c922f5023f85805a4ba969ce55f51d0ca Mon Sep 17 00:00:00 2001
+From: Yousong Zhou yszhou4t...@gmail.com
+Date: Sat, 31 Jan 2015 15:13:12 +0800
+Subject: [PATCH 330/331] MIPS: Malta: Mark kernel code and kernel data
+ segments as BOOT_MEM_RAM.
+
+Kexec-tools requires those segments listed as System RAM in
+/proc/iomem, otherwise, an error message of Invalid memory segment
+will be emitted when trying to load the ELF kernel image.
+
+Signed-off-by: Yousong Zhou yszhou4t...@gmail.com
+---
+ arch/mips/mti-malta/malta-memory.c |9 ++---
+ 1 file changed, 2 insertions(+), 7 deletions(-)
+
+diff --git a/arch/mips/mti-malta/malta-memory.c
b/arch/mips/mti-malta/malta-memory.c
+index 8fddd2cd..1d562f0 100644
+--- a/arch/mips/mti-malta/malta-memory.c
b/arch/mips/mti-malta/malta-memory.c
+@@ -106,14 +106,9 @@ fw_memblock_t * __init fw_getmdesc(int eva)
+ mdesc[2].base = mdesc[0].base + 0x000fUL;
+ mdesc[2].size = 0x0001;
+
+-mdesc[3].type = fw_dontuse;
++mdesc[3].type = fw_free;
+ mdesc[3].base = mdesc[0].base + 0x0010UL;
+-mdesc[3].size = CPHYSADDR(PFN_ALIGN((unsigned long)_end)) -
+-0x0010UL;
+-
+-mdesc[4].type = fw_free;
+-mdesc[4].base = mdesc[0].base + CPHYSADDR(PFN_ALIGN(_end));
+-mdesc[4].size = memsize - CPHYSADDR(mdesc[4].base);
++mdesc[3].size = memsize - CPHYSADDR(mdesc[3].base);
+
will the CPHYSADDR() call work on 64bit systems ? 64bit userland is
currenty broken and disbaled in openwrt, we should however try to fix
this before we send the patch upstream to ralf
John
+ return mdesc[0];
+ }
+--
+1.7.10.4
+
diff --git
a/target/linux/generic/patches-3.19/331-MIPS-kexec-Accept-command-line-parameters-from-users.patch
b/target/linux/generic/patches-3.19/331-MIPS-kexec-Accept-command-line-parameters-from-users.patch
new file mode 100644
index 000..457b0bd
--- /dev/null
+++
b/target/linux/generic/patches-3.19/331-MIPS-kexec-Accept-command-line-parameters-from-users.patch
@@ -0,0 +1,308 @@
+From 734dd58ef3a2161e1aaeb02d47e8b86c74379161 Mon Sep 17 00:00:00 2001
+From: Yousong Zhou yszhou4t...@gmail.com
+Date: Sat, 31 Jan 2015 22:26:03 +0800
+Subject: [PATCH 331/331] MIPS: kexec: Accept command line parameters from
+ userspace.
+
+Signed-off-by: Yousong Zhou yszhou4t...@gmail.com
+---
+ arch/mips/kernel/machine_kexec.c | 153
+++-
+ arch/mips/kernel/machine_kexec.h | 20 +
+ arch/mips/kernel/relocate_kernel.S | 21 +++--
+ 3 files changed, 167 insertions(+), 27 deletions(-)
+ create mode 100644 arch/mips/kernel/machine_kexec.h
+
+diff --git a/arch/mips/kernel/machine_kexec.c
b/arch/mips/kernel/machine_kexec.c
+index 50980bf3..b9c0f75 100644
+--- a/arch/mips/kernel/machine_kexec.c
b/arch/mips/kernel/machine_kexec.c
+@@ -10,45 +10,145 @@
+ #include linux/mm.h
+ #include linux/delay.h
+
++#include asm/bootinfo.h
+ #include asm/cacheflush.h
+ #include asm/page.h
+-
+-extern const unsigned char relocate_new_kernel[];
+-extern const size_t relocate_new_kernel_size;
+-
+-extern unsigned long kexec_start_address;
+-extern unsigned long kexec_indirection_page;
++#include asm/uaccess.h
++#include machine_kexec.h
+
+ int (*_machine_kexec_prepare)(struct kimage *) = NULL;
+ void (*_machine_kexec_shutdown)(void) = NULL;
+ void (*_machine_crash_shutdown)(struct pt_regs *regs) = NULL;
++
+ #ifdef CONFIG_SMP
+ void (*relocated_kexec_smp_wait) (void *);
+ atomic_t kexec_ready_to_reboot = ATOMIC_INIT(0);
+ #endif
+
+-int
+-machine_kexec_prepare(struct kimage *kimage)
++static void machine_kexec_print_args(void)
+ {
++unsigned long argc = (int)kexec_args[0];
++int i;
++
++pr_info(kexec_args[0] (argc): %lu\n, argc);
++pr_info(kexec_args[1] (argv): %p\n, (void *)kexec_args[1]);
++pr_info(kexec_args[2] (env ): %p\n, (void *)kexec_args[2]);
++pr_info(kexec_args[3] (desc): %p\n, (void *)kexec_args[3]);
++
++for (i = 0; i argc; i++) {
++pr_info(kexec_argv[%d] = %p,
Re: [OpenWrt-Devel] Module option in Makefile?
Hi Matti, On 12/02/2015 20:34, Matti Laakso wrote: Hi, Is there a way to specify in a Makefile for a kernel module that the entry under /etc/modules.d should be created with a specific option? For example mymodule option=1 that syntax is already supported by kmodloader I looked through ModuleAutoLoad in include/kernel.mk, but couldn't figure out a way... yes, missing feature inside the makefiles. i would suggest adding a 3rd parameter to probe_module and a 4th parameter to add_module and then extend the echo call inside the 2 for loops to also print the value to the files in /etc/modules.d/ Matti Laakso ___ 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] [PATCH] hostapd: backport BSSID black/whitelists
this one is ok, just pulled it into my tree On 11/02/2015 18:42, Stefan Tomanek wrote: Dies schrieb John Crispin (blo...@openwrt.org): Any more feedback regarding both patches? still on my todo, sorry for the delay it'll take a few more days till i can go over all the hostapd patches in the queue. Nevermind, I just wanted to make sure that it didn't slide off the table :-) ___ 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] [PATCH] hostapd: Add client association log file
nak on this one as it was rejected upstream aswell
On 21/01/2015 14:59, Stefan Tomanek wrote:
This change adds the configuration option assoc_log_file to hostapd, making
it possible to specify a log file to which clients joining and parting the
corresponding BSS are written.
Every BSS can have an individual log file, and each entry written contains a
timestamp, an indicator whether the client is associating (+) or
disassociating
(-), the client and the bss hardware addresses as well as the device and SSID
identifiers of the affected network. This makes it easy to join the file with
the leases database of an DHCP server like dnsmasq.
To use a logfile with OpenWrt, simply add an assoc_log_file entry to the
wireless network:
config wifi-iface
option device 'radio1'
option network 'hotspot'
option ssid 'MyNetwork'
option mode 'ap'
option encryption 'none'
option assoc_log_file '/tmp/assoc_log-hotspot'
Signed-off-by: Stefan Tomanek stefan.tomanek+open...@wertarbyte.de
---
package/network/services/hostapd/files/netifd.sh |7 +-
...rite-client-dis-associations-to-a-logfile.patch | 231
2 files changed, 237 insertions(+), 1 deletions(-)
create mode 100644
package/network/services/hostapd/patches/720-Write-client-dis-associations-to-a-logfile.patch
diff --git a/package/network/services/hostapd/files/netifd.sh
b/package/network/services/hostapd/files/netifd.sh
index ed2a631..be94398 100644
--- a/package/network/services/hostapd/files/netifd.sh
+++ b/package/network/services/hostapd/files/netifd.sh
@@ -159,6 +159,8 @@ hostapd_common_add_bss_config() {
config_add_int mcast_rate
config_add_array basic_rate
config_add_array supported_rates
+
+ config_add_string assoc_log_file
}
hostapd_set_bss_options() {
@@ -177,7 +179,7 @@ hostapd_set_bss_options() {
wps_pushbutton wps_label ext_registrar wps_pbc_in_m1 \
wps_device_type wps_device_name wps_manufacturer wps_pin \
macfilter ssid wmm uapsd hidden short_preamble rsn_preauth \
- iapp_interface
+ iapp_interface assoc_log_file
set_default isolate 0
set_default maxassoc 0
@@ -189,6 +191,9 @@ hostapd_set_bss_options() {
set_default uapsd 1
append bss_conf ctrl_interface=/var/run/hostapd
+ if [ $assoc_log_file ]; then
+ append bss_conf assoc_log_file=$assoc_log_file $N
+ fi
if [ $isolate -gt 0 ]; then
append bss_conf ap_isolate=$isolate $N
fi
diff --git
a/package/network/services/hostapd/patches/720-Write-client-dis-associations-to-a-logfile.patch
b/package/network/services/hostapd/patches/720-Write-client-dis-associations-to-a-logfile.patch
new file mode 100644
index 000..7a87529
--- /dev/null
+++
b/package/network/services/hostapd/patches/720-Write-client-dis-associations-to-a-logfile.patch
@@ -0,0 +1,231 @@
+Write client (dis)associations to a logfile
+
+This change adds the configuration option assoc_log_file to hostapd, making
+it possible to specify a log file to which clients joining and parting the
+corresponding BSS are written.
+
+Every BSS can have an individual log file, and each entry written contains a
+timestamp, an indicator whether the client is associating (+) or
disassociating
+(-), the client and the bss hardware addresses as well as the device and SSID
+identifiers of the affected network. This makes it easy to join the file with
+the leases database of an DHCP server like dnsmasq.
+---
+ hostapd/config_file.c | 3 +++
+ hostapd/hostapd.conf | 3 +++
+ hostapd/main.c| 6 ++
+ src/ap/ap_config.c| 27 +++
+ src/ap/ap_config.h| 5 +
+ src/ap/ap_mlme.c | 26 ++
+ src/ap/hostapd.c | 4
+ src/ap/hostapd.h | 2 ++
+ 8 files changed, 76 insertions(+)
+
+diff --git a/hostapd/config_file.c b/hostapd/config_file.c
+index ddebf1f..827f9b4 100644
+--- a/hostapd/config_file.c
b/hostapd/config_file.c
+@@ -1876,6 +1876,9 @@ static int hostapd_config_fill(struct hostapd_config
*conf,
+ bss-logger_syslog = atoi(pos);
+ } else if (os_strcmp(buf, logger_stdout) == 0) {
+ bss-logger_stdout = atoi(pos);
++} else if (os_strcmp(buf, assoc_log_file) == 0) {
++os_free(bss-assoc_log_file);
++bss-assoc_log_file = os_strdup(pos);
+ } else if (os_strcmp(buf, dump_file) == 0) {
+ wpa_printf(MSG_INFO, Line %d: DEPRECATED: 'dump_file'
configuration variable is not used anymore,
+line);
+diff --git a/hostapd/hostapd.conf b/hostapd/hostapd.conf
+index 2e6f841..31b2193 100644
+--- a/hostapd/hostapd.conf
b/hostapd/hostapd.conf
+@@ -51,6 +51,9 @@ logger_syslog_level=2
+ logger_stdout=-1
+ logger_stdout_level=2
+
++# Clients joining
Re: [OpenWrt-Devel] ar71xx update to v3.18
On 16/02/2015 21:47, Paul Blazejowski wrote: On Mon, 2015-02-16 at 08:10 +0100, John Crispin wrote: On 16/02/2015 00:15, Paul Blazejowski wrote: 00 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 21.73] cfg80211: (549 KHz - 573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s) [ 21.74] cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A) [ 21.75] cfg80211: (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A) [ 22.17] ath9k ar934x_wmac: Direct firmware load for soc_wmac.eeprom failed with error -2 [ 22.18] ath: phy0: Unable to load EEPROM file soc_wmac.eeprom [ 22.19] ath9k ar934x_wmac: failed to initialize device [ 22.19] ath9k: probe of ar934x_wmac failed with error -22 [ 22.20] PCI: Enabling device :00:00.0 ( - 0002) [ 22.22] ath9k :00:00.0: Direct firmware load for pci_wmac0.eeprom failed with error -2 [ 22.23] ath: phy1: Unable to load EEPROM file pci_wmac0.eeprom [ 22.23] ath9k :00:00.0: Failed to initialize device [ 22.24] ath9k: probe of :00:00.0 failed with error -22 [ 29.76] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready probably related to this - https://dev.openwrt.org/ticket/18992 do a cat /tmp/sysinfo/* please nope sir, just replied to your other mail...but here it is again: root@router:~# cat /tmp/sysinfo/* wndr3700v4 NETGEAR WNDR3700v4 the firmware loader was not enabled in 3.18 and 3.19. r44481 fixes this. it is now working as expected on my wndr4300 i also decided to set 3.18 as the default as this was the only issue that was reported. thanks for testing, John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] ar71xx update to v3.18
On 16/02/2015 21:47, Paul Blazejowski wrote: On Mon, 2015-02-16 at 08:10 +0100, John Crispin wrote: On 16/02/2015 00:15, Paul Blazejowski wrote: 00 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 21.73] cfg80211: (549 KHz - 573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s) [ 21.74] cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A) [ 21.75] cfg80211: (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A) [ 22.17] ath9k ar934x_wmac: Direct firmware load for soc_wmac.eeprom failed with error -2 [ 22.18] ath: phy0: Unable to load EEPROM file soc_wmac.eeprom [ 22.19] ath9k ar934x_wmac: failed to initialize device [ 22.19] ath9k: probe of ar934x_wmac failed with error -22 [ 22.20] PCI: Enabling device :00:00.0 ( - 0002) [ 22.22] ath9k :00:00.0: Direct firmware load for pci_wmac0.eeprom failed with error -2 [ 22.23] ath: phy1: Unable to load EEPROM file pci_wmac0.eeprom [ 22.23] ath9k :00:00.0: Failed to initialize device [ 22.24] ath9k: probe of :00:00.0 failed with error -22 [ 29.76] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready probably related to this - https://dev.openwrt.org/ticket/18992 do a cat /tmp/sysinfo/* please nope sir, just replied to your other mail...but here it is again: root@router:~# cat /tmp/sysinfo/* wndr3700v4 NETGEAR WNDR3700v4 Hi Paul looks like the WNDR3700v4 and WNDR4300 use a eeprom hack for the mac. i have a wndr4300 in the office. will try to reproduce the bug on that tomorrow. i'll let you know if there is anything to test. Thanks for testing, John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 0/3] at91: fixes for 3.18 kernel update
On 19/02/2015 03:29, Owen Kirby wrote: The following are some fixes from testing the v3.18 update to the at91 target. In particular, I found that the drivers for the poweroff and reset controllers were missing (they were built implicitly in 3.14), which would cause the router to hang when trying to reboot. The AT91 USB gadget driver was broken from changes in clock registration in 3.18, so I have backported a patch to the at91_udc driver posted to the linux-arm-kernel mailing list a few months ago. This was tested on an AT91SAM9G20-EK and an Exegin Q5x board. Nice, i also built a few patches last night to get some of the iio stuff built, add some uci-defaults, sysupgrade, i'll hopefully get those ready during the day. Owen Kirby (3): at91: Enable power and reset controller drivers. at91: USB gadget subsystem cleanup and driver fix. at91: Add dts for Exegin Q5x boards. target/linux/at91/Makefile | 4 +- target/linux/at91/config-default | 16 +- .../at91/files/arch/arm/boot/dts/at91-q5xr5.dts| 193 + target/linux/at91/image/Makefile | 4 + target/linux/at91/modules.mk | 18 ++ .../100-ARM-at91-build-dtb-for-LMU5000.patch | 2 +- .../patches/101-ARM-at91-build-dtb-for-q5xr5.patch | 10 ++ .../200-ARM-at91-udc-clockfix-backport.patch | 82 + 8 files changed, 318 insertions(+), 11 deletions(-) create mode 100644 target/linux/at91/files/arch/arm/boot/dts/at91-q5xr5.dts create mode 100644 target/linux/at91/patches/101-ARM-at91-build-dtb-for-q5xr5.patch create mode 100644 target/linux/at91/patches/200-ARM-at91-udc-clockfix-backport.patch ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] kernel: Fix USB gadget modules for v3.18
On 19/02/2015 02:54, Owen Kirby wrote: The directory layout of the USB gadget subsystem changed between kernels 3.14 and 3.18, so the makefile for kmod-usb-eth-gadget and kmod-usb-serial-gadget need to be adjusted to match. i think this will break 3.14 builds and we should use the new syntax introduced by jow recently. Signed-off-by: Owen Kirby o...@exegin.com --- package/kernel/linux/modules/usb.mk | 28 ++-- target/linux/generic/config-3.18| 1 + 2 files changed, 15 insertions(+), 14 deletions(-) diff --git a/package/kernel/linux/modules/usb.mk b/package/kernel/linux/modules/usb.mk index 6faa437..ef58b9d 100644 --- a/package/kernel/linux/modules/usb.mk +++ b/package/kernel/linux/modules/usb.mk @@ -254,15 +254,15 @@ define KernelPackage/usb-eth-gadget CONFIG_USB_ETH_RNDIS=y \ CONFIG_USB_ETH_EEM=n DEPENDS:=+kmod-usb-gadget +kmod-usb-lib-composite -ifneq ($(wildcard $(LINUX_DIR)/drivers/usb/gadget/u_ether.ko),) +ifneq ($(wildcard $(LINUX_DIR)/drivers/usb/gadget/function/u_ether.ko),) FILES:= \ -$(LINUX_DIR)/drivers/usb/gadget/u_ether.ko \ -$(LINUX_DIR)/drivers/usb/gadget/usb_f_ecm.ko \ -$(LINUX_DIR)/drivers/usb/gadget/usb_f_ecm_subset.ko \ -$(LINUX_DIR)/drivers/usb/gadget/usb_f_rndis.ko \ -$(LINUX_DIR)/drivers/usb/gadget/g_ether.ko - ifneq ($(wildcard $(LINUX_DIR)/drivers/usb/gadget/u_rndis.ko),) -FILES+=$(LINUX_DIR)/drivers/usb/gadget/u_rndis.ko +$(LINUX_DIR)/drivers/usb/gadget/function/u_ether.ko \ +$(LINUX_DIR)/drivers/usb/gadget/function/usb_f_ecm.ko \ +$(LINUX_DIR)/drivers/usb/gadget/function/usb_f_ecm_subset.ko \ +$(LINUX_DIR)/drivers/usb/gadget/function/usb_f_rndis.ko \ +$(LINUX_DIR)/drivers/usb/gadget/legacy/g_ether.ko + ifneq ($(wildcard $(LINUX_DIR)/drivers/usb/gadget/function/u_rndis.ko),) +FILES+=$(LINUX_DIR)/drivers/usb/gadget/function/u_rndis.ko endif AUTOLOAD:=$(call AutoLoad,52,usb_f_ecm g_ether) else @@ -283,13 +283,13 @@ define KernelPackage/usb-serial-gadget TITLE:=USB Serial Gadget support KCONFIG:=CONFIG_USB_G_SERIAL DEPENDS:=+kmod-usb-gadget +kmod-usb-lib-composite -ifneq ($(wildcard $(LINUX_DIR)/drivers/usb/gadget/u_serial.ko),) +ifneq ($(wildcard $(LINUX_DIR)/drivers/usb/gadget/function/u_serial.ko),) FILES:= \ -$(LINUX_DIR)/drivers/usb/gadget/u_serial.ko \ -$(LINUX_DIR)/drivers/usb/gadget/usb_f_acm.ko \ -$(LINUX_DIR)/drivers/usb/gadget/usb_f_obex.ko \ -$(LINUX_DIR)/drivers/usb/gadget/usb_f_serial.ko \ -$(LINUX_DIR)/drivers/usb/gadget/g_serial.ko +$(LINUX_DIR)/drivers/usb/gadget/function/u_serial.ko \ +$(LINUX_DIR)/drivers/usb/gadget/function/usb_f_acm.ko \ +$(LINUX_DIR)/drivers/usb/gadget/function/usb_f_obex.ko \ +$(LINUX_DIR)/drivers/usb/gadget/function/usb_f_serial.ko \ +$(LINUX_DIR)/drivers/usb/gadget/legacy/g_serial.ko AUTOLOAD:=$(call AutoLoad,52,usb_f_acm g_serial) else FILES:=$(LINUX_DIR)/drivers/usb/gadget/g_serial.ko diff --git a/target/linux/generic/config-3.18 b/target/linux/generic/config-3.18 index e8ae342..7ad0efc 100644 --- a/target/linux/generic/config-3.18 +++ b/target/linux/generic/config-3.18 @@ -4055,6 +4055,7 @@ CONFIG_USB_EZUSB=y # CONFIG_USB_GADGET_DEBUG_FS is not set CONFIG_USB_GADGET_STORAGE_NUM_BUFFERS=2 CONFIG_USB_GADGET_VBUS_DRAW=2 +# CONFIG_USB_GADGET_XILINX is not set # CONFIG_USB_GL860 is not set # CONFIG_USB_GOKU is not set # CONFIG_USB_GPIO_VBUS is not set ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH netifd] bridge: allow enabling or disabling the multicast querier independently of IGMP snooping
Hi,
On 27/01/2015 03:49, Matthias Schiffer wrote:
In larger networks, especially big batman-adv meshes, it may be desirable to
enable IGMP snooping on every bridge without enabling the multicast querier
to specifically put the querier on a well-connected node.
This patch adds a new UCI option 'multicast_querier' for bridges which allows
this. The default is still the value of the 'igmp_snooping' option to maintain
backwards compatiblity.
per-se a good patch but its not reentrant
Signed-off-by: Matthias Schiffer mschif...@universe-factory.net
---
bridge.c | 8 +++-
system-linux.c | 2 +-
system.h | 1 +
3 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/bridge.c b/bridge.c
index f8478ad..f7dbf61 100644
--- a/bridge.c
+++ b/bridge.c
@@ -32,6 +32,7 @@ enum {
BRIDGE_ATTR_HELLO_TIME,
BRIDGE_ATTR_MAX_AGE,
BRIDGE_ATTR_BRIDGE_EMPTY,
+ BRIDGE_ATTR_MULTICAST_QUERIER,
__BRIDGE_ATTR_MAX
};
@@ -45,6 +46,7 @@ static const struct blobmsg_policy
bridge_attrs[__BRIDGE_ATTR_MAX] = {
[BRIDGE_ATTR_MAX_AGE] = { max_age, BLOBMSG_TYPE_INT32 },
[BRIDGE_ATTR_IGMP_SNOOP] = { igmp_snooping, BLOBMSG_TYPE_BOOL },
[BRIDGE_ATTR_BRIDGE_EMPTY] = { bridge_empty, BLOBMSG_TYPE_BOOL },
+ [BRIDGE_ATTR_MULTICAST_QUERIER] = { multicast_querier,
BLOBMSG_TYPE_BOOL },
};
static const struct uci_blob_param_info bridge_attr_info[__BRIDGE_ATTR_MAX]
= {
@@ -547,6 +549,7 @@ bridge_apply_settings(struct bridge_state *bst, struct
blob_attr **tb)
cfg-stp = false;
cfg-forward_delay = 2;
cfg-igmp_snoop = true;
+ cfg-multicast_querier = true;
cfg-bridge_empty = false;
cfg-priority = 0x7FFF;
@@ -560,7 +563,10 @@ bridge_apply_settings(struct bridge_state *bst, struct
blob_attr **tb)
cfg-priority = blobmsg_get_u32(cur);
if ((cur = tb[BRIDGE_ATTR_IGMP_SNOOP]))
- cfg-igmp_snoop = blobmsg_get_bool(cur);
+ cfg-multicast_querier = cfg-igmp_snoop =
blobmsg_get_bool(cur);
i make 1 ubus call and set multicast_querier=0 and then a 2nd call and
set igmp_snoop=1 this will break my prior call.
dont change the above line and then
+
+ if ((cur = tb[BRIDGE_ATTR_MULTICAST_QUERIER]))
+ cfg-multicast_querier = blobmsg_get_bool(cur);
if ((cur = tb[BRIDGE_ATTR_AGEING_TIME])) {
cfg-ageing_time = blobmsg_get_u32(cur);
diff --git a/system-linux.c b/system-linux.c
index 4737fa6..ef90880 100644
--- a/system-linux.c
+++ b/system-linux.c
@@ -772,7 +772,7 @@ int system_bridge_addbr(struct device *bridge, struct
bridge_config *cfg)
bridge-ifname, cfg-igmp_snoop ? 1 : 0);
system_set_dev_sysctl(/sys/devices/virtual/net/%s/bridge/multicast_querier,
- bridge-ifname, cfg-igmp_snoop ? 1 : 0);
+ bridge-ifname, cfg-multicast_querier ? 1 : 0);
change this to
bridge-ifname, (cfg-igmp_snoop cfg-multicast_querier) ? 1 : 0);
this should not break anything with multiple ubus calls. the default
behavior also wont change as we set cfg-multicast_querier = true;
Please make those changes to the patch and resend it.
args[0] = BRCTL_SET_BRIDGE_PRIORITY;
args[1] = cfg-priority;
diff --git a/system.h b/system.h
index 9a2326b..94e0dd9 100644
--- a/system.h
+++ b/system.h
@@ -50,6 +50,7 @@ struct bridge_config {
enum bridge_opt flags;
bool stp;
bool igmp_snoop;
+ bool multicast_querier;
unsigned short priority;
int forward_delay;
bool bridge_empty;
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH netifd] bridge: allow enabling or disabling the multicast querier independently of IGMP snooping
On 27/01/2015 03:49, Matthias Schiffer wrote:
In larger networks, especially big batman-adv meshes, it may be desirable to
enable IGMP snooping on every bridge without enabling the multicast querier
to specifically put the querier on a well-connected node.
This patch adds a new UCI option 'multicast_querier' for bridges which allows
this. The default is still the value of the 'igmp_snooping' option to maintain
backwards compatiblity.
Signed-off-by: Matthias Schiffer mschif...@universe-factory.net
---
bridge.c | 8 +++-
system-linux.c | 2 +-
system.h | 1 +
3 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/bridge.c b/bridge.c
index f8478ad..f7dbf61 100644
[...]
@@ -560,7 +563,10 @@ bridge_apply_settings(struct bridge_state *bst, struct
blob_attr **tb)
cfg-priority = blobmsg_get_u32(cur);
if ((cur = tb[BRIDGE_ATTR_IGMP_SNOOP]))
- cfg-igmp_snoop = blobmsg_get_bool(cur);
+ cfg-multicast_querier = cfg-igmp_snoop =
blobmsg_get_bool(cur);
+
+ if ((cur = tb[BRIDGE_ATTR_MULTICAST_QUERIER]))
+ cfg-multicast_querier = blobmsg_get_bool(cur);
how about this ?
if ((cur = tb[BRIDGE_ATTR_IGMP_SNOOP]))
cfg-igmp_snoop = blobmsg_get_bool(cur);
if ((cur = tb[BRIDGE_ATTR_MULTICAST_QUERIER]))
cfg-multicast_querier = blobmsg_get_bool(cur);
else
cfg-multicast_querier = cfg-igmp_snoop;
if ((cur = tb[BRIDGE_ATTR_AGEING_TIME])) {
cfg-ageing_time = blobmsg_get_u32(cur);
diff --git a/system-linux.c b/system-linux.c
index 4737fa6..ef90880 100644
--- a/system-linux.c
+++ b/system-linux.c
@@ -772,7 +772,7 @@ int system_bridge_addbr(struct device *bridge, struct
bridge_config *cfg)
bridge-ifname, cfg-igmp_snoop ? 1 : 0);
system_set_dev_sysctl(/sys/devices/virtual/net/%s/bridge/multicast_querier,
- bridge-ifname, cfg-igmp_snoop ? 1 : 0);
+ bridge-ifname, cfg-multicast_querier ? 1 : 0);
args[0] = BRCTL_SET_BRIDGE_PRIORITY;
args[1] = cfg-priority;
diff --git a/system.h b/system.h
index 9a2326b..94e0dd9 100644
--- a/system.h
+++ b/system.h
@@ -50,6 +50,7 @@ struct bridge_config {
enum bridge_opt flags;
bool stp;
bool igmp_snoop;
+ bool multicast_querier;
unsigned short priority;
int forward_delay;
bool bridge_empty;
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH netifd] bridge: allow enabling or disabling the multicast querier independently of IGMP snooping
On 28/01/2015 13:30, Matthias Schiffer wrote:
On 01/28/2015 11:54 AM, John Crispin wrote:
Hi,
On 27/01/2015 03:49, Matthias Schiffer wrote:
In larger networks, especially big batman-adv meshes, it may be
desirable to enable IGMP snooping on every bridge without
enabling the multicast querier to specifically put the querier
on a well-connected node.
This patch adds a new UCI option 'multicast_querier' for
bridges which allows this. The default is still the value of
the 'igmp_snooping' option to maintain backwards compatiblity.
per-se a good patch but its not reentrant
Signed-off-by: Matthias Schiffer
mschif...@universe-factory.net --- bridge.c | 8
+++- system-linux.c | 2 +- system.h | 1 + 3 files
changed, 9 insertions(+), 2 deletions(-)
diff --git a/bridge.c b/bridge.c index f8478ad..f7dbf61 100644
--- a/bridge.c +++ b/bridge.c @@ -32,6 +32,7 @@ enum {
BRIDGE_ATTR_HELLO_TIME, BRIDGE_ATTR_MAX_AGE,
BRIDGE_ATTR_BRIDGE_EMPTY, + BRIDGE_ATTR_MULTICAST_QUERIER,
__BRIDGE_ATTR_MAX };
@@ -45,6 +46,7 @@ static const struct blobmsg_policy
bridge_attrs[__BRIDGE_ATTR_MAX] = { [BRIDGE_ATTR_MAX_AGE] = {
max_age, BLOBMSG_TYPE_INT32 }, [BRIDGE_ATTR_IGMP_SNOOP] = {
igmp_snooping, BLOBMSG_TYPE_BOOL },
[BRIDGE_ATTR_BRIDGE_EMPTY] = { bridge_empty,
BLOBMSG_TYPE_BOOL }, + [BRIDGE_ATTR_MULTICAST_QUERIER] = {
multicast_querier, BLOBMSG_TYPE_BOOL }, };
static const struct uci_blob_param_info
bridge_attr_info[__BRIDGE_ATTR_MAX] = { @@ -547,6 +549,7 @@
bridge_apply_settings(struct bridge_state *bst, struct
blob_attr **tb) cfg-stp = false; cfg-forward_delay = 2;
cfg-igmp_snoop = true; + cfg-multicast_querier = true;
cfg-bridge_empty = false; cfg-priority = 0x7FFF;
@@ -560,7 +563,10 @@ bridge_apply_settings(struct bridge_state
*bst, struct blob_attr **tb) cfg-priority =
blobmsg_get_u32(cur);
if ((cur = tb[BRIDGE_ATTR_IGMP_SNOOP])) - cfg-igmp_snoop =
blobmsg_get_bool(cur); +cfg-multicast_querier =
cfg-igmp_snoop = blobmsg_get_bool(cur);
i make 1 ubus call and set multicast_querier=0 and then a 2nd
call and set igmp_snoop=1 this will break my prior call.
dont change the above line and then
+ + if ((cur = tb[BRIDGE_ATTR_MULTICAST_QUERIER])) +
cfg-multicast_querier = blobmsg_get_bool(cur);
if ((cur = tb[BRIDGE_ATTR_AGEING_TIME])) { cfg-ageing_time =
blobmsg_get_u32(cur); diff --git a/system-linux.c
b/system-linux.c index 4737fa6..ef90880 100644 ---
a/system-linux.c +++ b/system-linux.c @@ -772,7 +772,7 @@ int
system_bridge_addbr(struct device *bridge, struct bridge_config
*cfg) bridge-ifname, cfg-igmp_snoop ? 1 : 0);
system_set_dev_sysctl(/sys/devices/virtual/net/%s/bridge/multicast_querier,
- bridge-ifname, cfg-igmp_snoop ? 1 : 0);
+ bridge-ifname, cfg-multicast_querier ? 1 : 0);
change this to
bridge-ifname, (cfg-igmp_snoop cfg-multicast_querier) ? 1
: 0);
this should not break anything with multiple ubus calls. the
default behavior also wont change as we set
cfg-multicast_querier = true;
Please make those changes to the patch and resend it.
Wouldn't it be better to change the possible values of
multicast_querier to yes, no and unset? That way it could
always default to the igmp_snoop value when it is unset, but it
would be possible to override it in both ways.
do you call this by hand or via webui/rpc ?
args[0] = BRCTL_SET_BRIDGE_PRIORITY; args[1] = cfg-priority;
diff --git a/system.h b/system.h index 9a2326b..94e0dd9 100644
--- a/system.h +++ b/system.h @@ -50,6 +50,7 @@ struct
bridge_config { enum bridge_opt flags; bool stp; bool
igmp_snoop; + bool multicast_querier; unsigned short priority;
int forward_delay; bool bridge_empty;
___ 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] [PATCH] hostapd: backport BSSID black/whitelists
On 28/01/2015 17:56, Stefan Tomanek wrote: Dies schrieb Stefan Tomanek (stefan.tomanek+open...@wertarbyte.de): This change adds the configuration options bssid_whitelist and bssid_blacklist used to limit the AP selection of a network to a specified (finite) set or discard certain APs. Any feedback regarding this backported feature? this patch is fine, the log file one scares me though as there is no log rotate logic. ___ 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] [PATCH netifd] bridge: allow enabling or disabling the multicast querier independently of IGMP snooping
On 28/01/2015 21:31, Matthias Schiffer wrote:
On 01/28/2015 11:54 AM, John Crispin wrote:
Hi,
On 27/01/2015 03:49, Matthias Schiffer wrote:
In larger networks, especially big batman-adv meshes, it may be
desirable to enable IGMP snooping on every bridge without
enabling the multicast querier to specifically put the querier
on a well-connected node.
This patch adds a new UCI option 'multicast_querier' for
bridges which allows this. The default is still the value of
the 'igmp_snooping' option to maintain backwards compatiblity.
per-se a good patch but its not reentrant
Signed-off-by: Matthias Schiffer
mschif...@universe-factory.net --- bridge.c | 8
+++- system-linux.c | 2 +- system.h | 1 + 3 files
changed, 9 insertions(+), 2 deletions(-)
diff --git a/bridge.c b/bridge.c index f8478ad..f7dbf61 100644
--- a/bridge.c +++ b/bridge.c @@ -32,6 +32,7 @@ enum {
BRIDGE_ATTR_HELLO_TIME, BRIDGE_ATTR_MAX_AGE,
BRIDGE_ATTR_BRIDGE_EMPTY, + BRIDGE_ATTR_MULTICAST_QUERIER,
__BRIDGE_ATTR_MAX };
@@ -45,6 +46,7 @@ static const struct blobmsg_policy
bridge_attrs[__BRIDGE_ATTR_MAX] = { [BRIDGE_ATTR_MAX_AGE] = {
max_age, BLOBMSG_TYPE_INT32 }, [BRIDGE_ATTR_IGMP_SNOOP] = {
igmp_snooping, BLOBMSG_TYPE_BOOL },
[BRIDGE_ATTR_BRIDGE_EMPTY] = { bridge_empty,
BLOBMSG_TYPE_BOOL }, + [BRIDGE_ATTR_MULTICAST_QUERIER] = {
multicast_querier, BLOBMSG_TYPE_BOOL }, };
static const struct uci_blob_param_info
bridge_attr_info[__BRIDGE_ATTR_MAX] = { @@ -547,6 +549,7 @@
bridge_apply_settings(struct bridge_state *bst, struct
blob_attr **tb) cfg-stp = false; cfg-forward_delay = 2;
cfg-igmp_snoop = true; + cfg-multicast_querier = true;
cfg-bridge_empty = false; cfg-priority = 0x7FFF;
@@ -560,7 +563,10 @@ bridge_apply_settings(struct bridge_state
*bst, struct blob_attr **tb) cfg-priority =
blobmsg_get_u32(cur);
if ((cur = tb[BRIDGE_ATTR_IGMP_SNOOP])) - cfg-igmp_snoop =
blobmsg_get_bool(cur); +cfg-multicast_querier =
cfg-igmp_snoop = blobmsg_get_bool(cur);
i make 1 ubus call and set multicast_querier=0 and then a 2nd
call and set igmp_snoop=1 this will break my prior call.
dont change the above line and then
+ + if ((cur = tb[BRIDGE_ATTR_MULTICAST_QUERIER])) +
cfg-multicast_querier = blobmsg_get_bool(cur);
if ((cur = tb[BRIDGE_ATTR_AGEING_TIME])) { cfg-ageing_time =
blobmsg_get_u32(cur); diff --git a/system-linux.c
b/system-linux.c index 4737fa6..ef90880 100644 ---
a/system-linux.c +++ b/system-linux.c @@ -772,7 +772,7 @@ int
system_bridge_addbr(struct device *bridge, struct bridge_config
*cfg) bridge-ifname, cfg-igmp_snoop ? 1 : 0);
system_set_dev_sysctl(/sys/devices/virtual/net/%s/bridge/multicast_querier,
- bridge-ifname, cfg-igmp_snoop ? 1 : 0);
+ bridge-ifname, cfg-multicast_querier ? 1 : 0);
change this to
bridge-ifname, (cfg-igmp_snoop cfg-multicast_querier) ? 1
: 0);
this should not break anything with multiple ubus calls. the
default behavior also wont change as we set
cfg-multicast_querier = true;
Please make those changes to the patch and resend it.
I just re-read the whole function and noticed why I made my change
like this in the first place: all values in bridge_config are
always reset to their defaults at the top of
bridge_apply_settings() anyways, not regarding if the blobmsg
contains a new value for the options or not.
yep, i will cook up a patch tomorrow ...
Doesn't this mean that all option's values are lost in the case of
multiple ubus calls anyways? Is this intended for bridge devices,
or should this be fixed as well?
probably not
I hope I don't misunderstand how this is supposed to work, I'm not
really familar with the way dynamic reconfiguration works in
netifd...
me neither :)
args[0] = BRCTL_SET_BRIDGE_PRIORITY; args[1] = cfg-priority;
diff --git a/system.h b/system.h index 9a2326b..94e0dd9 100644
--- a/system.h +++ b/system.h @@ -50,6 +50,7 @@ struct
bridge_config { enum bridge_opt flags; bool stp; bool
igmp_snoop; + bool multicast_querier; unsigned short priority;
int forward_delay; bool bridge_empty;
___ 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] [PATCH] ramips: HooToo HT-TM02 factory image generation.
On 09/01/2015 09:16, Vittorio G (VittGam) wrote:
Hi,
What is the reason has this been rejected? Do I need to change
something?
Thanks, Vittorio
Il 28.12.2014 13:34 Vittorio G (VittGam) ha scritto:
The mkhootoofw.sh is a shell script, because official factory
images are shell scripts by themselves, and it made more sense to
me to just use a shell script on the build host to put the pieces
for the factory image file together, rather than reimplement the
wheel in C.
The hootoo_mtd_writer is a stripped-down and modified version of
mtd that includes support for flashing at an offset in the MTD.
This is needed for the HooToo, because the only usable partition
for factory flashing is the one labeled ALL, and we don't want
to flash the u-boot, u-boot-env and factory partitions too...
The hootoo_mtd_writer binary has been compiled using the
toolchain contained in the GPL tarball provided by HooToo. (It
seems to me from some tests that this is the only way to get
executables running on the stock kernel...)
In order to update the firmware from the web interface you need
to put a FAT-formatted pendrive in the router USB port, since
the original firmware needs this as temporary storage, because
the RAM is quite bloated. Then you upload the OpenWrt factory
image generated by mkhootoofw.sh, and the script kills unneeded
services and partitions to free up RAM, backs up the original
firmware on the pendrive, extracts the hootoo_mtd_writer and the
sysupgrade image, flashes the sysupgrade image and then reboots.
I've tested the resulting image on the factory firmware, and it
successfully installed OpenWrt on my HT-TM02.
Signed-off-by: Vittorio Gambaletta open...@vittgam.net
--- a/target/linux/ramips/image/Makefile +++
b/target/linux/ramips/image/Makefile @@ -317,6 +317,15 @@ fi
endef
+# Build HooToo factory images +define
BuildFirmware/HooToo8M/squashfs +$(call
BuildFirmware/Default8M/$(1),$(1),$(2),$(3)) +[ -e $(call
sysupname,$(1),$(2)) ] \ +$(SCRIPT_DIR)/download.pl
$(DL_DIR) hootoo_mtd_writer
3d72349cbb1d8e96086a084a6940304d
https://github.com/VittGam/hootoo_mtd_writer/releases/download/1.0/;
\
+mkhootoofw.sh $(DL_DIR)/hootoo_mtd_writer $(call
sysupname,$(1),$(2)) $(call imgname,$(1),$(2))-factory.bin
+endef +BuildFirmware/HooToo8M/initramfs=$(call
BuildFirmware/OF/initramfs,$(1),$(2),$(3)) +
this bit is really bad. you cannot install a binary from a random
source and use that to flash the unit. the tool needs to be compiled
during the build process
# # RT288X Profiles # @@ -480,7 +489,7 @@ endef
Image/Build/Profile/HLKRM04=$(call
BuildFirmware/HLKRM04/$(1),$(1),hlk-rm04,HLKRM04,HLK-RM02)
-Image/Build/Profile/HT-TM02=$(call
BuildFirmware/Default8M/$(1),$(1),ht-tm02,HT-TM02)
+Image/Build/Profile/HT-TM02=$(call
BuildFirmware/HooToo8M/$(1),$(1),ht-tm02,HT-TM02)
Image/Build/Profile/M3=$(call
BuildFirmware/Poray4M/$(1),$(1),m3,M3)
--- a/tools/firmware-utils/Makefile +++
b/tools/firmware-utils/Makefile @@ -76,6 +76,7 @@
define Host/Install $(INSTALL_BIN) $(HOST_BUILD_DIR)/bin/*
$(STAGING_DIR_HOST)/bin/ +$(INSTALL_BIN) src/mkhootoofw.sh
$(STAGING_DIR_HOST)/bin/ endef
$(eval $(call HostBuild)) --- /dev/null +++
b/tools/firmware-utils/src/mkhootoofw.sh @@ -0,0 +1,88 @@
+#!/bin/sh +# +# HooToo Factory Firmware Generator for OpenWrt +#
Copyright (C) 2014 Vittorio Gambaletta open...@vittgam.net +#
+# This is free software, licensed under the GNU General Public
License v2. +# See /LICENSE for more information. +# +# Sources
for the hootoo_mtd_writer utility, which must be compiled with
the GPL +# toolchain provided by HooToo for it to work on the
factory kernel, can be +# found at:
https://github.com/VittGam/hootoo_mtd_writer +# +# Usage:
mkhootoofw.sh path-to-hootoo_mtd_writer
path-to-openwrt-sysupgrade.bin path-to-openwrt-factory.bin +# +
+# Write the shellscript stub +cat ${3}.tmp 'EOF' +SKIP=57
+ +echo Checking firmware checksum... +[ $CRCSUM != `sed
'1,3d' $0 | cksum | sed -e 's/ /Z/' -e 's/ /Z/' | cut -dZ -f1`
] { +echo Firmware checksum error! +exit 1 +} +echo
Firmware checksum OK + +echo Killing unneeded services...
+killall -9 fileserv ioos upnpd led_control owndns ownhttp
vstddns udhcpc udhcpd udevd minidlna smbd nmbd +sleep 1 + +echo
Unmounting unneeded mounts... +umount /etc +umount /boot/tmp
+umount /usr/local/samba/var +umount /opt +umount /var + +echo
Backing up original firmware...
+BKPDIRBASE=/data/UsbDisk1/Volume1/OpenWrt-HooToo-Backup-`sed
's/:/-/g' /sys/class/net/ra0/address`- +BKPDIRNUM=1
+BKPDIR=${BKPDIRBASE}${BKPDIRNUM} +while [ -e $BKPDIR ]; do +
BKPDIRNUM=$((${BKPDIRNUM}+1)) +
BKPDIR=${BKPDIRBASE}${BKPDIRNUM} +done +echo Backup directory:
${BKPDIR} + +mkdir $BKPDIR +cp /dev/mtdblock* ${BKPDIR}/ ||
{ +echo Backup failed! +exit 1 +} +sync echo 3
/proc/sys/vm/drop_caches +echo Backup OK + +echo Extracting
OpenWrt
Re: [OpenWrt-Devel] au1xxx v3.18
On 09/02/2015 21:56, Bruno Randolf wrote: [0.00] Kernel command line: root=/dev/mtdblock/0 console=ttyS0,115200 root=/dev/mtdblock0 rootfstype=squashfs,jffs2 what does that look like on 3.14 ? on mediatek the bug was that the wrong cmdline was used, causing a bad base_baud to be set in the 8250 driver ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] @44360 scripts
Hi,
the subject is wonky
On 09/02/2015 15:55, . wrote:
From d1f104b6fe94507a80b85943fd1d4ba895f4e0a0 Mon Sep 17 00:00:00
2001 From: Detlef Schmitt blubb...@nurfuerspam.de
not sure what to think of this email addr
Date: Mon, 9 Feb 2015 15:35:28 +0100 Subject: [PATCH 2/2]
daemon.notice netifd: wan (4235): udhcpc: option -h NAME is
deprecated, use -x hostname:NAME daemon.notice netifd: wan (4235):
udhcpc (v1.22.1) started
replaced the deprecated option -h HOSTNAME for udhcpc with the
new one
the text is at least formatted in a very messy way and it seems to
have part of an error and then part of a sentence
John
--- package/network/config/netifd/files/lib/netifd/proto/dhcp.sh |
2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/package/network/config/netifd/files/lib/netifd/proto/dhcp.sh
b/package/network/config/netifd/files/lib/netifd/proto/dhcp.sh
index d4c483d..bde60a2 100755 ---
a/package/network/config/netifd/files/lib/netifd/proto/dhcp.sh +++
b/package/network/config/netifd/files/lib/netifd/proto/dhcp.sh @@
-52,7 +52,7 @@ proto_dhcp_setup() { -s /lib/netifd/dhcp.script \ -f
-t 0 -i $iface \ ${ipaddr:+-r $ipaddr} \ -
${hostname:+-H $hostname} \ + ${hostname:+-x
hostname:$hostname} \ ${vendorid:+-V $vendorid} \ $clientid
$broadcast $dhcpopts }
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] au1xxx v3.18
On 09/02/2015 21:56, Bruno Randolf wrote: Hi John, Something's wrong with the serial, but I was able to login via Ethernet. I did not verify PCI yet, as I only have a PCI adapter on the cubes which are in use. Serial log below: bruno On 02/09/2015 12:26 PM, John Crispin wrote: Hi Bruno, (or anyone else that has the hw at hand) i pushed the v3.18 support. could you test it please and let me know if it is working ? you need to set 3.18 in the Makefile, it is still at 3.14. [0.00] Linux version 3.18.6 (br1@shiva) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r44360) ) #1 Mon Feb 9 20:19:34 WET 2015 [0.00] bootconsole [early0] enabled [0.00] CPU0 revision is: 01030202 (Au1500) [0.00] 4G Systems MTX-1 Board [0.00] Determined physical RAM map: [0.00] memory: 0400 @ (usable) [0.00] Initrd not found or empty - disabling initrd [0.00] Zone ranges: [0.00] Normal [mem 0x-0x03ff] [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x-0x03ff] [0.00] Initmem setup node 0 [mem 0x-0x03ff] [0.00] Primary instruction cache 16kB, VIPT, 4-way, linesize 32 bytes. [0.00] Primary data cache 16kB, 4-way, VIPT, no aliases, linesize 32 bytes [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256 [0.00] Kernel command line: root=/dev/mtdblock/0 console=ttyS0,115200 root=/dev/mtdblock0 rootfstype=squashfs,jffs2 [0.00] PID hash table entries: 256 (order: -2, 1024 bytes) [0.00] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) [0.00] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) [0.00] Memory: 60556K/65536K available (2412K kernel code, 95K rwdata, 476K rodata, 144K init, 195K bss, 4980K reserved) [0.00] NR_IRQS:128 [0.00] Alchemy clocksource installed [0.004000] Calibrating delay loop... 395.26 BogoMIPS (lpj=790528) [0.04] pid_max: default: 32768 minimum: 301 [0.044000] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [0.048000] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [0.056000] NET: Registered protocol family 16 [0.06] Alchemy clocktree installed [0.064000] Alchemy DMA initialized [0.068000] alchemy-pci alchemy-pci.0: PCI controller at 32 MHz [0.10] PCI host bridge to bus :00 [0.104000] pci_bus :00: root bus resource [mem 0x4000-0x4fff] [0.108000] pci_bus :00: root bus resource [io 0x1000-0x] [0.112000] pci_bus :00: No busn resource found for root bus, will use [bus 00-ff] [0.116000] Switched to clocksource alchemy-counter1 [0.124000] NET: Registered protocol family 2 [0.128000] TCP established hash table entries: 1024 (order: 0, 4096 bytes) [0.136000] TCP bind hash table entries: 1024 (order: 0, 4096 bytes) [0.144000] TCP: Hash tables configured (established 1024 bind 1024) [0.152000] TCP: reno registered [0.156000] UDP hash table entries: 256 (order: 0, 4096 bytes) [0.16] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) [0.168000] NET: Registered protocol family 1 [0.176000] futex hash table entries: 256 (order: -1, 3072 bytes) [0.188000] squashfs: version 4.0 (2009/01/31) Phillip Lougher [0.192000] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc. [0.216000] msgmni has been set to 118 [0.224000] io scheduler noop registered [0.228000] io scheduler deadline registered (default) [0.232000] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [0.24] console [ttyS0] disabled [0.244000] serial8250.8: ttyS0 at MMIO 0x1110 (irq = 8, base_baud = 18187500) is a 16550A ��� ok, bad baudrate. i fixed this on mediatek in the upstream kernel for 3.16 or 17. need to think of what the issue was. it was easy to fix though. With 14.07 the last part looks like this: [0.18] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [0.192000] serial8250.8: ttyS0 at MMIO 0x1110 (irq = 8) is a 16550A [0.20] console [ttyS0] enabled, bootconsole disabled [0.20] console [ttyS0] enabled, bootconsole disabled [0.216000] serial8250.8: ttyS1 at MMIO 0x1140 (irq = 11) is a 16550A ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] raspberry pi v3.19
On 09/02/2015 18:12, Florian Fainelli wrote: Could you share the boot log to see if there is anything obvious? Hi, without uart i get no bootlog. i just see the coloured palette on the hdmi. but the uart stays quiet. i am starting to wonder if the uart is dead. John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lantiq v3.18
there is no ar9 target. can you give me your .config file please ? On 09/02/2015 18:30, Daniel Gimpelevich wrote: On Mon, 2015-02-09 at 13:30 +0100, John Crispin wrote: Hi, i bumped the lantiq support to v3.18 and tested it on 6 different boards. I have not tested vdsl support due to lack of a vdsl line. could someone please do so. @antii: can you rebase/resnd the dwc2 series ? it does not apply to the v3.18 patches John Build now fails for AR9. Relevant log: scripts/kconfig/conf --silentoldconfig Kconfig net/sched/Kconfig:43: warning: menuconfig statement without prompt * * Restart config... * * * Staging drivers * Staging drivers (STAGING) [Y/n/?] y Data acquisition support (comedi) (COMEDI) [N/m/?] n RealTek RTL8192U Wireless LAN NIC driver (RTL8192U) [N/m/?] n Support for rtllib wireless devices (RTLLIB) [N/m/?] n RealTek RTL8712U (RTL8192SU) Wireless LAN NIC driver (R8712U) [N/m/y/?] n Realtek RTL8188EU Wireless LAN NIC driver (R8188EU) [N/m/y/?] n Realtek RTL8723AU Wireless LAN NIC driver (R8723AU) [N/m/?] (NEW) aborted! ___ 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] lantiq v3.18
On 09/02/2015 18:30, Daniel Gimpelevich wrote: On Mon, 2015-02-09 at 13:30 +0100, John Crispin wrote: Hi, i bumped the lantiq support to v3.18 and tested it on 6 different boards. I have not tested vdsl support due to lack of a vdsl line. could someone please do so. @antii: can you rebase/resnd the dwc2 series ? it does not apply to the v3.18 patches John Build now fails for AR9. Relevant log: scripts/kconfig/conf --silentoldconfig Kconfig net/sched/Kconfig:43: warning: menuconfig statement without prompt * * Restart config... * * * Staging drivers * Staging drivers (STAGING) [Y/n/?] y Data acquisition support (comedi) (COMEDI) [N/m/?] n RealTek RTL8192U Wireless LAN NIC driver (RTL8192U) [N/m/?] n Support for rtllib wireless devices (RTLLIB) [N/m/?] n RealTek RTL8712U (RTL8192SU) Wireless LAN NIC driver (R8712U) [N/m/y/?] n Realtek RTL8188EU Wireless LAN NIC driver (R8188EU) [N/m/y/?] n Realtek RTL8723AU Wireless LAN NIC driver (R8723AU) [N/m/?] (NEW) aborted! try r44366 or newer please ___ 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] lantiq v3.18
look at /proc/cpuinfo please and tell us how many bogomips are reported On 13/02/2015 19:32, Daniel Gimpelevich wrote: On Fri, 13 Feb 2015 09:23:16 +0100, Sylwester Petela wrote: PCI works, I have one more issue (present from 3.14 kernel) , unit will hang (without any errors in console output) when trying to reboot from cli/luci, but only when dsl_control is started at boot, without attached line or with dsl_control excluded from running on boot, everything works ok, even trying to stop dsl_control before reboot doesn't help. I'm thinking that dts for P-2812HNU has something to do with it, but I cannot trace it. I'm not sure whether this is the same issue, but when I boot with the DSL connected, it takes another five minutes after the console shows the line procd: - init complete - before the DSL actually connects, and if I type time /etc/init.d/dsl_control status after it connects and walk away, it tells me it took twenty minutes to complete. This makes LuCI unusable, because it tries to query the status every few seconds, exhausting the RAM, which causes a reboot. This problem did not exist on 3.14, so I suspect it may be related to the kernel config. I might not be able to test anything new till the middle of next week. ___ 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] lantiq v3.18
ok, i think the spi clock is just really slow
m25p80@0 {
#address-cells = 1;
#size-cells = 1;
compatible = s25fl129p0;
reg = 0 0;
linux,modalias = m25p80, mx25l3205d;
spi-max-frequency = 100;
try increasing it to 10 or 20 mhz. running the flash at 1 Mhz explains
why it takes a week to boot and do anything useful. even with the bus
being bitbanged it should be possible to go beyond 1mhz
On 13/02/2015 20:45, Daniel Gimpelevich wrote:
On Fri, 13 Feb 2015 19:43:32 +0100, John Crispin wrote:
look at /proc/cpuinfo please and tell us how many bogomips are reported
system type : AR9 rev 1.2
machine : DGN3500 - Netgear DGN3500
processor : 0
cpu model : MIPS 34Kc V4.12
BogoMIPS: 221.18
wait instruction: yes
microsecond timers : yes
tlb_entries : 16
extra interrupt vector : yes
hardware watchpoint : yes, count: 4, address/irw mask: [0x0ffc,
0x0ffc, 0x0ffb, 0x0ffb]
isa : mips1 mips2 mips32r1 mips32r2
ASEs implemented: mips16 dsp mt
shadow register sets: 1
kscratch registers : 0
package : 0
core: 0
VCED exceptions : not available
VCEI exceptions : not available
___
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] [PATCH] ramips: add back missing M25P80 flash driver
On 14/02/2015 17:26, Russell Senior wrote: fixes bug introduced by r44349 which prevents, e.g. AsiaRF AWM002 from booting. oops my bad, the config files currently used are the ones for 3.18 i will push a different patch that adds the old files in a sec Signed-off-by: Russell Senior russ...@personaltelco.net --- target/linux/ramips/rt305x/config-default | 1 + 1 file changed, 1 insertion(+) diff --git a/target/linux/ramips/rt305x/config-default b/target/linux/ramips/rt305x/config-default index 8478b6d..5ae0b1f 100644 --- a/target/linux/ramips/rt305x/config-default +++ b/target/linux/ramips/rt305x/config-default @@ -109,6 +109,7 @@ CONFIG_MIPS_L1_CACHE_SHIFT=5 CONFIG_MODULES_USE_ELF_REL=y # CONFIG_MTD_CFI_INTELEXT is not set CONFIG_MTD_CMDLINE_PARTS=y +CONFIG_MTD_M25P80=y CONFIG_MTD_PHYSMAP=y CONFIG_MTD_SPLIT_FIRMWARE=y CONFIG_MTD_SPLIT_SUPPORT=y ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] enabling seccomp by default in kernel
On 15/02/2015 00:31, David Lang wrote: On Sat, 14 Feb 2015, Nikos Mavrogiannopoulos wrote: Hello, I've added libseccomp into packages. That library allows programs to easily restrict the system calls they are allowed to use. In turn that uses the kernel's seccomp filter. That's one of the most reliable ways to restrict/sandbox processes into specific tasks which cannot be overriden even in the event of code injection. I've also enabled the ocserv package to use seccomp if configured to, but in order for that protection to become meaningful for other programs to use as well, it would also need the default kernel option to enable seccomp filter. It needs the kernel support to use the seccomp filter, but why is this so critical that it must be enabled by default? David Lang the snapshots will now have libseccomp but the kernels built wont have the feature enabled. this means the lib is useless without building your own kernel. i guess nikos is trying to solve this problem. John ___ 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] [PATCH 1/4] ipq806x: update target to v3.18
i folded all 4 patches into 1 prior to the commit ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ar71xx:Add QCA953X version2 SoC support
Hi, late reply, see below On 01/02/2015 13:48, Chuanhong Guo wrote: From: 郭传鈜 gch981...@gmail.com This patch adds support for QCA953Xv2 SoC. I got this patch from QSDK here: https://www.codeaurora.org/cgit/quic/qsdk/oss/system/openwrt/tree/target/linux/ar71xx/patches-3.3/627-QCA-MIPS-ath79-add-QCA9531-version2-support.patch?h=release/banana_10.4_c1 This patch is tested on QCA9533-BL3A and everything seems to be OK. Signed-off-by: 郭传鈜 gch981...@gmail.com --- ...6-MIPS-ath79-add-QCA953X-version2-support.patch | 41 ++ 1 file changed, 41 insertions(+) create mode 100644 target/linux/ar71xx/patches-3.14/736-MIPS-ath79-add-QCA953X-version2-support.patch diff --git a/target/linux/ar71xx/patches-3.14/736-MIPS-ath79-add-QCA953X-version2-support.patch b/target/linux/ar71xx/patches-3.14/736-MIPS-ath79-add-QCA953X-version2-support.patch [...] +--- a/arch/mips/ath79/setup.c b/arch/mips/ath79/setup.c +@@ -152,10 +152,13 @@ + rev = id AR934X_REV_ID_REVISION_MASK; + break; + +-case REV_ID_MAJOR_QCA9533: ++case REV_ID_MAJOR_QCA9533_V1: ++case REV_ID_MAJOR_QCA9533_V2: + ath79_soc = ATH79_SOC_QCA9533; + chip = 9533; + rev = id QCA953X_REV_ID_REVISION_MASK; ++if (major == REV_ID_MAJOR_QCA9533_V2) ++rev = 2; i wanted to confirm this first and it turns out it is almost correct there is one case missing. after confirming with mathieu (thanks!) the following ids should be used 0x140 – v1.0 0x141 – v1.1 0x160 – v2.0 i will rework your patch in the morning and add both of the new ids. John + break; + + case REV_ID_MAJOR_QCA9556: +--- a/arch/mips/include/asm/mach-ath79/ar71xx_regs.h b/arch/mips/include/asm/mach-ath79/ar71xx_regs.h +@@ -709,7 +709,8 @@ + #define REV_ID_MAJOR_AR9341 0x0120 + #define REV_ID_MAJOR_AR9342 0x1120 + #define REV_ID_MAJOR_AR9344 0x2120 +-#define REV_ID_MAJOR_QCA95330x0140 ++#define REV_ID_MAJOR_QCA9533_V1 0x0140 ++#define REV_ID_MAJOR_QCA9533_V2 0x0160 + #define REV_ID_MAJOR_QCA95560x0130 + #define REV_ID_MAJOR_QCA95580x1130 + #define REV_ID_MAJOR_TP9343 0x0150 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lantiq v3.18
On 10/02/2015 19:35, Joerg Hollmann wrote: Hello Daniel, could it be, that the definition of the kernel partition in the dts file of your device ist too small? i think the problem is that spi-gpio is either not loaded or loaded too late. i wont have time to look at it till friday though. I have seen similar error messages on the builds for the VG3503J. there is a kernel part defined in the dts ? the mtdsplit should handle it for your. i'll look at that aswell, only tested a initramfs on the VG3503J John Regards, Joerg On 02/10/2015 10:40 AM, Daniel Gimpelevich wrote: Is there a patchset I could try? On Mon, 2015-02-09 at 12:44 -0800, Daniel Gimpelevich wrote: On Mon, 2015-02-09 at 21:27 +0100, John Crispin wrote: bootlog please On 09/02/2015 21:25, Daniel Gimpelevich wrote: On Mon, 2015-02-09 at 19:18 +0100, John Crispin wrote: try r44366 or newer please SPI flash is not detected, bricking the device. [0.00] Linux version 3.18.6 (danielg4@chimera) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r43982) ) #3 Mon Feb 9 115 [0.00] SoC: AR9 rev 1.2 [0.00] bootconsole [early0] enabled [0.00] CPU0 revision is: 0001954c (MIPS 34Kc) [0.00] MIPS: machine is DGN3500 - Netgear DGN3500 [0.00] Determined physical RAM map: [ 0.00] memory: 0400 @ (usable) [0.00] User-defined physical RAM map: [0.00] memory: 0400 @ (usable) [0.00] Initrd not found or empty - disabling initrd [0.00] Zone ranges: [0.00] Normal [mem 0x-0x03ff] [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x-0x03ff] [ 0.00] Initmem setup node 0 [mem 0x-0x03ff] [ 0.00] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes. [0.00] Primary data cache 16kB, 4-way, VIPT, no aliases, linesize 32 bytes [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256 [0.00] Kernel command line: root=/dev/mtdblock0 ip=192.168.1.1:192.168.1.15eth0:on console=ttyS1,115200 ethaddr=30:46:90 [0.00] PID hash table entries: 256 (order: -2, 1024 bytes) [0.00] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) [0.00] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) [ 0.00] Writing ErrCtl register=5880 [0.00] Readback ErrCtl register=5880 [0.00] Memory: 60404K/65536K available (3312K kernel code, 147K rwdata, 664K rodata, 144K init, 194K bss, 5132K reserved) [0.00] NR_IRQS:256 [0.00] CPU Clock: 333MHz [0.00] Calibrating delay loop... 221.18 BogoMIPS (lpj=442368) [ 0.036000] pid_max: default: 32768 minimum: 301 [0.04] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.044000] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [0.052000] pinctrl core: initialized pinctrl subsystem [0.056000] NET: Registered protocol family 16 [ 0.064000] pinctrl-xway 1e100b10.pinmux: Init done [ 0.068000] dma-xway 1e104100.dma: Init done - hw rev: 6, ports: 5, channels: 20 [0.076000] PCI host bridge /fpi@1000/pci@E105400 ranges: [0.08] MEM 0x1800..0x19ff [0.084000] IO 0x1ae0..0x1aff [0.088000] ath9k,eeprom ath9k_eep: failed to load eeprom address [ 0.10] usbcore: registered new interface driver usbfs [ 0.104000] usbcore: registered new interface driver hub [ 0.108000] usbcore: registered new device driver usb [ 0.112000] PCI host bridge to bus :00 [0.116000] pci_bus :00: root bus resource [mem 0x1800-0x19ff] [ 0.12] pci_bus :00: root bus resource [io 0x] [ 0.124000] pci_bus :00: No busn resource found for root bus, will use [bus 00-ff] [0.128000] pci :00:0e.0: BAR 0: assigned [mem 0x1800-0x1800] [0.132000] Switched to clocksource MIPS [0.136000] NET: Registered protocol family 2 [0.144000] TCP established hash table entries: 1024 (order: 0, 4096 bytes) [0.148000] TCP bind hash table entries: 1024 (order: 0, 4096 bytes) [0.156000] TCP: Hash tables configured (established 1024 bind 1024) [0.164000] TCP: reno registered [0.164000] UDP hash table entries: 256 (order: 0, 4096 bytes) [0.172000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) [0.18] NET: Registered protocol family 1 [0.184000] gptu: totally 6 16-bit timers/counters [0.188000] gptu: misc_register on minor 63 [0.192000] gptu: succeeded to request irq 126 [ 0.196000] gptu: succeeded to request irq 127 [0.20] gptu: succeeded to request irq 128 [0.204000] gptu: succeeded to request irq 129 [0.212000] gptu: succeeded to request irq 130 [0.216000] gptu: succeeded to request irq 131
Re: [OpenWrt-Devel] raspberry pi v3.19
On 10/02/2015 20:16, Álvaro Fernández Rojas wrote: It's based on https://github.com/raspberrypi/linux/tree/rpi-3.18.y-rebase oh goddie, i wonder what i did wrong when trying the same ones. BTW, I'm also trying to get the Raspberry Pi 2 working before sending the patches. amazon wont ship mine till the 13th, so i wont be able to play with it till start of next week. patches welcome, as always ;) El 10/02/2015 a las 20:02, John Crispin escribió: On 10/02/2015 19:53, Álvaro Fernández Rojas wrote: Okay, it's working now: http://files.noltari.es/openwrt/bcm2708/bcm2708_3-18_log.txt Patches: http://files.noltari.es/openwrt/bcm2708/brcm2708_3-18.tgz :-) one less todo off my list. just merged it locally and started a test build. which patches is this series based on ? i tried to make the ~150 patches from the rpi repo on github work in the hope that they would also make the rpi2 work with openwrt. thanks, John ___ 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 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] raspberry pi v3.19
On 10/02/2015 19:53, Álvaro Fernández Rojas wrote: Okay, it's working now: http://files.noltari.es/openwrt/bcm2708/bcm2708_3-18_log.txt Patches: http://files.noltari.es/openwrt/bcm2708/brcm2708_3-18.tgz :-) one less todo off my list. just merged it locally and started a test build. which patches is this series based on ? i tried to make the ~150 patches from the rpi repo on github work in the hope that they would also make the rpi2 work with openwrt. thanks, John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 3/3] sunxi: add support for Linux 3.19
On 10/02/2015 22:42, Rafał Miłecki wrote: On 10 February 2015 at 15:09, Daniel Golle dan...@makrotopia.org wrote: simple-framebuffer now works on the A20. I'm really not sure about other developers opinion (will be happy to hear it), but I guess you could try to generate a patch using git and git format-patch -C That would allow ppl/developers to review changes you had to made. zoltan maintains the sunxi target. he might already have done work on this and might have some updates or whatever that he plans to incorporate. bumping a kernel maintained actively always has the risk of duplicating work and / or doing superfluous work ___ 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] lantiq v3.18
On 10/02/2015 21:40, Sylwester Petela wrote: Got problem with pci on P-2812HNU-F1, it was simply not initialized (missing whole pci part in bootlog), I've added target/linux/lantiq/xrx200/config-3.18 from config-3.14(changed only UBI_GLUEBI to UBI_BLOCK), and pci went back, not sure how build config is generated but that solved my problem. VDSL Annex A is working atm, if anything regarding stability will happen I'll post an update. Best Regards / Pozdrawiam Sylwester Petela / ScApi ok i only tested the pcie on the 8970, will diff the 2 config tomorrow to figure out what the problem is has anyone got a line that uses ptm ? i had to make an api update to the ptm driver to get it to compile W dniu 2015-02-10 o 19:39, John Crispin pisze: On 10/02/2015 19:35, Joerg Hollmann wrote: Hello Daniel, could it be, that the definition of the kernel partition in the dts file of your device ist too small? i think the problem is that spi-gpio is either not loaded or loaded too late. i wont have time to look at it till friday though. I have seen similar error messages on the builds for the VG3503J. there is a kernel part defined in the dts ? the mtdsplit should handle it for your. i'll look at that aswell, only tested a initramfs on the VG3503J John Regards, Joerg On 02/10/2015 10:40 AM, Daniel Gimpelevich wrote: Is there a patchset I could try? On Mon, 2015-02-09 at 12:44 -0800, Daniel Gimpelevich wrote: On Mon, 2015-02-09 at 21:27 +0100, John Crispin wrote: bootlog please On 09/02/2015 21:25, Daniel Gimpelevich wrote: On Mon, 2015-02-09 at 19:18 +0100, John Crispin wrote: try r44366 or newer please SPI flash is not detected, bricking the device. [0.00] Linux version 3.18.6 (danielg4@chimera) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r43982) ) #3 Mon Feb 9 115 [0.00] SoC: AR9 rev 1.2 [0.00] bootconsole [early0] enabled [0.00] CPU0 revision is: 0001954c (MIPS 34Kc) [0.00] MIPS: machine is DGN3500 - Netgear DGN3500 [0.00] Determined physical RAM map: [ 0.00] memory: 0400 @ (usable) [0.00] User-defined physical RAM map: [0.00] memory: 0400 @ (usable) [0.00] Initrd not found or empty - disabling initrd [0.00] Zone ranges: [0.00] Normal [mem 0x-0x03ff] [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x-0x03ff] [ 0.00] Initmem setup node 0 [mem 0x-0x03ff] [ 0.00] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes. [0.00] Primary data cache 16kB, 4-way, VIPT, no aliases, linesize 32 bytes [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256 [0.00] Kernel command line: root=/dev/mtdblock0 ip=192.168.1.1:192.168.1.15eth0:on console=ttyS1,115200 ethaddr=30:46:90 [0.00] PID hash table entries: 256 (order: -2, 1024 bytes) [0.00] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) [0.00] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) [ 0.00] Writing ErrCtl register=5880 [0.00] Readback ErrCtl register=5880 [0.00] Memory: 60404K/65536K available (3312K kernel code, 147K rwdata, 664K rodata, 144K init, 194K bss, 5132K reserved) [0.00] NR_IRQS:256 [0.00] CPU Clock: 333MHz [0.00] Calibrating delay loop... 221.18 BogoMIPS (lpj=442368) [ 0.036000] pid_max: default: 32768 minimum: 301 [0.04] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.044000] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [0.052000] pinctrl core: initialized pinctrl subsystem [0.056000] NET: Registered protocol family 16 [ 0.064000] pinctrl-xway 1e100b10.pinmux: Init done [ 0.068000] dma-xway 1e104100.dma: Init done - hw rev: 6, ports: 5, channels: 20 [0.076000] PCI host bridge /fpi@1000/pci@E105400 ranges: [0.08] MEM 0x1800..0x19ff [0.084000] IO 0x1ae0..0x1aff [0.088000] ath9k,eeprom ath9k_eep: failed to load eeprom address [ 0.10] usbcore: registered new interface driver usbfs [ 0.104000] usbcore: registered new interface driver hub [ 0.108000] usbcore: registered new device driver usb [ 0.112000] PCI host bridge to bus :00 [0.116000] pci_bus :00: root bus resource [mem 0x1800-0x19ff] [ 0.12] pci_bus :00: root bus resource [io 0x] [ 0.124000] pci_bus :00: No busn resource found for root bus, will use [bus 00-ff] [0.128000] pci :00:0e.0: BAR 0: assigned [mem 0x1800-0x1800] [0.132000] Switched to clocksource MIPS [0.136000] NET: Registered protocol family 2 [0.144000] TCP established hash table entries: 1024 (order: 0, 4096 bytes) [0.148000] TCP
Re: [OpenWrt-Devel] [PATCH 1/4] ipq806x: update target to v3.18
[...] On 11/02/2015 03:38, Mathieu Olivari wrote: .../0179-spi-qup-Add-DMA-capabilities.patch| 490 -- ...ARM-dts-Add-ADM-DMA-nodes-and-SPI-linkage.patch | 83 - ...1-mtd-nand-qcom-Align-clk-and-reset-names.patch | 41 - ...m-Kconfig-Make-drivers-mutually-exclusive.patch | 47 - 180 files changed, 370 insertions(+), 44215 deletions(-) ;-) if it could always be like this ... ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 2/3] brcm2708: add Raspberry Pi 2 support
On 11/02/2015 12:42, Álvaro Fernández Rojas wrote: From popcornmix: https://github.com/raspberrypi/linux/issues/22 Technically 2708 is the family, and 2835 is a specific implementation. We now know that 2835 is the only implementation in the family that can run linux, (and there won't be new models of this family), so it probably doesn't matter which model is used, although it should be consistent. good to know If we wanted to use BCM2835, it would make sense also to use BCM2836. So it would be BOARDNAME:=Broadcom BCM2708/BCM2835/BCM2709/BCM2836, which is kinda long :$. I suggest either using BCM2708/BCM2709 or BCM2835/BCM2836, but using both seems weird, at least for me. patch looks fine in that case i am already building a test tree ;) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 2/3] brcm2708: add Raspberry Pi 2 support
On 11/02/2015 12:33, Álvaro Fernández Rojas wrote: -BOARDNAME:=Broadcom BCM2708/BCM2835 should this not be +BOARDNAME:=Broadcom BCM2708/BCM2835/BCM2709 i think BCM2835 is used on one of the B+ variants John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 3/3] sunxi: add support for Linux 3.19
On 11/02/2015 00:13, Daniel Golle wrote: Is there anything wrong with that? Or did anyone feel offended by that? no just pointing out that this might lead to the work not being used, which ended up being the case. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lantiq v3.18
bootlog please On 09/02/2015 21:25, Daniel Gimpelevich wrote: On Mon, 2015-02-09 at 19:18 +0100, John Crispin wrote: try r44366 or newer please SPI flash is not detected, bricking the device. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ar71xx: ZyXEL NBG6716 leds improvement ( correction - second attempt )
the 3 patches sent are white space broken and patchwork failed to pick them up. i have manually applied this patch, but please use git for sending patches in future. On 06/02/2015 12:27, Marcin Mikołajczak wrote: This patch fixes LEDs in ZyXEL NBG6716 - POWER LED was missing - USB LEDs incorrect order Signed-off-by: Marcin Mikolajczak gr4ffy at gmail.com --- Sorry, but this is my first patch for OpenWrt - previous one was splitted in two half. Index: trunk/target/linux/ar71xx/base-files/etc/diag.sh === --- trunk/target/linux/ar71xx/base-files/etc/diag.sh(wersja 44288) +++ trunk/target/linux/ar71xx/base-files/etc/diag.sh(kopia robocza) @@ -130,7 +130,7 @@ status_led=nbg460n:green:power ;; nbg6716) - status_led=nbg6716:white:power + status_led=zyxel:white:power ;; om2p | \ om2pv2 | \ Index: trunk/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds === --- trunk/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds (wersja 44288) +++ trunk/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds (kopia robocza) @@ -215,8 +215,8 @@ ucidef_set_led_netdev wan WAN zyxel:white:internet eth1 ucidef_set_led_wlan wlan WLAN zyxel:white:wifi2g phy1tpt ucidef_set_led_wlan wlan5 WLAN5 zyxel:white:wifi5g phy0tpt - ucidef_set_led_usbdev usb1 USB1 zyxel:white:usb0 1-1 - ucidef_set_led_usbdev usb2 USB2 zyxel:white:usb1 2-1 + ucidef_set_led_usbdev usb1 USB1 zyxel:white:usb0 2-1 + ucidef_set_led_usbdev usb2 USB2 zyxel:white:usb1 1-1 ;; om2p | \ ___ 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
[OpenWrt-Devel] raspberry pi v3.19
Hi, i synced our rpi port with the upstream tree on github. it boots and i can see the coloured palette test pic on the hdmi, however ethernet fails to come up. i attached a uart just to find out that my rpi is either broken or i am connecting it wrong. has anyone managed to get uart working ? to my understanding i need to connect pin6 to gnd and use 8 and 10 for the 2 data lines. should i see output from the bootloader prior to board detecting/loading the sd card ? John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] More bad RPATH
On 09/02/2015 14:07, Etienne Champetier wrote:
Hi
2015-02-09 14:01 GMT+01:00 John Crispin blo...@openwrt.org
mailto:blo...@openwrt.org:
On 09/02/2015 13:57, Etienne Champetier wrote:
Hi all,
To follow r44328
(https://dev.openwrt.org/browser/trunk?rev=44328) (jow fix for
cmake RPATH) I've launched a full build of ar71xx to check all
bin/lib for bad
RPATH
# cd ./staging_dir/target-mips_34kc_uClibc-0.9.33.2/root-ar71xx #
find . -type f | xargs -n1 -P24 file | grep ': ELF' | awk -F':'
'{print $1}' | xargs -n1 ./checksec.sh --file | grep -v 'STACK
CANARY'
checksec.txt # awk '{print $NF}' checksec.txt lib.txt # awk
'{print $NF}' checksec.txt | xargs -n1 readelf -a | grep RPATH |
awk -F'[' '{print [$2}' rpath.txt
you can merge libs.txt and rpath.txt with # paste lib.txt
rpath.txt
I will try to fix later Also i think we should have a test that
fail the build if there is builroot path in the RPATH
Regards Etienne
can you build a script to turns this into a list of package names
that are effected ?
I'll try, but not before tonight
$root/var/lib/opkg/* has files that will help you map the
file-ipkg/package
John
___ 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] [PATCH 3/5] generic: improve kexec support of MIPS.
Hi, after some very basic testing i would suggest that On 10/02/2015 13:10, Yousong Zhou wrote: create mode 100644 target/linux/generic/patches-3.10/330-MIPS-Malta-Mark-kernel-code-and-kernel-data-segments.patch create mode 100644 target/linux/generic/patches-3.10/331-MIPS-kexec-Accept-command-line-parameters-from-users.patch create mode 100644 target/linux/generic/patches-3.14/330-MIPS-Malta-Mark-kernel-code-and-kernel-data-segments.patch create mode 100644 target/linux/generic/patches-3.14/331-MIPS-kexec-Accept-command-line-parameters-from-users.patch i'll ignore the ones above as we want to move to 3.18+ asap create mode 100644 target/linux/generic/patches-3.18/330-MIPS-Malta-Mark-kernel-code-and-kernel-data-segments.patch create mode 100644 target/linux/generic/patches-3.18/331-MIPS-kexec-Accept-command-line-parameters-from-users.patch create mode 100644 target/linux/generic/patches-3.19/330-MIPS-Malta-Mark-kernel-code-and-kernel-data-segments.patch create mode 100644 target/linux/generic/patches-3.19/331-MIPS-kexec-Accept-command-line-parameters-from-users.patch move the 2 mti-mala patche into the malta folder is that ok with you ? John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lantiq v3.18
On 12/02/2015 18:30, Daniel Gimpelevich wrote: On Thu, Feb 12, 2015 at 8:54 AM, Daniel Gimpelevich dan...@gimpelevich.san-francisco.ca.us mailto:dan...@gimpelevich.san-francisco.ca.us wrote: On Thu, Feb 12, 2015 at 3:19 AM, John Crispin blo...@openwrt.org mailto:blo...@openwrt.org wrote: On 10/02/2015 10:40, Daniel Gimpelevich wrote: Is there a patchset I could try? try r44421 or newer Tried initramfs, bootlog attached. With this image, booting from SPI flash still fails, because there is no longer a kernel partition, so the rootfs is now /dev/mtdblock4, while the DTS file still specifies /dev/mtdblock5. and why does that cause booting to fail ? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lantiq v3.18
On 12/02/2015 18:33, John Crispin wrote: On 12/02/2015 18:30, Daniel Gimpelevich wrote: On Thu, Feb 12, 2015 at 8:54 AM, Daniel Gimpelevich dan...@gimpelevich.san-francisco.ca.us mailto:dan...@gimpelevich.san-francisco.ca.us wrote: On Thu, Feb 12, 2015 at 3:19 AM, John Crispin blo...@openwrt.org mailto:blo...@openwrt.org wrote: On 10/02/2015 10:40, Daniel Gimpelevich wrote: Is there a patchset I could try? try r44421 or newer Tried initramfs, bootlog attached. With this image, booting from SPI flash still fails, because there is no longer a kernel partition, so the rootfs is now /dev/mtdblock4, while the DTS file still specifies /dev/mtdblock5. and why does that cause booting to fail ? ah i see, not even sure why we attach that info. the mtdsplid should automatically set the root= try removing the root= parameter please and see if it boots properly ___ 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
[OpenWrt-Devel] ar71xx update to v3.18
Hi, i just pushed the v3.18 support for ar71xx. i have tested this on carambola2, unifi and wndr4300. the default is still at 3.14. please start testing on more hardware. to do so you need to set the kernel to 3.18 in target/linux/ar71xx/Makefile as the default is still at 3.14. 902-unaligned_access_hacks.patch was rebased, however there might be new places in the stack that need the hack applied. testing for this is also welcome. John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] ar71xx update to v3.18
Hi, On 15/02/2015 20:56, Daniel Petre wrote: are there any extra big advantages for OpenWrt since 3.14 ? eBPF is my personal favorite. John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] ar71xx update to v3.18
On 15/02/2015 21:44, Michaël Zweers wrote: Hello, I got a error message (kernel compile log included) when building v3.18 for wr703n. If you need additional info let me know. please retry, i just pushed a fix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] raspberry pi v3.19
ok, so uart, how do you connect it ? On 10/02/2015 02:02, Álvaro Fernández Rojas wrote: I tried adding support for 3.18 and I have issues booting the raspberry. There must be something wrong with the new mmc driver, because it detects the SD card insertions/extractiones, but doesn't read the partitions: http://pastebin.com/GWFYrXnT My patches: http://files.noltari.es/openwrt/bcm2708/brcm2708_3-18.tgz Regards, Álvaro. El 09/02/2015 a las 18:12, Florian Fainelli escribió: On Feb 9, 2015 4:25 AM, John Crispin blo...@openwrt.org mailto:blo...@openwrt.org wrote: Hi, i synced our rpi port with the upstream tree on github. it boots and i can see the coloured palette test pic on the hdmi, however ethernet fails to come up. i attached a uart just to find out that my rpi is either broken or i am connecting it wrong. has anyone managed to get uart working ? to my understanding i need to connect pin6 to gnd and use 8 and 10 for the 2 data lines. should i see output from the bootloader prior to board detecting/loading the sd card You will not get any UART output prior to the kernel boot, the GPU boot code does not output anything (at least not in the builds we use). Could you share the boot log to see if there is anything obvious? John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org mailto: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 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] looking for at91 test hardware
On 16/02/2015 11:52, Nicolas FERRE wrote: John Crispin blogic at openwrt.org writes: Hi, does anyone have one of these - http://www.atmel.com/tools/ATSAMA5D3-XPLD.aspx that he wants to donate so that i have something to test at91 images on Hi Josh, Of course, I can surely do something for you ;-) Let's arrange the shipment in private. (Thanks to Maxime Ripard for the heads-up). Bye, Hi Nicolas, Oh Wow, that is something i did not expect. i am currently updating all targets in openwrt to v3.18 and while doing so i noticed that i do not own any recent AT91 hardware. I previously used an acmesystems board but gave it away a while ago for an art installation. totally awesome, put a big smile on my face John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] ar71xx update to v3.18
On 16/02/2015 11:05, Michaël Zweers wrote: I can confirm that it does work, i don't no where or why it didn't the previous time. I did a clean clone and used a clean config and now everything looks to be oké. Bootlog is attached: confirmed working: Boot: Yes Ethernet: Yes WiFI: Yes Luci: Yes (used to scan for wifi) If you want me to test something else or something specific please let me know. ok, you got me scared for a moment ;) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] ar71xx update to v3.18
On 16/02/2015 00:15, Paul Blazejowski wrote: 00 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 21.73] cfg80211: (549 KHz - 573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s) [ 21.74] cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A) [ 21.75] cfg80211: (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A) [ 22.17] ath9k ar934x_wmac: Direct firmware load for soc_wmac.eeprom failed with error -2 [ 22.18] ath: phy0: Unable to load EEPROM file soc_wmac.eeprom [ 22.19] ath9k ar934x_wmac: failed to initialize device [ 22.19] ath9k: probe of ar934x_wmac failed with error -22 [ 22.20] PCI: Enabling device :00:00.0 ( - 0002) [ 22.22] ath9k :00:00.0: Direct firmware load for pci_wmac0.eeprom failed with error -2 [ 22.23] ath: phy1: Unable to load EEPROM file pci_wmac0.eeprom [ 22.23] ath9k :00:00.0: Failed to initialize device [ 22.24] ath9k: probe of :00:00.0 failed with error -22 [ 29.76] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready probably related to this - https://dev.openwrt.org/ticket/18992 do a cat /tmp/sysinfo/* please ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
