Re: [OpenWrt-Devel] Help with SysupgradeNAND
On 10/07/2014 08:27, Ben Mulvihill wrote: > On Wed, 2014-07-09 at 16:27 +0200, Daniel Golle wrote: >> On Wed, Jul 09, 2014 at 04:10:52PM +0200, Ben Mulvihill wrote: JFFS2 works on bare MTD devices (originally NOR only, hackish NAND support exists in the wild though YAFFS2 is more commonly used). UBIFS is the only read-write filesystem which works on top of UBI, thus the only possible choice for overlay support. >>> >>> Not the only possibility surely? Currently we generate two >>> images for the BTHOMEHUBV2B. Both use ubi. One has pure ubifs >>> on top. The other has a squashfs/jffs2 overlay making use of >>> gluebi. Everything works apart from sysupgrade but the only >>> reason for doing things that way was that it was a natural >>> progression from the pre-ubi arrangement and it worked out of >>> the box. A squashfs/ubifs overlay is certainly cleaner. I'll >>> see what I need to do to get it working. >> >> Ah, ok, now I understand the question :) And yes, you should use >> squashfs/ubifs for overlay and disable gluebi alltogether. gluebi >> is deprectated and was meant only for transition. ubiblock offers >> a much cleaner way for read-only filesystems and UBIFS makes much >> more sense than jffs2-on-gluebi. > > The penny has finally dropped! When I first made images using the > new ubi support a few weeks ago the squashfs/jffs2 gluebi overlay > worked out of the box, and the squashfs/ubifs overlay did not. I > assumed I would have to generate the squashfs images for the latter > case in some special way, preformatting an empty ubifs partition > perhaps, or adding some magic to tell the kernel to mount > rootfs_data as ubifs. I have just realised that the images work > fine as they are, as long as the gluebi/mtd code doesn't get there > first and attempt a jffs2 mount. So all that needs to be done to > move over to a squashfs/ubifs overlay is to disable gluebi in the > kernel configuration. I should like to ask John whether he would be > happy for me to submit a patch to do that, on xway at least, not on > xrx200 to avoid affecting the other lantiq nand boards? sorry i should have mentioned this. "gluebi is dead, long life ubiblock !!!" we backported ubiblock from 3.15, it allows raw r/o access to the squash. ubifs runs without intermediate gluebi/mtd layer, thus making the whole setup much simpler. from what i understand, ubiblock will obsolete gluebi in upstream so we decided to switch early. this should be done for xway and xrx200. John > > Or would it be better to find some way of enabling the > volume_identify code in procd to distinguish a jffs2 rootfs_data > from a ubifs rootfs_data. just in case in the future someone needs > gluebi in the kernel for some other reason? > > Thank you > > Ben > > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Status of DFS in OpenWrt -> ath9k
Hi, > for me it seems that DFS is broken in current trunk for ath9k. > I use trunk and compiled ar71xx. With the following configuration on a > Ubiquity Nanostation locoM5 > > - > config wifi-device 'radio0' > option type 'mac80211' > option hwmode '11na' > option path 'pci:00/:00:00.0' > option htmode 'HT20' > option country 'DE' > option channel '104' > option txpower '20' > > config wifi-iface > option device 'radio0' > option encryption 'none' > option network 'wifi' > option mode 'ap' > option ssid 'OpenWRT' > option ifname 'wlan0' > - > > All DFS channel attempts fail with > start_dfs_cac() failed, -1 At least on r40878 and ath10k DFS is currently working. The only difference in my config compared to yours is option hwmode '11a' (11na is obsolete). CONFIG_PACKAGE_ATH_DFS and CONFIG_ATH_USER_REGD are enabled, otherwise default build settings. Matti ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] iptables: NFLOG and NFQUEUE targets' full support
NFLOG and NFQUEUE targets' full support for iptables. Includes all needed kernel modules (Xtables's and Netlink's) and userspace libraries. All added kernel modules can be individually disabled, all other new libraries get their own individual packages. Reported-by: Fabian Hugelshofer Reported-by: Rainer Poisel Reported-by: Derek LaHousse Signed-off-by: Guillaume Déflache --- This patch merges the work from: - ddx0n which got initially submitted in 2011 as patch in ticket #9969 and completed with the kmod-ipt-nfqueue module by me - Fabian Hugelshofer he initially submitted in 2008 as patch on openwrt-devel which... - ...Rainer Poisel reworked and resend there in 2010 which... - ...Derek LaHousse reworked and resend there in 2013 (!). I hope all this work can be finally submitted. Please be kind as this is my first OpenWrt patch! include/netfilter.mk | 29 package/kernel/linux/modules/netfilter.mk | 58 +-- package/network/utils/iptables/Makefile | 28 +++ 3 files changed, 105 insertions(+), 10 deletions(-) diff --git a/include/netfilter.mk b/include/netfilter.mk index 906eb0f..c6d5322 100644 --- a/include/netfilter.mk +++ b/include/netfilter.mk @@ -224,6 +224,16 @@ $(eval $(call nf_add,IPT_QUEUE,CONFIG_IP_NF_QUEUE, $(P_V4)ip_queue, lt 3.5.0)) $(eval $(call nf_add,IPT_ULOG,CONFIG_IP_NF_TARGET_ULOG, $(P_V4)ipt_ULOG)) +# nflog + +$(eval $(call nf_add,IPT_NFLOG,CONFIG_NETFILTER_XT_TARGET_NFLOG, $(P_XT)xt_NFLOG)) + + +# nfqueue + +$(eval $(call nf_add,IPT_NFQUEUE,CONFIG_NETFILTER_XT_TARGET_NFQUEUE, $(P_XT)xt_NFQUEUE)) + + # debugging $(eval $(call nf_add,IPT_DEBUG,CONFIG_NETFILTER_XT_TARGET_TRACE, $(P_XT)xt_TRACE)) @@ -244,6 +254,21 @@ $(eval $(call nf_add,IPT_TEE,CONFIG_NETFILTER_XT_TARGET_TEE, $(P_XT)xt_TEE)) $(eval $(call nf_add,IPT_U32,CONFIG_NETFILTER_XT_MATCH_U32, $(P_XT)xt_u32)) + +# netlink + +$(eval $(call nf_add,NFNETLINK,CONFIG_NETFILTER_NETLINK, $(P_XT)nfnetlink)) + +# nflog + +$(eval $(call nf_add,NFNETLINK_LOG,CONFIG_NETFILTER_NETLINK_LOG, $(P_XT)nfnetlink_log)) +$(eval $(call nf_add,NFNETLINK_LOG,CONFIG_NETFILTER_XT_TARGET_NFLOG, $(P_XT)xt_NFLOG)) + +# nfqueue + +$(eval $(call nf_add,NFNETLINK_QUEUE,CONFIG_NETFILTER_NETLINK_QUEUE, $(P_XT)nfnetlink_queue)) +$(eval $(call nf_add,NFNETLINK_QUEUE,CONFIG_NETFILTER_XT_TARGET_NFQUEUE, $(P_XT)xt_NFQUEUE)) + # # ebtables # @@ -278,6 +303,7 @@ $(eval $(call nf_add,EBTABLES_IP4,CONFIG_BRIDGE_EBT_SNAT, $(P_EBT)ebt_snat)) $(eval $(call nf_add,EBTABLES_WATCHERS,CONFIG_BRIDGE_EBT_LOG, $(P_EBT)ebt_log)) $(eval $(call nf_add,EBTABLES_WATCHERS,CONFIG_BRIDGE_EBT_ULOG, $(P_EBT)ebt_ulog)) $(eval $(call nf_add,EBTABLES_WATCHERS,CONFIG_BRIDGE_EBT_NFLOG, $(P_EBT)ebt_nflog)) +$(eval $(call nf_add,EBTABLES_WATCHERS,CONFIG_BRIDGE_EBT_NFQUEUE, $(P_EBT)ebt_nfqueue)) # userland only @@ -298,6 +324,9 @@ IPT_BUILTIN += $(IPT_NATHELPER_EXTRA-y) IPT_BUILTIN += $(IPT_ULOG-y) IPT_BUILTIN += $(IPT_DEBUG-y) IPT_BUILTIN += $(IPT_TPROXY-y) +IPT_BUILTIN += $(NFNETLINK-y) +IPT_BUILTIN += $(NFNETLINK_LOG-y) +IPT_BUILTIN += $(NFNETLINK_QUEUE-y) IPT_BUILTIN += $(EBTABLES-y) IPT_BUILTIN += $(EBTABLES_IP4-y) IPT_BUILTIN += $(EBTABLES_IP6-y) diff --git a/package/kernel/linux/modules/netfilter.mk b/package/kernel/linux/modules/netfilter.mk index 316df69..4901b04 100644 --- a/package/kernel/linux/modules/netfilter.mk +++ b/package/kernel/linux/modules/netfilter.mk @@ -278,6 +278,40 @@ endef $(eval $(call KernelPackage,ipt-ulog)) +define KernelPackage/ipt-nflog + TITLE:=Module for user-space packet logging + KCONFIG:=$(KCONFIG_IPT_NFLOG) + FILES:=$(foreach mod,$(IPT_NFLOG-m),$(LINUX_DIR)/net/$(mod).ko) + AUTOLOAD:=$(call AutoLoad,45,$(notdir $(IPT_NFLOG-m))) + $(call AddDepends/ipt,+kmod-nfnetlink-log) +endef + +define KernelPackage/ipt-nflog/description + Netfilter module for user-space packet logging + Includes: + - NFLOG +endef + +$(eval $(call KernelPackage,ipt-nflog)) + + +define KernelPackage/ipt-nfqueue + TITLE:=Module for user-space packet queuing + KCONFIG:=$(KCONFIG_IPT_NFQUEUE) + FILES:=$(foreach mod,$(IPT_NFQUEUE-m),$(LINUX_DIR)/net/$(mod).ko) + AUTOLOAD:=$(call AutoLoad,45,$(notdir $(IPT_NFQUEUE-m))) + $(call AddDepends/ipt,+kmod-nfnetlink-queue) +endef + +define KernelPackage/ipt-nfqueue/description + Netfilter module for user-space packet queuing + Includes: + - NFQUEUE +endef + +$(eval $(call KernelPackage,ipt-nfqueue)) + + define KernelPackage/ipt-debug TITLE:=Module for debugging/development KCONFIG:=$(KCONFIG_IPT_DEBUG) @@ -530,10 +564,10 @@ $(eval $(call KernelPackage,ebtables-watchers)) define KernelPackage/nfnetlink SUBMENU:=$(NF_MENU) TITLE:=Netlink-based userspace interface - DEPENDS:=+kmod-ipt-core - FILES:=$(LINUX_DIR)/net/netfilter/nfnetlink.ko - KCONFIG:=CONFIG_NETFILTER_NETLINK - AUTOLOAD:=$(call AutoProbe,nfnetlink) + FILES:=$(foreach mod,$(NFNETLINK-m),$(LINUX_DIR)/net/$(mod).ko) + KCONFIG:=$(K
[OpenWrt-Devel] [PATCH] mac80211: Fix config variable name for dtim_period
From: Sven Eckelmann
The vif option dtim_period was accidently renamed dtim_interval in r38988
("netifd: add wireless configuration support and port mac80211 to the new
framework"). This is wrong and makes the dtim_period/dtim_interval a dead
option because the rest of the config generation code still uses dtim_period.
Reported-by: Jeppe Ledet-Pedersen
Signed-off-by: Sven Eckelmann
---
package/kernel/mac80211/files/lib/netifd/wireless/mac80211.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/kernel/mac80211/files/lib/netifd/wireless/mac80211.sh
b/package/kernel/mac80211/files/lib/netifd/wireless/mac80211.sh
index a9f9db1..64b0f98 100644
--- a/package/kernel/mac80211/files/lib/netifd/wireless/mac80211.sh
+++ b/package/kernel/mac80211/files/lib/netifd/wireless/mac80211.sh
@@ -53,7 +53,7 @@ drv_mac80211_init_iface_config() {
config_add_boolean wds powersave
config_add_int maxassoc
config_add_int max_listen_int
- config_add_int dtim_interval
+ config_add_int dtim_period
# mesh
config_add_string mesh_id
--
2.0.1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] mac80211: Fix config variable name for dtim_period
On 2014-07-10 13:59, s...@open-mesh.com wrote:
> From: Sven Eckelmann
>
> The vif option dtim_period was accidently renamed dtim_interval in r38988
> ("netifd: add wireless configuration support and port mac80211 to the new
> framework"). This is wrong and makes the dtim_period/dtim_interval a dead
> option because the rest of the config generation code still uses dtim_period.
>
> Reported-by: Jeppe Ledet-Pedersen
> Signed-off-by: Sven Eckelmann
Applied in r41557, thanks.
- Felix
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] There ar some strange things in bb
After compression of the rootfs, there is a failure. ... mcopy -i /home/smilebef/Downloads/OpenWRT/openwrt/build_dir/target-arm_arm1176jzf-s+vfp_uClibc-0.9.33.2_eabi/linux-brcm2708/boot.img /home/smilebef/Downloads/OpenWRT/openwrt/build_dir/target-arm_arm1176jzf-s+vfp_uClibc-0.9.33.2_eabi/linux-brcm2708/Image ::kernel.img # Copy OpenWrt built kernel ./gen_rpi_sdcard_img.sh /home/smilebef/Downloads/OpenWRT/openwrt/bin/brcm2708/openwrt-brcm2708-sdcard-vfat-squashfs.img /home/smilebef/Downloads/OpenWRT/openwrt/build_dir/target-arm_arm1176jzf-s+vfp_uClibc-0.9.33.2_eabi/linux-brcm2708/boot.img /home/smilebef/Downloads/OpenWRT/openwrt/build_dir/target-arm_arm1176jzf-s+vfp_uClibc-0.9.33.2_eabi/linux-brcm2708/root.squashfs 20 + '[' 4 == 5 ']' + echo 'SYNTAX: ./gen_rpi_sdcard_img.sh ' SYNTAX: ./gen_rpi_sdcard_img.sh + exit 1 Makefile:40: recipe for target 'install' failed make[5]: *** [install] Error 1 make[5]: Leaving directory '/home/smilebef/Downloads/OpenWRT/openwrt/target/linux/brcm2708/image' Makefile:30: recipe for target 'install' failed make[4]: *** [install] Error 2 make[4]: Leaving directory '/home/smilebef/Downloads/OpenWRT/openwrt/target/linux/brcm2708' Makefile:13: recipe for target 'install' failed make[3]: *** [install] Error 2 make[3]: Leaving directory '/home/smilebef/Downloads/OpenWRT/openwrt/target/linux' target/Makefile:21: recipe for target 'target/linux/install' failed make[2]: *** [target/linux/install] Error 2 make[2]: Leaving directory '/home/smilebef/Downloads/OpenWRT/openwrt' target/Makefile:17: recipe for target '/home/smilebef/Downloads/OpenWRT/openwrt/staging_dir/target-arm_arm1176jzf-s+vfp_uClibc-0.9.33.2_eabi/stamp/.target_install' failed make[1]: *** [/home/smilebef/Downloads/OpenWRT/openwrt/staging_dir/target-arm_arm1176jzf-s+vfp_uClibc-0.9.33.2_eabi/stamp/.target_install] Error 2 make[1]: Leaving directory '/home/smilebef/Downloads/OpenWRT/openwrt' /home/smilebef/Downloads/OpenWRT/openwrt/include/toplevel.mk:169: recipe for target 'world' failed make: *** [world] Error 2 smilebef@Vigor18:~/Downloads/OpenWRT/openwrt$ Any ideas? Thanks ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] There ar some strange things in bb
Hi, i just checked the BB builder and the rpi images get built there. are you testing on HEAD ? John On 10/07/2014 17:10, smile...@gmail.com wrote: > After compression of the rootfs, there is a failure. > > > > > > ... mcopy -i > /home/smilebef/Downloads/OpenWRT/openwrt/build_dir/target-arm_arm1176jzf-s+vfp_uClibc-0.9.33.2_eabi/linux-brcm2708/boot.img > /home/smilebef/Downloads/OpenWRT/openwrt/build_dir/target-arm_arm1176jzf-s+vfp_uClibc-0.9.33.2_eabi/linux-brcm2708/Image > ::kernel.img # Copy OpenWrt built kernel ./gen_rpi_sdcard_img.sh > /home/smilebef/Downloads/OpenWRT/openwrt/bin/brcm2708/openwrt-brcm2708-sdcard-vfat-squashfs.img > /home/smilebef/Downloads/OpenWRT/openwrt/build_dir/target-arm_arm1176jzf-s+vfp_uClibc-0.9.33.2_eabi/linux-brcm2708/boot.img > /home/smilebef/Downloads/OpenWRT/openwrt/build_dir/target-arm_arm1176jzf-s+vfp_uClibc-0.9.33.2_eabi/linux-brcm2708/root.squashfs > 20 + '[' 4 == 5 ']' + echo 'SYNTAX: ./gen_rpi_sdcard_img.sh >' SYNTAX: > ./gen_rpi_sdcard_img.sh > + exit 1 Makefile:40: recipe for target > 'install' failed make[5]: *** [install] Error 1 make[5]: Leaving > directory > '/home/smilebef/Downloads/OpenWRT/openwrt/target/linux/brcm2708/image' > > Makefile:30: recipe for target 'install' failed > make[4]: *** [install] Error 2 make[4]: Leaving directory > '/home/smilebef/Downloads/OpenWRT/openwrt/target/linux/brcm2708' > Makefile:13: recipe for target 'install' failed make[3]: *** > [install] Error 2 make[3]: Leaving directory > '/home/smilebef/Downloads/OpenWRT/openwrt/target/linux' > target/Makefile:21: recipe for target 'target/linux/install' > failed make[2]: *** [target/linux/install] Error 2 make[2]: Leaving > directory '/home/smilebef/Downloads/OpenWRT/openwrt' > target/Makefile:17: recipe for target > '/home/smilebef/Downloads/OpenWRT/openwrt/staging_dir/target-arm_arm1176jzf-s+vfp_uClibc-0.9.33.2_eabi/stamp/.target_install' > failed make[1]: *** > [/home/smilebef/Downloads/OpenWRT/openwrt/staging_dir/target-arm_arm1176jzf-s+vfp_uClibc-0.9.33.2_eabi/stamp/.target_install] > Error 2 make[1]: Leaving directory > '/home/smilebef/Downloads/OpenWRT/openwrt' > /home/smilebef/Downloads/OpenWRT/openwrt/include/toplevel.mk:169: > recipe for target 'world' failed make: *** [world] Error 2 > smilebef@Vigor18:~/Downloads/OpenWRT/openwrt$ > > > Any ideas? > > Thanks ___ > 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] OpenWRT on the Ubiquiti airGateway
Hello, can someone test and make patch for trunk or stable openwrt on Ubiquiti AirGateway. We are looking for small cheap boxes like this with capability of openvpn. Thanks for help. Best regards, Jakub Janco ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] lantiq xway: disable gluebi and enable ubiblock
Disables gluebi and enables ubiblock on lantiq xway. Squashfs images on nand use ubifs instead of jffs2 for the overlay. I'll leave the equivalent patch for xrx200 to someone who has a board to test. Signed-off-by: Ben Mulvihill --- --- a/target/linux/lantiq/xway/config-default 2014-07-10 19:14:11.835361151 +0200 +++ b/target/linux/lantiq/xway/config-default 2014-07-10 03:05:48.519946416 +0200 @@ -29,8 +29,9 @@ CONFIG_MTD_NAND_XWAY=y CONFIG_MTD_SPLIT_UIMAGE_FW=y CONFIG_MTD_UBI=y CONFIG_MTD_UBI_BEB_LIMIT=20 +CONFIG_MTD_UBI_BLOCK=y # CONFIG_MTD_UBI_FASTMAP is not set -CONFIG_MTD_UBI_GLUEBI=y +# CONFIG_MTD_UBI_GLUEBI is not set CONFIG_MTD_UBI_WL_THRESHOLD=4096 CONFIG_NLS=y # CONFIG_PROC_DEVICETREE is not set @@ -57,4 +58,3 @@ CONFIG_USB_SUPPORT=y # CONFIG_XRX200_PHY_FW is not set CONFIG_ZLIB_DEFLATE=y CONFIG_ZLIB_INFLATE=y -# CONFIG_MTD_UBI_BLOCK is not set ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] lantiq: enable SysupgradeNAND for BTHOMEHUBV2B
Enables SysupgradeNAND for BTHOMEHUBV2B.
Depends on the following patches:
http://patchwork.openwrt.org/patch/5817/
http://patchwork.openwrt.org/patch/5848/
http://patchwork.openwrt.org/patch/5851/
Many thanks everyone for your help the last couple of days.
Ben
Signed-off-by: Ben Mulvihill
---
--- a/target/linux/lantiq/base-files/lib/upgrade/platform.sh2014-07-09
08:07:29.682202944 +0200
+++ b/target/linux/lantiq/base-files/lib/upgrade/platform.sh2014-07-09
08:19:19.990740981 +0200
@@ -1,7 +1,17 @@
+. /lib/functions/lantiq.sh
+
PART_NAME=firmware
platform_check_image() {
[ "$#" -gt 1 ] && return 1
+ local board=$(lantiq_board_name)
+
+ case "$board" in
+ BTHOMEHUBV2B )
+ nand_do_platform_check $board $1
+ return $?;
+ ;;
+ esac
case "$(get_magic_word "$1")" in
# uImage
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Porting OpenWRT to Buffalo WZR-1750DHP
Hi all, I have a Buffalo WZR-1750DHP and I would like some one to help me porting OpenWRT to this hardware. Any help would be appreciated. If someone has already started doing the port, I can help doing some tests too. Regards -- Ronaldo Afonso 11 9 5252 0484 www.ronaldoafonso.com.br ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Status of DFS in OpenWrt -> ath9k
On 7/10/14, 9:47 AM, Matti Laakso wrote: > Hi, > >> for me it seems that DFS is broken in current trunk for ath9k. >> I use trunk and compiled ar71xx. With the following configuration on a >> Ubiquity Nanostation locoM5 >> >> - >> config wifi-device 'radio0' >> option type 'mac80211' >> option hwmode '11na' >> option path 'pci:00/:00:00.0' >> option htmode 'HT20' >> option country 'DE' >> option channel '104' >> option txpower '20' >> >> config wifi-iface >> option device 'radio0' >> option encryption 'none' >> option network 'wifi' >> option mode 'ap' >> option ssid 'OpenWRT' >> option ifname 'wlan0' >> - >> >> All DFS channel attempts fail with >> start_dfs_cac() failed, -1 > > > At least on r40878 and ath10k DFS is currently working. The only Okay, I updated ones again my trunk git and now everything works as expected. Very good. Thanks, Martin > difference in my config compared to yours is > > option hwmode '11a' > > (11na is obsolete). CONFIG_PACKAGE_ATH_DFS and CONFIG_ATH_USER_REGD are > enabled, otherwise default build settings. > > Matti > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Status of DFS in OpenWrt -> ath9k
On 7/8/14, 12:20 AM, Andre Valentin wrote: > Hi! > > this should also be in your .config > # CONFIG_ATH_USER_REGD is not set > See http://wireless.kernel.org/en/users/Drivers/ath10k -> Limitations 3/3 What does it mean exactly? For ath9k the option CONFIG_PACKAGE_ATH_DFS needs to be set. For ath10k this option must not be set? Regards, Martin > > Kind regards, > > André > > > > On 04.07.2014 16:29, Jacek Kikiewicz wrote: >> Hello, >> >> I have CONFIG_PACKAGE_ATH_DFS=y and still cannot use this... any idea >> how / what should be debugged? > .. >>>CONFIG_PACKAGE_ATH_DFS=y > ___ > 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] Porting OpenWRT to Buffalo WZR-1750DHP
On 10 July 2014 21:30, Ronaldo Afonso wrote: > I have a Buffalo WZR-1750DHP and I would like some one to help me porting > OpenWRT to this hardware. It's not too kind to don't even post info about SoC. Well, it's BCM4708A0. What kind of help do you need? Specify. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] ar71xx: add TP-LINK TL-WA860RE v1
New router/repeater from TP-LINK
- CPU: Atheros AR9341-DL3A (AP123)
- Flash: 4MB
- Ram: 32MB
Similar to TL-WA850RE
Signed-off-by: Cezary Jackiewicz
---
Index: target/linux/ar71xx/base-files/etc/diag.sh
===
--- target/linux/ar71xx/base-files/etc/diag.sh (revision 41570)
+++ target/linux/ar71xx/base-files/etc/diag.sh (working copy)
@@ -167,6 +167,9 @@
tl-wa850re)
status_led="tp-link:blue:re"
;;
+ tl-wa860re)
+ status_led="tp-link:green:power"
+ ;;
tl-mr3220 | \
tl-mr3220-v2 | \
tl-mr3420 | \
Index: target/linux/ar71xx/base-files/etc/uci-defaults/01_leds
===
--- target/linux/ar71xx/base-files/etc/uci-defaults/01_leds (revision 41570)
+++ target/linux/ar71xx/base-files/etc/uci-defaults/01_leds (working copy)
@@ -234,6 +234,11 @@
ucidef_set_led_rssi "rssihigh" "RSSIHIGH" "tp-link:blue:signal5"
"wlan0" "80" "100" "-79" "13"
;;
+tl-wa860re)
+ ucidef_set_led_netdev "lan" "LAN" "tp-link:green:lan" "eth0"
+ ucidef_set_led_wlan "wlan" "WLAN" "tp-link:green:wlan" "phy0tpt"
+ ;;
+
tl-wa901nd)
ucidef_set_led_netdev "lan" "LAN" "tp-link:green:lan" "eth0"
;;
Index: target/linux/ar71xx/base-files/etc/uci-defaults/02_network
===
--- target/linux/ar71xx/base-files/etc/uci-defaults/02_network (revision 41570)
+++ target/linux/ar71xx/base-files/etc/uci-defaults/02_network (working copy)
@@ -269,6 +269,7 @@
tl-mr3040-v2 |\
tl-wa750re |\
tl-wa850re |\
+tl-wa860re |\
tl-wa801nd-v2 |\
tl-wa901nd |\
tl-wa901nd-v2 |\
Index: target/linux/ar71xx/base-files/lib/ar71xx.sh
===
--- target/linux/ar71xx/base-files/lib/ar71xx.sh(revision 41570)
+++ target/linux/ar71xx/base-files/lib/ar71xx.sh(working copy)
@@ -145,6 +145,9 @@
"085000"*)
model="TP-Link TL-WA850RE"
;;
+ "086000"*)
+ model="TP-Link TL-WA860RE"
+ ;;
"090100"*)
model="TP-Link TL-WA901N/ND"
;;
@@ -541,6 +544,9 @@
*TL-WA850RE)
name="tl-wa850re"
;;
+ *TL-WA860RE)
+ name="tl-wa860re"
+ ;;
*"TL-WA801ND v2")
name="tl-wa801nd-v2"
;;
Index: target/linux/ar71xx/base-files/lib/upgrade/platform.sh
===
--- target/linux/ar71xx/base-files/lib/upgrade/platform.sh (revision 41570)
+++ target/linux/ar71xx/base-files/lib/upgrade/platform.sh (working copy)
@@ -240,6 +240,7 @@
tl-wa7510n | \
tl-wa750re | \
tl-wa850re | \
+ tl-wa860re | \
tl-wa801nd-v2 | \
tl-wa901nd | \
tl-wa901nd-v2 | \
Index: target/linux/ar71xx/files/arch/mips/ath79/mach-tl-wax50re.c
===
--- target/linux/ar71xx/files/arch/mips/ath79/mach-tl-wax50re.c (revision 41570)
+++ target/linux/ar71xx/files/arch/mips/ath79/mach-tl-wax50re.c (working copy)
@@ -33,6 +33,12 @@
#define TL_WAX50RE_GPIO_LED_SIGNAL43
#define TL_WAX50RE_GPIO_LED_SIGNAL54
+#define TL_WA860RE_GPIO_LED_WLAN_ORANGE0
+#define TL_WA860RE_GPIO_LED_WLAN_GREEN 2
+#define TL_WA860RE_GPIO_LED_POWER_ORANGE 12
+#define TL_WA860RE_GPIO_LED_POWER_GREEN14
+#define TL_WA860RE_GPIO_LED_LAN20
+
#define TL_WA801ND_V2_GPIO_LED_LAN 18
#define TL_WA801ND_V2_GPIO_LED_SYSTEM 14
@@ -39,6 +45,10 @@
#define TL_WAX50RE_GPIO_BTN_RESET 17
#define TL_WAX50RE_GPIO_BTN_WPS16
+#define TL_WA860RE_GPIO_BTN_RESET 17
+#define TL_WA860RE_GPIO_BTN_WPS16
+#define TL_WA860RE_GPIO_BTN_ONOFF 11
+
#define TL_WAX50RE_KEYS_POLL_INTERVAL 20 /* msecs */
#define TL_WAX50RE_KEYS_DEBOUNCE_INTERVAL (3 * TL_WAX50RE_KEYS_POLL_INTERVAL)
@@ -123,7 +133,31 @@
},
};
+static struct gpio_led tl_wa860re_leds_gpio[] __initdata = {
+ {
+ .name = "tp-link:green:lan",
+ .gpio = TL_WA860RE_GPIO_LED_LAN,
+ .active_low = 1,
+ }, {
+ .name = "tp-link:green:power",
+ .gpio = TL_WA860RE_GPIO_LED_POWER_GREEN,
+ .active_low = 1,
+ }, {
+ .name = "tp-link:orange:power",
+ .gpio = TL_WA860RE_GPIO_LED_POWER_ORANGE,
+ .active_low = 1,
+ }, {
+ .name = "tp-link:green:wlan",
+ .gpio = TL_WA860RE_GPIO_LED_WLAN_GREEN,
+ .active_low = 1,
+ }, {
+ .name = "t
Re: [OpenWrt-Devel] Status of DFS in OpenWrt -> ath9k
Hi Jacek, summarising all information from the mailinglist the following configuration should work: 1. select CONFIG_PACKAGE_ATH_DFS=y 2. if ath9k select CONFIG_ATH_USER_REGD=y if ath10k deactivate CONFIG_ATH_USER_REGD 3. compile current OpenWRT trunk 4. Configuration - config wifi-device radio0 option type mac80211 option channel 104 option hwmode 11a option path 'pci:00/:00:00.0' option htmode HT20 option country 'DE' config wifi-iface option device radio0 option network lan option mode ap option ssid OpenWrt option encryption none - If this setting does not work for you please do the following. - on AP exec "wifi down" - on AP exec "logread -f" (on a second ssh session) - on AP exec "wifi up" - send us the log output + "iw phy0 info" output + information about your hardware Martin On 7/4/14, 4:29 PM, Jacek Kikiewicz wrote: > Hello, > > I have CONFIG_PACKAGE_ATH_DFS=y and still cannot use this... any idea how / > what should be debugged? > > Jacek > > > On 03.07.2014 18:14, Martin Garbe wrote: >> The command "iw phy ..." only shows hardware capabilities. For DFS >> hardware AND software support is needed. In OpenWRT you need hostapd to >> support DFS too. The config parameter CONFIG_PACKAGE_ATH_DFS explicitely >> activates DFS in hostapd. This parameter is not set by default. >> For more information see also the patch with comment in git: >> http://git.openwrt.org/?p=openwrt.git;a=commitdiff;h=5fd90c893f86e88150ea81be7afd337ac1b802aa >> >> Regards, >> Martin >> >> Jacek On 07/02/14 22:50, Martin Garbe wrote: >> On 7/1/14, 10:04 AM, Jacek Kikiewicz wrote: Hello, I have few APs that are using ath9k driver, I've read that now DFS is supported on that driver, so I compiled latest revision (yesterday: 41415), and started playing, basically when as per manual / howto I run 'iw phy phy1 info' I can see DFS channels, exactly like in howto on a wiki, problem is however that I cannot make it work on those channels (I've tried 52,56,100, 104), after changing config and restarting wifi I saw in dmesg 'interface wlan1 entered disabled mode) - I tried with HT20 for the beginning. So, question here is, should this work in current state or is there still some support missing? I can pull any logs / settings that are of interest. >> Have you elected >> CONFIG_PACKAGE_ATH_DFS=y >> when compiling the driver? This way you agree to the fact that your >> hardware supports DFS. After that DFS channels can be selected. >> >> > ___ > 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] ramips: add support for Zbtlink WA05 router
Signed-off-by: Roman Yeryomin
---
.../ramips/base-files/etc/uci-defaults/01_leds | 5 +
.../ramips/base-files/etc/uci-defaults/02_network | 3 +-
target/linux/ramips/base-files/lib/ramips.sh | 3 +
.../ramips/base-files/lib/upgrade/platform.sh | 3 +-
target/linux/ramips/dts/ZBT-WA05.dts | 112 +
target/linux/ramips/image/Makefile | 2 +
6 files changed, 126 insertions(+), 2 deletions(-)
create mode 100644 target/linux/ramips/dts/ZBT-WA05.dts
diff --git a/target/linux/ramips/base-files/etc/uci-defaults/01_leds
b/target/linux/ramips/base-files/etc/uci-defaults/01_leds
index c2f768b..00b6040 100755
--- a/target/linux/ramips/base-files/etc/uci-defaults/01_leds
+++ b/target/linux/ramips/base-files/etc/uci-defaults/01_leds
@@ -181,6 +181,11 @@ case $board in
ucidef_set_led_default "power" "power" "buffalo:green:power" "1"
ucidef_set_led_default "router" "router" "buffalo:green:router"
"1"
;;
+ zbt-wa05)
+ ucidef_set_led_default "power" "power" "zbtlink:blue:power" "1"
+ set_wifi_led "zbtlink:blue:air"
+ set_usb_led "zbtlink:blue:usb"
+ ;;
esac
ucidef_commit_leds
diff --git a/target/linux/ramips/base-files/etc/uci-defaults/02_network
b/target/linux/ramips/base-files/etc/uci-defaults/02_network
index 4eef735..a14acb6 100755
--- a/target/linux/ramips/base-files/etc/uci-defaults/02_network
+++ b/target/linux/ramips/base-files/etc/uci-defaults/02_network
@@ -112,7 +112,8 @@ ramips_setup_interfaces()
hg255d | \
rt-n14u | \
wrtnode | \
- ur-326n4g)
+ ur-326n4g | \
+ zbt-wa05)
ucidef_set_interfaces_lan_wan "eth0.1" "eth0.2"
ucidef_add_switch "switch0" "1" "1"
ucidef_add_switch_vlan "switch0" "1" "1 2 3 4 6t"
diff --git a/target/linux/ramips/base-files/lib/ramips.sh
b/target/linux/ramips/base-files/lib/ramips.sh
index ca339b3..2ae8c9e 100755
--- a/target/linux/ramips/base-files/lib/ramips.sh
+++ b/target/linux/ramips/base-files/lib/ramips.sh
@@ -307,6 +307,9 @@ ramips_board_detect() {
*"Sercomm NA930")
name="na930"
;;
+ *"Zbtlink ZBT-WA05")
+ name="zbt-wa05"
+ ;;
*)
name="generic"
;;
diff --git a/target/linux/ramips/base-files/lib/upgrade/platform.sh
b/target/linux/ramips/base-files/lib/upgrade/platform.sh
index a39c433..805a63f 100755
--- a/target/linux/ramips/base-files/lib/upgrade/platform.sh
+++ b/target/linux/ramips/base-files/lib/upgrade/platform.sh
@@ -91,7 +91,8 @@ platform_check_image() {
wmr300 |\
wrtnode |\
x5 |\
- x8)
+ x8 |\
+ zbt-wa05)
[ "$magic" != "27051956" ] && {
echo "Invalid image type."
return 1
diff --git a/target/linux/ramips/dts/ZBT-WA05.dts
b/target/linux/ramips/dts/ZBT-WA05.dts
new file mode 100644
index 000..714d273
--- /dev/null
+++ b/target/linux/ramips/dts/ZBT-WA05.dts
@@ -0,0 +1,112 @@
+/dts-v1/;
+
+/include/ "mt7620n.dtsi"
+
+/ {
+ compatible = "zbtlink,zbt-wa05", "ralink,mt7620n-soc";
+ model = "Zbtlink ZBT-WA05";
+
+ chosen {
+ bootargs = "console=ttyS0,115200";
+ };
+
+ palmbus@1000 {
+ gpio1: gpio@638 {
+ status = "okay";
+ };
+
+ gpio2: gpio@660 {
+ status = "okay";
+ };
+
+ gpio3: gpio@688 {
+ status = "okay";
+ };
+
+ spi@b00 {
+ status = "okay";
+
+ en25q64@0 {
+ #address-cells = <1>;
+ #size-cells = <1>;
+ compatible = "w25q64";
+ 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 {
+
Re: [OpenWrt-Devel] There ar some strange things in bb
??? git status Auf Branch master Ihr Branch ist auf dem selben Stand wie 'origin/master'. Unbeobachtete Dateien: (benutzen Sie "git add ..." um die Änderungen zum Commit vorzumerken) .config_rassspberryPI_backup PCB.00029398.backup backup/ backup2/ openwrt.elf package/utils/catdoc/ package/utils/swish-e/ package/utils/xpdf/ rb433UL.patch target/linux/ar71xx/patches-3.10/999-rb433ul.patch nichts zum Commit vorgemerkt, aber es gibt unbeobachtete Dateien (benutzen Sie "git add" zum Beobachten) Am Thu, 10 Jul 2014 17:17:56 +0200 schrieb John Crispin : > Hi, > > i just checked the BB builder and the rpi images get built there. > > are you testing on HEAD ? > > John > > On 10/07/2014 17:10, smile...@gmail.com wrote: > > After compression of the rootfs, there is a failure. > > > > > > > > > > > > ... mcopy -i > > /home/smilebef/Downloads/OpenWRT/openwrt/build_dir/target-arm_arm1176jzf-s+vfp_uClibc-0.9.33.2_eabi/linux-brcm2708/boot.img > > /home/smilebef/Downloads/OpenWRT/openwrt/build_dir/target-arm_arm1176jzf-s+vfp_uClibc-0.9.33.2_eabi/linux-brcm2708/Image > > ::kernel.img # Copy OpenWrt built kernel ./gen_rpi_sdcard_img.sh > > /home/smilebef/Downloads/OpenWRT/openwrt/bin/brcm2708/openwrt-brcm2708-sdcard-vfat-squashfs.img > > /home/smilebef/Downloads/OpenWRT/openwrt/build_dir/target-arm_arm1176jzf-s+vfp_uClibc-0.9.33.2_eabi/linux-brcm2708/boot.img > > /home/smilebef/Downloads/OpenWRT/openwrt/build_dir/target-arm_arm1176jzf-s+vfp_uClibc-0.9.33.2_eabi/linux-brcm2708/root.squashfs > > 20 + '[' 4 == 5 ']' + echo 'SYNTAX: ./gen_rpi_sdcard_img.sh > >' SYNTAX: > > ./gen_rpi_sdcard_img.sh > > + exit 1 Makefile:40: recipe for target > > 'install' failed make[5]: *** [install] Error 1 make[5]: Leaving > > directory > > '/home/smilebef/Downloads/OpenWRT/openwrt/target/linux/brcm2708/image' > > > > > Makefile:30: recipe for target 'install' failed > > make[4]: *** [install] Error 2 make[4]: Leaving directory > > '/home/smilebef/Downloads/OpenWRT/openwrt/target/linux/brcm2708' > > Makefile:13: recipe for target 'install' failed make[3]: *** > > [install] Error 2 make[3]: Leaving directory > > '/home/smilebef/Downloads/OpenWRT/openwrt/target/linux' > > target/Makefile:21: recipe for target 'target/linux/install' > > failed make[2]: *** [target/linux/install] Error 2 make[2]: Leaving > > directory '/home/smilebef/Downloads/OpenWRT/openwrt' > > target/Makefile:17: recipe for target > > '/home/smilebef/Downloads/OpenWRT/openwrt/staging_dir/target-arm_arm1176jzf-s+vfp_uClibc-0.9.33.2_eabi/stamp/.target_install' > > failed make[1]: *** > > [/home/smilebef/Downloads/OpenWRT/openwrt/staging_dir/target-arm_arm1176jzf-s+vfp_uClibc-0.9.33.2_eabi/stamp/.target_install] > > Error 2 make[1]: Leaving directory > > '/home/smilebef/Downloads/OpenWRT/openwrt' > > /home/smilebef/Downloads/OpenWRT/openwrt/include/toplevel.mk:169: > > recipe for target 'world' failed make: *** [world] Error 2 > > smilebef@Vigor18:~/Downloads/OpenWRT/openwrt$ > > > > > > Any ideas? > > > > Thanks ___ > > 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
[OpenWrt-Devel] [PATCH 1/2] kernel: add driver for Marvell 88E6171 switch
This is a swconfig driver for the Marvell 88E6171 switch,
which is a 7-port GigE switch with two CPU ports and 64
802.1q VLANs. The driver was initially based on the
mvswitch driver, although it has now diverged quite a bit.
I've been testing it for about a week as my primary switch
with no problems as far as I can tell.
Any comments are appreciated.
A few notes for consideration:
- The switch can use direct or indirect register access--see
comment in code for an explanation. Both modes are supported
and tested. Both tested boards use 88E6171R, the RGMII-only
version, but the regular one should work as well.
- So far this is tested only on kirkwood, hence patches are
only for 3.10 and 3.14.
- Since the switch does not really offer a true PHY interface
to the CPU (as far as I know) the PHY driver was having
trouble trying to reset it, and required a hack. So,
I rewrote the driver as a platform_driver, making it a
peripheral using MDIO for I/O and nothing more. The bus
is selected via the board DTS, where a few other parameters
are also configured.
- This should be fairly easy to adapt to similar Marvell
switches like the 88E6172, but I have no way to test that.
Signed-off-by: Claudio Leite
---
.../linux/generic/files/drivers/net/phy/mvsw6171.c | 866 +
.../linux/generic/files/drivers/net/phy/mvsw6171.h | 230 ++
.../generic/patches-3.10/733-phy_mvsw6171.patch| 23 +
.../generic/patches-3.14/732-phy_mvsw6171.patch| 23 +
4 files changed, 1142 insertions(+)
create mode 100644 target/linux/generic/files/drivers/net/phy/mvsw6171.c
create mode 100644 target/linux/generic/files/drivers/net/phy/mvsw6171.h
create mode 100644 target/linux/generic/patches-3.10/733-phy_mvsw6171.patch
create mode 100644 target/linux/generic/patches-3.14/732-phy_mvsw6171.patch
diff --git a/target/linux/generic/files/drivers/net/phy/mvsw6171.c
b/target/linux/generic/files/drivers/net/phy/mvsw6171.c
new file mode 100644
index 000..48bb3fc
--- /dev/null
+++ b/target/linux/generic/files/drivers/net/phy/mvsw6171.c
@@ -0,0 +1,866 @@
+/*
+ * Marvell 88E6171 switch driver
+ *
+ * Copyright (c) 2014 Claudio Leite
+ *
+ * Based on code (c) 2008 Felix Fietkau
+ *
+ * This program is free software; you can redistribute it and/or modify it
+ * under the terms of the GNU General Public License v2 as published by the
+ * Free Software Foundation
+ */
+
+#include
+#include
+#include
+#include
+#include
+#include
+#include
+#include
+#include
+#include
+#include
+#include
+
+#include "mvsw6171.h"
+
+MODULE_DESCRIPTION("Marvell 88E6171 Switch driver");
+MODULE_AUTHOR("Claudio Leite ");
+MODULE_LICENSE("GPL v2");
+MODULE_ALIAS("platform:mvsw6171");
+
+/*
+ * Register access is done through direct or indirect addressing,
+ * depending on how the switch is physically connected.
+ *
+ * Direct addressing: all port and global registers directly
+ * accessible via an address/register pair
+ *
+ * Indirect addressing: switch is mapped at a single address,
+ * port and global registers accessible via a single command/data
+ * register pair
+ */
+
+static int
+mvsw6171_wait_mask_raw(struct mii_bus *bus, int addr,
+ int reg, u16 mask, u16 val)
+{
+ int i = 100;
+ u16 r;
+
+ do {
+ r = bus->read(bus, addr, reg);
+ if ((r & mask) == val)
+ return 0;
+ } while (--i > 0);
+
+ return -ETIMEDOUT;
+}
+
+static u16
+r16(struct mii_bus *bus, bool indirect, int base_addr, int addr, int reg)
+{
+ u16 ind_addr;
+
+ if (!indirect)
+ return bus->read(bus, addr, reg);
+
+ /* Indirect read: First, make sure switch is free */
+ mvsw6171_wait_mask_raw(bus, base_addr, MV_INDIRECT_REG_CMD,
+ MV_INDIRECT_INPROGRESS, 0);
+
+ /* Load address and request read */
+ ind_addr = MV_INDIRECT_READ | (addr << MV_INDIRECT_ADDR_S) | reg;
+ bus->write(bus, base_addr, MV_INDIRECT_REG_CMD,
+ ind_addr);
+
+ /* Wait until it's ready */
+ mvsw6171_wait_mask_raw(bus, base_addr, MV_INDIRECT_REG_CMD,
+ MV_INDIRECT_INPROGRESS, 0);
+
+ /* Read the requested data */
+ return bus->read(bus, base_addr, MV_INDIRECT_REG_DATA);
+}
+
+static void
+w16(struct mii_bus *bus, bool indirect, int base_addr, int addr,
+ int reg, u16 val)
+{
+ u16 ind_addr;
+
+ if (!indirect) {
+ bus->write(bus, addr, reg, val);
+ return;
+ }
+
+ /* Indirect write: First, make sure switch is free */
+ mvsw6171_wait_mask_raw(bus, base_addr, MV_INDIRECT_REG_CMD,
+ MV_INDIRECT_INPROGRESS, 0);
+
+ /* Load the data to be written */
+ bus->write(bus, base_addr, MV_INDIRECT_REG_DATA, val);
+
+ /* Wait again for switch to be free */
+ mvsw6171_wait_mask_raw(bus, base_addr, MV_INDIRECT_REG_CMD,
+
[OpenWrt-Devel] [PATCH 2/2] kirkwood: add mvsw6171 switch for EA4500 board
Signed-off-by: Claudio Leite
---
target/linux/kirkwood/config-3.10 | 4 +++-
target/linux/kirkwood/config-3.14 | 4 +++-
target/linux/kirkwood/patches-3.14/160-ea4500.patch | 13 -
3 files changed, 18 insertions(+), 3 deletions(-)
diff --git a/target/linux/kirkwood/config-3.10
b/target/linux/kirkwood/config-3.10
index 3e68c71..28a7ccc 100644
--- a/target/linux/kirkwood/config-3.10
+++ b/target/linux/kirkwood/config-3.10
@@ -179,6 +179,7 @@ CONFIG_MTD_OF_PARTS=y
# CONFIG_MTD_SM_COMMON is not set
CONFIG_MTD_UBI=y
CONFIG_MTD_UBI_BEB_LIMIT=20
+# CONFIG_MTD_UBI_BLOCK is not set
# CONFIG_MTD_UBI_FASTMAP is not set
# CONFIG_MTD_UBI_GLUEBI is not set
CONFIG_MTD_UBI_WL_THRESHOLD=4096
@@ -187,6 +188,7 @@ CONFIG_MVEBU_CLK_CORE=y
CONFIG_MVEBU_CLK_GATING=y
CONFIG_MVEBU_MBUS=y
CONFIG_MVMDIO=y
+CONFIG_MVSW6171_PHY=y
CONFIG_NEED_DMA_MAP_STATE=y
CONFIG_NEED_KUSER_HELPERS=y
CONFIG_NEED_PER_CPU_KM=y
@@ -253,6 +255,7 @@ CONFIG_SPI=y
CONFIG_SPI_MASTER=y
CONFIG_SPI_ORION=y
CONFIG_SPLIT_PTLOCK_CPUS=99
+CONFIG_SWCONFIG=y
CONFIG_SYS_SUPPORTS_APM_EMULATION=y
CONFIG_TICK_CPU_ACCOUNTING=y
CONFIG_UBIFS_FS=y
@@ -285,4 +288,3 @@ CONFIG_ZBOOT_ROM_TEXT=0x0
CONFIG_ZLIB_DEFLATE=y
CONFIG_ZLIB_INFLATE=y
CONFIG_ZONE_DMA_FLAG=0
-# CONFIG_MTD_UBI_BLOCK is not set
diff --git a/target/linux/kirkwood/config-3.14
b/target/linux/kirkwood/config-3.14
index 750726c..fcacb2c 100644
--- a/target/linux/kirkwood/config-3.14
+++ b/target/linux/kirkwood/config-3.14
@@ -195,6 +195,7 @@ CONFIG_MTD_NAND_ORION=y
# CONFIG_MTD_SM_COMMON is not set
CONFIG_MTD_UBI=y
CONFIG_MTD_UBI_BEB_LIMIT=20
+# CONFIG_MTD_UBI_BLOCK is not set
# CONFIG_MTD_UBI_FASTMAP is not set
# CONFIG_MTD_UBI_GLUEBI is not set
CONFIG_MTD_UBI_WL_THRESHOLD=4096
@@ -204,6 +205,7 @@ CONFIG_MVEBU_CLK_COMMON=y
CONFIG_MVEBU_MBUS=y
CONFIG_MVMDIO=y
# CONFIG_MVNETA is not set
+CONFIG_MVSW6171_PHY=y
CONFIG_NEED_DMA_MAP_STATE=y
CONFIG_NEED_KUSER_HELPERS=y
CONFIG_NEED_PER_CPU_KM=y
@@ -270,6 +272,7 @@ CONFIG_SPI=y
CONFIG_SPI_MASTER=y
CONFIG_SPI_ORION=y
CONFIG_SPLIT_PTLOCK_CPUS=99
+CONFIG_SWCONFIG=y
CONFIG_SWIOTLB=y
CONFIG_SYS_SUPPORTS_APM_EMULATION=y
CONFIG_TICK_CPU_ACCOUNTING=y
@@ -302,4 +305,3 @@ CONFIG_ZBOOT_ROM_TEXT=0x0
CONFIG_ZLIB_DEFLATE=y
CONFIG_ZLIB_INFLATE=y
CONFIG_ZONE_DMA_FLAG=0
-# CONFIG_MTD_UBI_BLOCK is not set
diff --git a/target/linux/kirkwood/patches-3.14/160-ea4500.patch
b/target/linux/kirkwood/patches-3.14/160-ea4500.patch
index 0abf1a1..eeed2a4 100644
--- a/target/linux/kirkwood/patches-3.14/160-ea4500.patch
+++ b/target/linux/kirkwood/patches-3.14/160-ea4500.patch
@@ -10,7 +10,7 @@
kirkwood-ib62x0.dtb \
--- /dev/null
+++ b/arch/arm/boot/dts/kirkwood-ea4500.dts
-@@ -0,0 +1,156 @@
+@@ -0,0 +1,167 @@
+/*
+ * kirkwood-ea4500.dts - Device Tree file for Linksys EA4500
+ *
@@ -120,6 +120,17 @@
+ gpios = <&gpio0 14 GPIO_ACTIVE_HIGH>;
+ };
+ };
++
++ mvsw6171 {
++ compatible = "marvell,88e6171";
++ status = "okay";
++ reg = <0x10>;
++
++ mii-bus = <&mdio>;
++ cpu-port-0 = <5>;
++ cpu-port-1 = <6>;
++ is-indirect;
++ };
+};
+
+&nand {
--
2.0.1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 1/2] kernel: add driver for Marvell 88E6171 switch
* Claudio Leite (lei...@staticky.com) wrote: > Any comments are appreciated. I meant to send this is as an RFC and not a patch. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [Patch] [ar71xx] added support for TL-WA830RE V2
Hi, On 08/07/2014 20:29, Fredrik Jonson wrote: > +++ > b/target/linux/ar71xx/patches-3.10/714-MIPS-auth79-add-TL-WA830REv2-support.patch s/auth79/ath79/g :) John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v2 0/3] ar71xx: add support for the EnGenius ESR900
Is there something blocking this from becoming accepted? I can see the patches have been delegated to Gabor Juhos, but nothing has happened with them for weeks. If I need to change something, please let me know. Also, is it too late to add my name to the copyright message in mach-esr900.c? Would that even be appropriate when I didn't write most of the code? This is the first free software project I've contributed to so I'm a little unsure of myself when it comes to what I should or should not take credit for. -- Forest Crossman On Sun, Jun 22, 2014 at 4:20 PM, Forest Crossman wrote: > Apparrently, Gmail likes to mangle patches if you send them from the web > interface. This patch series contains a slightly cleaned-up version of the > original patch. > > Forest Crossman (3): > ar71xx: add kernel support for the EnGenius ESR900 > ar71xx: add board support for the EnGenius ESR900 > ar71xx: add user-space support for the EnGenius ESR900 > > package/base-files/files/lib/functions/system.sh | 1 + > 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 | 10 + > target/linux/ar71xx/base-files/lib/ar71xx.sh | 3 + > target/linux/ar71xx/config-3.10| 1 + > .../ar71xx/files/arch/mips/ath79/mach-esr900.c | 222 > + > target/linux/ar71xx/files/arch/mips/ath79/nvram.c | 16 ++ > target/linux/ar71xx/generic/profiles/engenius.mk | 16 ++ > target/linux/ar71xx/image/Makefile | 2 + > .../610-MIPS-ath79-openwrt-machines.patch | 18 +- > 11 files changed, 294 insertions(+), 3 deletions(-) > create mode 100644 target/linux/ar71xx/files/arch/mips/ath79/mach-esr900.c > create mode 100644 target/linux/ar71xx/generic/profiles/engenius.mk > > -- > 1.9.2 > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 1/2] kernel: add driver for Marvell 88E6171 switch
Hi, what board you are using? Alex Guo On 07/11/2014 05:29 AM, Claudio Leite wrote: * Claudio Leite (lei...@staticky.com) wrote: Any comments are appreciated. I meant to send this is as an RFC and not a patch. ___ 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/2] kernel: add driver for Marvell 88E6171 switch
Sorry, i missing that, it's Linksys EA4500. On 07/11/2014 11:53 AM, Xiongfei Guo wrote: Hi, what board you are using? Alex Guo On 07/11/2014 05:29 AM, Claudio Leite wrote: * Claudio Leite (lei...@staticky.com) wrote: Any comments are appreciated. I meant to send this is as an RFC and not a patch. ___ 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] [PATCH 3/3][ESR1750][V2] ar71xx: add support for EnGenius ESR1750
> diff --git a/target/linux/ar71xx/base-files/etc/diag.sh
> b/target/linux/ar71xx/base-files/etc/diag.sh
> index ef172b4..144459b 100755
> --- a/target/linux/ar71xx/base-files/etc/diag.sh
> +++ b/target/linux/ar71xx/base-files/etc/diag.sh
> @@ -69,6 +69,9 @@ get_status_led() {
> el-m150)
> status_led="EasyLink:green:system"
> ;;
> + esr1750)
> + status_led="esr1750:amber:power"
> + ;;
> hiwifi-hc6361)
> status_led="hiwifi:blue:system"
> ;;
> +static struct gpio_led esr1750_leds_gpio[] __initdata = {
> + {
> + .name = "esr1750:amber:power",
> + .gpio = ESR1750_GPIO_LED_POWER_AMBER,
> + .active_low = 1,
> + },
> + {
> + .name = "esr1750:blue:wps",
> + .gpio = ESR1750_GPIO_LED_WPS_BLUE,
> + .active_low = 1,
> + },
> + {
> + .name = "esr1750:amber:wps",
> + .gpio = ESR1750_GPIO_LED_WPS_AMBER,
> + .active_low = 1,
> + },
> + {
> + .name = "esr1750:blue:wlan-2g",
> + .gpio = ESR1750_GPIO_LED_WLAN_2G,
> + .active_low = 1,
> + },
> + {
> + .name = "esr1750:blue:wlan-5g",
> + .gpio = ESR1750_GPIO_LED_WLAN_5G,
> + .active_low = 1,
> + }
> +};
> +
This isn't really specific to the ESR1750, but does anyone know if
it's better to use "device:color:name" or "manufacturer:color:name"
for the LEDs? For the ESR900, I made it "manufacturer:color:name" (ex.
"engenius:amber:power") because they're the same for each of the
saucer-shaped ESR routers and I saw some other routers with
similarly-named LEDs. I tried searching the wiki to see if there was a
standard convention to use, but I haven't had any luck finding one.
--
Forest Crossman
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Trac: Custom Query results in "Missing or invalid form token."
1) Please enter https://dev.openwrt.org/query 2) Click "Update" button This will results in: > Error: Bad Request > Missing or invalid form token. Do you have cookies enabled? Could someone take a look at this, please? -- Rafał ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Trac: Custom Query results in "Missing or invalid form token."
On 11/07/2014 08:12, Rafał Miłecki wrote: > 1) Please enter https://dev.openwrt.org/query 2) Click "Update" > button > > This will results in: >> Error: Bad Request Missing or invalid form token. Do you have >> cookies enabled? > > Could someone take a look at this, please? > works for me, Do you have cookies enabled? John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] [packages] EmailRelay: added new package version 1.9
Hi, please make a PR to https://github.com/openwrt/packages
Le 1 juil. 2014 02:53, "Federico Di Marco" a écrit :
> From: Federico Di Marco
>
> Body of explanation:
> A new package has been added in packages feed under net/emailrelay
> directory, porting a simple SMTP proxy and store-and-forward message
> transfer agent (MTA) called EmailRelay (please see
> http://emailrelay.sourceforge.net/) to OpenWRT.
> The patch consists of the following files:
> - Makefile: standard makefile of OpenWRT packages which downloads from
> sourceforge the source code and compiles it into a package using the
> uClibc++.
> - Makefile.libstdc++: alternative makefile to perform compilation with
> the standard c++ library.
> - files/emailrelay.auth: configuration file for emailrelay
> - files/emailrelay.init: simple shell script for managing service
> installation and startup.
>
>
> Sign-off:
> Developer's Certificate of Origin 1.1
>
> By making a contribution to this project, I certify that:
>
> (a) The contribution was created in whole or in part by me and I
> have the right to submit it under the open source license
> indicated in the file; or
>
> (b) The contribution is based upon previous work that, to the best
> of my knowledge, is covered under an appropriate open source
> license and I have the right under that license to submit that
> work with modifications, whether created in whole or in part
> by me, under the same open source license (unless I am
> permitted to submit under a different license), as indicated
> in the file; or
>
> (c) The contribution was provided directly to me by some other
> person who certified (a), (b) or (c) and I have not modified
> it.
>
> (d) I understand and agree that this project and the contribution
> are public and that a record of the contribution (including all
> personal information I submit with it, including my sign-off) is
> maintained indefinitely and may be redistributed consistent with
> this project or the open source license(s) involved.
>
> Signed-off-by: Federico Di Marco
>
> ---
>
> Diff output (according to
> https://dev.openwrt.org/wiki/SubmittingPatches/Diff)
>
> diff -uprN packages/net/emailrelay/files/emailrelay.auth
> mypackages/net/emailrelay/files/emailrelay.auth
> --- packages/net/emailrelay/files/emailrelay.auth 1970-01-01
> 01:00:00.0 +0100
> +++ mypackages/net/emailrelay/files/emailrelay.auth 2014-07-01
> 01:56:20.297997383 +0200
> @@ -0,0 +1,16 @@
> +#
> +# emailrelay secrets file
> +#
> +#see http://emailrelay.sourceforge.net/reference.html for reference
> +
> +#Mostly used options:
> +#
> +#NONE server specifies ip address range allowed to connect to
> emailrelay SMTP server
> +#LOGIN client specifies the credentials to be used when forwarding
> emails to another SMTP server
> +#LOGIN server specifies the credentials to be needed to authenticate
> with the emailrelay SMTP server
> +
> +#Examples:
> +#
> +#NONE server 192.168.1.* keyword
> +#LOGIN client smtpuser@smtpserver smtppassword
> +#LOGIN server user1 secret
> \ No newline at end of file
> diff -uprN packages/net/emailrelay/files/emailrelay.init
> mypackages/net/emailrelay/files/emailrelay.init
> --- packages/net/emailrelay/files/emailrelay.init 1970-01-01
> 01:00:00.0 +0100
> +++ mypackages/net/emailrelay/files/emailrelay.init 2014-07-01
> 01:56:20.293997264 +0200
> @@ -0,0 +1,15 @@
> +#!/bin/sh /etc/rc.common
> +#see http://emailrelay.sourceforge.net/reference.html for command
> line reference
> +
> +START=90
> +
> +
> +start() {
> +logger -t 'emailrelay' "Starting emailrelay service."
> +service_start emailrelay --as-server --poll 60 --forward-to
> smtpserver:smtpport --spool-dir /tmp --client-tls --client-auth
> /etc/emailrelay.auth --server-auth /etc/emailrelay.auth --log
> +}
> +
> +stop() {
> +logger -t 'emailrelay' "Stopping emailrelay service."
> +killall -9 emailrelay
> +}
> diff -uprN packages/net/emailrelay/Makefile
> mypackages/net/emailrelay/Makefile
> --- packages/net/emailrelay/Makefile 1970-01-01 01:00:00.0 +0100
> +++ mypackages/net/emailrelay/Makefile 2014-07-01 01:56:20.297997383 +0200
> @@ -0,0 +1,75 @@
> +#
> +# Copyright (C) 2006-2011 OpenWrt.org
> +#
> +# This is free software, licensed under the GNU General Public License v2.
> +# See /LICENSE for more information.
> +#
> +
> +include $(TOPDIR)/rules.mk
> +
> +PKG_NAME:=emailrelay
> +PKG_VERSION:=1.9
> +PKG_RELEASE:=1
> +
> +PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION)-src.tar.gz
> +PKG_SOURCE_URL:=@SF/emailrelay/$(PKG_VERSION)
> +PKG_MD5SUM:=0892fbf993407c6b5a16f96e23299b62
> +PKG_INSTALL_DIR:=$(PKG_BUILD_DIR)/ipkg-install
> +PKG_BUILD_DIR := $(BUILD_DIR)/$(PKG_NAME)-$(PKG_VERSION)
> +PKG_CAT :=zcat
> +
> +include $(INCLUDE_DIR)/package.mk
> +
> +define Package/emailrelay
> + SECTION:=net
> + CATEGORY:=Network
> + DEPENDS:=+uclibcxx +libopenssl
> + SUBMENU:=Web Servers/Proxies
> + TITLE:=A simple SMTP proxy and st
Re: [OpenWrt-Devel] Trac: Custom Query results in "Missing or invalid form token."
On 11 July 2014 08:34, John Crispin wrote: > On 11/07/2014 08:12, Rafał Miłecki wrote: >> 1) Please enter https://dev.openwrt.org/query 2) Click "Update" >> button >> >> This will results in: >>> Error: Bad Request Missing or invalid form token. Do you have >>> cookies enabled? >> >> Could someone take a look at this, please? >> > > works for me, Do you have cookies enabled? Yes, I do. I've tried this in: Chromium 35.0.1916.114 Opera 12.16 Firefox 30.0 Getting this error in every browser. Also tried on some machine with Windows 7 and VPN using IP from another country. Same problem using: Google Chrome 35.0.1916.153 Opera 22.0 IE 8 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Trac: Custom Query results in "Missing or invalid form token."
On 11 July 2014 08:34, John Crispin wrote: > On 11/07/2014 08:12, Rafał Miłecki wrote: >> 1) Please enter https://dev.openwrt.org/query 2) Click "Update" >> button >> >> This will results in: >>> Error: Bad Request Missing or invalid form token. Do you have >>> cookies enabled? >> >> Could someone take a look at this, please? >> > > works for me, Do you have cookies enabled? Maybe you are signed in using your account? I don't have one, so testing it as non logged user. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
