From: Ben Greear <greearb@candelatech.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: ath10k <ath10k@lists.infradead.org>
Subject: Re: Anyone have luck with WLE900VX?
Date: Mon, 24 Feb 2014 10:00:26 -0800 [thread overview]
Message-ID: <530B88BA.1020602@candelatech.com> (raw)
In-Reply-To: <87txbosakq.fsf@kamboji.qca.qualcomm.com>
On 02/24/2014 09:08 AM, Kalle Valo wrote:
> I was actually referring to the internal chip id, not PCI id, which is a
> good way to check what chip it really is:
>
> static int ath10k_core_check_chip_id(struct ath10k *ar)
> {
> u32 hw_revision = MS(ar->chip_id, SOC_CHIP_ID_REV);
>
> ath10k_dbg(ATH10K_DBG_BOOT, "boot chip_id 0x%08x hw_revision 0x%x\n",
> ar->chip_id, hw_revision);
>
Ahh, like this?
ath10k: boot chip_id 0x043202ff hw_revision 0x2
I do not see any OTP errors when loading my firmware, at least not
as seen from the ath10k driver.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-02-24 18:00 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
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 [this message]
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=530B88BA.1020602@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.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.