Hi everybody,
I have a TP-Link Archer C7 v2 running a fairly recent build of LEDE (r1952,
Linux 4.4.26, compat-wireless-2016-10-08). It all works well except for the
fact that when I connect a Nexus 5X device to the 5GHz radio, the kernel or
ath10k driver will crash after a while. 5Ghz wifi will
On Saturday, October 29, 2016 8:44:27 PM CEST Christian Lamparter wrote:
> [...]
> [7.849577] dwc2 1e101000.ifxhcd: Mode Mismatch Interrupt: currently in
> Host mode
> [7.855582] dwc2 1e101000.ifxhcd: Mode Mismatch Interrupt: currently in
> Host mode
> [7.862820] dwc2 1e101000.ifxhcd
On Friday, October 28, 2016 11:22:12 PM CEST Ben Mulvihill wrote:
> On Fri, 2016-10-28 at 18:28 +0200, Christian Lamparter wrote:
> > Hello,
> >
> > On Friday, October 28, 2016 4:30:56 PM CEST Ben Mulvihill wrote:
> > > Add device tree binding for dwc2 usb driver on lantiq danube
> > >
> > > Sign
Hello
looks like there are lots of broken packages currently.
was going to install i2c-tools but it looks like it failed with lots of
messages like:
include/linux/i2c-dev.h:156:21: warning: inlining failed in call to
'i2c_smbus_access': call is unlikely and code size would grow [-Winline]
st
Hi Jo,
thanks, I've switched to latest gcc-5 via update-alternatives and my
buildroot ist up & running ... ;-)
gcc (Debian 5.4.1-3) 5.4.1 20161019
Copyright (C) 2015 Free Software Foundation, Inc.
br
dirk
Am Samstag, den 29.10.2016, 18:13 +0200 schrieb Jo-Philipp Wich:
> Hi Dirk,
I guess it bo
On Sat, Oct 29, 2016 at 6:13 PM, Jo-Philipp Wich wrote:
> Hi Dirk,
>
> I guess it boils down to gcc 6 being unsupported yet, I would anticipate
> issues with other host builds as well.
>
> For now I suggest to downgrade to gcc 5.x
Arch Linux also uses gcc 6:
$ gcc --version
gcc (GCC) 6.2.1 2016083
Hi Dirk,
I guess it boils down to gcc 6 being unsupported yet, I would anticipate
issues with other host builds as well.
For now I suggest to downgrade to gcc 5.x
~ Jo
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/m
Hi Alex,
you're right, but I'm using testing of course and the right codename is
"stretch"
root@blackserve:~# uname -a
Linux blackserve 4.7.0-1-amd64 #1 SMP Debian 4.7.8-1 (2016-10-19)
x86_64 GNU/Linux
root@blackserve:~# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Descrip
On Sat, 2016-10-29 at 13:28 +0200, Ben Mulvihill wrote:
> On Fri, 2016-10-28 at 23:35 +0200, Ben Mulvihill wrote:
> > On Fri, 2016-10-28 at 19:14 +0300, Antti Seppälä wrote:
> > > On 28 October 2016 at 17:30, Ben Mulvihill
> > > wrote:
> > > > Add device tree binding for dwc2 usb driver on lantiq
Hei hei,
On 29.10.2016 11:00, Dirk wrote:
> I'm using debian testing/jessie as host - see output below.
How? Jessie is stable since 2015, current testing is stretch. o.O
Greets
Alex
signature.asc
Description: OpenPGP digital signature
___
Lede-dev
Hi
> 2. When looking at lede I'm somewhat missing the release engineering
> part. This has nothing to do with infrastructure or build setups or
> even coding. When looking at Debian they have a release team taking
> care of freezing, planning and releases. - or take Theo de Raadt's
> job in OpenB
On Fri, 2016-10-28 at 23:35 +0200, Ben Mulvihill wrote:
> On Fri, 2016-10-28 at 19:14 +0300, Antti Seppälä wrote:
> > On 28 October 2016 at 17:30, Ben Mulvihill wrote:
> > > Add device tree binding for dwc2 usb driver on lantiq danube
> > >
> > > Signed-off-by: Ben Mulvihill
> > > ---
> > > diff
As already said... in lede is missing the patch I've added to bb to support vmmc
On Fri, Oct 28, 2016 at 11:24 PM, Eddi De Pieri wrote:
> Give a look at
> https://github.com/pgid69/bcm63xx-phone/tree/master/bcm63xx-ast-chan
>
> they have the same source for both 1.8 1.11 and 1.13, it seems that i
On 10/29/2016 03:18 AM, J Mo wrote:
>
> On 10/28/2016 11:39 AM, yanosz wrote:
>> 1. I'm unhappy with the state of OpenWRT at the moment. I see some
>> trouble in building and releasing. The current code base has some bugs.
>> I'ven't seen a fix for "mad cow" yet. For me it is hard to estimate
>>
Hi Jo,
that doesn't help. I've added the -fPIC command to your test:
root@x250:/home/dirk/Downloads/lede/clean/source# echo 'int main(int a,
char **v) { gzdopen(0, "rb"); return 0; }' | gcc -include zlib.h -x
c -o test - -fPIC -Wl,-Bstatic -lz -Wl,-Bdynamic
/usr/bin/ld: /usr/lib/gcc/x86_64-li
Hello,
Am 10/29/2016 um 03:18 AM schrieb J Mo:
>
> On 10/28/2016 11:39 AM, yanosz wrote:
>> 1. I'm unhappy with the state of OpenWRT at the moment. I see some
>> trouble in building and releasing. The current code base has some bugs.
>> I'ven't seen a fix for "mad cow" yet. For me it is hard to e
Hi Dirk,
please try the following patch:
http://git.lede-project.org/3bc496c
~ Jo
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Hi Jo,
that's the output:
root@x250:/usr/lib/x86_64-linux-gnu# echo 'int main(int a, char **v) {
gzdopen(0, "rb"); return 0; }' | \
> gcc -include zlib.h -x c -o test - -Wl,-Bstatic -lz -Wl,-Bdynamic
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-
gnu/libz.a(gzlib.o): relo
On 2016-10-25 13:02, Jo-Philipp Wich wrote:
> The current default rootfs size of 256MB in conjunction with 4K blocks
> produces an ext4 filesystem which lacks the appropriate amount of backup GDT
> entries to support online-resizing.
>
> For x86 targets, increase the default rootfs size to 2048MB
Hi Dirk,
please run the following command and see if it is reporting any errors:
echo 'int main(int a, char **v) { gzdopen(0, "rb"); return 0; }' | \
gcc -include zlib.h -x c -o test - -Wl,-Bstatic -lz -Wl,-Bdynamic
~ Jo
___
Lede-dev mailing list
Hi,
something scrumbled my formerly working LEDE buildroot environment.
I'm using debian testing/jessie as host - see output below.
The static zlib package (zlib1g-dev) is installed and the library is
located in /usr/lib/x86_64-linux-gnu/libz.a.
Any idea how to nail down this problem?
Thanks!
Dir
From: Paul Wassi
Refresh patches for all targets that support kernel 4.4.
compile/run-tested on ar71xx, brcm47xx, kirkwood.
Signed-off-by: Paul Wassi
---
include/kernel-version.mk
|4 +-
target/linux/brcm2708/patc
> Have you tested your patch on these mvebu devices? or just in theory?
I've successfully tested on WRT1200AC, which is affected by this patch.
(I.e. eth0 and eth1 are swapped then)
That's the only mvebu device I have here right now.
___
Lede-dev mailin
Have you tested your patch on these mvebu devices? or just in theory?
Best Regards,
Syrone Wong
On Sat, Oct 29, 2016 at 2:50 PM, wrote:
>> According to https://wiki.openwrt.org/toh/linksys/wrt_ac_series, they
>> have different switch layouts, especially mamba(WRT1900ac v1).
>
> No, they do no
24 matches
Mail list logo
