12/11/20 1:05 PM, Andre Heider:
Shut up these warnings:
/usr/include/vdsl/cmv_message_format.h:33:6: warning:
"MEI_SUPPORT_DEBUG_STREAMS" is not defined, evaluates to 0 [-Wundef]
#if (MEI_SUPPORT_DEBUG_STREAMS == 1)
^
/usr/include/vdsl/drv_mei_cpe_interface.h:22
12/11/20 7:44 PM, Andre Heider:
On 11/12/2020 18:59, Mathias Kresin wrote:
12/11/20 1:05 PM, Andre Heider:
Shut up these warnings:
/usr/include/vdsl/cmv_message_format.h:33:6: warning:
"MEI_SUPPORT_DEBUG_STREAMS" is not defined, evaluates to 0 [-Wundef]
#if (MEI_SUPPORT_DEBUG_ST
1/13/21 3:00 PM, Martin Schiller:
On 2021-01-09 09:40, Andre Heider wrote:
Hi,
(cc'ed some recent commiters for lantiq)
On 15/12/2020 10:35, Andre Heider wrote:
v2:
- drop 0002-ltq-vdsl-app-fix-Wundef-warnings.patch
- use "/dev/dsl_cpe_api" without the "0" suffix for the adsl daemon:
packa
These boards have a fixed size kernel partition but do not limit the
kernel size during image building.
Disable image building for both boards as well, since the kernel of the
last release as well as master are to big to fit into the 2 MByte kernel
partition.
Signed-off-by: Mathias Kresin
The QOS feature depends on KPI2UDP which was removed from the tree with
commit a95775e4b2a9 ("drop unmaintained packages") in 2012.
Since QOS was the last user of the KPI, the feature can be disabled by
default.
Signed-off-by: Mathias Kresin
---
package/kernel/lantiq/ltq-tapi/Con
driver as well, to indicate a relation to the
values used for the vdsl app and to be not surprised by a changed
default in case the MEI driver gets updated. Use the current default
values defined in the MEI driver.
Signed-off-by: Mathias Kresin
---
package/kernel/lantiq/ltq-vdsl-mei/Makefile | 1
Assign the usbdev trigger via devicetree and drop the userspace
handling of the usb leds.
Signed-off-by: Mathias Kresin
---
.../files/arch/mips/boot/dts/lantiq/vr9.dtsi | 14 ++
.../mips/boot/dts/lantiq/vr9_lantiq_easy80920.dtsi | 12 +++-
.../mips/boot/dts/lantiq
Assign the usbdev trigger via devicetree and drop the userspace
handling of the usb leds
Add the PCI attached usb controller as trigger sources for the usb led
as well.
Signed-off-by: Mathias Kresin
---
.../arch/mips/boot/dts/lantiq/danube.dtsi | 7 +
.../lantiq
2/16/21 10:51 PM, Adrian Schmutzler:
Hi,
-Original Message-
From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
On Behalf Of Mathias Kresin
Sent: Dienstag, 16. Februar 2021 19:35
To: openwrt-devel@lists.openwrt.org
Subject: [PATCH] lantiq: vr9: set the usb led trigger
Assign the usbdev trigger via devicetree and drop the userspace
handling of the usb leds.
Drop the now unused userspace helper code as well.
Signed-off-by: Mathias Kresin
---
Changes in v2:
- drop the now unused userspace helper code
.../files/arch/mips/boot/dts/lantiq/vr9.dtsi | 14
2/16/21 10:54 PM, Adrian Schmutzler:
Hi,
-Original Message-
From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
On Behalf Of Mathias Kresin
Sent: Dienstag, 16. Februar 2021 19:35
To: openwrt-devel@lists.openwrt.org
Subject: [PATCH] ltq-vdsl-app: fix -Wundef warnings
2/19/21 2:17 PM, Adrian Schmutzler:
-Original Message-
From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
On Behalf Of Mathias Kresin
Sent: Dienstag, 16. Februar 2021 19:35
To: openwrt-devel@lists.openwrt.org
Subject: [PATCH] lantiq: ARV752DPW22: set the usb led trigger
2/25/21 9:18 PM, Jan Hoffmann:
This patch makes use of the Sercomm partition table parser on some
Netgear routers. This applies to the boards CHJ (R6260, R6350, R6850,
WAC124) and BZV (R6800, R6700-v2, R7200, Nighthawk AC2400).
On these models, each device has an individual partition table that
Hey Weijie Gao,
2015-08-05 20:07 GMT+02:00 Weijie Gao :
> This patch adds header version 2 option for mktplinkfw.
As long as we talk about the same, the new header version is v3. The
v2 header is already covered by mktplinkfw2.c.
Currently, I'm working on the same topic. Everything that is know
Am 14.08.2015 um 04:39 schrieb Yousong Zhou:
Never played with tplink's v3 header. But I found on other devices
that the RSA2048-SHA1 implementation there was flawed in that it used
pubkeys from firmwares to verifying signatures. Hmm, is it possible
that this v3 header from tplink also has suc
Am 24.07.2015 um 01:20 schrieb Martin Blumenstingl:
On Fri, Jul 24, 2015 at 1:00 AM, Aleksander Wałęski wrote:
Actually, it just dawned on me that they can be doing just that. In
the bootloader. This is the only part of firmware we are not changing.
If PCBs turn out to be identical we might wan
Signed-off-by: Mathias Kresin
---
.../linux/lantiq/patches-4.4/0018-MTD-nand-lots-of-xrx200-fixes.patch | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/target/linux/lantiq/patches-4.4/0018-MTD-nand-lots-of-xrx200-fixes.patch
b/target/linux/lantiq/patches-4.4/0018-MTD-nand
The stock u-boot doesn't disable unused flash banks. Therefore, the nand
driver tries to initialize a not connected NOR flash and the device
hangs on boot.
Workaround the issue by selecting the second flash bank (NAND).
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/dts/BTHOMEHUBV5
.
This fixes the detection of the wireless chipset of the VGV7510KW22.
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/dts/VGV7510KW22.dtsi | 2 +-
target/linux/lantiq/dts/VGV7519.dtsi | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/target/linux/lantiq/dts/VGV7510K
Am 21.04.2016 um 23:43 schrieb Vittorio Gambaletta (VittGam):
After recent patches, the status LED on this router would stay
switched off after boot is completed. A switched off status LED
often indicates a boot failure (eg. kernel panic), so fix this and
get back to the previous behaviour.
NAK
Am 21.04.2016 um 23:43 schrieb Vittorio Gambaletta (VittGam):
Signed-off-by: Vittorio Gambaletta
Acked-by: Mathias Kresin
---
--- a/target/linux/lantiq/base-files/etc/diag.sh
+++ b/target/linux/lantiq/base-files/etc/diag.sh
@@ -25,7 +25,7 @@
;;
done
Use the kernel with the appended dtb as base, otherwise the kernel will
panic with "no dtb found".
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/image/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/lantiq/image/Makefile
b/target/li
Set the kernel entry address to the same value as it is used for the old
image build build process.
Fixes boot of uImages on VGV7510KW22NOR and others.
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/image/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/image/Makefile | 22 --
1 file changed, 22 deletions(-)
diff --git a/target/linux/lantiq/image/Makefile
b/target/linux/lantiq/image/Makefile
index d78c035..6bad91b 100644
--- a/target/linux/lantiq/image/Makefile
+++ b
Tested with VGV7510KW22NOR.
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/image/Makefile | 2 ++
1 file changed, 2 insertions(+)
diff --git a/target/linux/lantiq/image/Makefile
b/target/linux/lantiq/image/Makefile
index 4a358b5..d78c035 100644
--- a/target/linux/lantiq/image/Makefile
Required to compress kernels in a brnboot compatible way.
Signed-off-by: Mathias Kresin
---
include/image.mk | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/include/image.mk b/include/image.mk
index 7c11aa1..bc383e6 100644
--- a/include/image.mk
+++ b/include/image.mk
meter is
required for some reason, the static keyword "squashfs" can be used.
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/image/Makefile | 42 +-
1 file changed, 28 insertions(+), 14 deletions(-)
diff --git a/target/linux/lantiq/image/Mak
only the VG3503J
has more than one led connected per phy. Using the phy led device tree
bindings to assign the functionality to the "additional" leds, the
VG3503J phy leds should behave as before.
Signed-off-by: Mathias Kresin
[1] https://forum.openwrt.org/viewtopic.php?pid=321523
---
Signed-off-by: Mathias Kresin
---
.../patches-4.4/0023-NET-PHY-adds-driver-for-lantiq-PHY11G.patch | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
a/target/linux/lantiq/patches-4.4/0023-NET-PHY-adds-driver-for-lantiq-PHY11G.patch
b/target/linux/lantiq/patches-4.4
only the VG3503J
has more than one led connected per phy. Using the phy led device tree
bindings to assign the functionality to the "additional" leds, the
VG3503J phy leds should behave as before.
Signed-off-by: Mathias Kresin
[1] https://forum.openwrt.org/viewtopic.php?pid=321523
---
Signed-off-by: Mathias Kresin
---
.../patches-4.4/0023-NET-PHY-adds-driver-for-lantiq-PHY11G.patch | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
a/target/linux/lantiq/patches-4.4/0023-NET-PHY-adds-driver-for-lantiq-PHY11G.patch
b/target/linux/lantiq/patches-4.4
Based on the vg3503j_gphy_led.sh script published in the VG3503J wiki
article, the OEM Firmware uses the following PHY led functionality:
gphy led 0: LINK/ACTIVITY
gphy led 1: LINK
gphy led 2: ACTIVITY
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/dts/VG3503J.dtsi | 16
source.
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/dts/VGV7510KW22BRN.dts | 6 ++
1 file changed, 6 insertions(+)
diff --git a/target/linux/lantiq/dts/VGV7510KW22BRN.dts
b/target/linux/lantiq/dts/VGV7510KW22BRN.dts
index 1880c8c..d7c6b51 100644
--- a/target/linux/lantiq/dts/VGV
Signed-off-by: Mathias Kresin
---
...x200-add-gphy-clk-src-device-tree-binding.patch | 26 ++
1 file changed, 26 insertions(+)
create mode 100644
target/linux/lantiq/patches-4.4/0301-xrx200-add-gphy-clk-src-device-tree-binding.patch
diff --git
a/target/linux/lantiq
Use the same name for TP-Link images as it was with the old image build
code.
Move the BOARD_ID export to the TP-Link image build recipe, to indicate
that the variable is only related in this context.
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/image/Makefile | 7 ---
1 file
Starting with kernel 4.4, the use of partitions as direct subnodes of the
mtd device is discouraged and only supported for backward compatiblity
reasons.
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/dts/ACMP252.dts| 67 +++---
target/linux/lantiq/dts/ARV4510PW.dts | 36
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/dts/VGV7510KW22BRN.dts | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/target/linux/lantiq/dts/VGV7510KW22BRN.dts
b/target/linux/lantiq/dts/VGV7510KW22BRN.dts
index 5f48323..f93249b 100644
--- a/target/linux/lantiq
for
Code_Image_1.
By using the information about the active "Code Image", it is possible
to ensure that the rootfs belongs to the current booted Image/Kernel.
Signed-off-by: Mathias Kresin
---
.../lantiq/patches-4.4/0101-find_active_root.patch | 93 ++
1 file c
Signed-off-by: Mathias Kresin
---
Changes in v2:
- moved logic into its own function (no functional change)
...x200-add-gphy-clk-src-device-tree-binding.patch | 30 ++
1 file changed, 30 insertions(+)
create mode 100644
target/linux/lantiq/patches-4.4/0301-xrx200
source.
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/dts/VGV7510KW22BRN.dts | 6 ++
1 file changed, 6 insertions(+)
diff --git a/target/linux/lantiq/dts/VGV7510KW22BRN.dts
b/target/linux/lantiq/dts/VGV7510KW22BRN.dts
index 1880c8c..d7c6b51 100644
--- a/target/linux/lantiq/dts/VGV
I got the same device last Weekend and planned to add support for this
device during the next days. Glad to see that most of the work is
already done.
Find my remarks in-line.
2016-05-18 9:37 GMT+02:00 Oswald Buddenhagen :
> Ethernet, WiFi, ADSL2+, and LEDS are fully functional.
>
> The RFkill sw
2016-05-18 23:00 GMT+02:00 Oswald Buddenhagen :
> On Wed, May 18, 2016 at 01:19:59PM +0200, Mathias Kresin wrote:
>> But I need to identify the boot_sel pins first. I have looked at it
>> only briefly and was only able to identify one of the boot_sel pins:
>> R77. Unfortu
Hi Oliver,
2016-06-10 11:37 GMT+02:00 :
> Signed-off-by: Olivier Hardouin
> ---
Your patch doesn't have a commit message, which explains why these
options are required by default.
I've used mountd recently with ext4 and was able to read/write the
mounted filesystem out of the box.
Mathias
>
Hi Zoltan,
I've noticed that you have imported a lot of patches from the LEDE repo
into the OpenWrt github repo.
I'm concerted about the fact that you have omitted at least a few of my
Signed-off-bys[1][2], so that it isn't any longer noticeable that the
changes are my work. Even though it m
Am 10.08.2016 um 22:41 schrieb Daniel Niasoff:
Hi Mathias,
ADSL works fine on chaos calmer and I cannot reproduce the issue, so it looks
like it's a recently introduced issue.
Thanks for the idea, it should make it easier to pinpoint
Any idea's where the issue might be?
Nope, no idea yet.
Am 11.08.2016 um 00:15 schrieb John Crispin:
try reverting 8333a6d0bab913285770449f5100597b691b544f aswell please
Had this commit in mind as well. According to Daniels initial mail to
openwrt-devel, he is using a TP-LINK TD-W8980 (xrx200) and the
kmod-ltq-adsl isn't build for xrx200.
I supp
2016-08-11 13:38 GMT+02:00 joerg jungermann :
> Hi,
>
> I have an instance on a W8970/ADSL/Annex B running from build around th
> 24th of March.
> That time I build from GIT. I cannot name the git hash but
>
> # cat /etc/openwrt_version
> r49081
>
> I tested remotely that it suffers from the same r
The device is similar to the TD-W8970, beside a different Atheros 2.4 GHz
wireless chip and the additional, PCI connected, WAVE300 5 GHz wireless.
Signed-off-by: Mathias Kresin
---
The DTS should work for a TD-W9980 as well. But due to lack of the
appropriate hardware, it has not been tested
Port of r41856.
In contrast to the brcm63xx target, it isn't sufficient to enable/disable
the bridge. The device needs to be enabled/disabled to fix the hang. The
bridge will be automatically enabled by the time the connected device is
enabled.
Fixes boot on TD-W8980.
Signed-off-by: Ma
-continuation-handling-in-proc-net.patch was applied
upstream and dropped.
Signed-off-by: Mathias Kresin
---
Runtime tested on lantiq.
Compile tested on ar7, ar71xx, arm64, bcm53xx, brcm47xx, brcm63xx,
brcm2708 (brcm2708 & brcm2709), gemini (raidsonic & wiligear), ipq806x,
ixp4xx, m
linux.git/commit/?id=d8bf368d0631d4bc2612d8bf2e4e8e74e620d0cc
Signed-off-by: Mathias Kresin
---
The issue was reported in https://dev.openwrt.org/ticket/20679 and the
patch was successfully test by an affected user.
package/kernel/lantiq/ltq-hcd/src/ifxhcd.c | 2 +
package/kernel/lantiq/ltq-hc
Am 11.10.2015 um 10:50 schrieb Arjen de Korte:
Citeren Mathias Kresin :
diff --git a/package/kernel/lantiq/ltq-hcd/src/ifxhcd.c
b/package/kernel/lantiq/ltq-hcd/src/ifxhcd.c
index be0a91d..14dc7a1 100644
--- a/package/kernel/lantiq/ltq-hcd/src/ifxhcd.c
+++ b/package/kernel/lantiq/ltq-hcd/src
linux.git/commit/?id=d8bf368d0631d4bc2612d8bf2e4e8e74e620d0cc
Signed-off-by: Mathias Kresin
---
The issue was reported in https://dev.openwrt.org/ticket/20679 and the
v1 patch was successfully test by an affected user.
v2:
Remove IRQF_DISABLED flags or replace them with 0x0 instead of using
conditiona
Dynamic Spectrum Management is a precondition for G.993.5 (VDSL2 vectoring).
Signed-off-by: Mathias Kresin
---
It has been sucessfully tested by a user with a german 1&1 VDSL2 vectoring line,
who could only get the ADSL2+ fallback speed[1] without this patch (regardless
of vectoring suppor
Signed-off-by: Mathias Kresin
---
Tested by my self with a "normal" VDSL2 line and by a user with a german 1&1
VDSL2 vectoring line:
/etc/init.d/dsl_control status
ATU-C Vendor ID: B5,00,42,44,43,4D,A4,61
ATU-C System Vendor ID: B5,00,42,
Starting with r47755 the pppoe wan interface section isn't any longer added to
the network config on firstboot, using the default configuration. Since the
commit message does not mention such a change, I assume that this wasn't
intentionally.
Signed-off-by: Mathias Kresin
---
ta
Signed-off-by: Mathias Kresin
---
.../patches/0045-no_extern_inline.patch| 101 +
.../uboot-lantiq/patches/0046-no_weak_alias.patch | 28 ++
.../patches/0047-add-gcc5-support.patch| 93 +++
3 files changed, 222 insertions
ith the initial state
"switched off"
With the final result of a switched off power led after boot.
The only led that needs to be added is the BTHOMEHUBV5A specific dimmed led.
Signed-off-by: Mathias Kresin
---
The loop was introduced with r34698 to compact the leds file. The mentioned b
ncreases to 103912 byte (+4256 byte) uncompressed.
Signed-off-by: Mathias Kresin
---
package/network/config/ltq-vdsl-app/Makefile | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/package/network/config/ltq-vdsl-app/Makefile
b/package/network/config/ltq-vdsl-app/Makefile
index da
le or disable features that
are covered by the feature set
The config.log contains the same values as before. The vdsl_cpe_control binary
has the same checksum as before.
Signed-off-by: Mathias Kresin
---
package/network/config/ltq-vdsl-app/Makefile | 22 --
1 file chang
adsl as well as vdsl
over ptm.
It's pppd which sends packages over the ptm device before in showtime.
As far as I can see, pppd is started unconditionally since netif can
not gather the link status of the ptm network interface.
Signed-off-by: Mathias Kresin
---
Test with a VDSL line. It ha
debug loglevel.
But it reduces the amount of ppp related messages significant.
Signed-off-by: Mathias Kresin
---
Tested with an ADSL line.
package/kernel/lantiq/ltq-atm/src/ltq_atm.c | 15 ++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/package/kernel/lantiq/ltq-at
Am 16.12.2015 um 05:42 schrieb Vittorio G (VittGam):
This patch configures the correct ath9k WLAN LED polarity for the TDW8970.
Signed-off-by: Vittorio Gambaletta
---
The TDW8970 LED is active high, but I'm not sure about the TDW8980 as
I don't have one. If the TDW8980 LED is active high as w
Am 16.12.2015 um 05:42 schrieb Vittorio G (VittGam):
Signed-off-by: Vittorio Gambaletta
---
--- a/target/linux/lantiq/base-files/etc/board.d/01_leds
+++ b/target/linux/lantiq/base-files/etc/board.d/01_leds
@@ -38,6 +38,10 @@ BTHOMEHUBV5A)
ucidef_set_led_netdev "internet" "internet" "so
Still unused, but u-boot doesn't take care of the led, which results in a
permanent switched on 5GHz LED.
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/dts/TDW8980.dts | 7 +++
1 file changed, 7 insertions(+)
diff --git a/target/linux/lantiq/dts/TDW8980.dts
b/target/linux/l
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/base-files/etc/board.d/01_leds | 1 +
target/linux/lantiq/base-files/sbin/dsl_notify.sh | 14 +++---
2 files changed, 8 insertions(+), 7 deletions(-)
diff --git a/target/linux/lantiq/base-files/etc/board.d/01_leds
b/target/linux
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/dts/ARV4510PW.dts | 2 +-
target/linux/lantiq/dts/ARV4520PW.dts | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/target/linux/lantiq/dts/ARV4510PW.dts
b/target/linux/lantiq/dts/ARV4510PW.dts
index 4772495..67c
to the ptm/atm
device.
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/base-files/etc/board.d/01_leds | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/target/linux/lantiq/base-files/etc/board.d/01_leds
b/target/linux/lantiq/base-files/etc/board.d/01_leds
index 8422ec0
2015-12-17 7:52 GMT+01:00 John Crispin :
> Hi,
>
> we had a discussion yesterday with a few people and agreed to cleanup
> the led names on for the lantiq target to match the format expected by
> the kernel. i like this patch however we need to do the led renaming
> first i guess.
>From my point o
- GIGASX76X: doesn't have leds defined, where the old mach file had
This series has been runtime tested on BTHOMEHUBV5A, TDW8980,
VGV7510KW22 and ARV752DPW22.
All other boards are compile tested.
Mathias Kresin (12):
lantiq: P2812HNUFX - move leds to dtsi
lantiq: BTHOMEHUBV2B - remove mis
Beside the used labels, they are the same on both boards.
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/dts/P2812HNUF1.dts | 61 -
target/linux/lantiq/dts/P2812HNUF3.dts | 53
target/linux/lantiq/dts/P2812HNUFX.dtsi | 61
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/dts/ARV4518PWR01.dts | 179 +
target/linux/lantiq/dts/ARV4518PWR01.dtsi | 184 ++
target/linux/lantiq/dts/ARV4518PWR01A.dts | 179 +
3 files changed, 186
The workaround shouldn't be in the default configuration.
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/base-files/etc/board.d/01_leds | 1 -
1 file changed, 1 deletion(-)
diff --git a/target/linux/lantiq/base-files/etc/board.d/01_leds
b/target/linux/lantiq/base-files/etc/bo
No need to switch (and keep) on all leds at boot. Use the same led
logic and labels as the OEM firmware (red = okay, blue = failure).
Add the red internet led.
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/dts/ARV752DPW22.dts | 34 -
1 file changed, 12
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/dts/DGN1000B.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/lantiq/dts/DGN1000B.dts
b/target/linux/lantiq/dts/DGN1000B.dts
index 4ccab93..199d3a9 100644
--- a/target/linux/lantiq/dts/DGN1000B.dts
+++ b
Remove all now double defined leds from the led board file. Use pppoe
as default for all broadband connections, since it's the default in
OpenWrt now.
Rename the the wifi leds to make sure, the not applicable default
values get overwritten.
Signed-off-by: Mathias Kresin
---
target/linux/l
- ARV7525PW: use the power led as dsl led as done by the stock firmware
- FRITZ3370: use the info led as internet led
- FRITZ7320: use the power led as dsl led as done by the stock firmware
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/dts/ARV4510PW.dts | 24
g the shared led according to the status of the ppp interface
isn't suitable, since the led would be switched of if the ppp
connection goes down, but the line is still in sync.
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/base-files/etc/board.d/01_leds | 19 +++
ta
Use the same led logic and labels as the OEM firmware (red = okay,
blue = failure).
Add the red internet led.
Remove missing usb led workaround. The workaround shouldn't be in the
default configuration.
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/dts/ARV752DPW.dts
Use the power leds defined in the dts file instead of hardcoded led names.
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/base-files/etc/diag.sh | 34 +-
1 file changed, 19 insertions(+), 15 deletions(-)
diff --git a/target/linux/lantiq/base-files/etc/diag.sh
ned-off-by: Mathias Kresin
---
target/linux/lantiq/base-files/etc/board.d/01_leds | 6 +-
target/linux/lantiq/dts/ARV4519PW.dts | 50
target/linux/lantiq/dts/ARV4520PW.dts | 40 +++--
target/linux/lantiq/dts/ARV4525PW.dts | 10 ++--
ta
led after boot
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/base-files/etc/board.d/01_leds | 18
target/linux/lantiq/base-files/etc/diag.sh | 52 +++---
target/linux/lantiq/dts/ARV4510PW.dts | 7 ++-
target/linux/lantiq/dts/ARV4518PWR01.dtsi
read as well.
While touching the dts file, I fixed the dtc compiler warnings.
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/dts/TDW89X0.dtsi | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/target/linux/lantiq/dts/TDW89X0.dtsi
b/target/linux/lantiq/dts/TDW8
Signed-off-by: Mathias Kresin
---
package/kernel/lantiq/ltq-adsl-mei/patches/100_no-date-time.patch | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/kernel/lantiq/ltq-adsl-mei/patches/100_no-date-time.patch
b/package/kernel/lantiq/ltq-adsl-mei/patches/100_no-date
d
were not present in the 3.18 patches.
Signed-off-by: Mathias Kresin
---
.../patches-4.1/0001-MIPS-lantiq-add-pcie-driver.patch | 12 ++--
1 file changed, 2 insertions(+), 10 deletions(-)
diff --git
a/target/linux/lantiq/patches-4.1/0001-MIPS-lantiq-add-pcie-driver.patch
b/target/li
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/image/Makefile | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/target/linux/lantiq/image/Makefile
b/target/linux/lantiq/image/Makefile
index 686cb6d..553bdc1 100644
--- a/target/linux/lantiq/image/Makefile
+++ b/target
Beside the used labels, they are the same on both boards.
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/dts/P2812HNUF1.dts | 61 -
target/linux/lantiq/dts/P2812HNUF3.dts | 53
target/linux/lantiq/dts/P2812HNUFX.dtsi | 61
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/dts/ARV4518PWR01.dts | 179 +
target/linux/lantiq/dts/ARV4518PWR01.dtsi | 184 ++
target/linux/lantiq/dts/ARV4518PWR01A.dts | 179 +
3 files changed, 186
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/dts/DGN1000B.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/lantiq/dts/DGN1000B.dts
b/target/linux/lantiq/dts/DGN1000B.dts
index 4ccab93..199d3a9 100644
--- a/target/linux/lantiq/dts/DGN1000B.dts
+++ b
The workaround shouldn't be in the default configuration.
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/base-files/etc/board.d/01_leds | 1 -
1 file changed, 1 deletion(-)
diff --git a/target/linux/lantiq/base-files/etc/board.d/01_leds
b/target/linux/lantiq/base-files/etc/bo
are compile tested.
V2:
- fix not updated lan led name in the leds file (ARV7519RW22)
- fix not renamed ISDN led (ARV4520PW)
- fix spaces vs. tabs issue in diag.sh
- use boardname instead of the generic soc
Mathias Kresin (12):
lantiq: P2812HNUFX - move leds to dtsi
lantiq
No need to switch (and keep) on all leds at boot. Use the same led
logic and labels as the OEM firmware (red = okay, blue = failure).
Add the red internet led.
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/dts/ARV752DPW22.dts | 34 -
1 file changed, 12
Use the power leds defined in the dts file instead of hardcoded led names.
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/base-files/etc/diag.sh | 34 +-
1 file changed, 19 insertions(+), 15 deletions(-)
diff --git a/target/linux/lantiq/base-files/etc/diag.sh
Remove all now double defined leds from the led board file. Use pppoe
as default for all broadband connections, since it's the default in
OpenWrt now.
Rename the the wifi leds to make sure, the not applicable default
values get overwritten.
Signed-off-by: Mathias Kresin
---
target/linux/l
g the shared led according to the status of the ppp interface
isn't suitable, since the led would be switched of if the ppp
connection goes down, but the line is still in sync.
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/base-files/etc/board.d/01_leds | 19 +++
ta
- ARV7525PW: use the power led as dsl led as done by the stock firmware
- FRITZ3370: use the info led as internet led
- FRITZ7320: use the power led as dsl led as done by the stock firmware
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/dts/ARV4510PW.dts | 24
Use the same led logic and labels as the OEM firmware (red = okay,
blue = failure).
Add the red internet led.
Remove missing usb led workaround. The workaround shouldn't be in the
default configuration.
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/dts/ARV752DPW.dts
led after boot
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/base-files/etc/board.d/01_leds | 18
target/linux/lantiq/base-files/etc/diag.sh | 52 +++---
target/linux/lantiq/dts/ARV4510PW.dts | 7 ++-
target/linux/lantiq/dts/ARV4518PWR01.dtsi
ned-off-by: Mathias Kresin
---
target/linux/lantiq/base-files/etc/board.d/01_leds | 8 +--
target/linux/lantiq/dts/ARV4519PW.dts | 50
target/linux/lantiq/dts/ARV4520PW.dts | 42 +++--
target/linux/lantiq/dts/ARV4525PW.dts | 10 ++--
ta
The ppp0 interface is renamed after the connection is established. Due
to a missing NETDEV_REGISTER event, the ledtrig-netdev isn't aware of
the renamed interface and literally ignores the device
(no tx/rx indication, led isn't switched off with 'ifdown wan').
Signed-of
1 - 100 of 266 matches
Mail list logo
