Along with Jonathan's Engenius ECB-3500 and my Open Mesh OM1P, I think
there is a very good chance this changeset will also affect FONera
2100, Engenius EOC-1650, Engenius EOC-2610, and maybe Engenius EOC
2611.
What are next steps for supporting multiple board configs on atheros
target? I.e. is t
I can confirm that this issue effects EnGenius ECB-3500 as well.
On 08/27/2012 09:24 AM, Karl Palsson wrote:
>
> I think this really just means that the Atheros platform needs to be broken
> up into separate boards,
> like ar71xx and other newer platforms. Currently a Atheros targets get
>
I think this really just means that the Atheros platform needs to be broken up
into separate boards,
like ar71xx and other newer platforms. Currently a Atheros targets get the
same init code, and
clearly your board needs different init code to mine :)
Cheers,
Karl P
On Sun, Aug 26, 2012 a
This changeset on trunk appears to prevent booting up on a OM1P
(Atheros AR2315). That is, freshly compiled r32884 boots fine on
OM1P, but flashing the device with r32885+ leads to unresponsive eth0
interface on OM1P. I am lacking a TTL/serial cable, so I can't share
more information.
https://de
From: Karl Palsson
atheros trunk moved to full sysfs gpiolib, but the leds were forgotten.
This restores the wlan led that was missing after switching from backfire
to trunk.
Signed-off-by: Karl Palsson
---
.../linux/atheros/base-files/etc/uci-defaults/leds | 11 +++
target/linux/ath
