Hi Johannes,
I'm re-sending this because I accidentally replied only to you in the
first email.
>> There's at least one firmware file that should do vectoring that you
>> haven't covered, in more recent tarballs for the Speedport W921V (you
>> have V_5.3.4.A.1.6-5.3.6.4.1.2 from an older one)
>
>
Hi Johannes,
> You said you also don't actually have the current one working though,
> which was working well for me (on both Annex A and Annex B with VDSL
> fallback).
Like I previously said: there's probably something wrong at my end.
I have the Annex A version of the TD-W8970 and I am trying to
> I've never seen that, but which firmware are you using?
>
> I'd been using the speedport 1.21
> (e1ef690e8dc0075468d4b6ba7bcdd0fc710bc671) one IIRC.
I am running Chaos Calmer (but I've also tried Barrier Breaker) and that
is exactly the firmware I am using.
> Are you on VDSL Annex B, where you'd
The PCIe bus seems to require a hack/workaround when PCI is enabled as
well. Unfortunately this is guarded by an CONFIG_IFX_PCI ifdef, which is
only defined in lantiq's BSP code. The config symbol for the upstream
lantiq PCI driver is CONFIG_PCI_LANTIQ.
Signed-off-by: Martin Blumens
There are already ifx_pcie_bios_{map_irq,plat_dev_init} hooks defined in
ifxmips_pcie.c. Instead of defining a new hook we simply re-use the
existing ones (this is basically what the lantiq BSP code does).
Signed-off-by: Martin Blumenstingl
---
.../0001-MIPS-lantiq-add-pcie-driver.patch
This patch plus my previous one (see [0]) make PCIe and PCI work
at the same time (at least on the device I'm testing with).
Unfortunately I have no other lantiq device with PCIe - so it would be
nice if someone else could test that this doesn't break any existing
devices.
Regards,
Martin
[0] ht
> Also, using binwalk, I was able to extract dsl firmware from latest
> W9980 firmware update (TD-W9980_V1_150507).
>
> filename: xcpe_574306_571801.bin
> version: 5.7.4.3.0.6-5.7.1.8.0.1
> sha1sum: f8a13f16f5ead64bb0d2d551fbef8f1a838322f7
Thanks a lot - added that one as well.
___
> Was quite obvious but I've missed it, default debug level have been changed
Excellent catch, I should have noticed it when I removed "-DDSL_DEBUG_DISABLE"
> Newest trunk with patches from xdarklight, packages from DrayTek.
What do you mean exactly with "packages from DrayTek"?
> Full log: http:
> Waiting impatiently for this new patch. For now I can say that I have
> problems with old driver combined with newest TP-LINK dsl firmware on
> VDSL line. Once I establish known working configuration I'll build fw
> with latest driver and test again.
New patch is ready: [0]
Let me know if VDSL w
This patch is taken from the gentoo guys who extracted this from a large
upstream commit (with many unrelated changes).
Signed-off-by: Martin Blumenstingl
---
package/libs/ncurses/Makefile | 2 +-
.../ncurses/patches/102-ncurses-5.9-gcc-5.patch| 46
z
[4] http://filebin.ca/22vnWceEtRCR/dsl_cpe_control_vrx-4.15.2.tar.gz
[5] http://filebin.ca/22w5lADvJHn0/drv_dsl_cpe_api_ugw511_vrx-4.15.2.tar.gz
[6] http://filebin.ca/22w5junG6FCc/dsl_cpe_control_ugw511_vrx-4.15.2.tar.gz
On Sun, May 24, 2015 at 6:04 PM, Martin Blumenstingl
wrote:
>> Wai
On Mon, May 25, 2015 at 3:05 PM, Dirk Neukirchen wrote:
> What about switching to the invisible islands version ?
That is probably a question for the OpenWrt maintainers, not me :)
However, the first RC of Chaos Calmer has already been released. So
maybe an update to the "invisible islands" versi
Hi Arnold,
On Fri, May 29, 2015 at 5:50 PM, Arnold Schulz wrote:
> My current questions center on the .dts settings:
> 1. How to access WLAN hardware
Do you know if wifi is connected via PCI or PCIe?
You then need to configure the corresponding pins in the pinmux section.
Of course you also need
On Sat, May 30, 2015 at 1:58 AM, Arnold Schulz wrote:
> I don't know. According to console output PCI seems to be recognized, for
> PCIe there are error messages ("pcie_rc_initialize link up failed!").
> The lspci command shows nothing.
Can you see the physical wifi chip on your board? If you
Hi,
On Sat, May 30, 2015 at 3:00 PM, Maciej Soltysiak wrote:
> I'd like to see if I can fix the bug, but I don't know where is the official
> repo for uhttp. Does anyone know?
The official uhttpd2 repo is hosted by nbd: [0]
Regards,
Martin
[0] http://nbd.name/gitweb.cgi?p=uhttpd2.git;a=summar
CC'ing you.
On Mon, May 25, 2015 at 4:29 PM, Martin Blumenstingl
wrote:
> That is probably a question for the OpenWrt maintainers, not me :)
> However, the first RC of Chaos Calmer has already been released. So
> maybe an update to the "invisible islands" version should be
new code but passing the old CRC32
poly value. Both resulted in a brnboot image with the same sha1sum.
Signed-off-by: Martin Blumenstingl
---
tools/firmware-utils/src/mkbrnimg.c | 20 +---
1 file changed, 13 insertions(+), 7 deletions(-)
diff --git a/tools/firmware-utils/src
This also adds the old hardcoded value to the VGV7519BRN profile to make
sure that images are still generated correctly.
Signed-off-by: Martin Blumenstingl
---
target/linux/lantiq/image/Makefile | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/target/linux/lantiq
Hi Aleksander,
On Wed, May 27, 2015 at 9:20 PM, Aleksander Wałęski wrote:
> add --enable-debug-prints=err to ltq-vdsl-app and change
> enable-debug-prints to err in ltq-vdsl-vr9.
> ...
> Additionally, I added --disable-dsl-ceoc to ltq-vdsl-app since CEOC is
> disabled in API by default anyway.
Th
e $(obj).depend
++
++#
+--- /dev/null
b/board/arcadyan/vgv7510kw22/vgv7510kw22.c
+@@ -0,0 +1,133 @@
++/*
++ * Copyright (C) 2015 Martin Blumenstingl
++ *
++ * SPDX-License-Identifier: GPL-2.0+
++ */
++
++#include
++#include
++#include
++#include
++#include
++#include
++#include
++
++#if defined(C
08b085a07efe12568d86dff064e6f089e2971744 Mon Sep 17 00:00:00 2001
+From: Martin Blumenstingl
+Date: Mon, 25 May 2015 22:39:50 +0200
+Subject: gpio-stp-xway: Fix enabling the highest bit of the PHY LEDs
+
+0x3 only masks two bits, but three bits have to be allowed. This fixes
+GPHY0 LED2 (which is the highest bit of
---
.../etc/hotplug.d/firmware/10-rt2x00-eeprom| 11 +
.../lantiq/base-files/etc/uci-defaults/01_leds | 7 +
.../lantiq/base-files/etc/uci-defaults/02_network | 8 +
target/linux/lantiq/dts/VGV7510KW22.dtsi | 256 +
target/linux/lantiq/dts/VGV7510KW2
any market" in
> vdsl.scr). I guess ADSL over ISDN is not very popular elsewhere.
Yes, Germany is a bit special regarding this...
> On Mon, Jun 1, 2015 at 11:32 PM, Martin Blumenstingl
> wrote:
>> I can test it this weekend on an Annex B ADSL connectio
On Fri, Jun 5, 2015 at 4:56 AM, Aleksander Wałęski wrote:
> Try playing with /etc/init.d/dsl_control when you'll have a moment to
> spare to see if all parameters it passes to control application are
> necessary. Selecting between ADSL and VDSL may be necessary but
> firmware for ADSL seems to be
On Fri, Jun 5, 2015 at 4:56 AM, Aleksander Wałęski wrote:
> Try playing with /etc/init.d/dsl_control when you'll have a moment to
> spare to see if all parameters it passes to control application are
> necessary.
It seems that the lowlevel configuration is indeed not required
anymore.
Removing the
Hi Flo,
On Thu, Jun 18, 2015 at 10:59 AM, Florian Eckert
wrote:
> I have the new source packages for lantiq dsl stuffs. This are the new
> packages rom UGW-6.1.
As far as I know these are the *latest* driver versions.
Do you have a link to those packages (or a link to some GPL source
which includ
Hi Imre,
> On the dgl5500 the mac in the eeprom is the same on all devices (and iirc
> it's the default mac the firmware also uses). Patching it to the right one
> in the firmware file is what happens in 82_patch_ath10k.
I am not very familiar with ath10k, but why are you not patching the
calibrat
an be found here: https://paste.kde.org/pffvzpzdv
Martin Blumenstingl (3):
Add support for linux 4.1
lantiq: Make ltq-ifxos compile with kernel 4.1
lantiq: Make ATM and PTM drivers compatible with kernel 4.1
package/kernel/lantiq/ltq-atm/src/ltq_atm.c|4 +
.../lantiq/ltq-ifxos/pa
Signed-off-by: Martin Blumenstingl
---
.../lantiq/ltq-ifxos/patches/100-compat.patch | 119 +
1 file changed, 97 insertions(+), 22 deletions(-)
diff --git a/package/kernel/lantiq/ltq-ifxos/patches/100-compat.patch
b/package/kernel/lantiq/ltq-ifxos/patches/100
Signed-off-by: Martin Blumenstingl
---
package/kernel/lantiq/ltq-atm/src/ltq_atm.c | 4
package/kernel/lantiq/ltq-ptm/src/ifxmips_ptm_adsl.c | 4
package/kernel/lantiq/ltq-ptm/src/ifxmips_ptm_vdsl.c | 4
3 files changed, 12 insertions(+)
diff --git a/package/kernel
Make it consistent with the net_device struct and the xrx200 driver
Signed-off-by: Martin Blumenstingl
---
.../lantiq/patches-3.18/0028-NET-lantiq-various-etop-fixes.patch | 2 +-
.../0035-owrt-lantiq-wifi-and-ethernet-eeprom-handling.patch | 9 -
2 files changed, 1 insertion(+), 10
This is useful if the device also has an ethernet WAN interface with a
separate mac address (that is derived from the LAN mac address).
Signed-off-by: Martin Blumenstingl
---
.../patches-3.18/681-NET-add-of_get_mac_address_mtd.patch| 12
.../patches-4.0/681-NET-add
i.openwrt.org/toh/bt/homehub_v5a
Signed-off-by: Martin Blumenstingl
---
.../etc/hotplug.d/firmware/11-ath10k-caldata | 51
.../lantiq/base-files/etc/uci-defaults/01_leds | 2 +-
.../lantiq/base-files/etc/uci-defaults/02_network | 8 +
.../lantiq/base-files/lib/upgrade/pl
Newer DSL driver versions depend on the address information.
Signed-off-by: Martin Blumenstingl
---
target/linux/lantiq/dts/vr9.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/target/linux/lantiq/dts/vr9.dtsi b/target/linux/lantiq/dts/vr9.dtsi
index bdb1270..136483a 100644
--- a/target
On Sat, Jun 6, 2015 at 3:23 PM, Sylwester Petela wrote:
> After 9 days and bit of performance drop I reverted back to stripped out
> init script and also lowered debug level to default so I can track what is
> causing these issues.
If it is a driver issue then you can test the new version (more in
Basically the only error I am seeing is "Correctable Error". Also newer
lantiq PCIe drivers have this message wrapped in a "if debug enabled"
block. So it should be safe to disable this warning.
Signed-off-by: Martin Blumenstingl
---
target/linux/lantiq/patches-3.18/0001-
i.openwrt.org/toh/bt/homehub_v5a
V2: Use the correct PCI interrupt (fixes 2.4GHz wifi)
Signed-off-by: Martin Blumenstingl
---
.../etc/hotplug.d/firmware/11-ath10k-caldata | 51
.../lantiq/base-files/etc/uci-defaults/01_leds | 2 +-
.../lantiq/base-files/etc/uci-defaults/02_network
Hi Felix,
On Mon, Jul 6, 2015 at 12:26 PM, Felix Fietkau wrote:
> Instead of adding more options that most people don't know what to do
> with, please test the current v5 firmware in trunk and provide details
> about any issues that you find.
I am not sure which issue Günther is trying to solve,
On Mon, Jul 6, 2015 at 12:39 PM, Felix Fietkau wrote:
> What's the newest firmware that still works on your card?
> Also, please report these issues to the ath10k firmware maintainer.
I think the latest working version was the newest -2 (10.1 branch). I
can look it up when I have access to the dev
Hi,
On Sat, Jul 11, 2015 at 9:39 AM, Sylwester Petela wrote:
> Where did You get/find v4.16.2.4 packages ?
Someone with access to lantiq's "UGW" replied last month on the
mailing list and sent me the updated package versions.
Since my latest patches were merged into the OpenWrt repository the
pa
On Mon, Jul 13, 2015 at 6:04 PM, Jonathan Bennett wrote:
> So, the real problem is that for some reason, my system is ignoring the make
> error.
I think there was a discussion some time ago that images that are "too
large" should not break the whole image-builder (for nightlies,
release-builds, et
This ports 9e2a7b779e6f0914395da3657b00f0ac00209bfd to the 4.1 patches.
I forgot this when preparing the initial 4.1 patch.
Signed-off-by: Martin Blumenstingl
---
target/linux/lantiq/patches-4.1/0001-MIPS-lantiq-add-pcie-driver.patch | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
request_mem_region returns NULL when requesting the region failed, and
a valid pointer when it was successful. Currently the condition is
inverted.
Signed-off-by: Martin Blumenstingl
---
package/kernel/lantiq/ltq-ifxos/patches/100-compat.patch | 2 +-
1 file changed, 1 insertion(+), 1 deletion
Signed-off-by: Martin Blumenstingl
---
target/linux/generic/config-4.1 | 2 ++
1 file changed, 2 insertions(+)
diff --git a/target/linux/generic/config-4.1 b/target/linux/generic/config-4.1
index 9f5904c..1d4108c 100644
--- a/target/linux/generic/config-4.1
+++ b/target/linux/generic/config-4.1
Signed-off-by: Martin Blumenstingl
---
package/kernel/mac80211/Makefile | 19 +++
1 file changed, 19 insertions(+)
diff --git a/package/kernel/mac80211/Makefile b/package/kernel/mac80211/Makefile
index cc98fb7..8133d75 100644
--- a/package/kernel/mac80211/Makefile
+++ b/package
Hi Arnold,
On Thu, Jun 18, 2015 at 11:15 PM, Jonas Gorski wrote:
> There is no special chip, the RTL8367 provides several means of
> accessing the chip registers; using MDIO registers is one of them.
Jonas seems to be right! Out of interested I just checked the source
code again and found more in
Hi Andre,
On Thu, Jul 23, 2015 at 11:32 PM, Andre Heider wrote:
> The dsl line never syncs, and letting 'vdsl_cpe_control --c' just sit
> there spits out repeatedly:
> 'DSL_CPE: Wrong combination of DSL PHY Firmware and hybrid type used!
> Please change one of it.'.
At some point during my tests
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 want to check this.
That was my first guess, but I a
The BT Home Hub 5A uses three PEF7071 with PHY ID 0xd565a401. Daniel's
PHY driver (for his u-boot sources) already supports that PHY because
it uses a PHY ID mask of 0xfff8.
Signed-off-by: Martin Blumenstingl
---
.../patches-3.18/0023-NET-PHY-adds-driver-for-lantiq-PHY11G.patch
On Thu, Jul 30, 2015 at 10:35 AM, feckert wrote:
> Signed-off-by: Florian Eckert
> Signed-off-by: Helge Mader
Tested-by: Martin Blumenstingl
I only have two minor nitpicks:
1. Annex and "Line Mode" are ending with a comma (e.g. "Annex: B, ")
2. I guess latency sho
Hi John,
I have just seen that you are not CC'ed here yet.
Could you please have a look at Florian's patch [0] and merge it,
since quite a few people seem to be interested in this kind of
functionality?
Regards,
Martin
[0] http://patchwork.ozlabs.org/patch/504567/
_
Hi John,
On Tue, Aug 18, 2015 at 9:03 PM, Martin Blumenstingl
wrote:
> Could you please have a look at Florian's patch [0] and merge it
I have just seen that the patch was accepted but I cannot find the
commit in the repository yet.
Could you please check what happened here?
Regards
Fixes support for AR9287 on TP-Link TD-W8980 and possibly other devices
which have an ath wifi chip at a PCI address other than 0xb800
(TD-W8980 for example has it's wifi chip at 0xbc00).
Signed-off-by: Geoffrey McRae
Signed-off-by: Martin Blumenstingl
---
This patch was init
Thanks to Sylwester Petela for testing my patch (successfully on an
ADSL connection) and for pointing out some configuration mistakes.
Others (including me) have also successfully tested this extensively
on VDSL connections.
Signed-off-by: Martin Blumenstingl
---
package/kernel/lantiq/ltq-ifxos
This patchset solves multiple problems:
- mtdsplit code for TP-Link images was partially duplicated within the
lantiq target. The generic implementation supports also v1 and v3 images,
instead of "just" v2.
- mtdsplit_brnimage fixes a bug in the existing brnImage parser. The old
code assumed
partition which was not aligned properly (and thus ended up
being readonly):
0x0048-0x0085a800 : "rootfs_data" (128 KiB EB)
Signed-off-by: Martin Blumenstingl
---
target/linux/generic/files/drivers/mtd/mtdsplit/mtdsplit_squashfs.c | 2 +-
1 file changed, 1 inser
This allows splitting EVA images (usually found in fritz devices). The
firmware will be split into a kernel and a separate rootfs partition.
Signed-off-by: Martin Blumenstingl
---
target/linux/generic/config-3.18 | 1 +
target/linux/generic/config-4.1| 1
partition.
Signed-off-by: Martin Blumenstingl
---
target/linux/generic/config-3.18 | 1 +
target/linux/generic/config-4.1| 1 +
target/linux/generic/config-4.3| 1 +
target/linux/generic/config-4.4| 1 +
.../gen
This removes the arch-specific mtdsplit parsers and enables the generic
implementations for brnImage, EVA and TP-Link instead.
Signed-off-by: Martin Blumenstingl
---
target/linux/lantiq/config-4.1 | 3 +
.../linux/lantiq/patches-4.1/0101-mtd-split.patch | 192
Hi Daniel,
On Wed, Jan 13, 2016 at 9:05 PM, Daniel Schwierzeck
wrote:
> could you retry with the attached driver?
>
> It is a complete rewrite with DT support and runs against the UGW-6.1.1
> kernel. Unfortunately I hadn't time yet to adapt and test it with
> OpenWRT. Maybe you want to volunteer
to Mathias Kresin for reporting this.
Signed-off-by: Martin Blumenstingl
---
target/linux/lantiq/image/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/lantiq/image/Makefile
b/target/linux/lantiq/image/Makefile
index 553bdc1..f986d38 100644
--- a/target/li
Hi Daniel,
On Sat, Jan 16, 2016 at 1:06 AM, Martin Blumenstingl
wrote:
>> It is a complete rewrite with DT support and runs against the UGW-6.1.1
>> kernel. Unfortunately I hadn't time yet to adapt and test it with
>> OpenWRT. Maybe you want to volunteer for that ;)
>
On Sat, Jan 16, 2016 at 4:34 PM, Daniel Schwierzeck
wrote:
> nice, thanks for testing :)
Thanks for writing nice patches ;-)
>> - replace INIT_COMPLECTION with reinit_completion (this is due the
>> newer kernel version in OpenWrt)
>> - use clk_get_fpi() to obtain the FPI clock (horrible, I am cur
Hi Ben,
On Sat, Jan 16, 2016 at 6:00 PM, Ben Whitten wrote:
> This patch series adds support for kernel 4.1 to the at91 target.
> Patches for legacy boards are dropped as the platform has been converted
> to DT in 4.1.
Do you have plans for updating at91 to linux 4.4?
As far as I know the DD (tru
On Sat, Jan 16, 2016 at 7:07 PM, Daniel Schwierzeck
wrote:
> If you use native CS, you should use the same numbering as in the
> datasheet:
>
> &spi {
> ...
> spi-nor@4 {
> #address-cells = <1>;
> #size-cells = <1>;
> compatible = "jedec,spi-
On Sat, Jan 16, 2016 at 10:48 PM, Daniel Schwierzeck
wrote:
> Am Samstag, den 16.01.2016, 21:17 +0100 schrieb Martin Blumenstingl:
>
>> So compared to your patch the final list of changes is:
>> - INIT_COMPLETION -> reinit_completion
>> - use clk_get_fpi()
>> - of
While upgrading the lantiq target to linux 4.4 it was discovered that the
SPI driver is not working with 4.4 anymore. Fixing it also does not seem
to be trivial.
However, Daniel Schwierzeck (thanks!) has provided a rewritten SPI driver.
His version works fine on 4.1 and 4.5, is now independant of s
e the new compatible strings for the pinctrl
node are used.
Additionally 0150-lantiq-pinctrl-xway.patch and the "GPIO PORT3 fix"
(which was part of 0012-pinctrl-lantiq-fix-up-pinmux.patch) were
replaced with their upstream variants which are also in 4.5.
Signed-off-by: Martin Blumenstingl
some SoCs. VRX200 SoCs for example only have 50 pins, but previously 56
pins were exposed. This means that all places which are using hardcoded
GPIO numbers (which are not passed via device-tree) need to be adjusted
(because the first GPIO number is now 462, instead of 456).
Signed-off-by: Martin Bl
!
To prevent more of these issues in the future we remove the hardcoded
PCIe reset GPIO definition and simply pass it via device-tree (like the
PCI driver does).
Signed-off-by: Martin Blumenstingl
---
target/linux/lantiq/dts/vr9.dtsi | 1 +
.../0151-lantiq-ifxmips_pcie-use
This removes the duplicate SPI register definition.
Signed-off-by: Martin Blumenstingl
---
target/linux/lantiq/dts/TDW89X0.dtsi | 76 +---
1 file changed, 36 insertions(+), 40 deletions(-)
diff --git a/target/linux/lantiq/dts/TDW89X0.dtsi
b/target/linux/lantiq
This allows devices to use SPI without having to re-define (and thus
duplicating) the whole SPI node.
By default SPI is disabled (as before) because only few devices need it.
Signed-off-by: Martin Blumenstingl
---
target/linux/lantiq/dts/ar9.dtsi | 10 ++
target/linux/lantiq/dts/vr9
Signed-off-by: Martin Blumenstingl
---
target/linux/lantiq/dts/FRITZ3370.dts | 71 +++
1 file changed, 31 insertions(+), 40 deletions(-)
diff --git a/target/linux/lantiq/dts/FRITZ3370.dts
b/target/linux/lantiq/dts/FRITZ3370.dts
index 7344052..c6a593b 100644
Also switch to the SPI definition provided by vr9.dtsi
Signed-off-by: Martin Blumenstingl
---
target/linux/lantiq/dts/EASY80920.dtsi | 87 --
1 file changed, 41 insertions(+), 46 deletions(-)
diff --git a/target/linux/lantiq/dts/EASY80920.dtsi
b/target/linux
Signed-off-by: Martin Blumenstingl
---
target/linux/lantiq/dts/DGN3500.dtsi | 91 +++-
1 file changed, 38 insertions(+), 53 deletions(-)
diff --git a/target/linux/lantiq/dts/DGN3500.dtsi
b/target/linux/lantiq/dts/DGN3500.dtsi
index bda4006..d43da9d 100644
--- a
All devices are now using the HW SPI driver, so this is not necessary
anymore.
Signed-off-by: Martin Blumenstingl
---
target/linux/lantiq/xrx200/config-default | 1 -
target/linux/lantiq/xway/config-default | 1 -
2 files changed, 2 deletions(-)
diff --git a/target/linux/lantiq/xrx200/config
0)
Signed-off-by: Martin Blumenstingl
---
...spi-add-support-for-Lantiq-SPI-controller.patch | 1133
1 file changed, 1133 insertions(+)
create mode 100644
target/linux/lantiq/patches-4.1/0100-spi-add-support-for-Lantiq-SPI-controller.patch
diff --git
a/target/linux
ctly.
- We use the new "compatible" strings to make the driver choose the
correct number of chip-selects for each SoC.
- The new driver starts counting the chip-selects at 1 (instead of 0, like
the old one did). Thus we have to adjust the devices accordingly.
Signed-off-by:
Signed-off-by: Martin Blumenstingl
---
.../0033-SPI-MIPS-lantiq-adds-spi-xway.patch | 1048
1 file changed, 1048 deletions(-)
delete mode 100644
target/linux/lantiq/patches-4.1/0033-SPI-MIPS-lantiq-adds-spi-xway.patch
diff --git
a/target/linux/lantiq/patches-4.1
Re-defining the compatible property is not required since the correct
value is inherited from vr9.dtsi.
Signed-off-by: Martin Blumenstingl
---
target/linux/lantiq/dts/ARV7519RW22.dts | 1 -
target/linux/lantiq/dts/TDW89X0.dtsi| 4
2 files changed, 5 deletions(-)
diff --git a/target
Until linux 4.1 the lantiq target used CONFIG_MTD_UIMAGE_SPLIT=y. That
option however is only available until linux 4.3 - thus it was not added
to lantiq's 4.4 kernel config (in r48307). This results in broken images
for devices which are using uImages. This fixes #21652
Signed-off-by: M
iq: Enable the uImage mtd splitter
Signed-off-by: Martin Blumenstingl
---
target/linux/lantiq/config-4.4 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/lantiq/config-4.4 b/target/linux/lantiq/config-4.4
index 08a1228..5d4b7cc 100644
--- a/target/linux/lantiq/config
This removes a lot of duplicate register and interrupt definitions by
moving the xrx200-net definition to vr9.dtsi and making all devices re-
use it.
Signed-off-by: Martin Blumenstingl
---
target/linux/lantiq/dts/ARV7519RW22.dts | 147 -
target/linux/lantiq/dts
All other SoC types are using "lantiq,sram" and "simple-bus" to ensure
that all child nodes are set up correctly during linux kernel
initialization (plat_of_setup(void) in arch/mips/lantiq/prom.c). Without
this some of sram child nodes might not be parsed.
Signed-off-by:
Hello,
currently we (Mathias and I) are planning to simplify the installation
procedure for a lantiq based device (HH5A).
Currently the installation steps require copying the calibration data
from an UBI volume on the original firmware and moving the data to a
separate mtd partition. This way the
k (NAND).
>
> Signed-off-by: Mathias Kresin
Acked-by: Martin Blumenstingl
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
On Tue, Feb 16, 2016 at 8:06 AM, Martin Schiller wrote:
> Hi!
>
> I need to set up the xrx200 switch with one LAN switch part (phy2-phy5) and
> one WAN port (phy1).
>
> The problem is, that I can see the LAN traffic on the WAN port and vice versa.
>
> It doesn't also matter if SW_PORTMAP is defin
On Tue, Mar 8, 2016 at 7:49 AM, John Crispin wrote:
> what happened to these patches ? it look slike they are gone from
> patchwork and they dont seem to apply.
it seems that Felix has already merged them yesterday (in svn r48939)
___
openwrt-devel maili
On Wed, Mar 9, 2016 at 12:14 AM, Christian Lamparter
wrote:
> Some devices (like the Cisco Meraki Z1 Cloud Managed Teleworker Gateway)
> need to be able to initialize the PCIe wifi device. Normally, this is done
> during the early stages of booting linux, because the necessary init code
> is read
On Wed, Mar 9, 2016 at 6:30 PM, Christian Lamparter
wrote:
> lantiq on the other hand has copied the func from ar71xx and adapted
> and renamed it, but kept the signature:
> ltq_pci_ath_fixup(unsigned slot, u16 *cal_data)
> it's in arch/mips/lantiq/xway/pci-ath-fixup.c.
Maybe we could also move pc
On Thu, Mar 10, 2016 at 12:22 PM, Christian Lamparter
wrote:
>> Seems like there are only two differences between the lantiq and the
>> ar71xx code:
>> 1. pci_write_config_dword(dev, PCI_BASE_ADDRESS_0, base); vs per-SoC
>> value in ar71xx
>> 2. swab32(val) when writing the caldata
> Ok, if this c
> The ftp module is in kernel 3, but not in kernel 4 for which the patch was
> built.
> Is there a way to include modules conditionally dependent on the kernel
> version?
sure, you can either exclude .ko files from the package/AUTOLOAD (see
[0]) or make a whole package depend on specific kernel v
Hi Adrian,
On Wed, Apr 6, 2016 at 4:57 AM, Adrian Panella wrote:
> Author: Adrian Panella
>
> Date: Tue Apr 5 21:45:14 2016 -0500
>
> IPQ806X: enable hard float
>
> tested with Linksys EA8500
>
> Signed-off-by: Adrian Panella
>
> diff --git a/target/linux/ipq806x/Makefile b/target/linux/ipq806
On Mon, Apr 25, 2016 at 3:00 PM, John Crispin wrote:
> is this not a bit risky ? normally we try to keep them read-only so that
> users cannot accidentally kill them. is the calib data normally not
> located in the art partition or why do you need to copy it after flashing ?
I think the caldata pa
On Mon, Apr 25, 2016 at 3:11 PM, John Crispin wrote:
> i dont see why this is needed.the patch in the tree does not look broken
> and seems to compile fine.
It seems that Hauke already pushed a similar fix:
https://dev.openwrt.org/changeset/49221/
___
op
On Mon, Apr 25, 2016 at 8:51 PM, Vittorio G (VittGam)
wrote:
> For the record, if anyone wants the old behaviour they just need to put
> this in /etc/config/system:
>
> config led 'led_system'
> option name 'System'
> option sysfs 'tdw89x0:green:wps'
> option default '1'
>
On Mon, Apr 25, 2016 at 5:38 PM, Ben Mulvihill wrote:
>> @Ben: one probably has to enable caldata swapping in the .dts.
>
> I saw your comment on openwrt.ebilan.co.uk that the "ath,eep-swap;"
> flag should be added to the dts in order to use unmodified calibration
> data, but actually this does no
On Sat, May 7, 2016 at 12:40 AM, Sebastian Ortwein wrote:
> Hey
>
> I have tried do get openwrt working on my Fritzbox. Openwrt will start
> Network and VDSL Modem is working. But WLAN ist not working. The Chip is
> supported bei the ath9k driver. Any hint how I can get Wifi working ?
I see you al
On Sun, May 8, 2016 at 10:33 AM, Sebastian Ortwein wrote:
> I get the eeprom from the ath9k driver working, but wifi will not showed.
> First, I get a error message that from the ath9k driver that the eeprom
> couldn't load. After PCI Bus is initialize the eeprom is loaded.
That is "normal" - noth
On Sun, May 8, 2016 at 5:49 PM, Sebastian Ortwein wrote:
> can I add it the following way ?
> mdio@0 {
> #address-cells = <1>;
> #size-cells = <0>;
> compatible = "lantiq,xrx200-mdio";
> phy0: ethernet-phy@0 {
>
1 - 100 of 199 matches
Mail list logo
