Re: [OpenWrt-Devel] LUCI works extremely slow...
My understanding is that OpenWRT Attitude Adjustment, along with current versions of trunk, are not expected to run in any reliable way under less than 32MB of RAM. In particular, the v3.x kernel is not supported for so little memory, and the OpenWRT dev community likewise doesn't support it. Hi Ben What you means is v3.x kernel don't support 32MB RAM? not the issue of LUCI? Everything else works fine, and I can see some devices with same hardware on openwrt supported list. Also new gargoyle works pretty good. During LUCI operations filesystem is heavly used, I can see a 50-90% CPU usage in [spi0] kernel process. Using precompiled version helps a little, but it's still unusable. Best regards. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] [lantiq] set mips16 support.
Set mips16 support in XWAY subtarget. This patch is based in changeset #36600 Signed-off-by: José Vázquez Fernández ppvazquez...@gmail.com Signed-off-by: Felix Fietkau n...@openwrt.org ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] [lantiq] set mips16 support.
- Mensaje reenviado De: José Vázquez Fernández ppvazquez...@gmail.com Para: openwrt-devel@lists.openwrt.org openwrt-devel@lists.openwrt.org Cc: openwrt-devel@lists.openwrt.org openwrt-devel@lists.openwrt.org Asunto: [OpenWrt-Devel] [PATCH] [lantiq] set mips16 support. Fecha: Tue, 11 Jun 2013 13:42:24 +0200 Set mips16 support in XWAY subtarget. This patch is based in changeset #36600 Signed-off-by: José Vázquez Fernández ppvazquez...@gmail.com Signed-off-by: Felix Fietkau n...@openwrt.org Index: target/linux/lantiq/xway/target.mk === --- target/linux/lantiq/xway/target.mk (revisión: 36913) +++ target/linux/lantiq/xway/target.mk (copia de trabajo) @@ -1,7 +1,7 @@ ARCH:=mips SUBTARGET:=xway BOARDNAME:=XWAY -FEATURES:=squashfs atm +FEATURES:=squashfs atm mips16 DEFAULT_PACKAGES+=kmod-leds-gpio kmod-gpio-button-hotplug ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] [lantiq] Tune the XWAY subtarget cflags.
Tune the XWAY subtarget cflags. This patch sets the cflags -mtune=34kc -mdsp only in XWAY subtarget, while the others remain with mtune=mips32r2. Although the Danube has a Mips 24KEc core performs well with the above cflags. Signed-off-by: José Vázquez Fernández ppvazquez...@gmail.com Index: target/linux/lantiq/svip_be/target.mk === --- target/linux/lantiq/svip_be/target.mk (revisión: 36913) +++ target/linux/lantiq/svip_be/target.mk (copia de trabajo) @@ -3,6 +3,7 @@ BOARDNAME:=SVIP Big Endian FEATURES:=squashfs DEVICE_TYPE:=other +CFLAGS+= -mtune=mips32r2 DEFAULT_PACKAGES+= uboot-svip hostapd-mini Index: target/linux/lantiq/xway/target.mk === --- target/linux/lantiq/xway/target.mk (revisión: 36913) +++ target/linux/lantiq/xway/target.mk (copia de trabajo) @@ -2,6 +2,7 @@ SUBTARGET:=xway BOARDNAME:=XWAY FEATURES:=squashfs atm +CFLAGS+= -mtune=34kc -mdsp DEFAULT_PACKAGES+=kmod-leds-gpio kmod-gpio-button-hotplug Index: target/linux/lantiq/svip_le/target.mk === --- target/linux/lantiq/svip_le/target.mk (revisión: 36913) +++ target/linux/lantiq/svip_le/target.mk (copia de trabajo) @@ -3,6 +3,7 @@ BOARDNAME:=SVIP Little Endian FEATURES:=squashfs DEVICE_TYPE:=other +CFLAGS+= -mtune=mips32r2 DEFAULT_PACKAGES+= uboot-svip hostapd-mini Index: target/linux/lantiq/falcon/target.mk === --- target/linux/lantiq/falcon/target.mk(revisión: 36913) +++ target/linux/lantiq/falcon/target.mk(copia de trabajo) @@ -3,6 +3,7 @@ BOARDNAME:=Falcon FEATURES:=squashfs DEVICE_TYPE:=other +CFLAGS+= -mtune=mips32r2 DEFAULT_PACKAGES+= kmod-ifxos gpon-base-files kmod-leds-gpio kmod-ledtrig-heartbeat \ kmod-gpon-optic-drv gpon-optic-drv kmod-gpon-onu-drv gpon-onu-drv \ Index: target/linux/lantiq/ase/target.mk === --- target/linux/lantiq/ase/target.mk (revisión: 36913) +++ target/linux/lantiq/ase/target.mk (copia de trabajo) @@ -2,6 +2,7 @@ SUBTARGET:=ase BOARDNAME:=Amazon-SE FEATURES:=squashfs atm +CFLAGS+= -mtune=mips32r2 DEFAULT_PACKAGES+=kmod-pppoa ppp-mod-pppoa linux-atm atm-tools br2684ctl kmod-ltq-dsl-ase ltq-dsl-app Index: target/linux/lantiq/Makefile === --- target/linux/lantiq/Makefile(revisión: 36913) +++ target/linux/lantiq/Makefile(copia de trabajo) @@ -13,7 +13,7 @@ LINUX_VERSION:=3.8.13 -CFLAGS=-Os -pipe -mips32r2 -mtune=mips32r2 -fno-caller-saves -mno-branch-likely +CFLAGS=-Os -pipe -mips32r2 -fno-caller-saves -mno-branch-likely define Target/Description Build firmware images for Lantiq SoC ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Compiling kernel modules with debugging symbols
Following up from: https://lists.openwrt.org/pipermail/openwrt-devel/2013-February/018845.html Hello Siva, On 02/18/2013 05:11 AM, Sivateja Patibandla wrote: Hi, I'm using attitude adjustment latest stable release. And I'm trying to compile the kernel modules with debugging symbols enables so that I could load the kernel module in gdb. In the menuconfig although I checked Compile the packages with debugging info, gdb is still not able to see the debugging symbols in the kernel module. I'm trying to debug ath5k.ko and mac80211.ko. My kernel image (vmlinux) is loaded fine in gdb with debugging symbols but not the kernel modules. Could anyone tell me what I'm missing? The option Compile the packages with debugging info is actually relevant only for applications packages (not modules). For modules, the debugging option is controlled by the configuration symbol Compile the kernel with debug information which also affects the entire Linux kernel. -- Florian I'm also using Attitude Adjustment and can't seem to figure out how to build the kernel modules with debugging symbols. I have CONFIG_KERNEL_KALLSYMS=y and CONFIG_NO_STRIP=y but still don't have the symbols in the kernel modules, only the kernel itself. I made a Backfire build with these options and debugging symbols are in those kernel modules. Regards, Nathan ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] free Linksys E3200
Hey openwrt devs, I clearly have no time to mess with the the E3200 I have. I have modded the thing to have a rs232 db9 port. I'd like to offer it for free to anyone that wants to work on OpenWRT on this device. Any takers? wt ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] free Linksys E3200
On Tue, 2013-06-11 at 11:00 -0700, Warren Turkal wrote: Hey openwrt devs, I clearly have no time to mess with the the E3200 I have. I have modded the thing to have a rs232 db9 port. I'd like to offer it for free to anyone that wants to work on OpenWRT on this device. Any takers? wt I'm not familiar with that model. How much RAM and flash, and which target? Any special features, e.g. USB? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] free Linksys E3200
2013/6/11 Daniel Gimpelevich dan...@gimpelevich.san-francisco.ca.us: On Tue, 2013-06-11 at 11:00 -0700, Warren Turkal wrote: Hey openwrt devs, I clearly have no time to mess with the the E3200 I have. I have modded the thing to have a rs232 db9 port. I'd like to offer it for free to anyone that wants to work on OpenWRT on this device. Any takers? wt I'm not familiar with that model. How much RAM and flash, and which target? Any special features, e.g. USB? Have you tried something called Google? http://wiki.openwrt.org/toh/linksys/e3200 http://wikidevi.com/wiki/Linksys_E3200 -- Rafał ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] LUCI works extremely slow...
Quoting from the supported hardware list, and likewise from the Attitude Adjustment announcement made earlier this year: Note that with the release of 'Attitude Adjustment (12.09 final)' on 25th April 2013, 'Lower end devices with only 16 MiB RAM will easily run out of Memory…'. http://wiki.openwrt.org/toh/start I do see that some device on that list are spec'ed at 16MB RAM, and I can only guess those are old entries. My own attempts to get recent versions of OpenWRT running on a FONera 2100 router, which has the same CPU and RAM capacity as your device, proved futile due to memory exhaustion and random kernel crashes. Even without the LUCI UI. My understanding is that the memory requirement is a hard limit. On Tue, Jun 11, 2013 at 4:13 AM, Wojciech Kromer wojciech.kro...@dgt.com.pl wrote: My understanding is that OpenWRT Attitude Adjustment, along with current versions of trunk, are not expected to run in any reliable way under less than 32MB of RAM. In particular, the v3.x kernel is not supported for so little memory, and the OpenWRT dev community likewise doesn't support it. Hi Ben What you means is v3.x kernel don't support 32MB RAM? not the issue of LUCI? Everything else works fine, and I can see some devices with same hardware on openwrt supported list. Also new gargoyle works pretty good. During LUCI operations filesystem is heavly used, I can see a 50-90% CPU usage in [spi0] kernel process. Using precompiled version helps a little, but it's still unusable. Best regards. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel -- Ben West http://gowasabi.net b...@gowasabi.net 314-246-9434 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] free Linksys E3200
On Tue, 2013-06-11 at 20:52 +0200, Rafał Miłecki wrote: 2013/6/11 Daniel Gimpelevich dan...@gimpelevich.san-francisco.ca.us: On Tue, 2013-06-11 at 11:00 -0700, Warren Turkal wrote: Hey openwrt devs, I clearly have no time to mess with the the E3200 I have. I have modded the thing to have a rs232 db9 port. I'd like to offer it for free to anyone that wants to work on OpenWRT on this device. Any takers? wt I'm not familiar with that model. How much RAM and flash, and which target? Any special features, e.g. USB? Have you tried something called Google? http://wiki.openwrt.org/toh/linksys/e3200 http://wikidevi.com/wiki/Linksys_E3200 Looks like a nice update of the WRT350Nv1 I've been meaning to get back to. Pity about the wifi. Wifi was the big issue with the WRT350Nv1 last I tried. I figure I should try it again first to see how trunk or at least AA will function with its 32MB RAM. If it's too tight now, I might be interested, but I no longer have a car, so you'd have to drop it off in that case. I'd strongly prefer one of the TP-Link models Felix has been working on instead, though. I might just order one of those if it comes to that; we'll see within the next few weeks. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Add elliptic curve crypto compilation options to openssl
Etienne, would you happen to know if the EC implementations in other embedded SSL implementations like cyasslhttp://www.yassl.com/yaSSL/Docs-cyassl-manual-4-features.htmlwould work with authsae? On Tue, May 28, 2013 at 12:11 PM, Etienne Champetier etienne.champet...@free.fr wrote: This patch adds EC compilation options to openssl OPENSSL_WITH_EC is needed for authsae (OPENSSL_WITH_EC2M isn't) Activating ec (but not ec2m) in openssl take 35Ko more on ar71xx (ipk size) Activating both take 52Ko. Signed-off-by: Etienne CHAMPETIER etienne.champet...@free.fr diff --git a/package/libs/openssl/Config.in b/package/libs/openssl/Config.in index 70d520c..b8a3779 100644 --- a/package/libs/openssl/Config.in +++ b/package/libs/openssl/Config.in @@ -1,6 +1,15 @@ menu Configuration depends on PACKAGE_libopenssl +config OPENSSL_WITH_EC + bool + prompt Enable elliptic curve support + +config OPENSSL_WITH_EC2M +bool +depends on OPENSSL_WITH_EC +prompt Enable ec2m support + config OPENSSL_ENGINE_CRYPTO bool prompt Crypto acceleration support diff --git a/package/libs/openssl/Makefile b/package/libs/openssl/Makefile index 0091579..8b0f524 100644 --- a/package/libs/openssl/Makefile +++ b/package/libs/openssl/Makefile @@ -9,7 +9,7 @@ include $(TOPDIR)/rules.mk PKG_NAME:=openssl PKG_VERSION:=1.0.1e -PKG_RELEASE:=1 +PKG_RELEASE:=2 PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz PKG_SOURCE_URL:=http://www.openssl.org/source/ \ @@ -20,7 +20,8 @@ PKG_MD5SUM:=66bf6f10f060d561929de96f9dfe5b8c PKG_LICENSE:=SSLEAY OPENSSL PKG_LICENSE_FILES:=LICENSE PKG_BUILD_DEPENDS:=ocf-crypto-headers -PKG_CONFIG_DEPENDS:=CONFIG_OPENSSL_ENGINE_CRYPTO CONFIG_OPENSSL_ENGINE_DIGEST +PKG_CONFIG_DEPENDS:=CONFIG_OPENSSL_ENGINE_CRYPTO CONFIG_OPENSSL_ENGINE_DIGEST \ + OPENSSL_WITH_EC OPENSSL_WITH_EC2M include $(INCLUDE_DIR)/package.mk @@ -75,7 +76,7 @@ endef OPENSSL_NO_CIPHERS:= no-idea no-md2 no-mdc2 no-rc5 no-sha0 no-smime \ no-rmd160 no-aes192 no-ripemd no-camellia no-ans1 no-krb5 -OPENSSL_OPTIONS:= shared no-ec no-err no-hw no-threads zlib-dynamic no-sse2 +OPENSSL_OPTIONS:= shared no-err no-hw no-threads zlib-dynamic no-sse2 ifdef CONFIG_OPENSSL_ENGINE_CRYPTO OPENSSL_OPTIONS += -DHAVE_CRYPTODEV @@ -86,6 +87,14 @@ else OPENSSL_OPTIONS += no-engines endif +ifndef CONFIG_OPENSSL_WITH_EC + OPENSSL_OPTIONS += no-ec +endif + +ifndef CONFIG_OPENSSL_WITH_EC2M + OPENSSL_OPTIONS += no-ec2m +endif + ifeq ($(CONFIG_x86_64),y) OPENSSL_TARGET:=linux-x86_64 else ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel -- Ben West http://gowasabi.net b...@gowasabi.net 314-246-9434 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
