[OpenWrt-Devel] brcm47xx: building smaller images to fit LuCI

The snapshot brcm47xx .trx does not leave enough space remaining to install LuCI. This may not be an issue on the released images where LuCI is included in the squashfs, if it is gets better compression on squash

Re: [OpenWrt-Devel] no such plugin: noip.com

ddns-scripts (main package, and commandline interface), with luci-app-ddns (gui). Here http://wiki.openwrt.org/doc/howto/ddns.client?s%5B%5D=ddns , on the wiki, there is a good explanation of how to use the ddns-scripts and luci-app-ddns (actually I learnt of them from this :-) ). Also found yaddn

[OpenWrt-Devel] android rootfs using proot and openwrt

I just put online a small project. It uses OpenWrt for the rootfs, which is one of its main components. More info and downloads are at https://sites.google.com/site/taldewandroid/ Any feedback, questions, comments etc. would be appreciated :-). Enjoy!

[OpenWrt-Devel] [PATCH][mac80211]b43: REFORMATTED: UPDATED fix for Linksys E1000 V1 GPIOs

Here is the patch from https://lists.openwrt.org/pipermail/openwrt-devel/2013-January/018171.html (which itself was an update for https://lists.openwrt.org/pipermail/openwrt-devel/2013-January/018155.html). It is reformatted to apply straight to the OpenWrt tree. Is this the way it is supposed to

Re: [OpenWrt-Devel] [PATCH][mac80211]b43: UPDATED fix for Linksys E1000 V1 GPIOs

orted; his work, suggestions, and advice helped a lot! On Fri, Jan 4, 2013 at 7:10 AM, hhm wrote: > UPDATE: > > This patch INVALIDATES the first one I sent for this fix. > The other one made the LEDs behave properly, however the wireless did not > work. > This one fixes it, the w

Re: [OpenWrt-Devel] [PATCH][toolchain/uclibc] build: enable ld.so standalone (LDSO_STANDALONE_SUPPORT)

> How does it affect the size of the libc binaries? It seems to be about 4k (the most concrete measurement I have is from compiling it standalone for x86_64; in OpenWrt builds it is hard to tell the difference, a few of the binaries are bigger by about 4k altogether). I tested the difference in s

[OpenWrt-Devel] [PATCH][toolchain/uclibc] build: enable ld.so standalone (LDSO_STANDALONE_SUPPORT)

This patch enables the LDSO_STANDALONE_SUPPORT kconfig option of uClibc by default. This can be useful e.g. for faking chroot of a rootfs, for example, using proot (http://proot.me/ https://github.com/cedric-vincent/PRoot). Right now this can be done by hacking the makefiles (for example the way *

[OpenWrt-Devel] [PATCH][mac80211]b43: UPDATED fix for Linksys E1000 V1 GPIOs

UPDATE: This patch INVALIDATES the first one I sent for this fix. The other one made the LEDs behave properly, however the wireless did not work. This one fixes it, the wireless work properly. (It uses the value of the "leddc" nvram var, 0x, of the Linksys E1000 v1; see https://forum.openwrt.o

[OpenWrt-Devel] [PATCH][mac80211]b43: fix for Linksys E1000 V1 GPIOs

This patch fixes a problem with wrong GPIOs being changed when the wlan is on, which disables the wired network ports until the right GPIO is turned back off. (see https://lists.openwrt.org/pipermail/openwrt-devel/2012-December/018113.html). The patch makes it only use the correct GPIO pin. NOTE:

Re: [OpenWrt-Devel] [brcm47xx] Linksys E1000 V1: "wifi up" messing up LEDs (which disables ethernet ports)

Thanks so much! It works now! Changing the mask and set vars worked! (and some printk'ing to see what was happening). On Mon, Dec 31, 2012 at 1:47 PM, Rafał Miłecki wrote: > 2012/12/31 hhm : >> So I am guessing this may be because of some of these: 1) the wireless >> driver,

[OpenWrt-Devel] [brcm47xx] Linksys E1000 V1: "wifi up" messing up LEDs (which disables ethernet ports)

There is a problem on my E1000, where when the wifi is turned on, some LEDs/GPIOs are set and unset (the same ones every time). This is a problem because there is one GPIO which turns on all the LAN/WAN LEDs and (physically/electrically) disconnects all wired ports, thereby breaking the wired netwo

[OpenWrt-Devel] [PATCH][brcm47xx] add diag support for Linksys E1000 V1

This adds diag leds/buttons support for Linksys E1000 V1. It worked on my router, however it may need some tweaking by people more familiar with openwrt and c to make it fit for commiting. --- diff --git a/package/broadcom-diag/src/diag.c b/package/broadcom-diag/src/diag.c index 7e0ff02

[OpenWrt-Devel] regression: Serial flash not found on linksys e1000 (brcm47162)

Hi, Until recently (including with the RC1 release of OpenWrt Attitude Adjustment) things were working ok on the linksys e1000 (besides the things which were not ready then). However, using recent builds of trunk (built by me, and built by http://downloads.openwrt.org/snapshots/), the serial flas

Re: [OpenWrt-Devel] CFE help for bricked WRT54GS v2.

On a linksys e1000, I do: For default stock firmware: flash -ctheader : flash1.trx and for openwrt: flash -noheader : flash1.trx I use tftp/tftp-hfa on debian, using tftp PUT instead of having a tftp server, with something like this: cd ; echo -e 'binary\nrexmt 1\ntimeout 613\ntrace\nverbose\nput