wifi: ath11k: ipq6018 monitor mode is not working properly

[Kalle Valo]

Robert Marko <robert.marko at sartura.hr> writes:

> On Wed, Dec 7, 2022 at 2:13 PM Kalle Valo <kvalo at kernel.org> wrote:
>> Robert Marko <robert.marko at sartura.hr> writes:
>>
>> > The issue with mainline kernels is that there is no remoteproc support
>> > for IPQ8074 nor IPQ6018, I have been working towards getting the
>> > IPQ8074 and its working with remoteproc patches added but the
>> > situation is not ideal as for example coldboot calibration does not
>> > work which could be a bug in the remoteproc patches I am using.
>>
>> Nice, do you have the patches available somewhere? What distro are you
>> using?
>
> Yes, they are available on my GitHub kernel repo under the
> ipq807x-next branches:
> https://github.com/robimarko/linux.git

Thanks, I will take a look.

> I am testing the next based branches with Buildroot as its quick and
> easy as I regularly update on newer next as I am upstreaming and stuff
> is getting merged. A lot of stuff got merged so the SoC is in a way,
> way better shape than a year or two ago but we are still missing
> upstream remoteproc support as well as CPR support and there is no
> offloading obviously.

Great that you brought this up. I have been thinking how could I do easy
and quickly do some smoke testing on IPQ8074 using latest ath11k from my
ath.git master branch and latest firmware from ath11k-firmware.git.
Currently I'm only testing PCI devices, so quite limited testing.

What you are using sounds like just what I would need as well :) Would
you happen to have any notes, pointers etc how to get started with that?
Unfortunately I can't use much time for this, so the simpler the
instructions are the better. I haven't used Buildroot for years.

> I am also maintaining an OpenWrt ipq807x target that is based on 5.15
> and 6.1 backports for which I plan to make a PR to get it officially
> included once 6.1 backports are merged. This is what a lot of users
> are currently using as it's gotten into quite a good state.

Excellent, looking forward to that.

> The one thing that has been bothering is move to FW 2.7 which is not
> working on a number of routers as their BDF-s were generated for way
> older BDF as well as outdated regulatory information.

The board files are always a major problem. But can you tell more about
this? Are you saying that firmware branches 2.5.0.1 [1] and 2.7.0.1 [2]
are using different board file formats?

[1] https://github.com/kvalo/ath11k-firmware/tree/master/IPQ8074/hw2.0/2.5.0.1

[2] https://github.com/kvalo/ath11k-firmware/tree/master/IPQ8074/hw2.0/2.7.0.1

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches