ath10k.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: ath10k@lists.infradead.org
Subject: ath10k-firmware: QCA4019: hw1.0: Add Google Wifi BDFs
Date: Sat, 19 Mar 2022 19:10:33 -0700	[thread overview]
Message-ID: <YjaNGW252Ls/yDw8@localhost> (raw)

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

Hi,

OpenWrt support for Google Wifi is under review, so I'd like to push the BDFs
into the mainline board-2.bin.

Per the wiki [1]:

 * description for what hardware this is

   - IPQ4019-based router, with two QCA4019 radios -- one for 2.4GHz (BMI board
     ID 16) and one for 5GHz (BMI board ID 21)
   - The Google Wifi product (notably, this is different than the Nest Wifi)
     was originally released in 2016, with a codename "Gale". It was refreshed
     in 2020 with near-identical hardware [2], using the same OS but a new BDF
     and new codename ("Breeze"). I include both Gale and Breeze BDFs but have
     only tested the former.

 * origin of the board file (did you create it yourself or where you
   downloaded)

   - Pulled from the factory device filesystem (version R89-13729.57.27), which
     supports both the "Gale" and the (very similar) "Breeze" variants

 * ids to be used with the board file (ATH10K_BD_IE_BOARD_NAME in ath10k) +
   md5sum of each new board file to add

   - QCA4019 hw1.0

     BoardNames[0]: 'bus=ahb,bmi-chip-id=0,bmi-board-id=16,variant=GO_GALE'
     BoardMD5[0]: ea35e78c88a8571201da8b75edc9b881
     BoardNames[1]: 'bus=ahb,bmi-chip-id=0,bmi-board-id=21,variant=GO_GALE'
     BoardMD5[1]: 44cbc4ca6cb7141ba4249615f7065582
     BoardNames[2]: 'bus=ahb,bmi-chip-id=0,bmi-board-id=16,variant=GO_BREEZE'
     BoardMD5[2]: b4ac055b3ab67d5a6f5607a96af39a1f
     BoardNames[3]: 'bus=ahb,bmi-chip-id=0,bmi-board-id=21,variant=GO_BREEZE'
     BoardMD5[3]: 8b26cb285032314247304114b8ac50e7

  Variant naming scheme reflects that used by other Google projects -- using a
  GO(ogle) prefix, an underscore (_), and the project code name, all in caps.

Attached filenames match the IDs above, with a '.bin' suffix appended.

Regards,
Brian

[1] https://wireless.wiki.kernel.org/en/users/drivers/ath10k/boardfiles
[2] https://9to5google.com/2020/10/06/new-google-wifi-launch/

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

[-- Attachment #3: bus=ahb,bmi-chip-id=0,bmi-board-id=16,variant=GO_GALE.bin --]
[-- Type: application/octet-stream, Size: 12064 bytes --]

[-- Attachment #4: bus=ahb,bmi-chip-id=0,bmi-board-id=21,variant=GO_BREEZE.bin --]
[-- Type: application/octet-stream, Size: 12064 bytes --]

[-- Attachment #5: bus=ahb,bmi-chip-id=0,bmi-board-id=21,variant=GO_GALE.bin --]
[-- Type: application/octet-stream, Size: 12064 bytes --]

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

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

             reply	other threads:[~2022-03-20  2:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-20  2:10 Brian Norris [this message]
2022-04-13  9:05 ` ath10k-firmware: QCA4019: hw1.0: Add Google Wifi 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=YjaNGW252Ls/yDw8@localhost \
    --to=computersforpeace@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;
as well as URLs for NNTP newsgroup(s).