Re: [LEDE-DEV] [PATCH] kirkwood: disable fault LEDs by default

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

[LEDE-DEV] [PATCH 1/1] usign: README: replace unicode character

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

[LEDE-DEV] [PATCH] kirkwood: disable fault LEDs by default

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

Re: [LEDE-DEV] [RFC 0/1] x86: Add support for the PC Engines APU2 Board

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

Re: [LEDE-DEV] [RFC 4/6 v2] Generic: Crypto - aesni - add ccm(aes) algorithm implementation

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 >

[LEDE-DEV] linux-x86_generic/linux-4.4.26 compile errors

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

Re: [LEDE-DEV] [RFC 0/6 v2] Add the PC Engines APU2 to LEDE

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

Re: [LEDE-DEV] [RFC 0/6 v2] Add the PC Engines APU2 to LEDE

> 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

[LEDE-DEV] [RFC 6/6 v2] x86: Add a Profile for the PC Engines APU2 board

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

[LEDE-DEV] [RFC 0/6 v2] Add the PC Engines APU2 to LEDE

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

[LEDE-DEV] [RFC 1/6 v2] Generic: Backport sp5100_tco patches for AMD platforms

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

[LEDE-DEV] [RFC 3/6 v2] x86: Add sp5100_tco as a kernel module

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

[LEDE-DEV] [RFC 5/6 v2] x86: Update the x86_64 kernel config

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

Re: [LEDE-DEV] [PATCH] apm821xx: fix USB LED trigger for WNDR4700

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

Re: [LEDE-DEV] [PATCH] base-files: ensure reset only works if an overlay exists

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

Re: [LEDE-DEV] bcm63xx and fxs is possible...

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

[LEDE-DEV] [PATCH] apm821xx: fix USB LED trigger for WNDR4700

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 ---