ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Lamparter <chunkeey@gmail.com>
To: ath10k@lists.infradead.org
Cc: gowhdok@mailfence.com
Subject: [V2] ath10k-firmware: QCA4019 hw1.0: Add P&W R619AC specific BDFs
Date: Fri, 1 Jul 2022 13:25:38 +0200	[thread overview]
Message-ID: <2d06065e-a7c9-bd6d-cc95-52e350fd413a@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 804 bytes --]

From: Tim Davis <gowhdok@mailfence.com>

Hello,
This is the board files for P&W R619ac, a dual-band wireless router with an IPQ4019 inside.

The boardfiles are extracted from the stock firmware:
/lib/firmware/IPQ4019/hw.1/boarddata_0.bin
/lib/firmware/IPQ4019/hw.1/boarddata_1.bin

The MD5 hashes are consistent with the ones included in the pull request.

ids to be used with the board file (ATH10K_BD_IE_BOARD_NAME in ath10k):
    - QCA4019 hw1.0
	BoardNames[0]: 'bus=ahb,bmi-chip-id=0,bmi-board-id=16,variant=P&W-R619AC'
	BoardMD5[0]: 05f6d61550d5ba8a0626fb7fa63703fe

	BoardNames[1]: 'bus=ahb,bmi-chip-id=0,bmi-board-id=17,variant=P&W-R619AC'
	BoardMD5[1]: 9265da348a1294c326cd0156fd92d0b5

Boardfiles are attached with the appropriate names.

Thanks,
Tim Davis

-- 
v2: removed space in variant name

[-- Attachment #2: bus=ahb,bmi-chip-id=0,bmi-board-id=16,variant=P&W-R619AC.bin --]
[-- Type: application/octet-stream, Size: 12064 bytes --]

[-- Attachment #3: bus=ahb,bmi-chip-id=0,bmi-board-id=17,variant=P&W-R619AC.bin --]
[-- Type: application/octet-stream, Size: 12064 bytes --]

[-- Attachment #4: Type: text/plain, Size: 146 bytes --]

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

             reply	other threads:[~2022-07-01 11:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-01 11:25 Christian Lamparter [this message]
2023-03-17 11:36 ` [V2] ath10k-firmware: QCA4019 hw1.0: Add P&W R619AC specific BDFs 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=2d06065e-a7c9-bd6d-cc95-52e350fd413a@gmail.com \
    --to=chunkeey@gmail.com \
    --cc=ath10k@lists.infradead.org \
    --cc=gowhdok@mailfence.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