We are using a QCA9377 based device (8devices Redbean) with the ath10k
over SDIO together with kernel 5.10. It works well. We also use qcacld
for regulative testing purpose. All our patches are mainlined.
Am 04.09.2023 16:28 schrieb Bastian Krause:
Hi Lukas and everybody else,
On 6/13/23
Hi Lukas and everybody else,
On 6/13/23 17:35, Lukas F. Hartmann wrote:
Gary Bisson writes:
Trying significantly older ath10k from an older kernel is something to
try in case there are recent regressions in ath10k.
I don't have an ath10k SDIO device myself so I don't know the state of
SDIO
Hi Gary & Kalle,
Gary Bisson writes:
>> Trying significantly older ath10k from an older kernel is something to
>> try in case there are recent regressions in ath10k.
>>
>> I don't have an ath10k SDIO device myself so I don't know the state of
>> SDIO support in ath10k. Does anyone else from
Hi Lukas & Kalle,
On Tue, Jun 13, 2023 at 11:05:14AM +0300, Kalle Valo wrote:
>
> EXTERNAL EMAIL: Be careful with attachments and links.
>
> "Lukas F. Hartmann" writes:
>
> > I'm trying to get the QCA9377 SDIO module on Boundary Devices'
> > i.MX8MPlus SOM working with the ath10k mainline
"Lukas F. Hartmann" writes:
> I'm trying to get the QCA9377 SDIO module on Boundary Devices'
> i.MX8MPlus SOM working with the ath10k mainline driver (from Linux git
> tip). Currently it can scan and see some APs and authenticate, but not
> associate (timeout). Several months ago I thought this
