Have the QCA6390 patches for XPS 9310 landed yet?

[wi nk]

On Fri, Jul 30, 2021 at 11:52 PM Justin Mazzola Paluska
<jmp at justinmp.com> wrote:
>
> On 7/30/21 4:08 PM, wi nk wrote:
> > On Fri, Jul 30, 2021 at 10:01 PM Kalle Valo <kvalo at codeaurora.org> wrote:
> >> Mitchell Nordine <mail at mitchellnordine.com> writes:
> >>
> >>> Hi kvalo and wink!
> >>>
> >>> It's been a while since I've had a chance to check in on this - have I
> >>> missed any QCA6390 progress?
> >>>
> >>> Currently the nixos-hardware repo is fixed to 5.10.18 along with most
> >>> of the patches on ath11k-qca6390-bringup, apart from two commits that
> >>> I'm sure were merged a while ago.
> >>>
> >>> https://github.com/NixOS/nixos-hardware/blob/31f61b90ddb9257b94888ee17ccf96236e180c76/dell/xps/13-9310/default.nix#L14
> >>>
> >>> Just wondering if the rest of the patches or some alternative fixes
> >>> have landed in a more recent version of the kernel yet, and whether
> >>> it's worth diving in and updating our nix expr yet?
> >> Basically all you need is a BIOS update for XPS 9310 (to get 32 MSI
> >> vectors working) and a recent Linux release. I don't remember the exact
> >> kernel release, and can't check it now, but something like v5.12 or
> >> v5.13 should work without extra patches.
> >>
> >> --
> >> https://patchwork.kernel.org/project/linux-wireless/list/
> >>
> >> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
> >>
> >> --
> >> ath11k mailing list
> >> ath11k at lists.infradead.org
> >> http://lists.infradead.org/mailman/listinfo/ath11k
> >
> > Hey Mitchell!
> >
> >    Just to add a little, Dell released a BIOS update that now allows
> > the driver to obtain all 32 MSI vectors (I posted around the time that
> > happened if you need the earliest version, otherwise just grab the
> > latest version).  I've been running 5.12 and 5.13 without WIFI issues.
> > Occasionally I still have bluetooth problems and the i915 drivers are
> > causing video artifacts randomly, but the wireless connection seems
> > pretty solid at this point.
>
> Which BIOS do you have?  I have 1.2.5.
>
> I'm currently running 5.13 with a patch that reverted
> 3579994476b65cb5e272ff0f720a1fd31322e53f.  I needed to do that or the
> 5.13 kernel wouldn't connect to my access point because the firmware
> crashed.  (I got that pointer from
> https://bugzilla.kernel.org/show_bug.cgi?id=212059.)  With 357999
> reverted, everything works well.
>
> I still have the memmap=20M$12M kernel argument set from the old qca
> bringup branch days.  Do you also use that?
>       --Justin

Interesting, I guess my AP / configuration doesn't aggravate that
issue...I also do not have to remap/reserve any memory
addresses...Everything from my side is basically off the shelf at this
point, even though the original smell of 32 vectors lingers...I will
be travelling for the first time in a while soon, I may very well bump
into this AP issue, I'll let you know...