All of lore.kernel.org
 help / color / mirror / Atom feed
From: <steven.lin@senao.com>
To: ath10k@lists.infradead.org
Subject: ath10k-firmware: QCA9888 hw2.0: Add EnGenius EAP2200 specific BDFs
Date: Mon, 2 Sep 2019 08:55:22 +0000	[thread overview]
Message-ID: <77B9977A4169C341AD4CDD465CB1B812BC44E4DF@snex01.senao.com> (raw)

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

Hi,

The support for this device was added a while ago to OpenWrt. This AP requires two special BDFs to get the Wi-Fi PHYs working (correctly). The bmi-board-id='s would clash with one of the the IPQ401X AP-DK boards because QCA doesn't provide special IDs for customers and seems to use the AP-DK board-ids in the wifi firmware to change its behavior.

Now to the questions from the wiki page [1]:

*	description for what hardware this is:
-	it is a IPQ4019 based board
-	one QCA4019 radio is used as 2.4GHz radio
-	one QCA4019 radio is used as 5GHz radio
-	one QCA9888 radio is used as 5GHz radio

*	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)
-	 QCA9888 hw2.0

md5sum of each new board file to add

+ bus=pci,bmi-chip-id=0,bmi-board-id=16,variant=EnGenius-EAP2200
md5sum: 271e88642c141a58e115819de756994d

Best regards,

Steven Lin


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

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

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

             reply	other threads:[~2019-09-02  8:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-02  8:55 steven.lin [this message]
2022-01-21 14:01 ` ath10k-firmware: QCA9888 hw2.0: Add EnGenius EAP2200 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=77B9977A4169C341AD4CDD465CB1B812BC44E4DF@snex01.senao.com \
    --to=steven.lin@senao.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 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.