Re: Anyone have luck with WLE900VX?

[Kalle Valo <kvalo@qca.qualcomm.com>]

Ben Greear <greearb@candelatech.com> writes:

> On 02/24/2014 08:17 AM, Kalle Valo wrote:
>> 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?
>
> http://www.compex.com.sg/Datasheets/WLE900VX_Dsv1.0.0.pdf
>
> I was told the ref design, but cannot remember it..will ask
> again.  It is not a high power design like the CUS223, evidently.

No need to ask, the PDF even mentions it:

"Qualcomm-Atheros QCA9880 Version 2, XB140 Reference Design"

XB140 is a dual band 3x3 board.

>> What's the chip id?
>
> 05:00.0 Network controller: Atheros Communications Inc. Device 003c
> 	Flags: bus master, fast devsel, latency 0, IRQ 18
> 	Memory at f4400000 (64-bit, non-prefetchable) [size=2M]
> 	Expansion ROM at f4600000 [disabled] [size=64K]
> 	Capabilities: [40] Power Management version 2
> 	Capabilities: [50] MSI: Enable- Count=1/8 Maskable+ 64bit-
> 	Capabilities: [70] Express Endpoint, MSI 00
> 	Capabilities: [100] Advanced Error Reporting
> 	Capabilities: [140] Virtual Channel
> 	Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00
> 	Kernel driver in use: ath10k_pci

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);

-- 
Kalle Valo

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