[OpenWrt-Devel] hostapd doubts
Hello, I have some doubts concerning to the hostapd package, working with Attitude Adjustment openwrt version. So, I would appreciate if someone might clarify them to me. Firstly, I have noticed that apart from the hostapd package included on package/hostapd directory, there is another small version of hostapd located in the drivers of the linux kernel (linux-3-3.8/drivers/net/wireless/hostap). My question is, if I had to change the main hostapd package, should I change the kernel version of hostap too? Might there be any kind of incompatibility if I only change the package and not the one in the kernel? I ask this, because I'm not sure whether they make use of each other or not. Secondly, could someone point me out where in hostapd code is distinguished between adhoc mode and ap mode? Thanks in advance, Regards, ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] ar71xx: Fix AP135 partition layout
From: Sujith Manoharan Signed-off-by: Sujith Manoharan --- target/linux/ar71xx/image/Makefile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/target/linux/ar71xx/image/Makefile b/target/linux/ar71xx/image/Makefile index 17092b4..05d2177 100644 --- a/target/linux/ar71xx/image/Makefile +++ b/target/linux/ar71xx/image/Makefile @@ -166,7 +166,7 @@ ap113_mtd_layout=mtdparts=spi0.0:64k(u-boot),3008k(rootfs),896k(uImage),64k(NVRA ap121_mtdlayout_2M=mtdparts=spi0.0:64k(u-boot)ro,1216k(rootfs),704k(kernel),64k(art)ro,1920k@0x1(firmware) ap121_mtdlayout_4M=mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,2752k(rootfs),896k(kernel),64k(nvram),64k(art)ro,3648k@0x5(firmware) ap132_mtdlayout=mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,1408k(kernel),6400k(rootfs),64k(art),7808k@0x5(firmware) -ap135_mtdlayout=mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,14528k(rootfs),1408k(kernel),64k(mib0),64k(art)ro,7744k@0x5(firmware) +ap135_mtdlayout=mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,14528k(rootfs),1472k(kernel),64k(art)ro,16000k@0x5(firmware) ap136_mtdlayout=mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,6336k(rootfs),1408k(kernel),64k(mib0),64k(art)ro,7744k@0x5(firmware) cameo7240_mtdlayout=mtdparts=spi0.0:192k(u-boot)ro,64k(nvram)ro,1024k(kernel),2688k(rootfs),64k(mac)ro,64k(art)ro,3712k@0x4(firmware) cameo913x_mtdlayout=mtdparts=spi0.0:128k(u-boot)ro,64k(config)ro,1024k(kernel),2752k(rootfs),64k(art)ro,3840k@0x3(firmware) @@ -837,7 +837,7 @@ $(eval $(call SingleProfile,AthLzma,$(fs_64k),AP121_2M,ap121-2M,AP121,ttyATH0,11 $(eval $(call SingleProfile,AthLzma,$(fs_64k),AP121_4M,ap121-4M,AP121,ttyATH0,115200,$$(ap121_mtdlayout_4M),917504,2818048,RKuImage)) $(eval $(call SingleProfile,AthLzma,$(fs_64k),AP121MINI,ap121-mini,AP121-MINI,ttyATH0,115200,$$(ap121_mtdlayout_4M),917504,2818048,RKuImage)) $(eval $(call SingleProfile,AthLzma,$(fs_64k),AP132,ap132,AP132,ttyS0,115200,$$(ap132_mtdlayout),1441792,6553600,KRuImage)) -$(eval $(call SingleProfile,AthLzma,$(fs_64k),AP135,ap135-020,AP135-020,ttyS0,115200,$$(ap135_mtdlayout),1441792,6488064,RKuImage)) +$(eval $(call SingleProfile,AthLzma,$(fs_64k),AP135,ap135-020,AP135-020,ttyS0,115200,$$(ap135_mtdlayout),1507328,14876672,RKuImage)) $(eval $(call SingleProfile,AthLzma,$(fs_64k),AP136_010,ap136-010,AP136-010,ttyS0,115200,$$(ap136_mtdlayout),1441792,6488064,RKuImage)) $(eval $(call SingleProfile,AthLzma,$(fs_64k),AP136_020,ap136-020,AP136-020,ttyS0,115200,$$(ap136_mtdlayout),1441792,6488064,RKuImage)) $(eval $(call SingleProfile,AthLzma,$(fs_64k),CAP4200AG,cap4200ag,CAP4200AG,ttyS0,115200,$$(cap4200ag_mtdlayout),1572864,12386304,KRuImage)) -- 1.8.2.2 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] hostapd doubts
On 2013-05-07 9:21 AM, Francisco Cuesta wrote: > Hello, > > I have some doubts concerning to the hostapd package, working with > Attitude Adjustment openwrt version. So, I would appreciate if someone > might clarify them to me. > > Firstly, I have noticed that apart from the hostapd package included > on package/hostapd directory, there is another small version of > hostapd located in the drivers of the linux kernel > (linux-3-3.8/drivers/net/wireless/hostap). Just because the name is similar doesn't mean that it's connected to hostapd :) > My question is, if I had to > change the main hostapd package, should I change the kernel version of > hostap too? Might there be any kind of incompatibility if I only > change the package and not the one in the kernel? I ask this, because > I'm not sure whether they make use of each other or not. There's no connection between the two, so no compatibility issues. > Secondly, could someone point me out where in hostapd code is > distinguished between adhoc mode and ap mode? Easy: AP mode uses it, Ad-Hoc mode doesn't. - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] boots compilation fix 1st try
Hello.
Boost fails to compile in current trunk
To fix it I have:
- changed version to 1.53 because 1.51 fails to crosscompile
- added stdint.h for uClibc
- removed not necessary cstdint patch
Best regards
Index: feeds/packages/libs/boost/patches/200-cstdint_missing_include.patch
===
--- feeds/packages/libs/boost/patches/200-cstdint_missing_include.patch
(revision 36556)
+++ feeds/packages/libs/boost/patches/200-cstdint_missing_include.patch
(working copy)
@@ -1,12 +0,0 @@
a/libs/context/src/fcontext.cpp.new2012-12-11
17:59:59.349131458 +0100
-+++ b/libs/context/src/fcontext.cpp2012-12-11 18:00:06.925131652 +0100
-@@ -9,6 +9,9 @@
- #include
-
- #include
-+extern "C" {
-+#include
-+}
-
- #ifdef BOOST_HAS_ABI_HEADERS
- # include BOOST_ABI_PREFIX
Index: feeds/packages/libs/boost/patches/200-uclibc_intptr_t.patch
===
--- feeds/packages/libs/boost/patches/200-uclibc_intptr_t.patch (revision 0)
+++ feeds/packages/libs/boost/patches/200-uclibc_intptr_t.patch (revision 0)
@@ -0,0 +1,13 @@
+--- boost_1_53_0_orig/boost/atomic/atomic.hpp2012-12-25
04:36:31.0 +0100
boost_1_53_0/boost/atomic/atomic.hpp2013-05-07
11:55:42.133251352 +0200
+@@ -17,6 +17,10 @@
+ #include
+ #include
+
++#if defined(__UCLIBC__)
++#include
++#endif
++
+ #ifdef BOOST_ATOMIC_HAS_PRAGMA_ONCE
+ #pragma once
+ #endif
Index: feeds/packages/libs/boost/patches/300-no_glibcxx_define.patch
===
--- feeds/packages/libs/boost/patches/300-no_glibcxx_define.patch
(revision 0)
+++ feeds/packages/libs/boost/patches/300-no_glibcxx_define.patch
(revision 0)
@@ -0,0 +1,25 @@
+--- boost_1_53_0_orig/boost/detail/container_fwd.hpp2012-03-31
21:34:56.0 +0200
boost_1_53_0/boost/detail/container_fwd.hpp2013-05-06
23:19:54.223261911 +0200
+@@ -43,18 +43,18 @@
+ # elif defined(_LIBCPP_VERSION)
+ // libc++
+ #define BOOST_DETAIL_NO_CONTAINER_FWD
+-# elif defined(__GLIBCPP__) || defined(__GLIBCXX__)
++# elif defined(__GLIBCXX__)
+ // GNU libstdc++ 3
+ //
+ // Disable forwarding for all recent versions, as the library has a
+ // versioned namespace mode, and I don't know how to detect it.
+-#if __GLIBCXX__ >= 20070513 \
+-|| defined(_GLIBCXX_DEBUG) \
++#if \
++ defined(_GLIBCXX_DEBUG) \
+ || defined(_GLIBCXX_PARALLEL) \
+ || defined(_GLIBCXX_PROFILE)
+ # define BOOST_DETAIL_NO_CONTAINER_FWD
+ #else
+-# if defined(__GLIBCXX__) && __GLIBCXX__ >= 20040530
++# if defined(__GLIBCXX__)
+ #define BOOST_CONTAINER_FWD_COMPLEX_STRUCT
+ # endif
+ #endif
Index: feeds/packages/libs/boost/Makefile
===
--- feeds/packages/libs/boost/Makefile(revision 36570)
+++ feeds/packages/libs/boost/Makefile(working copy)
@@ -10,14 +10,14 @@
include $(TOPDIR)/rules.mk
PKG_NAME:=boost
-PKG_VERSION:=1_51_0
+PKG_VERSION:=1_53_0
PKG_RELEASE:=1
PKG_SOURCE:=$(PKG_NAME)_$(PKG_VERSION).tar.gz
PKG_SOURCE_URL:=@SF/boost
PKG_BUILD_DIR:=$(BUILD_DIR)/$(PKG_NAME)_$(PKG_VERSION)
HOST_BUILD_DIR:=$(BUILD_DIR_HOST)/$(PKG_NAME)_$(PKG_VERSION)
-PKG_MD5SUM:=6a1f32d902203ac70fbec78af95b3cf8
+PKG_MD5SUM:=57a9e2047c0f511c4dfcf00eb5eb2fbb
PKG_BUILD_DEPENDS:=boost/host
PKG_BUILD_PARALLEL:=1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] grub2: Add sub package grub-editenv for target installation
Any update on this patch? Thanks, Helmut On Wed, Apr 17, 2013 at 5:15 PM, Helmut Schaa wrote: > grub-editenv allows to modify grub2 environment files. Add a new package > that build grub2 for the target and packs up grub-editenv. > > Signed-off-by: Helmut Schaa > --- > package/boot/grub2/Makefile | 25 - > 1 file changed, 24 insertions(+), 1 deletion(-) > > diff --git a/package/boot/grub2/Makefile b/package/boot/grub2/Makefile > index b606f54..26fe47a 100644 > --- a/package/boot/grub2/Makefile > +++ b/package/boot/grub2/Makefile > @@ -16,7 +16,6 @@ PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz > PKG_SOURCE_URL:=@GNU/grub > PKG_MD5SUM:=e927540b6eda8b024fb0391eeaa4091c > > -PKG_HOST_ONLY:=1 > HOST_BUILD_PARALLEL:=1 > PKG_BUILD_DEPENDS:=grub2/host > > @@ -32,6 +31,23 @@ define Package/grub2 >DEPENDS:=@TARGET_x86 > endef > > +define Package/grub2-editenv > + CATEGORY:=Utilities > + SECTION:=utils > + TITLE:=Grub2 Environment editor > + URL:=http://www.gnu.org/software/grub/ > + DEPENDS:=@TARGET_x86 > +endef > + > +define Package/grub2-editenv/description > + Edit grub2 environment files. > +endef > + > +CONFIGURE_ARGS += \ > + --target=$(REAL_GNU_TARGET_NAME) \ > + --disable-werror \ > + --disable-nls > + > HOST_CONFIGURE_ARGS += \ > --target=$(REAL_GNU_TARGET_NAME) \ > --sbindir="$(STAGING_DIR_HOST)/bin" \ > @@ -47,5 +63,12 @@ define Host/Configure > $(Host/Configure/Default) > endef > > +define Package/grub2-editenv/install > + $(INSTALL_DIR) $(1)/usr/sbin > + $(INSTALL_BIN) $(PKG_BUILD_DIR)/grub-editenv $(1)/usr/sbin/ > +endef > + > $(eval $(call HostBuild)) > $(eval $(call BuildPackage,grub2)) > +$(eval $(call BuildPackage,grub2-editenv)) > + > -- > 1.7.10.4 > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] grub2: Add sub package grub-editenv for target installation
On 07/05/13 14:29, Helmut Schaa wrote: Any update on this patch? Thanks, Helmut On Wed, Apr 17, 2013 at 5:15 PM, Helmut Schaa wrote: grub-editenv allows to modify grub2 environment files. Add a new package that build grub2 for the target and packs up grub-editenv. Signed-off-by: Helmut Schaa Thanks, applied in r36574 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] [base-files] Failsafe-mode: print short help on commandline (signed)]
* John Crispin [12.04.2013 22:19]: > let me fix up the wording a bit and push a slightly different version > of the patch ;) anything i can help with this patch? bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] libubox: Allow to build against libjson-c > 0.9
Signed-off-by: Helmut Schaa
---
Not sure where to send libubox patches to, openwrt-devel?
Helmut
CMakeLists.txt |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/CMakeLists.txt b/CMakeLists.txt
index c574bf7..015b8bd 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -13,7 +13,7 @@ IF(APPLE)
ENDIF()
INCLUDE(FindPkgConfig)
-PKG_CHECK_MODULES(JSONC json)
+PKG_CHECK_MODULES(JSONC json-c json)
IF(JSONC_FOUND)
ADD_DEFINITIONS(-DJSONC)
INCLUDE_DIRECTORIES(${JSONC_INCLUDE_DIRS})
--
1.7.10.4
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] hostapd doubts
Thanks Felix for clarifying my newbie doubts!! > Secondly, could someone point me out where in hostapd code is > distinguished between adhoc mode and ap mode? Easy: AP mode uses it, Ad-Hoc mode doesn't. So, where is the ad-hoc mode configured then? Is it done in the proprietary driver (in my case ath9k) or it is done in the kernel? Thanks again 2013/5/7 Felix Fietkau : > On 2013-05-07 9:21 AM, Francisco Cuesta wrote: >> Hello, >> >> I have some doubts concerning to the hostapd package, working with >> Attitude Adjustment openwrt version. So, I would appreciate if someone >> might clarify them to me. >> >> Firstly, I have noticed that apart from the hostapd package included >> on package/hostapd directory, there is another small version of >> hostapd located in the drivers of the linux kernel >> (linux-3-3.8/drivers/net/wireless/hostap). > Just because the name is similar doesn't mean that it's connected to > hostapd :) > >> My question is, if I had to >> change the main hostapd package, should I change the kernel version of >> hostap too? Might there be any kind of incompatibility if I only >> change the package and not the one in the kernel? I ask this, because >> I'm not sure whether they make use of each other or not. > There's no connection between the two, so no compatibility issues. > >> Secondly, could someone point me out where in hostapd code is >> distinguished between adhoc mode and ap mode? > Easy: AP mode uses it, Ad-Hoc mode doesn't. > > - Felix > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] hostapd doubts
Adhoc is configured by the 'iw' utility in the mac80211.sh script. On Tue 07 May 2013 09:10:11 AM EDT, Francisco Cuesta wrote: Thanks Felix for clarifying my newbie doubts!! Secondly, could someone point me out where in hostapd code is distinguished between adhoc mode and ap mode? Easy: AP mode uses it, Ad-Hoc mode doesn't. So, where is the ad-hoc mode configured then? Is it done in the proprietary driver (in my case ath9k) or it is done in the kernel? Thanks again 2013/5/7 Felix Fietkau : On 2013-05-07 9:21 AM, Francisco Cuesta wrote: Hello, I have some doubts concerning to the hostapd package, working with Attitude Adjustment openwrt version. So, I would appreciate if someone might clarify them to me. Firstly, I have noticed that apart from the hostapd package included on package/hostapd directory, there is another small version of hostapd located in the drivers of the linux kernel (linux-3-3.8/drivers/net/wireless/hostap). Just because the name is similar doesn't mean that it's connected to hostapd :) My question is, if I had to change the main hostapd package, should I change the kernel version of hostap too? Might there be any kind of incompatibility if I only change the package and not the one in the kernel? I ask this, because I'm not sure whether they make use of each other or not. There's no connection between the two, so no compatibility issues. Secondly, could someone point me out where in hostapd code is distinguished between adhoc mode and ap mode? Easy: AP mode uses it, Ad-Hoc mode doesn't. - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Use honour-copts if Openwrt toolchain itself is used as External.
I've tried using Openwrt toolchain itself as External toolchain by the following procedure:- # Compile and Install the toolchain in a different path make tools/install; make toolchain/install TOOLCHAIN_DIR="/opt/sw_toolchains/toolchain-mips_r2_gcc-4.7-linaro_uClibc-0.9.33.2" Used above path by setting the following macros:- CONFIG_TARGET_OPTIMIZATION="-Os -pipe -mips32r2 -mtune=mips32r2 -funit-at-a-time -fno-caller-saves" CONFIG_SOFT_FLOAT=y CONFIG_EXTERNAL_TOOLCHAIN=y # CONFIG_NATIVE_TOOLCHAIN is not set CONFIG_TARGET_NAME="mips-openwrt-linux-uclibc" CONFIG_TOOLCHAIN_PREFIX="mips-openwrt-linux-uclibc-" CONFIG_TOOLCHAIN_ROOT="/opt/sw_toolchains/toolchain-mips_r2_gcc-4.7-linaro_uClibc-0.9.33.2" CONFIG_TOOLCHAIN_BIN_PATH="./usr/bin ./bin" CONFIG_TOOLCHAIN_INC_PATH="./usr/include ./include" CONFIG_TOOLCHAIN_LIB_PATH="./usr/lib ./lib" Above method works well. But, I have trouble with setting honour-copts. As per rules.mk and include/kernel.mk, if we set an external toolchain, the buildsystem will not pass honour-copts to userspace packages as well as kernel packages. But what if we use openwrt toolchain itself as external toolchain? How we can set fhonour copts? One way is to pass on CONFIG_TARGET_OPTIMIZATION like:- CONFIG_TARGET_OPTIMIZATION="-Os -pipe -mips32r2 -mtune=mips32r2 -funit-at-a-time -fno-caller-saves -fhonour-copts" In this case, it works for userspace apps compilation. But not on kernel compilation. And I cannot use the same config file if the toolchain is built from scratch. Because the buildsystem will again add honour-copts and it will be a added twice. Is there a way to add additional config option on external toolchain like: Use Openwrt toolchain = y ? So that we export honour-copts as default? In this case even we can avoid configuring toolchain prefix, libpath, include path etc. and keep only toolchain root as configurable field. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] libubox: Allow to build against libjson-c > 0.9
On 2013-05-07 3:04 PM, Helmut Schaa wrote: > Signed-off-by: Helmut Schaa Applied and pushed, thanks. > --- > > Not sure where to send libubox patches to, openwrt-devel? > Helmut Yes, openwrt-devel is fine. - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] [ar71xx] Add support for Netgear WNDAP360
Here is corrected version (only thing not working are wifi LEDs):
Signed-off-by: Jacek Kikiewicz
---
Index: target/linux/ar71xx/image/Makefile
===
--- target/linux/ar71xx/image/Makefile (revision 36156)
+++ target/linux/ar71xx/image/Makefile (working copy)
@@ -185,6 +185,7 @@
uap_pro_mtdlayout=mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,1536k(kernel),14208k(rootfs),256k(cfg)ro,64k(EEPROM)ro,15744k@0x5(firmware)
ubdev_mtdlayout=mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,1024k(kernel),6464k(rootfs),64k(certs),256k(cfg)ro,64k(EEPROM)ro,7488k@0x5(firmware)
whrhpg300n_mtdlayout=mtdparts=spi0.0:248k(u-boot)ro,8k(u-boot-env)ro,1024k(kernel),2752k(rootfs),64k(art)ro,3712k@0x4(firmware)
+wndap360_mtdlayout=mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,1728k(kernel),6080k(rootfs),64k(art)ro,7808k@0x5(firmware)
wndr3700_mtdlayout=mtdparts=spi0.0:320k(u-boot)ro,128k(u-boot-env)ro,1024k(kernel),6656k(rootfs),64k(art)ro,7680k@0x7(firmware)
wndr3700v2_mtdlayout=mtdparts=spi0.0:320k(u-boot)ro,128k(u-boot-env)ro,1024k(kernel),14848k(rootfs),64k(art)ro,15872k@0x7(firmware)
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),1152k(kernel),24448k(rootfs),25600k@0x6c(firmware),256k(caldata_backup),-(reserved)
@@ -876,6 +877,8 @@
$(eval $(call
SingleProfile,MyLoader,$(fs_64k),WPE72_8M,wpe72,,ttyS0,115200,0x80,8M))
$(eval $(call
SingleProfile,MyLoader,$(fs_64k),WPE72_16M,wpe72,,ttyS0,115200,0x100,16M))
+# This is used with AthGzip profile for now
+$(eval $(call
SingleProfile,AthGzip,$(fs_64k),WNDAP360,wndap360,WNDAP360,ttyS0,9600,$$(wndap360_mtdlayout),1769472,6225920,KRuImage))
$(eval $(call
SingleProfile,Netgear,$(fs_64k),WNDR3700V1,wndr3700,WNDR3700,ttyS0,115200,$$(wndr3700_mtdlayout),3700,WNDR3700,""
NA,))
$(eval $(call
SingleProfile,Netgear,$(fs_64k),WNDR3700V2,wndr3700v2,WNDR3700,ttyS0,115200,$$(wndr3700v2_mtdlayout),3701,WNDR3700v2,"",-H
29763654+16+64))
$(eval $(call
SingleProfile,Netgear,$(fs_64k),WNDR3800,wndr3800,WNDR3700,ttyS0,115200,$$(wndr3700v2_mtdlayout),3701,WNDR3800,"",-H
29763654+16+128))
Index: target/linux/ar71xx/patches-3.8/610-MIPS-ath79-openwrt-machines.patch
===
--- target/linux/ar71xx/patches-3.8/610-MIPS-ath79-openwrt-machines.patch
(revision 36156)
+++ target/linux/ar71xx/patches-3.8/610-MIPS-ath79-openwrt-machines.patch
(working copy)
@@ -1,6 +1,6 @@
--- a/arch/mips/ath79/machtypes.h
+++ b/arch/mips/ath79/machtypes.h
-@@ -16,22 +16,112 @@
+@@ -16,22 +16,113 @@
enum ath79_mach_type {
ATH79_MACH_GENERIC = 0,
@@ -97,6 +97,7 @@
+ ATH79_MACH_WHR_HP_G300N,/* Buffalo WHR-HP-G300N */
+ ATH79_MACH_WHR_HP_GN, /* Buffalo WHR-HP-GN */
+ ATH79_MACH_WLAE_AG300N, /* Buffalo WLAE-AG300N */
++ ATH79_MACH_WNDAP360,/* NETGEAR WNDAP360 */
+ ATH79_MACH_WNDR3700,/* NETGEAR WNDR3700/WNDR3800/WNDRMAC */
+ ATH79_MACH_WNDR4300,/* NETGEAR WNDR4300 */
+ ATH79_MACH_WNR2000, /* NETGEAR WNR2000 */
@@ -216,7 +217,7 @@
config ATH79_MACH_PB44
bool "Atheros PB44 reference board"
select SOC_AR71XX
-@@ -68,6 +148,488 @@ config ATH79_MACH_PB44
+@@ -68,6 +148,498 @@ config ATH79_MACH_PB44
Say 'Y' here if you want your kernel to support the
Atheros PB44 reference board.
@@ -417,6 +418,16 @@
+ select ATH79_DEV_WMAC
+ select ATH79_ROUTERBOOT
+
++config ATH79_MACH_WNDAP360
++ bool "NETGEAR WNDAP360 board support"
++ select SOC_AR71XX
++ select ATH79_DEV_AP9X_PCI if PCI
++ select ATH79_DEV_ETH
++ select ATH79_DEV_GPIO_BUTTONS
++ select ATH79_DEV_LEDS_GPIO
++ select ATH79_DEV_M25P80
++ select ATH79_DEV_USB
++
+config ATH79_MACH_WNDR3700
+ bool "NETGEAR WNDR3700 board support"
+ select SOC_AR71XX
@@ -826,6 +837,7 @@
obj-$(CONFIG_ATH79_MACH_UBNT_XM) += mach-ubnt-xm.o
+obj-$(CONFIG_ATH79_MACH_WHR_HP_G300N) += mach-whr-hp-g300n.o
+obj-$(CONFIG_ATH79_MACH_WLAE_AG300N) += mach-wlae-ag300n.o
++obj-$(CONFIG_ATH79_MACH_WNDAP360) += mach-wndap360.o
+obj-$(CONFIG_ATH79_MACH_WNDR3700) += mach-wndr3700.o
+obj-$(CONFIG_ATH79_MACH_WNDR4300) += mach-wndr4300.o
+obj-$(CONFIG_ATH79_MACH_WNR2000) += mach-wnr2000.o
Index: target/linux/ar71xx/files/arch/mips/ath79/mach-wndap360.c
===
--- target/linux/ar71xx/files/arch/mips/ath79/mach-wndap360.c (revision 0)
+++ target/linux/ar71xx/files/arch/mips/ath79/mach-wndap360.c (working copy)
@@ -0,0 +1,105 @@
+/*
+ * Netgear WNDAP360 board support (proper leds / button support missing)
+ *
+ * Based on AP96
+ * Copyright (C) 2013 Jacek Kikiewicz
+ * Copyright (C) 2
[OpenWrt-Devel] [PATCH] AA:mac80211:rt2x00: Fix init of rt3290, rt3352, rt5350
After update upto compat-wireless-2013-02-22 some critical changes were lostand driver fail to allocate device. This fix was checked ondir620d1 (rt3352) and dir320b1 (rt5350). No check for rt3290 butit have the same init registers (reg2 - start init RF & reg17 - frequencyoffset eeprom value). Signed-off-by: Serge Vasilugin --- a/drivers/net/wireless/rt2x00/rt2800lib.c+++ b/drivers/net/wireless/rt2x00/rt2800lib.c@@ -4430,6 +4430,8 @@ static int rt2800_init_rfcsr(struct rt2x */ if (rt2x00_rt(rt2x00dev, RT3290) ||+ rt2x00_rt(rt2x00dev, RT3352) ||+ rt2x00_rt(rt2x00dev, RT5350) || rt2x00_rt(rt2x00dev, RT5390) || rt2x00_rt(rt2x00dev, RT5392)) { rt2800_rfcsr_read(rt2x00dev, 2, &rfcsr);@@ -4583,7 +4585,10 @@ static int rt2800_init_rfcsr(struct rt2x rt2x00_set_field32(®, OPT_14_CSR_BIT0, 1); rt2800_register_write(rt2x00dev, OPT_14_CSR, reg); - if (!rt2x00_rt(rt2x00dev, RT5390) &&+ if (!rt2x00_rt(rt2x00dev, RT3290) &&+ !rt2x00_rt(rt2x00dev, RT3352) &&+ !rt2x00_rt(rt2x00dev, RT5350) &&+ !rt2x00_rt(rt2x00dev, RT5390) && !rt2x00_rt(rt2x00dev, RT5392)) { rt2800_rfcsr_read(rt2x00dev, 17, &rfcsr); rt2x00_set_field8(&rfcsr, RFCSR17_TX_LO1_EN, 0);
618-rt2x00-fix-init-rt3352-rt5350-rt3290.patch
Description: Binary data
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] AA:mac80211:rt2x00: Fix init of rt3290, rt3352, rt5350
Thanks, will apply it to openwrt for dir320b1
2013/5/7 Сергей Василюгин
> After update upto compat-wireless-2013-02-22 some critical changes were
> lost
> and driver fail to allocate device. This fix was checked on
> dir620d1 (rt3352) and dir320b1 (rt5350). No check for rt3290 but
> it have the same init registers (reg2 - start init RF & reg17 - frequency
> offset eeprom value).
>
> Signed-off-by: Serge Vasilugin
>
> --- a/drivers/net/wireless/rt2x00/rt2800lib.c
> +++ b/drivers/net/wireless/rt2x00/rt2800lib.c
> @@ -4430,6 +4430,8 @@ static int rt2800_init_rfcsr(struct rt2x
> */
>
> if (rt2x00_rt(rt2x00dev, RT3290) ||
> +rt2x00_rt(rt2x00dev, RT3352) ||
> +rt2x00_rt(rt2x00dev, RT5350) ||
> rt2x00_rt(rt2x00dev, RT5390) ||
> rt2x00_rt(rt2x00dev, RT5392)) {
> rt2800_rfcsr_read(rt2x00dev, 2, &rfcsr);
> @@ -4583,7 +4585,10 @@ static int rt2800_init_rfcsr(struct rt2x
> rt2x00_set_field32(®, OPT_14_CSR_BIT0, 1);
> rt2800_register_write(rt2x00dev, OPT_14_CSR, reg);
>
> -if (!rt2x00_rt(rt2x00dev, RT5390) &&
> +if (!rt2x00_rt(rt2x00dev, RT3290) &&
> +!rt2x00_rt(rt2x00dev, RT3352) &&
> +!rt2x00_rt(rt2x00dev, RT5350) &&
> +!rt2x00_rt(rt2x00dev, RT5390) &&
> !rt2x00_rt(rt2x00dev, RT5392)) {
> rt2800_rfcsr_read(rt2x00dev, 17, &rfcsr);
> rt2x00_set_field8(&rfcsr, RFCSR17_TX_LO1_EN, 0);
>
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] bump anyremote to v6.3
This patch updates anyremote from 6.2 to 6.3
Signed-off-by: Mikhail Fedotov < anyremote at mail.ru >
Index: feeds/packages/utils/anyremote/Makefile
===
--- feeds/packages/utils/anyremote/Makefile (revision 36568)
+++ feeds/packages/utils/anyremote/Makefile (working copy)
@@ -8,12 +8,12 @@
include $(TOPDIR)/rules.mk
PKG_NAME:=anyremote
-PKG_VERSION:=6.2
+PKG_VERSION:=6.3
PKG_RELEASE:=1
PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz
PKG_SOURCE_URL:=@SF/${PKG_NAME}
-PKG_MD5SUM:=130369d8f632127b20de67930386e9ca
+PKG_MD5SUM:=f041a6e5938f021933e5052941d571c3
include $(INCLUDE_DIR)/package.mk
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [packages] polipo: Don't spuriously ignore CNAMEs after a DNS timeout. Polipo might quit with SIGPIPE without this patch
>> 2. The patch description is incorrect -- the bug symptom is not >> SIGPIPE. SIGPIPE is globally ignored by Polipo. > > I had polipo segfaulting before applying this patch. With gdb I > thought to understand it was a SIGPIPE problem, but I can be wrong > because I am not a experienced developer. Juliusz you are right. SIGPIPE was completely wrong. I went to study. I am very begineer gdb user and I did not have a good understanding of signals. The situation is the following: version 1.0.4: eventually segfaults, but I was not able yet to reproduce this bug in GDB version 1.0.4: you should ignore SIGPIPE signal in GDB if you want to debug version 1.0.4: debian applies this patch to the deb package on top of 1.0.4, so might have it also on OpenWRT because it should increase the overall stability git master: looks more stable, I have this version running now and it is not crashing. sorry for the confusion on the list. Making debug at late night after long days of work did not help :)) ciao :) Saverio ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
