From: Rafał Miłecki
The old usbdev trigger never supported assigning more than 1 USB port.
This code we got was never working as expected. Switch to usbport to
have LED working with both ports.
Signed-off-by: Rafał Miłecki
---
target/linux/apm821xx/base-files/etc/board.d/01_leds | 3 +--
1 fil
Hello folks,
running a community based wifi network based on OpenWRT I'm thinking
about using lede. Do you have any suggestions on this?
For doing so, I see the need for a more less stable base (stable as in:
few bugs, few refactorings / changes over time) Looking at lede at
moment I seed nightly
Hi,
On 21 October 2016 at 13:15, Eddi De Pieri wrote:
> Hi,
>
> Here to raise your attention to https://github.com/pgid69/bcm63xx-phone
> projet.
For this one I'd like to see the receipts, i.e. to know these aren't
based on (leaked) sources, or if derived through reverse engineering
as a white
Currently the reset script will try to run jffs2reset on boards that are
running a rw rootfs, such as ext4. This will cause jffs2reset to fail
and the board to never reboot while the LED blinks until a manual
reboot.
This commit does two different things:
1. Disables reset on boards that do not ha
Forgive me as I forgot the v3 in the patch header.
Previous patch discussion was at
http://lists.infradead.org/pipermail/lede-dev/2016-October/003473.html
- Chris Blake
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/m
Hello,
On Saturday, October 22, 2016 11:22:35 AM CEST Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> The old usbdev trigger never supported assigning more than 1 USB port.
> This code we got was never working as expected. Switch to usbport to
> have LED working with both ports.
>
> Signed-off-b
This adds the following changes to the x86_64 Kernel config:
1. Enables AES_x86_64, AEAD, and AES_NI_Intel.
2. Enables GPIO and GPIOLIB to match other targets.
Signed-off-by: Chris Blake
---
target/linux/x86/64/config-default | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
d
This patch was provided by Ben at http://lists.infradead.org/pipermail
/lede-dev/2016-October/003332.html and adds ccm(aes) support to the AES-NI
acceleration. Currently it is not submitted upstream, but has been confirmed
working on the PC Engines APU2 using openssl.
Cc: Ben Greear
Signed-off-by
This patch enables the kernel sp5100_tco watchdog driver to be built as
a kernel module.
Signed-off-by: Chris Blake
---
target/linux/x86/modules.mk | 15 +++
1 file changed, 15 insertions(+)
diff --git a/target/linux/x86/modules.mk b/target/linux/x86/modules.mk
index 1fc5ce5..f6a87e
This is the 2nd RFC to port the PC Engines APU2 board to LEDE. The last RFC can
be found at
http://lists.infradead.org/pipermail/lede-dev/2016-October/003326.html
Things Working:
- board detection
- USB ports
- LED/Button support
- ath9k and ath10k - to support both wireless cards sold via P
This patch adds the following drivers to the x86 target:
leds-apu2 - A driver that enables usage of the onboard LEDs and Reset
button wired to the chipset. This driver uses DMI to only enable on the
APU2 board.
gpio-nct5104d - A driver that allows for usage of the SuperIO GPIO chip
on the PC Engin
This patch adds the following upstream patches to the 4.4 kernel:
sp5100_tco: Add AMD Mullins platform support
sp5100_tco: Add AMD Carrizo platform support
sp5100_tco: fix the device check for SB800 and later chipsets
watchdog: sp5100_tco: properly check for new register layouts
These patches are
The following patch adds support for the PC Engines APU2 board within
the x86_64 target. Currently this patch relies on the beep package,
which is in review at http://lists.infradead.org/pipermail/lede-
dev/2016-October/003455.html
The changes are as follows:
- Enable the LED driver in the kernel
> This is the 2nd RFC to port the PC Engines APU2 board to LEDE. The last
RFC can be found at
http://lists.infradead.org/pipermail/lede-dev/2016-October/003326.html
Nice!
> Default Packages:
> - lm-sensors - Temp Monitoring
Does lm-sensors report all 4 core temps or just 1?
> Changes added from
On Sat, Oct 22, 2016 at 11:13 AM, STR . wrote:
>> This is the 2nd RFC to port the PC Engines APU2 board to LEDE. The last
> RFC can be found at
> http://lists.infradead.org/pipermail/lede-dev/2016-October/003326.html
> Nice!
>
>> Default Packages:
>> - lm-sensors - Temp Monitoring
> Does lm-senso
Compiling on XUbuntu x64 16.10 the following errors are shown
NOTICE: module
'/owbuild/trunk/build_dir/target-i386_pentium4_musl-1.1.15/linux-x86_generic/linux-4.4.26/fs/ext4/ext4.ko'
is built-in.
NOTICE: module
'/owbuild/trunk/build_dir/target-i386_pentium4_musl-1.1.15/linux-x86_generic/linux-
On Saturday, October 22, 2016 12:39:26 PM CEST Chris Blake wrote:
> This patch was provided by Ben at http://lists.infradead.org/pipermail
> /lede-dev/2016-October/003332.html and adds ccm(aes) support to the AES-NI
> acceleration. Currently it is not submitted upstream, but has been confirmed
> wo
* Chris Blake [22.10.2016 20:39]:
> +OVERLAY="$(cat /proc/mounts | grep ' /overlay ' 2>/dev/null)"
fix this line:
http://porkmail.org/era/unix/award.html
bye, bastian
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/ma
On Sun, Oct 16, 2016 at 9:22 AM, Ben Greear wrote:
>
>
> On 10/16/2016 08:30 AM, STR . wrote:
>>>
>>> BQL + fq_codel kills bufferbloat at line rate (10,100,1000mbit) on
>>> ethernet cards. It also works if you have hardware flow control on the the
>>> ethernet.
>>> It can't do anything on download
From: P.Wassi
Set the default value for status-fault LEDs to '0'
Signed-off-by: P.Wassi
---
The kirkwood-dockstar, kirkwood-goflex* and kirkwood-pogoplug devices have
one duo-color status LED (green+orange / health+fault).
For the dockstar and pogoplug the orange fault LED is enabled by default
Only use ASCII characters in README.
Signed-off-by: Heinrich Schuchardt
---
README | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README b/README
index 290dff6..ac34e30 100644
--- a/README
+++ b/README
@@ -5,7 +5,7 @@ It is described in the following paper:
Daniel J. Bern
2016-10-22 21:46 GMT+02:00 :
> From: P.Wassi
>
> Set the default value for status-fault LEDs to '0'
>
> Signed-off-by: P.Wassi
Full name please!
> ---
> The kirkwood-dockstar, kirkwood-goflex* and kirkwood-pogoplug devices have
> one duo-color status LED (green+orange / health+fault).
> For th
Hi,
so I found out bootloop is caused by activation of Qualcomm Atheros
QCA9880 802.11nac (radio1) - 5 GHz wireless.
I tried using QCA988x firmware as well as the CT modifications, but
still it seems that with activation of ac radio, router goes to boot-loop.
CONFIG_PACKAGE_ath10k-firmware-
on 2016-10-19 Charles wrote:
> Questions:
>
> 1. Why does LEDE show four regulatory domain blocks while OpenWrt shows
>only one?
>
> 2. What does the "country US: DFS-FCC" blocks tell me when radio is set
>to an ETSI region country (DE) according to uci?
>
> 3. What does AUTO-BW mean?
24 matches
Mail list logo
