Russell Senior writes:
> Works for me, on current HEAD*, with ar71xx (netgear wndr3800). Can
> you include your /etc/config/network and any other relevant
> configuration details?
>
> * $ git describe
> reboot-8373-gbc3d47cd12
Good to hear.
Is yours configured as a bridge anywhere? My apu2
The BDFs for all boards were upstreamed to the ath10k-firmware
repository and linux-firmware.git.
We switched to the upstream board-2.bin, hence the files can be removed
here.
Keep the ipq-wifi package in case new boards are added. It might take
some time till board-2.bins send upstream are
This patch replaces the custom autoload quirk of the
RT-AC58U with a bootargs-append overwrite.
The vendor's u-boot doesn't leave the bootargs / cmdline alone,
so the it can't be overwritten in any other way right now...
And of course, this will be a lot of fun to deal with once
the device
This patch updates the board-2.bin for the default
IPQ4019, QCA9984 and QCA9888 ath10k-firmware-xyz-ct
and -ct-htt firmwares.
Signed-off-by: Christian Lamparter
---
package/firmware/ath10k-firmware/Makefile | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
The NBG6617's boardfile was merged and this device can
now switch to the upstream ath10k board-2.bin.
Signed-off-by: Christian Lamparter
---
.../files-4.14/arch/arm/boot/dts/qcom-ipq4018-nbg6617.dts | 2 ++
1 file changed, 2 insertions(+)
diff --git
On Monday, October 22, 2018 11:04:14 PM CEST Robert Marko wrote:
> On Mon, 22 Oct 2018 at 23:03, Christian Lamparter wrote:
> >
> > The NBG6617's boardfile was merged and this device can
> > now switch to the upstream ath10k board-2.bin.
>
> This is only applicable if ath10k-firmware is selected
[resending without HTML attachment]
[see http://files.zajec.net/openwrt/ubifs-dbg.html instead]
On Mon, 22 Oct 2018 at 10:26, Richard Weinberger wrote:
> Am Montag, 22. Oktober 2018, 09:14:08 CEST schrieb Rafał Miłecki:
> > On Fri, 19 Oct 2018 at 14:31, Rafał Miłecki wrote:
> > > Since OpenWrt
On Mon, 22 Oct 2018 at 10:26, Richard Weinberger wrote:
> Am Montag, 22. Oktober 2018, 09:14:08 CEST schrieb Rafał Miłecki:
> > On Fri, 19 Oct 2018 at 14:31, Rafał Miłecki wrote:
> > > Since OpenWrt switch from kernel 4.9 to 4.14 users started randomly
> > > reporting file system corruptions.
On Mon, 22 Oct 2018 at 23:03, Christian Lamparter wrote:
>
> The NBG6617's boardfile was merged and this device can
> now switch to the upstream ath10k board-2.bin.
This is only applicable if ath10k-firmware is selected as by default
ath10k-firmware-ct is used and that one uses the old board
The BDFs for all boards were upstreamed to the ath10k-firmware
repository and linux-firmware.git.
We switched to the upstream board-2.bin, hence the files can be removed
here.
Keep the ipq-wifi package in case new boards are added. It might take
some time till board-2.bins send upstream are
This patch replaces the custom autoload quirk of the
RT-AC58U with a bootargs-append overwrite.
The vendor's u-boot doesn't leave the bootargs / cmdline alone,
so the it can't be overwritten in any other way right now...
And of course, this will be a lot of fun to deal with once
the device
This patch updates the board-2.bin for the default
IPQ4019, QCA9984 and QCA9888 ath10k-firmware-xyz-ct
and -ct-htt firmwares.
Signed-off-by: Christian Lamparter
---
package/firmware/ath10k-firmware/Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
The NBG6617's boardfile was merged and this device can
now switch to the upstream ath10k board-2.bin.
Signed-off-by: Christian Lamparter
---
.../files-4.14/arch/arm/boot/dts/qcom-ipq4018-nbg6617.dts | 2 ++
1 file changed, 2 insertions(+)
diff --git
We have confirmed fails for mips and x86 for even seeing any
ipv6 traffic on a comcast uplink, thus dhcpv6pd fails.
See:
https://bugs.openwrt.org/index.php?do=details_id=1763
And
https://forum.openwrt.org/t/openwrt-18-06-rc1-doesnt-obtain-ipv6-address/16759/6
It was bisected back a few
Hi Hauke,
Thanks for merging the other patch in master! Can you also merge this one
in the openwrt-18.06 branch? This will add support for the newer Mikrotik
boards in the next 18.06.X release.
Regards,
Baptiste
On 18-10-18, Baptiste Jonglez wrote:
> From: Baptiste Jonglez
>
> Newer batches
On Monday, October 22, 2018 3:48:29 PM CEST Koen Vandeputte wrote:
>
> On 20.10.18 17:46, Hauke Mehrtens wrote:
> > On 10/18/2018 02:28 PM, Koen Vandeputte wrote:
> >> starting from upstream commit 577b4eb23811 ("ubi: Reject MLC NAND")
> >> it is not allowed to use UBI and UBIFS on a MLC
On Mon, Oct 22, 2018 at 6:34 PM Rafał Miłecki wrote:
>
> On Mon, 22 Oct 2018 at 10:57, Amir Goldstein wrote:
> > On Mon, Oct 22, 2018 at 11:26 AM Richard Weinberger wrote:
> > >
> > > Am Montag, 22. Oktober 2018, 09:14:08 CEST schrieb Rafał Miłecki:
> > > > On Fri, 19 Oct 2018 at 14:31, Rafał
Can you drop the CAPS on words (not acronyms) and the _markup_?
Sent from my iPhone
> On Oct 18, 2018, at 6:28 AM, Koen Vandeputte
> wrote:
>
> starting from upstream commit 577b4eb23811 ("ubi: Reject MLC NAND")
> it is not allowed to use UBI and UBIFS on a MLC flavoured NAND flash chip. [1]
On Mon, 22 Oct 2018 at 10:57, Amir Goldstein wrote:
> On Mon, Oct 22, 2018 at 11:26 AM Richard Weinberger wrote:
> >
> > Am Montag, 22. Oktober 2018, 09:14:08 CEST schrieb Rafał Miłecki:
> > > On Fri, 19 Oct 2018 at 14:31, Rafał Miłecki wrote:
> > > > Since OpenWrt switch from kernel 4.9 to
From 3853cf0028e5721ea37da9f51c33f5ef19f67b93 Mon Sep 17 00:00:00 2001
From: tapper82
Date: Mon, 22 Oct 2018 07:57:31 +0100
Subject: Change driver version to 10.3.8.0-20181022.
Upgrade 88W8997 firmware to 8.4.0.52.
Removed unnecessary firmware settings.
Added vendor events.
Fixed crash problem when module
On 20.10.18 17:46, Hauke Mehrtens wrote:
On 10/18/2018 02:28 PM, Koen Vandeputte wrote:
starting from upstream commit 577b4eb23811 ("ubi: Reject MLC NAND")
it is not allowed to use UBI and UBIFS on a MLC flavoured NAND flash chip. [1]
According to David Oberhollenzer [2]:
The real problem
On Mon, Oct 22, 2018 at 11:26 AM Richard Weinberger wrote:
>
> Am Montag, 22. Oktober 2018, 09:14:08 CEST schrieb Rafał Miłecki:
> > On Fri, 19 Oct 2018 at 14:31, Rafał Miłecki wrote:
> > > Since OpenWrt switch from kernel 4.9 to 4.14 users started randomly
> > > reporting file system
Am Montag, 22. Oktober 2018, 09:14:08 CEST schrieb Rafał Miłecki:
> On Fri, 19 Oct 2018 at 14:31, Rafał Miłecki wrote:
> > Since OpenWrt switch from kernel 4.9 to 4.14 users started randomly
> > reporting file system corruptions. OpenWrt uses overlay(fs) with
> > squashfs as lowerdir and ubifs as
rapped
> automatically by the mailing list software.
>
>
> -- Forwarded message --
> From: tapper
> To: OpenWrt developers
> Cc:
> Bcc:
> Date: Mon, 22 Oct 2018 08:17:20 +0100
> Subject: Change mwlwifi driver version to 10.3.8.0-20181022.
>
From: tapper82
Date: Mon, 22 Oct 2018 07:57:31 +0100
Subject: [PATCH] Signed-off-by: Jonathan Lancett
Change driver version to 10.3.8.0-20181022.
Upgrade 88W8997 firmware to 8.4.0.52.
Removed unnecessary firmware settings.
Added vendor events.
Fixed crash problem when module is removed.
Modifie
On Fri, 19 Oct 2018 at 14:31, Rafał Miłecki wrote:
> Since OpenWrt switch from kernel 4.9 to 4.14 users started randomly
> reporting file system corruptions. OpenWrt uses overlay(fs) with
> squashfs as lowerdir and ubifs as upperdir. Russell managed to isolate
> & describe test case for
On Sat, 20 Oct 2018 at 08:58, Richard Weinberger wrote:
> Am Freitag, 19. Oktober 2018, 23:28:33 CEST schrieb Rafał Miłecki:
> > On Fri, 19 Oct 2018 at 16:59, Richard Weinberger wrote:
> > > Am Freitag, 19. Oktober 2018, 16:45:53 CEST schrieb Richard Weinberger:
> > > > Well, I fear it uncovers
27 matches
Mail list logo
