All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: wi nk <wink@technolu.st>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: Mitchell Nordine <mail@mitchellnordine.com>,
	 "ath11k@lists.infradead.org" <ath11k@lists.infradead.org>
Subject: Re: Have the QCA6390 patches for XPS 9310 landed yet?
Date: Fri, 30 Jul 2021 22:08:17 +0200	[thread overview]
Message-ID: <CAHUdJJWAbwnjUgSXEwVCu7TL6byD26FxZyMN4ZaR4o1eHQypYA@mail.gmail.com> (raw)
In-Reply-To: <87y29nefm7.fsf@codeaurora.org>

On Fri, Jul 30, 2021 at 10:01 PM Kalle Valo <kvalo@codeaurora.org> wrote:
>
> Mitchell Nordine <mail@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@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.

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

  reply	other threads:[~2021-07-30 20:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18 16:30 Have the QCA6390 patches for XPS 9310 landed yet? Mitchell Nordine
2021-07-30 20:00 ` Kalle Valo
2021-07-30 20:08   ` wi nk [this message]
2021-07-30 21:52     ` Justin Mazzola Paluska
2021-07-30 21:57       ` wi nk
2021-07-30 22:11       ` Jens Gecius
2021-08-02  7:20         ` Dominik Förderer
2021-08-02 14:06     ` Kalle Valo
2021-08-04 13:06     ` Mitchell Nordine
2021-08-26 14:40       ` Kalle Valo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAHUdJJWAbwnjUgSXEwVCu7TL6byD26FxZyMN4ZaR4o1eHQypYA@mail.gmail.com \
    --to=wink@technolu.st \
    --cc=ath11k@lists.infradead.org \
    --cc=kvalo@codeaurora.org \
    --cc=mail@mitchellnordine.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.