From: Ben Greear
The driver updates include:
ath10k driver backport to fix WPA 'pn' related security bugs
(4.13 based driver only currently),
a fix for off-channel TX for CT wave-1 firmware, a likely
fix for napi related crashes, and a backport of the firmware fetch
patch.
AHB is needed for the
From: Ben Greear
They are not automatically loaded on IPQ4019 (at least) machines
for some reason.
Signed-off-by: Ben Greear
---
package/kernel/ath10k-ct/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/kernel/ath10k-ct/Makefile
b/package/kernel/ath10k-ct/M
From: Ben Greear
Initial beta release of the CT IPQ4019 firmware. Features are
similar to the CT 9984 firmware
Signed-off-by: Ben Greear
---
package/firmware/ath10k-firmware/Makefile | 74 +--
1 file changed, 71 insertions(+), 3 deletions(-)
diff --git a/package/f
On Thu, Jan 4, 2018 at 8:23 AM, Koen Vandeputte
wrote:
> By default, when the imx6 PCIe RC boots up, the subordinate is set
> equally to the secondary bus (1), and does not alter afterwards.
>
> This means that theoretically, the highest bus reachable downstream is
> bus 1.
>
> Before upstream com
On 01/19/2018 01:03 PM, Christian Lamparter wrote:
On Friday, January 19, 2018 9:12:04 PM CET gree...@candelatech.com wrote:
From: Ben Greear
This will allow us to select the CT IPQ4019 firmware instead if
desired.
Signed-off-by: Ben Greear
---
package/firmware/ipq-wifi/Makefile | 2 +-
1 f
On Friday, January 19, 2018 9:12:04 PM CET gree...@candelatech.com wrote:
> From: Ben Greear
>
> This will allow us to select the CT IPQ4019 firmware instead if
> desired.
>
> Signed-off-by: Ben Greear
> ---
> package/firmware/ipq-wifi/Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deleti
On 01/19/2018 09:12 PM, gree...@candelatech.com wrote:
> From: Ben Greear
>
> The driver updates include:
>
> ath10k driver backport to fix WPA 'pn' related security bugs
> (4.13 based driver only currently),
> a fix for off-channel TX for CT wave-1 firmware, a likely
> fix for napi related cras
From: Ben Greear
This will allow us to select the CT IPQ4019 firmware instead if
desired.
Signed-off-by: Ben Greear
---
package/firmware/ipq-wifi/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/firmware/ipq-wifi/Makefile
b/package/firmware/ipq-wifi/Makefil
From: Ben Greear
The driver updates include:
ath10k driver backport to fix WPA 'pn' related security bugs
(4.13 based driver only currently),
a fix for off-channel TX for CT wave-1 firmware, a likely
fix for napi related crashes, and a backport of the firmware fetch
patch.
AHB is needed for the
From: Ben Greear
Initial beta release of the CT IPQ4019 firmware. Features are somewhat
similar to the CT 9984 firmware, but more testing and tweaking is yet
to come.
Signed-off-by: Ben Greear
---
package/firmware/ath10k-firmware/Makefile | 33 +++
1 file changed,
From: Ben Greear
For whatever reason, mac80211 and ath modules are not automatically
loaded when ath10k-ct driver is selected.
With this change, I still see module symbols fail, but then shortly
after the modules are loaded correctly.
Signed-off-by: Ben Greear
---
package/kernel/ath10k-ct/Mak
Tested-by: Stijn Segers
Compile-tested on: x86/64.
Run-tested on: x86/64.
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
CVE-2017-15107
An interesting problem has turned up in DNSSEC validation. It turns out
that NSEC records expanded from wildcards are allowed, so a domain can
include an NSEC record for *.example.org and an actual query reply could
expand that to anything in example.org and still have it signed by
CVE-2017-15107
An interesting problem has turned up in DNSSEC validation. It turns out
that NSEC records expanded from wildcards are allowed, so a domain can
include an NSEC record for *.example.org and an actual query reply could
expand that to anything in example.org and still have it signed by
On 19 January 2018 at 05:19, Karl Palsson wrote:
>> But I would not worry about making the lives of contributors
>> easier [since they come & go]. I would worry about making the
>> lives of core devs easier, since their number is rarely
>> changing, and they have to put in the effort.
>
> An examp
Hi Etienne,
On 19.01.2018 13:09, Etienne Champetier wrote:
Hi Piotr,
2018-01-19 9:54 GMT+01:00 Piotr Dymacz :
Hi Etienne,
On 18.01.2018 22:59, Etienne Champetier wrote:
Hi All,
Could someone enable this https://github.com/integration/dco on the
whole OpenWrt github org? (or at least on the
Hello Kyson,
Thank you for your patch, I merged it into my staging tree:
https://git.openwrt.org/openwrt/staging/pepe2k.git
--
Cheers,
Piotr
On 19.01.2018 09:36, Kyson Lok wrote:
This patch include GL.iNet vendor name in the
machine name for GL.iNet vendor products.
Signed-off-by: Kyson Lok
Hello Kyson,
Thank you for your patch, I merged it into my staging tree:
https://git.openwrt.org/openwrt/staging/pepe2k.git
--
Cheers,
Piotr
On 19.01.2018 09:36, Kyson Lok wrote:
The mach name of GL AR150 and GL AR300 is inconsistent
with other products.
Signed-off-by: Kyson Lok
---
target
Hi Piotr,
2018-01-19 9:54 GMT+01:00 Piotr Dymacz :
> Hi Etienne,
>
> On 18.01.2018 22:59, Etienne Champetier wrote:
>>
>> Hi All,
>>
>> Could someone enable this https://github.com/integration/dco on the
>> whole OpenWrt github org? (or at least on the packages repo)
>
>
> I think that packages re
Hi Zoltan,
I told you on IRC I'd check on an APU2, but that's in production on a
remote site so if it goes belly up people won't be happy. So when you
mentioned Ryzen on the mailing list here I figured I could as well do
it on my desktop ;-).
Dmesg excerpts below. I added the 17h microcode f
If a device only supports the 2nd verification method (uim),
the first method will fail as expected reporting an error:
"Command not supported"
Silence both separate methods and only report an error regarding
pin verification if both fail.
Signed-off-by: Koen Vandeputte
---
package/network/uti
> But I would not worry about making the lives of contributors
> easier [since they come & go]. I would worry about making the
> lives of core devs easier, since their number is rarely
> changing, and they have to put in the effort.
An example of wording you may wish to re-examine. This is exactly
>
> I started working on a script, here is how it works. its pretty
> much the same for patchwork and github with the difference that
> on github we write comments and patchwork we send mails. after
> 90 days we send a note saying "it stalled pleases remind folks
> and help get it merged" after 12
*cough*
https://patchwork.ozlabs.org/patch/830136/
It’s you, not me ;-)
Cheers,
Kevin D-B
012C ACB2 28C6 C53E 9775 9123 B3A2 389B 9DE2 334A
signature.asc
Description: Message signed with OpenPGP
___
Lede-dev mailing list
Lede-dev@lists.infradead.o
Hi Etienne,
On 18.01.2018 22:59, Etienne Champetier wrote:
Hi All,
Could someone enable this https://github.com/integration/dco on the
whole OpenWrt github org? (or at least on the packages repo)
I think that packages repository already uses Travis CI which checks for
such thing like a missi
The mach name of GL AR150 and GL AR300 is inconsistent
with other products.
Signed-off-by: Kyson Lok
---
target/linux/ar71xx/base-files/lib/ar71xx.sh | 4 ++--
target/linux/ar71xx/files/arch/mips/ath79/mach-gl-ar150.c | 2 +-
target/linux/ar71xx/files/arch/mips/ath79/mach-gl-ar300.c
This patch include GL.iNet vendor name in the
machine name for GL.iNet vendor products.
Signed-off-by: Kyson Lok
---
target/linux/ar71xx/files/arch/mips/ath79/mach-gl-ar150.c | 2 +-
target/linux/ar71xx/files/arch/mips/ath79/mach-gl-ar300.c | 2 +-
target/linux/ar71xx/files/arch/mips/ath79/mac
Hi Val,
On 19.01.2018 02:02, Val Kulkov wrote:
On 18 January 2018 at 19:49, Alberto Bursi wrote:
On 01/19/2018 01:05 AM, Val Kulkov wrote:
There is more than a handful of PRs currently bit-rotting in
openwrt/packages that are ready for merging, with all requested
changes in place since ma
On Fri, Jan 19, 2018 at 10:09 AM, John Crispin wrote:
>
>
> On 19/01/18 08:55, Alexandru Ardelean wrote:
>>
>> On Fri, Jan 19, 2018 at 3:02 AM, Val Kulkov wrote:
>>>
>>> On 18 January 2018 at 19:49, Alberto Bursi
>>> wrote:
On 01/19/2018 01:05 AM, Val Kulkov wrote:
>
On 19/01/18 08:55, Alexandru Ardelean wrote:
On Fri, Jan 19, 2018 at 3:02 AM, Val Kulkov wrote:
On 18 January 2018 at 19:49, Alberto Bursi wrote:
On 01/19/2018 01:05 AM, Val Kulkov wrote:
There is more than a handful of PRs currently bit-rotting in
openwrt/packages that are ready for mer
30 matches
Mail list logo
