All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nicolò Sprea" <nsprea@gmail.com>
To: Kalle Valo <kvalo@kernel.org>
Cc: ath10k@lists.infradead.org
Subject: Re: Firmware 4 vs Firmware 6 for QCA6174 hw3.0
Date: Wed, 8 Jun 2022 08:43:17 +0200	[thread overview]
Message-ID: <CA+BgFQV+H+YnTFhOG+d5GtWC7ZDzu8fh6S+K6wF4a5fhOP5Jmg@mail.gmail.com> (raw)
In-Reply-To: <87k09rr7bl.fsf@kernel.org>

Thanks for the answer.
Is there any feature that uses only api 6?
If I want to downgrade to api 4, is there anything that I should pay
attention to?

On Wed, Jun 8, 2022 at 8:35 AM Kalle Valo <kvalo@kernel.org> wrote:
>
> Nicolò Sprea <nsprea@gmail.com> writes:
>
> > What are the differences between firmware 4 and firmware 6 for QCA6174
> > hw3.0?
>
> They are just different firmware interface versions to maintain
> backwards compatibility:
>
> https://wireless.wiki.kernel.org/en/users/drivers/ath10k/firmware#firmware_api_versions
>
> The actual firmware versions are strings like 'WLAN.RM.4.4.1-00288-QCARMSWPZ-1'.
>
> https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/4.4.1
>
> > Is there a release note?
>
> If you are asking releases notes for firmware releases, unfortunately no.
>
> --
> https://patchwork.kernel.org/project/linux-wireless/list/
>
> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2022-06-08  6:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08  6:12 Firmware 4 vs Firmware 6 for QCA6174 hw3.0 Nicolò Sprea
2022-06-08  6:35 ` Kalle Valo
2022-06-08  6:43   ` Nicolò Sprea [this message]
2022-06-08  7:43     ` Kalle Valo
2022-06-08  9:16       ` Nicolò Sprea
2022-06-08 10:17         ` 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=CA+BgFQV+H+YnTFhOG+d5GtWC7ZDzu8fh6S+K6wF4a5fhOP5Jmg@mail.gmail.com \
    --to=nsprea@gmail.com \
    --cc=ath10k@lists.infradead.org \
    --cc=kvalo@kernel.org \
    /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.