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)
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 Blumenstingl
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 martin.blumensti...@googlemail.com
---
.../0001-MIPS
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]
Hello,
I recently purchased a TP-Link TD-W8970 on which I have installed OpenWrt.
My goal is to use it as my main DSL router, so it has to connect to
the internet.
For the reference: at the moment I'm using a AVM FritzBox for this
purpose, which is connected directly to the phone jack (the web
On Fri, Jun 5, 2015 at 4:56 AM, Aleksander Wałęski olewa...@gmail.com 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
/Germany 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
martin.blumensti...@googlemail.com wrote:
I can test it this weekend on an Annex B ADSL connection. So I will
test
On Fri, Jun 5, 2015 at 4:56 AM, Aleksander Wałęski olewa...@gmail.com 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
++
++#
+--- /dev/null
b/board/arcadyan/vgv7510kw22/vgv7510kw22.c
+@@ -0,0 +1,133 @@
++/*
++ * Copyright (C) 2015 Martin Blumenstingl martin.blumensti...@googlemail.com
++ *
++ * SPDX-License-Identifier: GPL-2.0+
++ */
++
++#include common.h
++#include spi.h
++#include asm/gpio.h
++#include asm/lantiq
08b085a07efe12568d86dff064e6f089e2971744 Mon Sep 17 00:00:00 2001
+From: Martin Blumenstingl martin.blumensti...@googlemail.com
+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
---
.../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 +
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
Hi Flo,
On Thu, Jun 18, 2015 at 10:59 AM, Florian Eckert
eckert.flor...@googlemail.com 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
CC'ing you.
On Mon, May 25, 2015 at 4:29 PM, Martin Blumenstingl
martin.blumensti...@googlemail.com 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
and then with the new code but passing the old CRC32
poly value. Both resulted in a brnboot image with the same sha1sum.
Signed-off-by: Martin Blumenstingl martin.blumensti...@googlemail.com
---
tools/firmware-utils/src/mkbrnimg.c | 20 +---
1 file changed, 13 insertions(+), 7 deletions(-)
diff
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 martin.blumensti...@googlemail.com
---
target/linux/lantiq/image/Makefile | 10 +-
1 file changed, 5 insertions(+), 5 deletions
Hi Aleksander,
On Wed, May 27, 2015 at 9:20 PM, Aleksander Wałęski olewa...@gmail.com 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
Hi Arnold,
On Fri, May 29, 2015 at 5:50 PM, Arnold Schulz arny...@gmx.net 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
On Sat, May 30, 2015 at 1:58 AM, Arnold Schulz arny...@gmx.net 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
Hi,
On Sat, May 30, 2015 at 3:00 PM, Maciej Soltysiak mac...@soltysiak.com 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]
/homehub_v5a
Signed-off-by: Martin Blumenstingl martin.blumensti...@googlemail.com
---
.../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
Newer DSL driver versions depend on the address information.
Signed-off-by: Martin Blumenstingl martin.blumensti...@googlemail.com
---
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
On Sat, Jun 6, 2015 at 3:23 PM, Sylwester Petela ssc...@gmail.com 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
Make it consistent with the net_device struct and the xrx200 driver
Signed-off-by: Martin Blumenstingl martin.blumensti...@googlemail.com
---
.../lantiq/patches-3.18/0028-NET-lantiq-various-etop-fixes.patch | 2 +-
.../0035-owrt-lantiq-wifi-and-ethernet-eeprom-handling.patch | 9 -
2
Signed-off-by: Martin Blumenstingl martin.blumensti...@googlemail.com
---
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
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 martin.blumensti...@googlemail.com
---
.../patches-3.18/681-NET-add-of_get_mac_address_mtd.patch| 12
Signed-off-by: Martin Blumenstingl martin.blumensti...@googlemail.com
---
.../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
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/patches
On Mon, Jul 6, 2015 at 12:39 PM, Felix Fietkau n...@openwrt.org 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
Hi Felix,
On Mon, Jul 6, 2015 at 12:26 PM, Felix Fietkau n...@openwrt.org 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
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
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 martin.blumensti...@googlemail.com
---
package/libs/ncurses/Makefile | 2 +-
.../ncurses/patches/102-ncurses-5.9-gcc-5
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:
On Mon, May 25, 2015 at 3:05 PM, Dirk Neukirchen dirkneukirc...@web.de 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
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.
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/
/homehub_v5a
V2: Use the correct PCI interrupt (fixes 2.4GHz wifi)
Signed-off-by: Martin Blumenstingl martin.blumensti...@googlemail.com
---
.../etc/hotplug.d/firmware/11-ath10k-caldata | 51
.../lantiq/base-files/etc/uci-defaults/01_leds | 2 +-
.../lantiq/base-files/etc/uci-defaults
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 martin.blumensti...@googlemail.com
---
target/linux/lantiq/patches
On Thu, Jul 30, 2015 at 10:35 AM, feckert eckert.flor...@googlemail.com wrote:
Signed-off-by: Florian Eckert eckert.flor...@googlemail.com
Signed-off-by: Helge Mader hma...@tdt.de
Tested-by: Martin Blumenstingl martin.blumensti...@googlemail.com
I only have two minor nitpicks:
1. Annex and Line
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 martin.blumensti...@googlemail.com
---
.../patches-3.18/0023-NET-PHY-adds-driver
On Fri, Jul 24, 2015 at 1:00 AM, Aleksander Wałęski olewa...@gmail.com 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
This ports 9e2a7b779e6f0914395da3657b00f0ac00209bfd to the 4.1 patches.
I forgot this when preparing the initial 4.1 patch.
Signed-off-by: Martin Blumenstingl martin.blumensti...@googlemail.com
---
target/linux/lantiq/patches-4.1/0001-MIPS-lantiq-add-pcie-driver.patch | 2 +-
1 file changed, 1
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 martin.blumensti...@googlemail.com
---
package/kernel/lantiq/ltq-ifxos/patches/100-compat.patch | 2 +-
1 file
Hi Arnold,
On Thu, Jun 18, 2015 at 11:15 PM, Jonas Gorski j...@openwrt.org 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
Signed-off-by: Martin Blumenstingl martin.blumensti...@googlemail.com
---
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
Signed-off-by: Martin Blumenstingl martin.blumensti...@googlemail.com
---
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
On Mon, Jul 13, 2015 at 6:04 PM, Jonathan Bennett jbscienc...@gmail.com 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,
Hi Felix,
On Sun, Nov 8, 2015 at 1:29 PM, Felix Fietkau wrote:
> Did you test this on a real VDSL line? Last time I tried a firmware from
> a newer Speedport build (some months ago), it did not work.
I thought it works as I've seen it entering SHOWTIME.
Unfortunately you are
On Sun, Nov 1, 2015 at 9:01 AM, John Crispin wrote:
> I'll merge this as is, however i am starting to wonder if we should not
> just autodetect the right fw to use and only pass 11G/22F as an option
I am *guessing* that it's due to binary size reasons (including all
GPHY
The old version (5.3.4.A.1.6-5.3.6.4.1.2) is not supported by the new
DSL driver. The new version (5.6.8.4.1.7-5.6.7.2.1.2) also brings
(theoretically) vectoring support.
Signed-off-by: Martin Blumenstingl <martin.blumensti...@googlemail.com>
---
package/kernel/lantiq/ltq-vdsl-
This updates the relevant source files to util-linux changeset
4419ffb9eff5801fdbd385a4a6199b3877f802ad.
Signed-off-by: Martin Blumenstingl <martin.blumensti...@googlemail.com>
---
libblkid-tiny/bitops.h| 166 ++
libblkid-tiny/blkdev.h| 47 +-
li
Hello,
this updates the libblkid code and additionally adds F2FS support.
The libblkid-tiny binary is now slightly smaller:
Before:
19268 libblkid-tiny.so
After:
18256 libblkid-tiny.so
mount output of a F2FS device:
# mount | grep f2fs
/dev/sda1 on /mnt type f2fs
Signed-off-by: Martin Blumenstingl <martin.blumensti...@googlemail.com>
---
Unfortunately I am not sure if and how px5g-standalone should be
adjusted, so this should be done by someone else if required.
package/utils/px5g/px5g.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
On Thu, Oct 8, 2015 at 6:13 PM, Sandy McArthur Jr wrote:
> While attempting to pivot overlay using the f2fs filesystem in a 4mib
> internal flash storage device on usb flash storage with the final CC
> 15.05 release I ran into the hurdle that the block command doesn't
>
Signed-off-by: Martin Blumenstingl <martin.blumensti...@googlemail.com>
---
CMakeLists.txt| 1 +
libblkid-tiny/f2fs.c | 101 ++
libblkid-tiny/libblkid-tiny.c | 1 +
3 files changed, 103 insertions(+)
create mode 100644 li
This fixes #20409
Signed-off-by: Martin Blumenstingl <martin.blumensti...@googlemail.com>
---
.../0043-MIPS-add-board-support-for-Arcadyan-VGV7510KW22.patch | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git
a/package/boot/uboot-lantiq/patches/0043-MIPS-add
On Wed, Oct 14, 2015 at 12:19 PM, Afkar Rafique wrote:
> Could anyone please explain how i can configure and read GPIO value.
There's an article on the wiki which explains how to set a GPIO to a
specific value: [0]
If you want to read a GPIO value then you use direction "in"
Hi John,
I am getting SPI errors on latest trunk.
It seems that those might be related to your SPI changes from last week.
I found that someone else reported a similar issue a few years ago: [0].
That patch was never applied and I'm not sure if it's 100% correct.
These are the errors I get
This should help finding potential problems with the SPI driver.
Signed-off-by: Martin Blumenstingl <martin.blumensti...@googlemail.com>
---
.../lantiq/patches-3.18/0033-SPI-MIPS-lantiq-adds-spi-xway.patch | 4 +++-
.../linux/lantiq/patches-4.1/0033-SPI-MIPS-lantiq-adds-spi-xway.pat
Until now the SPI driver used the TX bits for the RX FIFO. This seems
uncritical for now since both are equals on my devices (VR9), but this
could cause problems on other SoCs.
Signed-off-by: Martin Blumenstingl <martin.blumensti...@googlemail.com>
---
.../linux/lantiq/patches-3.18/0033-SP
Hi John,
On Thu, Oct 15, 2015 at 7:59 AM, John Crispin wrote:
> bummer. i had hoped that my patch fixed the issue.
>
> did you try the patch graham posted ?
I split the patch into two and tried:
1) flushing in ltq_spi_wait_ready
2) reducing rxreq_max in ltq_spi_rxreq_set
3)
Whenever two processes were executing different commands at the same
time then one of the commands sometimes got the response of the other
command.
Signed-off-by: Martin Blumenstingl <martin.blumensti...@googlemail.com>
---
target/linux/lantiq/base-files/lib/functions/lantiq_dsl.sh | 2
Hi,
On Sat, Jul 11, 2015 at 9:39 AM, Sylwester Petela ssc...@gmail.com 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
Hi John,
On Tue, Aug 18, 2015 at 9:03 PM, Martin Blumenstingl
<martin.blumensti...@googlemail.com> 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 c
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 <ge...@spacevs.com>
Signed-off-by: Martin Blumen
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 <martin.blumensti...@googlemail.
This adds the changes from r46219 to the linux 4.1 patches as well.
Signed-off-by: Martin Blumenstingl <martin.blumensti...@googlemail.com>
---
It seems that I forgot to include these in the original patchset which
added the 4.1 patches for the lantiq target.
Thanks to Mathias Kresin for f
On Sun, Nov 29, 2015 at 7:25 PM, Andre Heider wrote:
> --- a/target/linux/lantiq/xrx200/target.mk
> +++ b/target/linux/lantiq/xrx200/target.mk
> @@ -7,7 +7,6 @@ CPU_SUBTYPE:=dsp
>
> DEFAULT_PACKAGES+=kmod-leds-gpio \
> kmod-gpio-button-hotplug \
> -
On Thu, Dec 3, 2015 at 3:00 PM, Felix Fietkau wrote:
> Maybe it's worth testing the latest from here (seems to be newer):
> https://www.codeaurora.org/cgit/quic/qsdk/oss/firmware/ath10k-firmware/tree/10.2.4
I have just updated one of my devices to 10.2.4.97. I'll let it run
for
On Sat, Dec 12, 2015 at 3:19 PM, John Crispin wrote:
> ok, let me know how it went, if you dont mind i'll close the 2 pending
> patches for now. if we merge we will most likely want the newest FW.
sure, feel free.
___
openwrt-devel
linux 4.4 (since commit 08b3c894e56580b8ed3e601212a25bda974c3cc2
"MIPS: lantiq: Disable xbar fpi burst mode") requires that the xbar is
defined in the .dts of vrx200 (VR9) SoCs.
---
I am not sure if the xbar size is really 0x1000 or if it's smaller/larger.
Unfortunately there doesn't seem to be
gpio.h needs the linux/ prefix with linux 4.4.
---
package/kernel/lantiq/ltq-vmmc/patches/100-target.patch | 8
package/kernel/lantiq/ltq-vmmc/patches/400-falcon.patch | 2 +-
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git
Upstream linux 4.2 commit 84be456f883c4685680fba8e5154b5f72e92957e
"remove " moves scatterlist.h to linux/ instead of asm/.
Upstream linux 4.3 commit b0d955ba4688fcba8112884931aea1f1e6f50f03
"crypto: aead - Remove old AEAD interfaces" removed aead_request_set_assoc.
aead_request_set_ad should be
On Sat, Dec 12, 2015 at 3:19 PM, John Crispin wrote:
> if we merge we will most likely want the newest FW.
I have now tested 10.2.4.97 for a week and no crashes so far.
Thus I just sent an updated patchset.
___
openwrt-devel mailing
Signed-off-by: Martin Blumenstingl <martin.blumensti...@googlemail.com>
---
Working fine for me after a short test on a QCA9880-BR4A.
package/firmware/ath10k-firmware/Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/firmware/ath10k-firmware/Makef
Signed-off-by: Martin Blumenstingl <martin.blumensti...@googlemail.com>
---
I couldn't test this change since I don't have a device that uses this.
target/linux/ar71xx/base-files/lib/preinit/82_patch_ath10k | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/
This removes one patch which was applied upstream with commit
67b9bcd36906e12a15ffec19463afbbd6a41660e. All other patches were
refreshed.
Signed-off-by: Martin Blumenstingl <martin.blumensti...@googlemail.com>
---
include/kernel-version.mk | 4 +--
...spi-nor-d
On Mon, Jan 11, 2016 at 2:59 PM, John Crispin wrote:
> 0x1F40-0x1F400FFF means that its size is 0x1000. i think you having
> a off-by-one thinko ...
...and I think you are right!
Sorry for the noise, please drop this patch.
___
Remove the "DEU test manager" code which has not been used for more than
two years (as the kernel module is not installed anymore since
aa65888e08ec7279cfecc24c5bfe71cf9a016b91).
This fixes compilation on kernel 4.3 (which removes
aead_request_set_assoc) and newer.
Signed-off-
According to the datasheet says that the xbar register range is
0x1F40-0x1F400FFF. Thanks to John Crispin for looking it up.
Signed-off-by: Martin Blumenstingl <martin.blumensti...@googlemail.com>
---
target/linux/lantiq/dts/vr9.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 de
Hello,
this series adds linux 4.4 support to the lantiq target.
It depends on the linux/generic 4.4.0 update because -rc8 contains a
build-fix for MIPS devices.
I have tested it on two (VRX200) devices:
- VGV7510KW22 (seems to work fine)
- TD-W8970 (the mtd_reads in mtd_split seem to only return
Upstream linux 4.2 commit 84be456f883c4685680fba8e5154b5f72e92957e
"remove " requires us to include linux/scatterlist.h
instead. This also works with older kernels (at least 4.1, thanks to
Hauke Mehrtens for testing).
Signed-off-by: Martin Blumenstingl <martin.blumensti...@g
Hi John,
On Mon, Jan 11, 2016 at 3:25 PM, Martin Blumenstingl
<martin.blumensti...@googlemail.com> wrote:
> Here's the kernel log from the TD-W8970: https://paste.kde.org/pia7p73i9
> I have debugged it and split_tplink_kernel gets 0x2 as offset and
> 0x7A as size (whic
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
>
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
This removes the arch-specific mtdsplit parsers and enables the generic
implementations for brnImage, EVA and TP-Link instead.
Signed-off-by: Martin Blumenstingl <martin.blumensti...@googlemail.com>
---
target/linux/lantiq/config-4.1 | 3 +
.../linux/lantiq/patches-4.
partition which was not aligned properly (and thus ended up
being readonly):
0x0048-0x0085a800 : "rootfs_data" (128 KiB EB)
Signed-off-by: Martin Blumenstingl <martin.blumensti...@googlemail.com>
---
target/linux/generic/files/drivers/mtd/mtdsplit/mtdsplit_squa
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 <martin.blumensti...@googlemail.com>
---
target/linux/generic/config-3.18 | 1 +
target/linux/g
partition.
Signed-off-by: Martin Blumenstingl <martin.blumensti...@googlemail.com>
---
target/linux/generic/config-3.18 | 1 +
target/linux/generic/config-4.1| 1 +
target/linux/generic/config-4.3| 1 +
target/linux/ge
to Mathias Kresin for reporting this.
Signed-off-by: Martin Blumenstingl <martin.blumensti...@googlemail.com>
---
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
Hi Daniel,
On Sat, Jan 16, 2016 at 1:06 AM, Martin Blumenstingl
<martin.blumensti...@googlemail.com> 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. May
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
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
!
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 <martin.blumensti...@googlemail.com>
---
target/linux/lantiq/dts/vr9.dtsi
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
This removes the duplicate SPI register definition.
Signed-off-by: Martin Blumenstingl <martin.blumensti...@googlemail.com>
---
target/linux/lantiq/dts/TDW89X0.dtsi | 76 +---
1 file changed, 36 insertions(+), 40 deletions(-)
diff --git a/target/linux/lant
Also switch to the SPI definition provided by vr9.dtsi
Signed-off-by: Martin Blumenstingl <martin.blumensti...@googlemail.com>
---
target/linux/lantiq/dts/EASY80920.dtsi | 87 --
1 file changed, 41 insertions(+), 46 deletions(-)
diff --git a/target/linux/
Signed-off-by: Martin Blumenstingl <martin.blumensti...@googlemail.com>
---
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/FRI
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 <martin.blumensti...@googlemail.com>
---
target/linux/lantiq/dts/ar9.dts
All devices are now using the HW SPI driver, so this is not necessary
anymore.
Signed-off-by: Martin Blumenstingl <martin.blumensti...@googlemail.com>
---
target/linux/lantiq/xrx200/config-default | 1 -
target/linux/lantiq/xway/config-default | 1 -
2 files changed, 2 deletions(-)
diff
1 - 100 of 190 matches
Mail list logo