On 04/13/2018 03:17 PM, Matthias Schiffer wrote:
On 04/14/2018 12:05 AM, Ben Greear wrote:
On 04/13/2018 02:59 PM, Matthias Schiffer wrote:
On 03/21/2018 06:28 PM, gree...@candelatech.com wrote:
From: Ben Greear
The driver updates include:
ath10k driver backport to fix WPA 'pn' related secu
On 04/14/2018 12:05 AM, Ben Greear wrote:
> On 04/13/2018 02:59 PM, Matthias Schiffer wrote:
>> On 03/21/2018 06:28 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 drive
On 04/13/2018 03:38 AM, Mauro Mozzarelli wrote:
> I just pulled the latest from master and the build fails with the
> following:
>
> g++-uc -Os -pipe -mno-branch-likely -mips32r2 -mtune=24kc
> -fno-caller-saves -fno-plt -fhonour-copts
> -Wno-error=unused-but-set-variable -Wno-error=unused-result
On 04/13/2018 04:41 AM, Daniel Gonzalez Cabanelas wrote:
> Hi, since the adoption of the Linux kernel 4.9 there are available drivers
> for NAND flash in the brcm63xx target. However these drivers only support
> brcm NAND versions 4.0 and and up, giving support only for BCM6362 and
> BCM63268 S
On 04/13/2018 02:59 PM, Matthias Schiffer wrote:
On 03/21/2018 06:28 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
On 03/21/2018 06:28 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
Hi, since the adoption of the Linux kernel 4.9 there are available drivers for
NAND flash in the brcm63xx target. However these drivers only support brcm NAND
versions 4.0 and and up, giving support only for BCM6362 and BCM63268 SoCs
I've made a patch for including the versions present in BCM63
From: Rafał Miłecki
Commit cc63723d886fd ("overlay: use lstat rather than stat and make sure
there are no trailing spaces") changed behavior of foreachdir() breaking
some callbacks. Before that modification all callbacks were getting
directory with a trailing slash. Above commit started removing
I just pulled the latest from master and the build fails with the following:
g++-uc -Os -pipe -mno-branch-likely -mips32r2 -mtune=24kc
-fno-caller-saves -fno-plt -fhonour-copts
-Wno-error=unused-but-set-variable -Wno-error=unused-result -msoft-float
-mips16 -minterlink-mips16
-iremap/sto/rou
On 12-04-18 16:12, Antonio Silverio wrote:
> There are network setup where it would be required to turn off dhcpv4
> and have dhcpv6 (and all the address autoconfiguration) enabled
> An example is a full static ipv4 dual stack network, also an ipv4
> relayed bridge with ipv6 relay. Having the tag "
On 2018-04-13 11:34, Sven Eckelmann wrote:
> On Freitag, 13. April 2018 01:41:31 CEST Daniel Golle wrote:
>> Unlike when operating in Ad-Hoc mode, we apparently need to pass the
>> hostapd control socket interface to wpa_supplicant when using 802.11s
>> mesh mode.
>>
>> There also seems to still b
On Freitag, 13. April 2018 01:41:31 CEST Daniel Golle wrote:
> Unlike when operating in Ad-Hoc mode, we apparently need to pass the
> hostapd control socket interface to wpa_supplicant when using 802.11s
> mesh mode.
>
> There also seems to still be something wrong with the logic setting
> channel
12 matches
Mail list logo
