On 12/23/19 8:57 PM, Paul Fertser wrote:
> Hi Bjørn,
>
> On Mon, Dec 23, 2019 at 10:17:11AM +0100, Bjørn Mork wrote:
>> Paul Fertser writes:
>>> --- /dev/null
>>> +++
>>> b/package/kernel/ath10k-ct/patches/960-0011-ath10k-limit-pci-buffer-size.patch
>>> @@ -0,0 +1,100 @@
>>> +--- a/ath10k-4.19/p
Hi Bjørn,
On Mon, Dec 23, 2019 at 10:17:11AM +0100, Bjørn Mork wrote:
> Paul Fertser writes:
> > --- /dev/null
> > +++
> > b/package/kernel/ath10k-ct/patches/960-0011-ath10k-limit-pci-buffer-size.patch
> > @@ -0,0 +1,100 @@
> > +--- a/ath10k-4.19/pci.c
> > b/ath10k-4.19/pci.c
> > +@@ -142,7
On 12/23/19 10:17 AM, Bjørn Mork wrote:
> Paul Fertser writes:
>
>> --- /dev/null
>> +++
>> b/package/kernel/ath10k-ct/patches/960-0011-ath10k-limit-pci-buffer-size.patch
>> @@ -0,0 +1,100 @@
>> +--- a/ath10k-4.19/pci.c
>> b/ath10k-4.19/pci.c
>> +@@ -142,7 +142,11 @@ static struct ce_attr h
Paul Fertser writes:
> --- /dev/null
> +++
> b/package/kernel/ath10k-ct/patches/960-0011-ath10k-limit-pci-buffer-size.patch
> @@ -0,0 +1,100 @@
> +--- a/ath10k-4.19/pci.c
> b/ath10k-4.19/pci.c
> +@@ -142,7 +142,11 @@ static struct ce_attr host_ce_config_wla
> + .flags = CE_ATTR_
According to many bugreports [0][1][2] the default ath10k-ct kernel
module is unusable on devices with just 64 MiB RAM or with 128 MiB and
dual ath10k cards. The target boards boot but eventually oom-killer
starts to interfere with normal operation, so the current state is
effectively broken.
Sinc
