AFAICT OpenWRT comes with some support for the Hame MPR-A1 thingy
(although its 16MB of RAM and 4MB of flash probably prevent it from
being fully supported).
I had no trouble building an image for it, but now I'm wondering how to
install that image. I went to http://wiki.openwrt.org/toh/hame/mpr
True. Perhaps that makes it a moot issue for BB.
But I dont think it would hurt to be ahead of the curve in this day and age...
I am not the only one adding this latent protection to MIPS:
https://webrtc-codereview.appspot.com/994006/
https://gcc.gnu.org/ml/gcc-patches/2014-09/msg02430.html (s
On 10/03/2014 10:23 PM, John Crispin wrote:
>
>
> On 01/09/2014 17:53, Matthias Schiffer wrote:
>> All TP-LINK machine names begin with "TP-LINK", so there's no need
>> to check for more specific model names. This also allows adding new
>> models like the Archer series more easily.
>>
>
> are yo
On 02/10/2014 15:41, Michel Stam wrote:
> The scripts were based on the netifd dhcp scripts, and should add
> zeroconf support to /etc/config/network Example: config interface
> 'lan' option ifname 'eth0' option auto '0' option proto 'zeroconf'
>
> Optionally, the desired IP address can be added
On 01/09/2014 17:53, Matthias Schiffer wrote:
> All TP-LINK machine names begin with "TP-LINK", so there's no need
> to check for more specific model names. This also allows adding new
> models like the Archer series more easily.
>
are you sure, that they *all* start with TP-LINK ?
> Signed
the patch does not apply anymore. can you rebase it and send it again
please ?
On 17/09/2014 13:38, open...@rogerpueyo.com wrote:
> From: Roger Pueyo Centelles
>
> --- target/linux/ramips/base-files/etc/board.d/01_leds | 3 +
> .../linux/ramips/base-files/etc/board.d/02_network | 1 +
> target
have a look at FONER20N.dts
switch {
label = "switch";
gpios = <&gpio0 13 1>;
linux,code = <0xf7>;
linux,input-type = <5>; /* EV_SW */
};
that would obsolete 2 and you need to change 3. i have merged 1 into
my tree.
On 17/09/2014 10:22, Russell Senior wrote:
>
>
EOL as in not produced anymore or has no existing users ?
On 23/09/2014 21:33, Michael Heimpold wrote:
> This board is EOL, we should not bother anymore with it.
>
> Signed-off-by: Michael Heimpold ---
> .../files-3.10/arch/arm/mach-at91/board-tqma9263.c | 219
>
> .../fil
Add owrt mailing list to cc.
Any suggestions?
2014-09-30 0:57 GMT+04:00 Sergey Ryazanov :
> 2014-09-29 13:30 GMT+04:00 Jonas Gorski :
>> On Sun, Sep 28, 2014 at 8:33 PM, Sergey Ryazanov
>> wrote:
>>> Add common code for Atheros AR5312 and Atheros AR2315 SoCs families.
>>>
[...]
>>>
>>> +config
Hi Dave,
On Oct 3, 2014, at 01:07 , Dave Taht wrote:
[cut a lot...]
> But: the real killer, on ingress shaping, is the call to skb_clone in
> sch_ingress->act_mirred path, I think.
So I thought that we basically have around 50Mbps “shaping-capability”
on the wndrs which hew can distrib
On 03/10/2014 19:37, Jo-Philipp Wich wrote:
> Hi Michel, John.
>
>>> - for dev in $(ls /sys/class/ieee80211); do
>>> + for dev in $(ls /sys/class/ieee80211 2>/dev/null); do
>> what error do you see ? if you see an error we should try to fix that
>> rather than supressing it
> I suppose the cas
On 27/09/14 01:29 PM, Alive wrote:
> On 27/09/2014 23:34, Weedy wrote:
>> I got bit by this last week when I audited my ssh config and dropped all
>> weak/slow ciphers.
>> Couldn't log into my routers and had to add md5 ciphers and macs back.
>>
> You must rebuild dropbear package cleanly to test t
Hi Michel, John.
>> -for dev in $(ls /sys/class/ieee80211); do
>> +for dev in $(ls /sys/class/ieee80211 2>/dev/null); do
> what error do you see ? if you see an error we should try to fix that
> rather than supressing it
I suppose the case when "wifi detect" is invoked but no phy exists o
On 02/10/2014 15:28, Michel Stam wrote:
> Signed-off-by: Michel Stam
> ---
> package/kernel/mac80211/files/lib/wifi/mac80211.sh | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/package/kernel/mac80211/files/lib/wifi/mac80211.sh
> b/package/kernel/mac80211/files/lib/wifi/
On 02/10/2014 15:21, Michel Stam wrote:
> Early during bootup, kmodloader is started which loads the drivers
> in /etc/modules.d. Unfortunately at this time the system script has
> not run yet, which is supposed to set the console log level.
> Having the S10system script moved to an earlier time i
On 2014-10-03 19:14, Catalin Patulea wrote:
> On Wed, Oct 1, 2014 at 6:42 PM, Andrew McDonnell
> wrote:
>> It seems that OpenWRT sets the relevant flag to require uClibc to build with
>> NOEXECSTACK set. This is good. (For one introduction to NOEXECSTACK, see
>> http://wiki.gentoo.org/wiki/Harden
On Wed, Oct 1, 2014 at 6:42 PM, Andrew McDonnell
wrote:
> It seems that OpenWRT sets the relevant flag to require uClibc to build with
> NOEXECSTACK set. This is good. (For one introduction to NOEXECSTACK, see
> http://wiki.gentoo.org/wiki/Hardened/GNU_stack_quickstart )
Does anything actually en
see inline
On 02/10/2014 14:56, Michel Stam wrote:
> procd by default writes to /dev/console. When rebooting, this means
> that the terminal on which the reboot sequence was started will not
> see what is going on. This patch fixes that by reopening stdin,
> stdout and stderr to /dev/tty0 upon reb
stdout is already /dev/console i think and removing the messages on
shutdown also removes them in all other cases from the log.
should adding a single printf("%s", str); not work ?
On 02/10/2014 14:56, Michel Stam wrote:
> procd has the habit of logging startup/shutdown via rcS to syslog,
> which
On Tue, Aug 12, 2014 at 10:05 AM, Bas Mevissen wrote:
>
>
> On 08/09/2014 04:13 AM, Weedy wrote:
>> On Sun, Jul 27, 2014 at 3:31 PM, Weedy wrote:
>>> Is there anything I can do to stop this? It started sometime in the
>>> last 6months of trunk.
>>> Right after this and couple minutes after boot m
Hello Gert,
Good question.
What we discovered during an upgrade of our OpenWRT distribution (from a
fairly old one, I cannot exactly recall the version, I do recall it was
running kernel 2.6.22), was that suddenly our curses application did not
start anymore. And yes, for historical reasons, it w
This patch ensures that libgcc_s.so properly honours the NOEXECSTACK flag
for MIPS builds, when gcc-linaro-4.8 is the chosen C compiler.
Signed-off-by: Andrew McDonnell
---
Extended Summary: NOEXECSTACK is a security hardening feature of Linux that
prevents execution of arbitrary code for some c
This patch ensures that libgcc_s.so properly honours the NOEXECSTACK flag
for MIPS builds, when gcc-linaro-4.8 is the chosen C compiler.
Signed-off-by: Andrew McDonnell
---
Extended Summary: NOEXECSTACK is a security hardening feature of Linux that
prevents execution of arbitrary code for some c
Hi,
On Thu, Oct 02, 2014 at 02:56:18PM +0200, Michel Stam wrote:
> The problem was caused by procd not opening /dev/tty* (which ever was
> specified in
> /etc/inittab), causing /proc/PID/fd to point to /console instead.
> /dev/console is a
> non-controlling tty (CTTY), and cannot be used as one,
Am 03.10.2014 um 14:53 schrieb Jo-Philipp Wich:
> Hi,
>
> thanks for the patch. however the description still looks grammatically
> wrong: "On which interface up should start the ddns script process."
>
> Maybe it can be better written as "Trigger DDNS update when this
> interface is started"
>
Hi,
thanks for the patch. however the description still looks grammatically
wrong: "On which interface up should start the ddns script process."
Maybe it can be better written as "Trigger DDNS update when this
interface is started"
Ideas?
~ Jow
___
op
On Fri, 3 Oct 2014, Urs Rau (UK) wrote:
Hi Jo-Philipp,
On 26 Sep 2014, at 09:55, Jo-Philipp Wich
mailto:j...@openwrt.org>> wrote:
Hi.
The wan port is likely a dedicated, non-switch interface (e.g. eth1) on
this model. If you want to declare VLANs on it then simply create a new
interface usin
Hi Jo-Philipp,
On 26 Sep 2014, at 09:55, Jo-Philipp Wich
mailto:j...@openwrt.org>> wrote:
Hi.
The wan port is likely a dedicated, non-switch interface (e.g. eth1) on
this model. If you want to declare VLANs on it then simply create a new
interface using eth1.Y as manual physical ifname where Y
On Fri, Oct 3, 2014 at 11:32 AM, Christian Schoenebeck
wrote:
> Hi,
> we got a new ticket inside OpenWrt Ticket #18018 with problems inside LuCI
> app.
> This is normally not an OpenWrt ticket it's a LuCI ticket, but the user don't
> know.
> If the user try to post the ticket at LuCI trac it tak
Am 03.10.2014 um 12:24 schrieb Jo-Philipp Wich:
> Whats the meaning of this option?
>
> The description text is awful and since I do not know what it is
> supposed to do I cannot write a proper one.
>
> Also a signed-off-by would be good.
>
> ~ Jow
> _
Signed-off-by: Álvaro Fernández Rojas
---
diff --git a/target/linux/brcm63xx/patches-3.14/505-board_spw500v.patch
b/target/linux/brcm63xx/patches-3.14/505-board_spw500v.patch
index e2d36e7..f326a9e 100644
--- a/target/linux/brcm63xx/patches-3.14/505-board_spw500v.patch
+++ b/target/linux/brcm63xx
Whats the meaning of this option?
The description text is awful and since I do not know what it is
supposed to do I cannot write a proper one.
Also a signed-off-by would be good.
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http
Am 03.10.2014 um 09:31 schrieb OpenWrt:
> #18018: luci-app-ddns is missing the event interface option
> -+---
> Reporter: techstep@… | Owner: developers
> Type: defect | Status: new
> Priority: normal | Mile
Hi,
we got a new ticket inside OpenWrt Ticket #18018 with problems inside LuCI app.
This is normally not an OpenWrt ticket it's a LuCI ticket, but the user don't
know.
If the user try to post the ticket at LuCI trac it takes weeks before the
ticket
is reported by LuciTrac to the mailing lists.
During boot, a not found message is displayed for systems which do
not have uci 'network.globals.ula_prefix' defined in
/etc/config/network. The error message itself is not used and can
be ignored.
Signed-off-by: Michel Stam
---
package/base-files/files/etc/uci-defaults/12_network-generate-ula |
This patch fix the wnr2200 leds gpio, every lan led works now;
fix usb power, usb device can works now;
fix ar9287 led
Signed-off-by: Tao Guo
---
.../ar71xx/files/arch/mips/ath79/mach-wnr2200.c| 100 +
1 file changed, 41 insertions(+), 59 deletions(-)
diff --git a/target
Hello Jo,
I was not aware of this option, must have overlooked it. I will fix the
patch and resubmit it.
Kind regards,
Michel Stam
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt
Signed-off-by: Tao Guo
---
.../ar71xx/files/arch/mips/ath79/mach-wnr2200.c| 100 +
1 file changed, 41 insertions(+), 59 deletions(-)
diff --git a/target/linux/ar71xx/files/arch/mips/ath79/mach-wnr2200.c
b/target/linux/ar71xx/files/arch/mips/ath79/mach-wnr2200.c
index bf7f
Hey Felix,
I've already done this. My intention was to submit it to both OpenWRT
and Busybox, then add another commit to remove the patch once it is in a
busybox release.
See here:
OpenWRT commit -> busybox ticket
busybox/netifd: make zcip log to syslog (always) ->
ht
39 matches
Mail list logo
