Re: [OpenWrt-Devel] [PATCH 0/2] Initial 11ac support using ath10k
(resending my mail due to a stupid rule in ath10k-devel, I need to be subcribed before posting to that list) Hi Sven, adding ath...@lists.infradead.org. Sven Eckelmann s...@open-mesh.com writes: Hi, support for ath10k cards was added a while ago to OpenWrt. Unfortunately, the actual 802.11ac support was never added (patches on the mailing lists were just ignored). This is a rather unpleasant situation when trying to get some 11ac test hardware working. Yeah, it would be great to get proper ath10k support to OpenWrt. Thanks for working on this! I've picked up the patches and rebased them on top of the current master branch/trunk. Where did you take the ath10k patches? ath10k is under heavy development, so I strongly recommend taking patches directly from ath-next branch of my ath.git. That way you would be using the latest and greatest. Just as general information to the state of ath10k, my current test showed some problems with it: * Samsung GT-I9300 only got horrible slow connections to an QCA9880 but an Intel N6205 (using iwlwifi from v3.12) or Samsung S4 worked fine Could you report the I9300 issue to the ath10k list with more details, please? We can try to investigate it. * Adhoc mode doesn't work at all That was with 10.1 firmware? AFAIK it doesn't support adhoc at all. I think we need to add a firmware feature flag to disable adhoc with that firmware. * TX bitrate information is bogus (iw XXX station dump) Yeah, this is annoying. But firmware doesn't report this to the host at all so there is not much ath10k can do right now. But I'll send a query to the firmware team if they could provide that information to ath10k. * Crashed relative often on reconfiguration: Data bus error, epc 87b7a864, ra 87b7a864 On some QCA988x boards cold reset seems to cause problems on the PCI bus. We are investigating this. * Sometimes adding of station seems to fail: ath10k: Failed to add peer 5c:0a:5b:4e:6a:c4 for vdev 1 when adding a new sta: -145 This is new to me. Can you report this to the ath10k list, please? * Adhoc interface + iw dev wlan0 scan trigger just crashes the firmware: [ 296.16] ath10k: firmware crashed! [ 296.17] ath10k: hardware name qca988x hw2.0 version 0x4100016c [ 296.17] ath10k: firmware version: 65.467.0.0 What firmware version was this? The version printed here seems to be corrupted. -- Kalle Valo ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [OpenWrt-Devel, PATCH:, kernel, CONFIG:, kernel] OpenWRT for Raspberry PI - second version
Hello, On 17/01/2014 19:27, Oskari Rauta wrote: Hi. I previously provided a patch for OpenWrt that enabled use of kernel 3.12.2y which is a raspberry pi specific kernel. Patch was a huge blob, 8 megabytes and was not integrated to mainstream. What that patch did, was that it converted vanilla kernel from kernel.org of version 3.12.2 to 3.12.2y. Now I have made a new patch with high hopes of it being integrated into OpenWrt. It isn't as big anymore and it enables kernel version 3.12.7y for brcm2708 target. This time, I made it to download already patched version of 3.12.7y directly from official raspberry pi kernel repository. Maybe I'm missing the point, but 3.12.2y is still a 3.12.2 kernel with some added patches. There is no reason to handle this version like another kernel version, force all bcm2708 devices to use this kernel (Raspi may be the biggest provider for bcm2708 powerd board, it doesn't mean they are the only one) and so on. The fact that the current trunk build binaries for the raspi doesn't mean it targets only the raspi. There might be some better thing to do - as of today, it's possisble to have patches for a specific architecture - maybe you can take advantage of this, or maybe the OpenWRT makefiles should allow the possibility to propose patches for a specific arch profile. Best regards, -- Emmanuel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] LuCI: remove pages/nodes based on logged in user
Hi. At the first sight the problem is solved: you open System tab and you don't see LED Configuration option, but as soon as you select one of the System's tabs all hidden tabs appear. How can I remove the tab permanently for the current session? Why removing the tab from tree (c, contect.dispatch) is not enough? I see no easy way to do that. The least invasive solution would be simply not rendering specific menu points in the active theme's header.htm depending on the value of luci.dispatcher.context.authuser. Note that this will only cosmetically disable tabs, direct access by manipulating the url would be still possible. Kiran has proposed some questions, that could lead to the solution of the problem, but I can't answe them myself so far: Are we sure that c (variable containing the tree) is the only source from which the page is rendered? It is. Is the c created from the file or the cache. It is built by the cached index() functions from the controller files. Is it created from the file for the first time and then from the cache on consequent accesses? The tree is never cached, only the functions building it are cached. Why is it changing when I access different tabs? To cut down the amount of required processing work, only the subtree of the current location is processed - see http://luci.subsignal.org/trac/ticket/288 Is the c tree created even when sauth.user is empty? Yes. why? First of all, because one can have public menus / pages. Furthermore the tree is built before the login state is even determined, the authentication level is defined in the tree so you cannot perform auth before the tree is built in order to influence the tree layout depending on the auth, chicken-egg problem. Is this structure cached then? No. what is the difference between context.tree and context.treecache. context.treecache is a weak temporary scratch table used to hold implicitely created node objects during the tree building. . Can we use it for access restriction? No. ~ Jow signature.asc Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] ar71xx: Add platform machine support for the Netgear WNDR3700v4
This patch adds platform machine support for the Netgear WNDR3700v4.
Signed-off-by: Ralph Perlich rps...@arcor.de
--- a/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
+++ b/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
@@ -218,6 +218,7 @@ mynet-n750)
;;
dir-835-a1 |\
+wndr3700-v4 |\
wndr4300)
ucidef_set_interfaces_lan_wan eth0.1 eth0.2
ucidef_add_switch switch0 1 1
--- a/target/linux/ar71xx/base-files/lib/ar71xx.sh
+++ b/target/linux/ar71xx/base-files/lib/ar71xx.sh
@@ -558,6 +558,9 @@ ar71xx_board_detect() {
*WNDAP360)
name=wndap360
;;
+ *WNDR3700V4)
+ name=wndr3700-v4
+ ;;
*WNDR3700/WNDR3800/WNDRMAC)
wndr3700_board_detect $machine
;;
--- a/target/linux/ar71xx/config-3.10
+++ b/target/linux/ar71xx/config-3.10
@@ -98,6 +98,7 @@ CONFIG_ATH79_MACH_WLAE_AG300N=y
CONFIG_ATH79_MACH_WLR8100=y
CONFIG_ATH79_MACH_WNDAP360=y
CONFIG_ATH79_MACH_WNDR3700=y
+CONFIG_ATH79_MACH_WNDR3700_V4=y
CONFIG_ATH79_MACH_WNDR4300=y
CONFIG_ATH79_MACH_WNR2000=y
CONFIG_ATH79_MACH_WNR2000_V3=y
--- a/target/linux/ar71xx/base-files/etc/diag.sh
+++ b/target/linux/ar71xx/base-files/etc/diag.sh
@@ -187,6 +187,7 @@ get_status_led() {
;;
wndap360 | \
wndr3700 | \
+ wndr3700-v4 | \
wndr4300 | \
wnr2000 | \
wnr2200 |\
--- a/target/linux/ar71xx/image/Makefile
+++ b/target/linux/ar71xx/image/Makefile
@@ -218,6 +218,7 @@ wnr2200_mtdlayout=mtdparts=spi0.0:320k(u
wnr2000v3_mtdlayout=mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,3712k(firmware),64k(art)ro
wndr3700_mtdlayout=mtdparts=spi0.0:320k(u-boot)ro,128k(u-boot-env)ro,7680k(firmware),64k(art)ro
wndr3700v2_mtdlayout=mtdparts=spi0.0:320k(u-boot)ro,128k(u-boot-env)ro,15872k(firmware),64k(art)ro
+wndr3700v4_mtdlayout=mtdparts=ar934x-nfc:256k(u-boot)ro,256k(u-boot-env)ro,256k(caldata),512k(pot),2048k(language),512k(config),3072k(traffic_meter),2048k(kernel),23552k(ubiroot),25600k@0x6c(firmware),256k(caldata_backup),-(reserved)
ubi.mtd=ubiroot
wndr4300_mtdlayout=mtdparts=ar934x-nfc:256k(u-boot)ro,256k(u-boot-env)ro,256k(caldata),512k(pot),2048k(language),512k(config),3072k(traffic_meter),2048k(kernel),23552k(ubiroot),25600k@0x6c(firmware),256k(caldata_backup),-(reserved)
ubi.mtd=ubiroot
zcn1523h_mtdlayout=mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,6208k(rootfs),1472k(kernel),64k(configure)ro,64k(mfg)ro,64k(art)ro,7680k@0x5(firmware)
mynet_n600_mtdlayout=mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,64k(devdata)ro,64k(devconf)ro,15872k(firmware),64k(radiocfg)ro
@@ -1081,6 +1082,7 @@ endif # ifeq ($(SUBTARGET),generic)
ifeq ($(SUBTARGET),nand)
$(eval $(call
SingleProfile,NetgearNAND,64k,WNDR4300,wndr4300,WNDR4300,ttyS0,115200,$$(wndr4300_mtdlayout),0x33373033,WNDR4300,,-H
29763948+0+128+128+2x2+3x3))
+$(eval $(call
SingleProfile,NetgearNAND,64k,WNDR3700_V4,wndr3700v4,WNDR3700V4,ttyS0,115200,$$(wndr3700v4_mtdlayout),0x33373033,WNDR3700V4,,-H
29763948+128+128))
endif # ifeq ($(SUBTARGET),nand)
--- /dev/null
+++ b/target/linux/ar71xx/image/ubinize-wndr3700v4.ini
@@ -0,0 +1,27 @@
+[rootfs]
+# Volume mode (other option is static)
+mode=ubi
+# Source image
+image=root.squashfs
+# Volume ID in UBI image
+vol_id=0
+# Allow for dynamic resize
+vol_type=dynamic
+# Volume name
+vol_name=rootfs
+# Autoresize volume at first mount
+# vol_flags=autoresize
+
+[rootfs_data]
+# Volume mode (other option is static)
+mode=ubi
+# Source image
+image=jffs2.eof
+# Volume ID in UBI image
+vol_id=1
+# Allow for dynamic resize
+vol_type=dynamic
+# Volume name
+vol_name=rootfs_data
+# Autoresize volume at first mount
+vol_flags=autoresize
--- a/target/linux/ar71xx/nand/profiles/netgear.mk
+++ b/target/linux/ar71xx/nand/profiles/netgear.mk
@@ -16,4 +16,13 @@ endef
$(eval $(call Profile,WNDR4300))
+define Profile/WNDR3700_V4
+ NAME:=NETGEAR WNDR3700 V4
+ PACKAGES:=kmod-usb-core kmod-usb-ohci kmod-usb2 kmod-ledtrig-usbdev
+endef
+define Profile/WNDR3700_V4/Description
+ Package set optimized for the NETGEAR WNDR3700 V4
+endef
+
+$(eval $(call Profile,WNDR3700_V4))
--- /dev/null
+++
b/target/linux/ar71xx/patches-3.10/705-MIPS-ath79-WNDR3700V4-support.patch
@@ -0,0 +1,40 @@
+--- a/arch/mips/ath79/Kconfig
b/arch/mips/ath79/Kconfig
+@@ -441,6 +441,17 @@ config ATH79_MACH_WNDR3700
+ select ATH79_DEV_M25P80
+ select ATH79_DEV_USB
+
++config ATH79_MACH_WNDR3700_V4
++ bool NETGEAR WNDR3700 V4 board support
++ select SOC_AR934X
++ select ATH79_DEV_AP9X_PCI if PCI
++ select ATH79_DEV_ETH
++ select ATH79_DEV_GPIO_BUTTONS
++ select ATH79_DEV_LEDS_GPIO
++ select ATH79_DEV_NFC
++ select ATH79_DEV_USB
++ select ATH79_DEV_WMAC
++
+ config ATH79_MACH_WNDR4300
+ bool NETGEAR WNDR4300 board support
+ select SOC_AR934X
+--- a/arch/mips/ath79/Makefile
b/arch/mips/ath79/Makefile
[OpenWrt-Devel] nfs mount
Can any get a remote nfs volume to mount from openwrt on git head? I've been playing with it for a few days and can't get it to work. The nfs exports are ok and work from other machines. root@OpenWrt:/# mount -t nfs 192.168.1.40:/export/work /mnt mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd. mount.nfs: mounting 192.168.1.40:/export/work failed, reason given by server: No such file or directory mount: mounting 192.168.1.40:/export/work on /mnt failed: Invalid argument root@OpenWrt:/# mount -t nfs -o nolock 192.168.1.40:/export/work /mnt mount.nfs: Connection timed out mount: mounting 192.168.1.40:/export/work on /mnt failed: Invalid argument root@OpenWrt:/# -- Jon Smirl jonsm...@gmail.com ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
