All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: jloretto70 <jloretto70@proton.me>
Cc: "ath11k\@lists.infradead.org" <ath11k@lists.infradead.org>
Subject: Re: Question about WCN6855 firmware versions
Date: Tue, 11 Oct 2022 10:57:09 +0300	[thread overview]
Message-ID: <87y1tmokru.fsf@kernel.org> (raw)
In-Reply-To: <ozkZDmxXw0zoF9CbOu2CoxEILU4fpAb8udwK4yw-Jgwc1z7zvIZD91zIK0rxq-8vri3WDPztrozKOgZvm4-SLnBvOJoVmg_qr3s47YeckL4=@proton.me> (jloretto's message of "Tue, 04 Oct 2022 17:06:56 +0000")

jloretto70 <jloretto70@proton.me> writes:

> I have a WCN6855 (hw2.1) card and am currently using the latest
> firmware files from the kernel.org repo which are labeled 3.6510.9 in
> the commit message. I see that there is a more recent set of files
> labeled 3.6510.16 in the GitHub repo for this card. Are these firmware
> files safe to use or is the best practice to wait until they land in
> the official kernel.org repo?

For the end users I recommend using the ath11k firmware files from the
official linux-firmware unless you have a specific reason to update
(reporting a bug etc). That way there's more testing by the developers
before you get access to it.

I try update latest ath11k-firmware releases to linux-firmware roughly
every three months, so it really comes down to if you want run bleeding
edge or not.

-- 
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

  reply	other threads:[~2022-10-11  7:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-04 17:06 Question about WCN6855 firmware versions jloretto70
2022-10-11  7:57 ` Kalle Valo [this message]
2022-10-11 23:26   ` jloretto70

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=87y1tmokru.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath11k@lists.infradead.org \
    --cc=jloretto70@proton.me \
    /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.