From: Christian Marangi <ansuelsmth@gmail.com>
To: ath10k@lists.infradead.org
Subject: ath10k-firmware: QCA4019 hw1.0: Add Aruba AP-365
Date: Thu, 30 Jun 2022 01:54:16 +0200 [thread overview]
Message-ID: <62bce629.1c69fb81.2a90e.6915@mx.google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 972 bytes --]
Hi, we have many board file not pused upstream in openwrt. The intention
is to fix this and have all of them merged.
* description for what hardware this is:
- it is a IPQ4019 based board
- one QCA40xx radio is used as 2.4GHz radio
- one QCA40xx radio is used as 5GHz radio
* origin of the board file (did you create it yourself or where you
downloaded)
- extracted from the original stock firmware image
* ids to be used with the board file (ATH10K_BD_IE_BOARD_NAME in ath10k)
- QCA4019 hw1.0
+ bus=ahb,bmi-chip-id=0,bmi-board-id=20,variant=Aruba-AP-365
sha256sum:
a7fd4b262a3aa7bb1ae57bc442cc1e4bd0eb56c1883bd60d19178cfa1e099f44
+ bus=ahb,bmi-chip-id=0,bmi-board-id=21,variant=Aruba-AP-365
sha256sum:
63a8000380ad07689a091528f20f1a24465d08ba9540403a844f9ad6e203a298
* 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")
--
Ansuel
[-- Attachment #2: bus=ahb,bmi-chip-id=0,bmi-board-id=20,variant=Aruba-AP-365.bin --]
[-- Type: application/octet-stream, Size: 12064 bytes --]
[-- Attachment #3: bus=ahb,bmi-chip-id=0,bmi-board-id=21,variant=Aruba-AP-365.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
next reply other threads:[~2022-06-29 23:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 23:54 Christian Marangi [this message]
2023-03-17 11:31 ` ath10k-firmware: QCA4019 hw1.0: Add Aruba AP-365 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=62bce629.1c69fb81.2a90e.6915@mx.google.com \
--to=ansuelsmth@gmail.com \
--cc=ath10k@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox