From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Ben Greear <greearb@candelatech.com>
Cc: ath10k <ath10k@lists.infradead.org>
Subject: Re: Anyone have luck with WLE900VX?
Date: Mon, 24 Feb 2014 18:17:45 +0200 [thread overview]
Message-ID: <87fvn8trh2.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <5307F7D3.1030703@candelatech.com> (Ben Greear's message of "Fri, 21 Feb 2014 17:05:23 -0800")
Ben Greear <greearb@candelatech.com> writes:
> I managed to get a few WLE900VX, and I've seen some funny things so far.
Do you have any more info what type of board it is? Is it CUS223, XBNNN
(N being a decimal) or something else?
What's the chip id?
> First, with the official firmware 10.1.467.1-1 it immediately crashes on startup.
> I don't have that firmware source, so I don't know why it crashes.
> I wasn't even trying to create more than the default wlanX station.
Is that with stock ath10k driver or does ath10k contain any custom
changes?
> With my firmware (based on 10.1.389), it boots up OK and I can create
> and associate 32 station vifs.
>
> Both NICs that I have tried so far report the same mostly bogus
> MAC: 00:03:07:12:34:56
>
> The NIC's spec sheet claims it is 3x3, but 'iw phy phyX info' shows only
> 2 streams supported for both the 2.4Ghz n band and the 5Ghz /ac band.
Hmm, I wonder if otp.bin fails. Can you check what result code you get
from otp.bin? Add something like this to ath10k_download_and_run_otp():
ret = ath10k_bmi_execute(ar, address, &exec_param);
ath10k_dbg(ATH10K_DBG_BOOT, "boot otp execute result %d\n", exec_param);
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-02-24 16:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-22 1:05 Anyone have luck with WLE900VX? Ben Greear
2014-02-22 1:47 ` Yeoh Chun-Yeow
2014-02-22 3:13 ` Adrian Chadd
2014-02-22 19:25 ` Ben Greear
2014-02-22 19:20 ` Ben Greear
2014-02-22 19:24 ` Adrian Chadd
2014-02-22 19:27 ` Ben Greear
2014-02-24 23:47 ` Ben Greear
2014-02-24 23:49 ` Adrian Chadd
2014-02-24 6:15 ` Michal Kazior
2014-02-24 16:17 ` Kalle Valo [this message]
2014-02-24 16:35 ` Ben Greear
2014-02-24 16:55 ` Ben Greear
2014-02-24 17:08 ` Kalle Valo
2014-02-24 18:00 ` Ben Greear
2014-02-24 18:35 ` Ben Greear
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=87fvn8trh2.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.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