All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xuebing Wang <xbing6@gmail.com>
To: Michal Kazior <michal.kazior@tieto.com>, ath10k@lists.infradead.org
Cc: alanliu@qca.qualcomm.com
Subject: ath10k: is there hw3.0 firmware for qca6164 (one spatial stream)
Date: Thu, 25 Aug 2016 19:56:36 +0800	[thread overview]
Message-ID: <57BEDCF4.8050105@gmail.com> (raw)

Hi Michal,

First of all, thank you very much for your help.

1) As you are the author of adding qca6164 (one spatial stream) to 
ath10k, are you aware if there is qca6164 chip with hw3.x which requires 
hw3.x firmware?

1.1) What qca6164 wlan card did you use while you authored the support 
of qca6164?

2) From the source code in core.c, there is only hw2.1 (.id = 
QCA6174_HW_2_1_VERSION) for qca6164.
---
static const struct ath10k_hw_params ath10k_hw_params_list[] = {
     {
         .id = QCA6174_HW_2_1_VERSION,
         .dev_id = QCA6164_2_1_DEVICE_ID,
         .name = "qca6164 hw2.1",
....
     };
---

3) I checked Kalle's ath10k-firmware repository at github, there is no 
such QCA6164/ folder (one spatial stream). Does 6164 use the same 
firmware as 6174?

4) As in your commit message as below, would you please advise where can 
I get this special board.bin file?
---
     The QCA6164 needs a dedicated board.bin file which
     is different than the one used for QCA6174. If the
     board.bin is wrong the device will crash early
     while trying to boot firmware. The register dump
     will look like this:
---

Thanks again.

-- 
Xuebing

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

             reply	other threads:[~2016-08-25 11:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-25 11:56 Xuebing Wang [this message]
2016-08-29  6:57 ` ath10k: is there hw3.0 firmware for qca6164 (one spatial stream) Michal Kazior

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=57BEDCF4.8050105@gmail.com \
    --to=xbing6@gmail.com \
    --cc=alanliu@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=michal.kazior@tieto.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 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.