Linux wireless drivers development
 help / color / mirror / Atom feed
From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: Jianhua Lu <lujianhua000@gmail.com>, <ath11k@lists.infradead.org>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: ath11k-firmware: QCA6390 hw2.0: Add bdf for Xiaomi Pad 5 Pro
Date: Mon, 21 Oct 2024 07:21:39 -0700	[thread overview]
Message-ID: <bba049d4-39f2-491b-a5e5-ebae0a77fe45@quicinc.com> (raw)
In-Reply-To: <ZwR1hu-B0bGe4zG7@localhost.localdomain>

On 10/7/2024 4:57 PM, Jianhua Lu wrote:
> Add bdf for Xiaomi Pad 5 Pro, which running mainline kernel.
> 
> * description for what hardware this is:
> 
>   - it is a SM8250 based board
>   - it use QCA6390 as wlan module
> 
> * origin of the board file (did you create it yourself or where you
>   downloaded)
> 
>   - taken from stock firmware image
> 
> * ids to be used with the board file (ATH10K_BD_IE_BOARD_NAME in ath10k)
> 
>   - QCA6390 hw2.0
> 
>     + bus=pci,qmi-chip-id=0,qmi-board-id=255,variant=Xiaomi_Pad_5Pro
>       sha256sum:
> 	  a5c99867d398b4e8773d106100e8575e1b3c29b8e18921dae50029b1253eac06
> 
> * attach the actual board file (board.bin)
> 
>   - The name of the files are equal to the id string in the board-2.bin
>     (minus the ".bin")

This has been staged:

https://git.codelinaro.org/clo/ath-firmware/ath12k-firmware/-/commit/4c8ae2fb2b78d5b0bebed63fe8b0f348f9fbc33e

BTW in the future be sure to include linux-wireless with any ath1*k board
requests so that they can be tracked in patchwork.

/jeff

       reply	other threads:[~2024-10-21 14:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ZwR1hu-B0bGe4zG7@localhost.localdomain>
2024-10-21 14:21 ` Jeff Johnson [this message]
2024-10-21 14:23   ` ath11k-firmware: QCA6390 hw2.0: Add bdf for Xiaomi Pad 5 Pro Jeff Johnson
2024-10-21 14:33     ` Jianhua Lu

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=bba049d4-39f2-491b-a5e5-ebae0a77fe45@quicinc.com \
    --to=quic_jjohnson@quicinc.com \
    --cc=ath11k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lujianhua000@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox