Re: [OpenWrt-Devel] [PATCH] linux:generic: mtd backport for Spansion S25FL164K
On 29 June 2015 at 07:54, L. D. Pinney wrote:
> Backport for the Spansion S25FL164K
> It's an 8 MiB flash with 4 KiB erase sectors.
>
> Signed-off-by: L. D. Pinney
It looks much better but this patch doesn't seem to be refreshed, see:
Applying patch generic/091-mtd-spi-nor-add-support-for-the-Spansion_S25FL164K
patching file drivers/mtd/spi-nor/spi-nor.c
Hunk #1 succeeded at 566 (offset -7 lines).
Applying patch generic/472-mtd-m25p80-add-support-for-Winbond-W25X05-flash.patch
patching file drivers/mtd/spi-nor/spi-nor.c
Hunk #1 succeeded at 617 (offset 1 line).
And there is some general problem with your patch, see below
> diff --git
> a/target/linux/generic/patches-3.18/091-mtd-spi-nor-add-support-for-the-Spansion_S25FL164K
>
> b/target/linux/generic/patches-3.18/091-mtd-spi-nor-add-support-for-the-Spansion_S25FL164K
> new file mode 100644
> index 000..866567a
> --- /dev/null
> +++
> b/target/linux/generic/patches-3.18/091-mtd-spi-nor-add-support-for-the-Spansion_S25FL164K
> @@ -0,0 +1,10 @@
> +--- a/drivers/mtd/spi-nor/spi-nor.c
> b/drivers/mtd/spi-nor/spi-nor.c
> +@@ -573,6 +573,7 @@ static const struct spi_device_id spi_nor_ids[] = {
> + { "s25fl008k", INFO(0xef4014, 0, 64 * 1024, 16, SECT_4K) },
> + { "s25fl016k", INFO(0xef4015, 0, 64 * 1024, 32, SECT_4K) },
> + { "s25fl064k", INFO(0xef4017, 0, 64 * 1024, 128, SECT_4K) },
> ++ { "s25fl164k", INFO(0x014017, 0, 64 * 1024, 128, SECT_4K) },
> +
> + /* SST -- large erase sizes are "overlays", "sectors" are 4K */
> + { "sst25vf040b", INFO(0xbf258d, 0, 64 * 1024, 8, SECT_4K |
> SST_WRITE) },
A diff (patch) file should have space at the beginning for every
unmodified (reference) file. The file you added doesn't have it. How
did you prepare this file?
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Chaos Calmer regression in RC2 - MediaTek MT7621
works for me on both trunk and rc2/3. i tested this on 3 boards. show us the oops please. On 28/06/2015 10:21, Christian Mehlis wrote: > On my Firewrt (MediaTek MT7621) cc-rc1 was booting up correctly. > cc-rc2 fails with kernel oops: > > http://pastebin.com/raw.php?i=gCWKmG3J cc-rc1 (working) > http://pastebin.com/raw.php?i=GSXXtPxd cc-rc2 (kernel oops) > http://pastebin.com/raw.php?i=t1qRjzPy r46133 trunk (kernel oops) > > trunk is also broken (on this hardware). > > Best > 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] Chaos Calmer regression in RC2 - MediaTek MT7621
Am 29.06.2015 um 11:07 schrieb John Crispin: works for me on both trunk and rc2/3. i tested this on 3 boards. show us the oops please. have a look at pastebin: http://pastebin.com/raw.php?i=gCWKmG3J cc-rc1 (working) http://pastebin.com/raw.php?i=GSXXtPxd cc-rc2 (kernel oops) http://pastebin.com/raw.php?i=t1qRjzPy r46133 trunk (kernel oops) Best Christian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] iwinfo lua scanlist issue
Hi OpenWRT dev's,
It looks like the scanlist method of the iwinfo lua binding hangs when the
wifi stack is restarted.
This happens when my init script is called, which attempts to perform a
scan, but the wifi stack is restarted because the country and channel is
changed (according to the wireless configuration in uci). With hanging I
mean that Lua doesn't get past this function call, there is no timeout. And
not being able to make this non blocking makes this pretty problematic.
The only solution thus far was adding a 5 seconds sleep in my init script.
The only traces of info I could find are here:
http://wiki.openwrt.org/doc/howto/wireless.utilities#iwconfig
http://git.openwrt.org/?p=project/iwinfo.git;a=tree;hb=HEAD
This happens in the 14.07 version of OpenWRT.
I can reproduce this after boot with the following lua script:
> local io = require('io')
> local file = assert(io.open('/tmp/scan.log', "a+"))
> local function logger(message)
> print(message)
> file:write(message .. "\n")
> file:flush()
> end
>
> logger("init")
>
> logger("starting wifi restart")
> local handler = io.popen("wifi")
>
> local iwinfo = require('iwinfo')
> local deviceName = 'wlan0'
> local deviceID = iwinfo.type(deviceName)
>
> if not deviceID then
> logger("wireless device '" .. deviceName .. "' not found")
> else
> logger("found wireless device '" .. deviceName .. "'")
> end
>
> local wifiDevice = iwinfo[deviceID]
> if not wifiDevice then
> logger("'iwinfo." .. deviceID .. "' interface not found")
> else
> logger("found 'iwinfo." .. deviceID .. "' interface")
> end
>
> logger("calling scanlist")
> local scanList = wifiDevice.scanlist(deviceName)
> logger("scanlist completed")
> logger("scanlist:")
> for _,sn in ipairs(scanList) do
> logger(" - " .. (sn.ssid or ""))
> end
>
> logger("finished")
>
>
Isn't there a more specific project site, issue queue or mailinglist?
Thanks in advance,
Peter Uithoven
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] iwinfo lua scanlist issue
Hi Peter, I suspect the culprit is nl80211_wait() which calls nl_recvmsgs() internally. To overcome this problem we need to restructure the nl80211 code to use nonblocking sockets and then extend the nl80211_wait() implementation to have a timeout. ~ Jow ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Fwd: iwinfo lua scanlist issue
-- Forwarded message -- From: Peter Uithoven Date: Mon, Jun 29, 2015 at 12:38 PM Subject: Re: [OpenWrt-Devel] iwinfo lua scanlist issue To: Bastian Bittorf Hi Bastian, On Mon, Jun 29, 2015 at 12:03 PM, Bastian Bittorf wrote: > * Peter Uithoven [29.06.2015 11:46]: > > This happens when my init script is called, which attempts to perform a > > scan, but the wifi stack is restarted because the country and channel is > > i'am curious - what is your interest in scanning during bootup? > (if you only need it once, you should better do it via a hotplug > script...) > We do a little bit of our own wifi config. We try to find (using scanlist) known wifi networks and connect to them, when non appropriate are found we create a accesspoint. In the future, when connecting to a known networks fails it should also become a accesspoint. If I understand the OpenWRT wiki hotplug is replaced by procd? http://wiki.openwrt.org/doc/techref/hotplug I'll look into procd, this page seems relevant: http://wiki.openwrt.org/inbox/procd-init-scripts We're still figuring out how to best do network configuration through Lua. > bye, bastian > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] iwinfo lua scanlist issue
Should we maybe switch to using iwinfo though ubus in our Lua code? Can we use that to scan for networks? Could that be a more robust solution? http://wiki.openwrt.org/doc/techref/ubus#lua_module_for_ubus https://forum.openwrt.org/viewtopic.php?id=57554 If I understand the following two pages correctly the new luci (LuCI2) will also use ubus, over http. http://wiki.openwrt.org/doc/techref/luci2 http://wiki.openwrt.org/doc/techref/ubus#access_to_ubus_over_http On Mon, Jun 29, 2015 at 11:59 AM, Jo-Philipp Wich wrote: > Hi Peter, > > I suspect the culprit is nl80211_wait() which calls nl_recvmsgs() > internally. > > To overcome this problem we need to restructure the nl80211 code to use > nonblocking sockets and then extend the nl80211_wait() implementation to > have a timeout. > > ~ Jow > ___ > 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] iwinfo lua scanlist issue
Not really as the core issue is always within the same C code, however you access it. ~ Jow ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Fwd: iwinfo lua scanlist issue
* Peter Uithoven [29.06.2015 13:20]:
> We do a little bit of our own wifi config. We try to find (using scanlist)
> known wifi networks and connect to them, when non appropriate are found we
> create a accesspoint.
> In the future, when connecting to a known networks fails it should also
> become a accesspoint.
ok...then you can maybe with hotplug wait for ACTION='ifup'
maybe something like this (will not work, but you get the idea)
#!/bin/sh
# hotplug-script:
SCANNED='/your/path'
MYCHANNELS='1 2 3 154 168'
[ "$ACTION" = 'ifup' -a -e "$SCANNED" ] && {
scan_for_known_networks | while read NETWORK_SETTINGS ; do
connect $NETWORK_SETTINGS # ssid, channel, pass etc.
rm $SCANNED
done
}
[ "$ACTION" = 'ifup' -a "$INTERFACE" = 'mywifi' ] && {
for CHAN in $MYCHANNELS; do
create_adhoc $CHAN
touch 'SCANNED'
wifi
done
}
> If I understand the OpenWRT wiki hotplug is replaced by procd?
no. netifd will start hotplug if an interface comes up.
bye, bastian
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Chaos Calmer regression in RC2 - MediaTek MT7621
On 29/06/2015 11:13, Christian Mehlis wrote: > Am 29.06.2015 um 11:07 schrieb John Crispin: >> works for me on both trunk and rc2/3. i tested this on 3 boards. >> >> show us the oops please. > > have a look at pastebin: > >>> http://pastebin.com/raw.php?i=gCWKmG3J cc-rc1 (working) >>> http://pastebin.com/raw.php?i=GSXXtPxd cc-rc2 (kernel oops) >>> http://pastebin.com/raw.php?i=t1qRjzPy r46133 trunk (kernel oops) > > Best > Christian > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel are you sure that your board has 512mb ram ? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Chaos Calmer regression in RC2 - MediaTek MT7621
Am 29.06.2015 um 14:32 schrieb John Crispin: are you sure that your board has 512mb ram ? Hey John, good catch! You are right, my eval board only has 256mb. /target/linux/ramips/dts/FIREWRT.dts: line 11 can you tell me how this line has to look, with 256mb of RAM? Is it sufficient to remove the memory block to get the default value (=256) from MT7621.dts ? Can we create a target for this eval-edition of this board? Best Christian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Fwd: iwinfo lua scanlist issue
On Mon, Jun 29, 2015 at 1:35 PM, Bastian Bittorf
wrote:
> * Peter Uithoven [29.06.2015 13:20]:
> > We do a little bit of our own wifi config. We try to find (using
> scanlist)
> > known wifi networks and connect to them, when non appropriate are found
> we
> > create a accesspoint.
> > In the future, when connecting to a known networks fails it should also
> > become a accesspoint.
>
> ok...then you can maybe with hotplug wait for ACTION='ifup'
> maybe something like this (will not work, but you get the idea)
>
> #!/bin/sh
> # hotplug-script:
>
> SCANNED='/your/path'
> MYCHANNELS='1 2 3 154 168'
>
> [ "$ACTION" = 'ifup' -a -e "$SCANNED" ] && {
> scan_for_known_networks | while read NETWORK_SETTINGS ; do
> connect $NETWORK_SETTINGS # ssid, channel, pass etc.
> rm $SCANNED
> done
> }
>
> [ "$ACTION" = 'ifup' -a "$INTERFACE" = 'mywifi' ] && {
> for CHAN in $MYCHANNELS; do
> create_adhoc $CHAN
> touch 'SCANNED'
> wifi
> done
> }
>
> Thanks! I will look into this.
> > If I understand the OpenWRT wiki hotplug is replaced by procd?
>
> no. netifd will start hotplug if an interface comes up.
>
> But, why does the wiki say this then? Is that info incorrect? Is netifd an
exception?
> bye, bastian
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Fwd: iwinfo lua scanlist issue
* Peter Uithoven [29.06.2015 15:27]: > > > If I understand the OpenWRT wiki hotplug is replaced by procd? > > > > no. netifd will start hotplug if an interface comes up. > > > > But, why does the wiki say this then? Is that info incorrect? Is netifd an > exception? > you are right - procd will call '/sbin/hotplug $args' which is invoked from netifd via ubus...(hope you are confused now...) 8-) bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Chaos Calmer regression in RC2 - MediaTek MT7621
On 29/06/2015 15:05, Christian Mehlis wrote: > Am 29.06.2015 um 14:32 schrieb John Crispin: >> are you sure that your board has 512mb ram ? > > Hey John, > > good catch! > > You are right, my eval board only has 256mb. > > /target/linux/ramips/dts/FIREWRT.dts: line 11 > > can you tell me how this line has to look, with 256mb of RAM? > > Is it sufficient to remove the memory block to get the default value > (=256) from MT7621.dts ? > copy it over from the dtsi file and make a FIREWRT-256.dts > Can we create a target for this eval-edition of this board? > > Best > 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
[OpenWrt-Devel] [PATCH] ar71xx: Add support for The QCA AP147-010 reference board
Signed-off-by: Sven Eckelmann
---
I got the chance to test the AP147-010 but got no software/SDK or documentation.
Still wanted to post my results because the device worked well enough for me.
I am not sure if it originally comes with a PCIe card (I've used at QCA9880
based one for my tests).
Most of the SoC relevant code is based on the QCA955x implementation.
target/linux/ar71xx/base-files/etc/diag.sh | 3 +
.../ar71xx/base-files/etc/uci-defaults/01_leds | 9 ++
.../ar71xx/base-files/etc/uci-defaults/02_network | 7 +
target/linux/ar71xx/base-files/lib/ar71xx.sh | 3 +
.../lib/preinit/05_set_preinit_iface_ar71xx| 1 +
.../ar71xx/base-files/lib/upgrade/platform.sh | 1 +
target/linux/ar71xx/config-3.18| 1 +
.../ar71xx/files/arch/mips/ath79/mach-ap147.c | 119
target/linux/ar71xx/generic/profiles/atheros.mk| 11 ++
target/linux/ar71xx/image/Makefile | 3 +
target/linux/ar71xx/mikrotik/config-default| 1 +
target/linux/ar71xx/nand/config-default| 1 +
.../740-MIPS-ath79-add-PCI-for-QCA953x-SoC.patch | 158 +
.../741-MIPS-ath79-add-USB-for-QCA953x-SoC.patch | 56
.../742-MIPS-ath79-add-ap147-support.patch | 42 ++
15 files changed, 416 insertions(+)
create mode 100644 target/linux/ar71xx/files/arch/mips/ath79/mach-ap147.c
create mode 100644
target/linux/ar71xx/patches-3.18/740-MIPS-ath79-add-PCI-for-QCA953x-SoC.patch
create mode 100644
target/linux/ar71xx/patches-3.18/741-MIPS-ath79-add-USB-for-QCA953x-SoC.patch
create mode 100644
target/linux/ar71xx/patches-3.18/742-MIPS-ath79-add-ap147-support.patch
diff --git a/target/linux/ar71xx/base-files/etc/diag.sh
b/target/linux/ar71xx/base-files/etc/diag.sh
index 4313f2f..169d192 100644
--- a/target/linux/ar71xx/base-files/etc/diag.sh
+++ b/target/linux/ar71xx/base-files/etc/diag.sh
@@ -22,6 +22,9 @@ get_status_led() {
ap136-020)
status_led="ap136:green:status"
;;
+ ap147-010)
+ status_led="ap147:green:status"
+ ;;
ap135-020)
status_led="ap135:green:status"
;;
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 3cd17b1..1d4f88d 100644
--- a/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds
+++ b/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds
@@ -40,6 +40,15 @@ ap113)
ucidef_set_led_usbdev "usb" "USB" "ap113:green:usb" "1-1"
;;
+ap147-010)
+ ucidef_set_led_netdev "wan" "WAN" "ap147:green:wan" "eth1"
+ ucidef_set_led_switch "lan1" "LAN1" "ap147:green:lan1" "switch0" "0x10"
+ ucidef_set_led_switch "lan2" "LAN2" "ap147:green:lan2" "switch0" "0x08"
+ ucidef_set_led_switch "lan3" "LAN3" "ap147:green:lan3" "switch0" "0x04"
+ ucidef_set_led_switch "lan4" "LAN4" "ap147:green:lan4" "switch0" "0x02"
+ ucidef_set_led_wlan "wlan2g" "WLAN 2.4 GHz" "ap147:green:wlan-2g"
"phy0tpt"
+ ;;
+
bullet-m | \
nanostation-m | \
rocket-m | \
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 2fab4c2..1b39d2a 100644
--- a/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
+++ b/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
@@ -45,6 +45,13 @@ ap136-010)
ucidef_add_switch_vlan "switch0" "2" "5 6"
;;
+ap147-010)
+ ucidef_set_interfaces_lan_wan "eth0" "eth1"
+ ucidef_add_switch "switch0" "1" "1"
+ ucidef_add_switch_vlan "switch0" "1" "0 1 2 3 4"
+ ucidef_add_switch_vlan "switch0" "2" "5 6"
+ ;;
+
ap136-020 |\
ap135-020 |\
tl-wr1043nd-v2 |\
diff --git a/target/linux/ar71xx/base-files/lib/ar71xx.sh
b/target/linux/ar71xx/base-files/lib/ar71xx.sh
index 09c06d7..85aeda0 100755
--- a/target/linux/ar71xx/base-files/lib/ar71xx.sh
+++ b/target/linux/ar71xx/base-files/lib/ar71xx.sh
@@ -359,6 +359,9 @@ ar71xx_board_detect() {
*"AP135-020 reference board")
name="ap135-020"
;;
+ *"AP147-010 reference board")
+ name="ap147-010"
+ ;;
*AP81)
name="ap81"
;;
diff --git
a/target/linux/ar71xx/base-files/lib/preinit/05_set_preinit_iface_ar71xx
b/target/linux/ar71xx/base-files/lib/preinit/05_set_preinit_iface_ar71xx
index f11ea8c..d214e9b 100644
--- a/target/linux/ar71xx/base-files/lib/preinit/05_set_preinit_iface_ar71xx
+++ b/target/linux/ar71xx/base-files/lib/preinit/05_set_preinit_iface_ar71xx
@@ -12,6 +12,7 @@ set_preinit_iface() {
alfa-nx |\
ap135-020 |\
ap136-020 |\
+ ap147-010 |\
ap83 |\
archer-c5 |\
archer-c7 |\
diff --git a/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
b/target/linux/ar71xx/base-files/lib/upgra
Re: [OpenWrt-Devel] [PATCH] Improve wifi speed up to 2 times in AP mode.
Resending patch in text format. Return of wmm_* parameters to hostapd.conf file for wifi speed up. 2015-06-29 0:59 GMT+03:00 N.Leiten : > The thing is - this parameters I've got from hostapd.conf on my host > machine and due to comments they are strictly set from 802.11. As for > hostapd itself, I don't gone in deep inspection of WMM part but I saw > some default values regarding tx_queue* parameters (according to > comments this section is used to prioritize traffic from AP to STAs, > and WMM part is in opposite direction, in my oppinion last one is also > used to determine WMM capable stations which gives us such speed > improvements) in source code of hostapd, maybe there's some analogue > for WMM but somehow it don't get applied when configuration file > loaded. So for now the easiest and fast way to fix this is to set > config with parameters that hostapd expects. > > 2015-06-29 0:21 GMT+03:00 Linus Lüssing : >> On Sun, Jun 28, 2015 at 09:16:58PM +0300, N.Leiten wrote: >>> As a result I got full 100Mbit/s on AR71XX platform and 70-80Mbit on >>> Ralink. I think it is good performance improvement at this moment. >> >> Interesting, thanks for sharing your results! >> >> If these settings are generally diserable, maybe it might make >> sense to patch hostapd to set them by default if they aren't set >> explicitly, instead of through netifd? That way anyone, not only >> OpenWRT users might benefit from it. >> >> Cheers, Linus diff -c -r a/package/network/services/hostapd/files/netifd.sh b/package/network/services/hostapd/files/netifd.sh *** a/package/network/services/hostapd/files/netifd.sh 2015-06-09 15:00:07.0 +0300 --- b/package/network/services/hostapd/files/netifd.sh 2015-06-28 21:01:39.054827123 +0300 *** *** 207,212 --- 207,235 append bss_conf "disassoc_low_ack=$disassoc_low_ack" "$N" append bss_conf "preamble=$short_preamble" "$N" append bss_conf "wmm_enabled=$wmm" "$N" + if [ "$wmm" -gt 0 ];then + append bss_conf "wmm_ac_bk_cwmin=4" "$N" + append bss_conf "wmm_ac_bk_cwmax=10" "$N" + append bss_conf "wmm_ac_bk_aifs=7" "$N" + append bss_conf "wmm_ac_bk_txop_limit=0" "$N" + append bss_conf "wmm_ac_bk_acm=0" "$N" + append bss_conf "wmm_ac_be_aifs=3" "$N" + append bss_conf "wmm_ac_be_cwmin=4" "$N" + append bss_conf "wmm_ac_be_cwmax=10" "$N" + append bss_conf "wmm_ac_be_txop_limit=0" "$N" + append bss_conf "wmm_ac_be_acm=0" "$N" + append bss_conf "wmm_ac_vi_aifs=2" "$N" + append bss_conf "wmm_ac_vi_cwmin=3" "$N" + append bss_conf "wmm_ac_vi_cwmax=4" "$N" + append bss_conf "wmm_ac_vi_txop_limit=94" "$N" + append bss_conf "wmm_ac_vi_acm=0" "$N" + append bss_conf "wmm_ac_vo_aifs=2" "$N" + append bss_conf "wmm_ac_vo_cwmin=2" "$N" + append bss_conf "wmm_ac_vo_cwmax=3" "$N" + append bss_conf "wmm_ac_vo_txop_limit=47" "$N" + append bss_conf "wmm_ac_vo_acm=0" "$N" + fi + append bss_conf "ignore_broadcast_ssid=$hidden" "$N" append bss_conf "uapsd_advertisement_enabled=$uapsd" "$N" ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] HT modes apparently not working in adhoc under Barrier Breaker
Following up that I've verified this changeset presently in trunk/Chaos
Calmer resolves the HT mode issue in Barrier Breaker. Would it be possible
to backport this changeset?
https://dev.openwrt.org/changeset/44100/
On Sat, Jun 27, 2015 at 3:46 PM, Ben West wrote:
> This is the /etc/config/wireless I'm using on a UBNT M5 radio running
> Barrier Breaker r45620:
>
> config wifi-device radio0
> option type mac80211
> option channel 36
> option hwmode 11a
> option path 'pci:00/:00:00.0'
> option htmode HT20
> option country 'US'
> option beacon_int '500'
> list basic_rate '12000 18000 24000 36000 48000 54000'
> option diversity '1'
> option doth '0'
> option disabled 0
>
> config wifi-iface wlan0
> option device radio0
> option network 'mesh'
> option mode 'adhoc'
> option mcast_rate '12000'
> option ssid MyMesh
> option bssid '02:CA:FF:EE:BA:BE'
> option encryption 'psk2+aes'
> option key '...'
>
> ... and this is the /var/run/wpa_supplicant-wlan0.conf generated when
> using packages hostapd, hostapd-common, and wpa-supplicant:
>
> ap_scan=2
> network={
> scan_ssid=0
> ssid="MyMesh"
> key_mgmt=WPA-PSK
> mode=1
> fixed_freq=1
> frequency=5180
> mode=1
> psk="..."
> proto=RSN
> bssid=02:CA:FF:EE:BA:BE
> beacon_int=500
> mcast_rate=12
> }
>
> Running "iw wlan0 station dump" confirms no HT modes appear on links to
> other stations. By comparison, the same radio and same wireless config
> under Chaos Calmer r46069 sees this /var/run/wpa_supplicant-wlan0.conf
> generated:
>
> ap_scan=2
> network={
> scan_ssid=0
> ssid="MyMesh"
> key_mgmt=WPA-PSK
> mode=1
> fixed_freq=1
> frequency=5180
> mode=1
> psk="..."
> proto=RSN
> bssid=02:CA:FF:EE:BA:BE
> mcast_rate=12
> htmode=HT20
> }
>
> The station dump on the radio running Chaos Calmer does show HT modes in
> use.
>
> --
> Ben West
> http://gowasabi.net
> b...@gowasabi.net
> 314-246-9434
>
--
Ben West
http://gowasabi.net
b...@gowasabi.net
314-246-9434
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] This patch fixes a line that appears to clear beacon_int variable, prevent setting beacon interval for adhoc.
Signed-off-by: ben
---
package/network/services/hostapd/files/netifd.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/network/services/hostapd/files/netifd.sh
b/package/network/services/hostapd/files/netifd.sh
index 23d2e7e..f148544 100644
--- a/package/network/services/hostapd/files/netifd.sh
+++ b/package/network/services/hostapd/files/netifd.sh
@@ -632,7 +632,7 @@ wpa_supplicant_add_network() {
;;
esac
}
- local beacon_int brates mrate
+ local brates mrate
[ -n "$bssid" ] && append network_data "bssid=$bssid" "$N$T"
[ -n "$beacon_int" ] && append network_data "beacon_int=$beacon_int"
"$N$T"
--
1.9.1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] linux:generic: mtd backport for Spansion S25FL164K
The space was removed because "git apply" complainedI'll ignore the
complaint.
Please mark this one rejected...
I'll do better next time.
Thanks for your patience and guidance.
Larry
On Mon, Jun 29, 2015 at 2:16 AM, Rafał Miłecki wrote:
> On 29 June 2015 at 07:54, L. D. Pinney wrote:
> > Backport for the Spansion S25FL164K
> > It's an 8 MiB flash with 4 KiB erase sectors.
> >
> > Signed-off-by: L. D. Pinney
>
> It looks much better but this patch doesn't seem to be refreshed, see:
>
> Applying patch
> generic/091-mtd-spi-nor-add-support-for-the-Spansion_S25FL164K
> patching file drivers/mtd/spi-nor/spi-nor.c
> Hunk #1 succeeded at 566 (offset -7 lines).
>
> Applying patch
> generic/472-mtd-m25p80-add-support-for-Winbond-W25X05-flash.patch
> patching file drivers/mtd/spi-nor/spi-nor.c
> Hunk #1 succeeded at 617 (offset 1 line).
>
> And there is some general problem with your patch, see below
>
>
> > diff --git
> a/target/linux/generic/patches-3.18/091-mtd-spi-nor-add-support-for-the-Spansion_S25FL164K
> b/target/linux/generic/patches-3.18/091-mtd-spi-nor-add-support-for-the-Spansion_S25FL164K
> > new file mode 100644
> > index 000..866567a
> > --- /dev/null
> > +++
> b/target/linux/generic/patches-3.18/091-mtd-spi-nor-add-support-for-the-Spansion_S25FL164K
> > @@ -0,0 +1,10 @@
> > +--- a/drivers/mtd/spi-nor/spi-nor.c
> > b/drivers/mtd/spi-nor/spi-nor.c
> > +@@ -573,6 +573,7 @@ static const struct spi_device_id spi_nor_ids[] = {
> > + { "s25fl008k", INFO(0xef4014, 0, 64 * 1024, 16, SECT_4K)
> },
> > + { "s25fl016k", INFO(0xef4015, 0, 64 * 1024, 32, SECT_4K)
> },
> > + { "s25fl064k", INFO(0xef4017, 0, 64 * 1024, 128, SECT_4K)
> },
> > ++ { "s25fl164k", INFO(0x014017, 0, 64 * 1024, 128, SECT_4K)
> },
> > +
> > + /* SST -- large erase sizes are "overlays", "sectors" are 4K */
> > + { "sst25vf040b", INFO(0xbf258d, 0, 64 * 1024, 8, SECT_4K |
> SST_WRITE) },
>
> A diff (patch) file should have space at the beginning for every
> unmodified (reference) file. The file you added doesn't have it. How
> did you prepare this file?
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] linux:generic: mtd backport for Spansion S25FL164K
On 30 June 2015 at 01:38, L. D. Pinney wrote: > The space was removed because "git apply" complainedI'll ignore the > complaint. In this case it's alright to have this complain, git just doesn't handle nicely patches adding patches :) > Please mark this one rejected... > I'll do better next time. > Thanks for your patience and guidance. Sure, thanks. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] linux:generic: mtd backport for Spansion S25FL164K
On 30 June 2015 at 01:38, L. D. Pinney wrote: > Please mark this one rejected... > I'll do better next time. > Thanks for your patience and guidance. Every new try should also include increased V (like version) number. So the *next* one should be: [PATCH V3] linux:generic: mtd backport for Spansion S25FL164K you can get that e.g. using git format-patch --subject-prefix="PATCH V3" ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH V3] linux:generic: mtd backport for Spansion S25FL164K
Backport for the Spansion S25FL164K
It's an 8 MiB flash with 4 KiB erase sectors.
Signed-off-by: L. D. Pinney
---
target/linux/generic/patches-3.18/091-mtd-spi-nor-add-support-for-the-Spansion_S25FL164K
| 12
target/linux/generic/patches-4.0/091-mtd-spi-nor-add-support-for-the-Spansion_S25FL164K
| 12
target/linux/generic/patches-4.1/091-mtd-spi-nor-add-support-for-the-Spansion_S25FL164K
| 12
3 files changed, 36 insertions(+)
diff --git
a/target/linux/generic/patches-3.18/091-mtd-spi-nor-add-support-for-the-Spansion_S25FL164K
b/target/linux/generic/patches-3.18/091-mtd-spi-nor-add-support-for-the-Spansion_S25FL164K
new file mode 100644
index 000..866567a
--- /dev/null
+++
b/target/linux/generic/patches-3.18/091-mtd-spi-nor-add-support-for-the-Spansion_S25FL164K
@@ -0,0 +1,10 @@
+--- a/drivers/mtd/spi-nor/spi-nor.c
b/drivers/mtd/spi-nor/spi-nor.c
+@@ -573,6 +573,7 @@ static const struct spi_device_id spi_nor_ids[] = {
+ { "s25fl008k", INFO(0xef4014, 0, 64 * 1024, 16, SECT_4K) },
+ { "s25fl016k", INFO(0xef4015, 0, 64 * 1024, 32, SECT_4K) },
+ { "s25fl064k", INFO(0xef4017, 0, 64 * 1024, 128, SECT_4K) },
++ { "s25fl164k", INFO(0x014017, 0, 64 * 1024, 128, SECT_4K) },
+
+ /* SST -- large erase sizes are "overlays", "sectors" are 4K */
+ { "sst25vf040b", INFO(0xbf258d, 0, 64 * 1024, 8, SECT_4K | SST_WRITE)
},
diff --git
a/target/linux/generic/patches-4.0/091-mtd-spi-nor-add-support-for-the-Spansion_S25FL164K
b/target/linux/generic/patches-4.0/091-mtd-spi-nor-add-support-for-the-Spansion_S25FL164K
new file mode 100644
index 000..866567a
--- /dev/null
+++
b/target/linux/generic/patches-4.0/091-mtd-spi-nor-add-support-for-the-Spansion_S25FL164K
@@ -0,0 +1,10 @@
+--- a/drivers/mtd/spi-nor/spi-nor.c
b/drivers/mtd/spi-nor/spi-nor.c
+@@ -573,6 +573,7 @@ static const struct spi_device_id spi_nor_ids[] = {
+ { "s25fl008k", INFO(0xef4014, 0, 64 * 1024, 16, SECT_4K) },
+ { "s25fl016k", INFO(0xef4015, 0, 64 * 1024, 32, SECT_4K) },
+ { "s25fl064k", INFO(0xef4017, 0, 64 * 1024, 128, SECT_4K) },
++ { "s25fl164k", INFO(0x014017, 0, 64 * 1024, 128, SECT_4K) },
+
+ /* SST -- large erase sizes are "overlays", "sectors" are 4K */
+ { "sst25vf040b", INFO(0xbf258d, 0, 64 * 1024, 8, SECT_4K | SST_WRITE)
},
diff --git
a/target/linux/generic/patches-4.1/091-mtd-spi-nor-add-support-for-the-Spansion_S25FL164K
b/target/linux/generic/patches-4.1/091-mtd-spi-nor-add-support-for-the-Spansion_S25FL164K
new file mode 100644
index 000..866567a
--- /dev/null
+++
b/target/linux/generic/patches-4.1/091-mtd-spi-nor-add-support-for-the-Spansion_S25FL164K
@@ -0,0 +1,10 @@
+--- a/drivers/mtd/spi-nor/spi-nor.c
b/drivers/mtd/spi-nor/spi-nor.c
+@@ -573,6 +573,7 @@ static const struct spi_device_id spi_nor_ids[] = {
+ { "s25fl008k", INFO(0xef4014, 0, 64 * 1024, 16, SECT_4K) },
+ { "s25fl016k", INFO(0xef4015, 0, 64 * 1024, 32, SECT_4K) },
+ { "s25fl064k", INFO(0xef4017, 0, 64 * 1024, 128, SECT_4K) },
++ { "s25fl164k", INFO(0x014017, 0, 64 * 1024, 128, SECT_4K) },
+
+ /* SST -- large erase sizes are "overlays", "sectors" are 4K */
+ { "sst25vf040b", INFO(0xbf258d, 0, 64 * 1024, 8, SECT_4K | SST_WRITE)
},
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH V4] linux:generic: mtd backport for Spansion S25FL164K
Backport for the Spansion S25FL164K
It's an 8 MiB flash with 4 KiB erase sectors.
Signed-off-by: L. D. Pinney
---
target/linux/generic/patches-3.18/091-mtd-spi-nor-add-support-for-the-Spansion_S25FL164K
| 12
target/linux/generic/patches-4.0/091-mtd-spi-nor-add-support-for-the-Spansion_S25FL164K
| 12
target/linux/generic/patches-4.1/091-mtd-spi-nor-add-support-for-the-Spansion_S25FL164K
| 12
3 files changed, 36 insertions(+)Backport for the Spansion S25FL164K
diff --git
a/target/linux/generic/patches-3.18/091-mtd-spi-nor-add-support-for-the-Spansion_S25FL164K
b/target/linux/generic/patches-3.18/091-mtd-spi-nor-add-support-for-the-Spansion_S25FL164K
new file mode 100644
index 000..c58269d
--- /dev/null
+++
b/target/linux/generic/patches-3.18/091-mtd-spi-nor-add-support-for-the-Spansion_S25FL164K
@@ -0,0 +1,12 @@
+Index: linux-3.18.16/drivers/mtd/spi-nor/spi-nor.c
+===
+--- linux-3.18.16.orig/drivers/mtd/spi-nor/spi-nor.c
linux-3.18.16/drivers/mtd/spi-nor/spi-nor.c
+@@ -570,6 +570,7 @@ static const struct spi_device_id spi_no
+ { "s25fl008k", INFO(0xef4014, 0, 64 * 1024, 16, SECT_4K) },
+ { "s25fl016k", INFO(0xef4015, 0, 64 * 1024, 32, SECT_4K) },
+ { "s25fl064k", INFO(0xef4017, 0, 64 * 1024, 128, SECT_4K) },
++ { "s25fl164k", INFO(0x014017, 0, 64 * 1024, 128, SECT_4K) },
+
+ /* SST -- large erase sizes are "overlays", "sectors" are 4K */
+ { "sst25vf040b", INFO(0xbf258d, 0, 64 * 1024, 8, SECT_4K | SST_WRITE)
},
diff --git
a/target/linux/generic/patches-4.0/091-mtd-spi-nor-add-support-for-the-Spansion_S25FL164K
b/target/linux/generic/patches-4.0/091-mtd-spi-nor-add-support-for-the-Spansion_S25FL164K
new file mode 100644
index 000..d0fa02e
--- /dev/null
+++
b/target/linux/generic/patches-4.0/091-mtd-spi-nor-add-support-for-the-Spansion_S25FL164K
@@ -0,0 +1,12 @@
+Index: linux-4.0.5/drivers/mtd/spi-nor/spi-nor.c
+===
+--- linux-4.0.5.orig/drivers/mtd/spi-nor/spi-nor.c
linux-4.0.5/drivers/mtd/spi-nor/spi-nor.c
+@@ -602,6 +602,7 @@ static const struct spi_device_id spi_no
+ { "s25fl016k", INFO(0xef4015, 0, 64 * 1024, 32, SECT_4K) },
+ { "s25fl064k", INFO(0xef4017, 0, 64 * 1024, 128, SECT_4K) },
+ { "s25fl132k", INFO(0x014016, 0, 64 * 1024, 64, 0) },
++ { "s25fl164k", INFO(0x014017, 0, 64 * 1024, 128, SECT_4K) },
+
+ /* SST -- large erase sizes are "overlays", "sectors" are 4K */
+ { "sst25vf040b", INFO(0xbf258d, 0, 64 * 1024, 8, SECT_4K | SST_WRITE)
},
diff --git
a/target/linux/generic/patches-4.1/091-mtd-spi-nor-add-support-for-the-Spansion_S25FL164K
b/target/linux/generic/patches-4.1/091-mtd-spi-nor-add-support-for-the-Spansion_S25FL164K
new file mode 100644
index 000..1f541a9
--- /dev/null
+++
b/target/linux/generic/patches-4.1/091-mtd-spi-nor-add-support-for-the-Spansion_S25FL164K
@@ -0,0 +1,12 @@
+Index: linux-4.1/drivers/mtd/spi-nor/spi-nor.c
+===
+--- linux-4.1.orig/drivers/mtd/spi-nor/spi-nor.c
linux-4.1/drivers/mtd/spi-nor/spi-nor.c
+@@ -618,6 +618,7 @@ static const struct spi_device_id spi_no
+ { "s25fl016k", INFO(0xef4015, 0, 64 * 1024, 32, SECT_4K) },
+ { "s25fl064k", INFO(0xef4017, 0, 64 * 1024, 128, SECT_4K) },
+ { "s25fl132k", INFO(0x014016, 0, 64 * 1024, 64, 0) },
++ { "s25fl164k", INFO(0x014017, 0, 64 * 1024, 128, SECT_4K) },
+
+ /* SST -- large erase sizes are "overlays", "sectors" are 4K */
+ { "sst25vf040b", INFO(0xbf258d, 0, 64 * 1024, 8, SECT_4K | SST_WRITE)
},
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] [generic] ramips: adding support for OYE-0001 Wireless Router
From: Tom Deng <2579131...@qq.com>
Adding support for OYE-0001 Wireless Router.
OYE-0001 is a wireless router made by oyewifi.com. Below is the details:
MT7620A, 128MB DDR2, 16MB FLASH, SD Slot, USB 2.0, 4 x LAN + 1 x WAN.
Signed-off-by: Tom Deng <2579131...@qq.com>
---
Index: target/linux/ramips/base-files/etc/diag.sh
===
--- target/linux/ramips/base-files/etc/diag.sh(revision 43797)
+++ target/linux/ramips/base-files/etc/diag.sh(working copy)
@@ -185,6 +185,9 @@
f7c027)
status_led="belkin:orange:status"
;;
+oye-0001)
+status_led="oye:green:wifi"
+;;
na930)
status_led="na930:blue:power"
;;
Index: target/linux/ramips/base-files/etc/uci-defaults/01_leds
===
--- target/linux/ramips/base-files/etc/uci-defaults/01_leds(revision 43797)
+++ target/linux/ramips/base-files/etc/uci-defaults/01_leds(working copy)
@@ -198,6 +198,10 @@
set_wifi_led "zbtlink:blue:air"
set_usb_led "zbtlink:blue:usb"
;;
+oye-0001)
+ucidef_set_led_default "power" "power" "oye:green:power" "1"
+set_wifi_led "oye:green:wifi"
+;;
wr8305rt)
ucidef_set_led_default "power" "power" "wr8305rt:sys" "1"
set_usb_led "wr8305rt:usb"
Index: target/linux/ramips/base-files/etc/uci-defaults/02_network
===
--- target/linux/ramips/base-files/etc/uci-defaults/02_network(revision
43797)
+++ target/linux/ramips/base-files/etc/uci-defaults/02_network(working
copy)
@@ -103,6 +103,7 @@
dir-615-h1 | \
hlk-rm04 | \
mzk-w300nh2 | \
+oye-0001 | \
mzk-750dhp)
ucidef_set_interfaces_lan_wan "eth0.1" "eth0.2"
ucidef_add_switch "switch0" "1" "1"
@@ -220,6 +221,11 @@
wan_mac=$(mtd_get_mac_binary devdata 7)
;;
+oye-0001)
+lan_mac=$(mtd_get_mac_binary factory 40)
+wan_mac=$(mtd_get_mac_binary factory 46)
+;;
+
w306r-v20)
lan_mac=$(cat /sys/class/net/eth0/address)
wan_mac=$(macaddr_add "$lan_mac" 5)
Index: target/linux/ramips/base-files/lib/ramips.sh
===
--- target/linux/ramips/base-files/lib/ramips.sh(revision 43797)
+++ target/linux/ramips/base-files/lib/ramips.sh(working copy)
@@ -322,6 +322,9 @@
*"Zbtlink ZBT-WA05")
name="zbt-wa05"
;;
+*"OYE-0001")
+name="oye-0001"
+;;
*"ZBT WR8305RT")
name="wr8305rt"
;;
Index: target/linux/ramips/base-files/lib/upgrade/platform.sh
===
--- target/linux/ramips/base-files/lib/upgrade/platform.sh(revision 43797)
+++ target/linux/ramips/base-files/lib/upgrade/platform.sh(working copy)
@@ -95,6 +95,7 @@
wmr300 |\
wr8305rt |\
wrtnode |\
+oye-0001 |\
x5 |\
x8 |\
zbt-wa05 |\
Index: target/linux/ramips/dts/OYE-0001.dts
===
--- target/linux/ramips/dts/OYE-0001.dts(revision 0)
+++ target/linux/ramips/dts/OYE-0001.dts(revision 0)
@@ -0,0 +1,123 @@
+/dts-v1/;
+
+/include/ "mt7620a.dtsi"
+
+/ {
+compatible = "ralink,mt7620a-soc";
+model = "OYE-0001";
+
+chosen {
+bootargs = "console=ttyS0,115200";
+};
+
+palmbus@1000 {
+gpio2: gpio@660 {
+status = "okay";
+};
+
+gpio3: gpio@688 {
+status = "okay";
+};
+
+spi@b00 {
+status = "okay";
+
+m25p80@0 {
+#address-cells = <1>;
+#size-cells = <1>;
+compatible = "w25q128";
+reg = <0 0>;
+linux,modalias = "m25p80", "w25q128";
+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 0xfb>;
+};
+
+};
+};
+};
+
+pinctrl {
+state_default: pinctrl0 {
+gpio {
+ralink,group
