Re: [OpenWrt-Devel] lantiq DSL drivers / firmware info

2015-05-04 Thread Johannes Berg
On Mon, 2015-05-04 at 23:16 +0200, Sylwester Petela wrote: > [ 456.056000] DSL[00]: negative response for MsgID=0x2B0A > (Class=0x3100) - on try 0! > [ 456.764000] DSL[00]: Error for send CMD MsgID=0x2B0A - KEEP line! > [ 456.768000] DSL[00]: ERROR - ReTx PM counters read failed! > [ 457.

Re: [OpenWrt-Devel] Device tree issues with TL-WDR4900 (mpc85xx) and kernel 4.0.1

2015-05-04 Thread Wojciech Dubowik
On 04/05/15 22:45, Heiner Kallweit wrote: I tried to make the TL-WDR4900 work under kernel 4.0. Adjusting the platform-specific patches was quickly done and the system boots. However I get the following error messages. [2.959975] /leds/system: could not get #gpio-cells for /soc@ffe0/gpi

[OpenWrt-Devel] [Patch V2 2/2] ipq806x: add support for zImage kernel

2015-05-04 Thread Mathieu Olivari
This change enable zImage+appended dtb support in ipq806x kernel options. The zImage will now be generated as part of the kernel binaries. Platforms which do not have DT support enabled in U-boot can now make use of it by generating zImage files and appending dtb to it. It is not used yet but it i

[OpenWrt-Devel] [Patch V2 1/2] ipq806x: fix boot freeze on zImage kernel

2015-05-04 Thread Mathieu Olivari
ARCH_QCOM is using the ARCH_MULTIPLATFORM option, as now recommended on most ARM architectures. This automatically calculate ZRELADDR by masking PHYS_OFFSET with 0xf800. On IPQ806x though, the first ~20MB of RAM is reserved for the hardware. In newer bootloader, when DT is used, this is not a

Re: [OpenWrt-Devel] Intermittent Ethernet failure

2015-05-04 Thread Daniel Golle
Hi Bill! On Mon, May 04, 2015 at 05:53:21PM -0700, Bill wrote: > I have finally been able to reproduce the problem here at home by setting up > a bridge and leaving it alone for a few days. When it failed, this is what > dmesg told me: > [ 409.38] eth0: link up (100Mbps/Full duplex) > > [

[OpenWrt-Devel] Intermittent Ethernet failure

2015-05-04 Thread Bill
I have a number of Ubiquiti LOCO M5 units (ar71xx) in use as "transparent" (simulated layer 2) wireless bridges with the client devices relayd. I used a CC trunk pull of r42711 because I needed support for the new "XW" variant of this device (which was not, alas, present in BB). I'm seeing ve

Re: [OpenWrt-Devel] lantiq DSL drivers / firmware info

2015-05-04 Thread Sylwester Petela
W dniu 2015-05-04 o 21:13, Johannes Berg pisze: On Mon, 2015-05-04 at 21:00 +0200, Martin Blumenstingl wrote: 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 use it with my Annex B ADSL connection (for the recor

[OpenWrt-Devel] Device tree issues with TL-WDR4900 (mpc85xx) and kernel 4.0.1

2015-05-04 Thread Heiner Kallweit
I tried to make the TL-WDR4900 work under kernel 4.0. Adjusting the platform-specific patches was quickly done and the system boots. However I get the following error messages. [2.959975] /leds/system: could not get #gpio-cells for /soc@ffe0/gpio-controller@f000 [2.968276] leds-gpio:

Re: [OpenWrt-Devel] lantiq DSL drivers / firmware info

2015-05-04 Thread Martin Blumenstingl
> 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

Re: [OpenWrt-Devel] lantiq DSL drivers / firmware info

2015-05-04 Thread Johannes Berg
On Mon, 2015-05-04 at 21:00 +0200, Martin Blumenstingl wrote: > 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 use it with > my Annex B ADSL connection (for the record: I am not using a splitter). > While trying t

Re: [OpenWrt-Devel] lantiq DSL drivers / firmware info

2015-05-04 Thread Martin Blumenstingl
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

Re: [OpenWrt-Devel] lantiq DSL drivers / firmware info

2015-05-04 Thread Johannes Berg
Hi Martin, > >> Has anyone tried any of these firmwares with newer drivers to see if > >> they can do vectoring? > > > > Put another way - does anyone have a driver that works with firmware > > 6.x? > Neither v4.11.4 nor v4.11.11 support vectoring. > Thus you need at least v4.15.2 (see my other th

Re: [OpenWrt-Devel] [PATCH] tools/mkimage: backport gcc5 compatibility, patch

2015-05-04 Thread Dirk Neukirchen
On 23.04.2015 11:27, Dirk Neukirchen wrote: > > Fedora 22 includes gcc5 by default > build leads to error: > include/linux/compiler-gcc.h:114:30: fatal error: linux/compiler-gcc5.h: No > such file or directory > > backport upstream patch: "Add linux/compiler-gcc5.h to fix builds with gcc5" > id:

Re: [OpenWrt-Devel] Archer VR200v GPL code

2015-05-04 Thread Mirko Parthey
On Mon, May 04, 2015 at 12:23:10PM +0200, Daniel Golle wrote: > I cannot find the sourcecode on http://www.tp-link.de/support/gpl/ In the menu on the left, choose "VDSL/ADSL". This leads to: http://www.tp-link.de/support/gpl/?categoryid=548 http://www.tp-link.de/resources/gpl/Archer-VR200v_GPL.tar

[OpenWrt-Devel] Archer VR200v GPL code

2015-05-04 Thread Daniel Golle
Hi! Looks like the Firmware of the Archer VR200v is based on Linux. http://www.tp-link.de/support/download/?model=Archer+VR200v&version=V1 binwalk Archer_VR200vv1_0.8.0_0.14_up_boot\(150331\)_2015-03-31_09.02.51.bin DECIMAL HEXADECIMAL DESCRIPTION -

Re: [OpenWrt-Devel] Thoughts on shellcheck?

2015-05-04 Thread Bastian Bittorf
* Eric Schultz [03.05.2015 20:28]: > Hey, I wanted to let folks know about this open source tool for finding > errors in shell scripts that I stumbled on: > https://github.com/koalaman/shellcheck. Not sure on how applicable it will > be to the complex features that OpenWrt uses but if it worked we