HP 560 Access Point WW Support (J9846A)

For Developers
1

Should be the same for the other models. I only have tested on one of my J9846A's. I'm probably going to test the other three I have soon.

Creating a new topic instead of spamming the MSM support thread.

Of note is it's the same baseboard as the MSM460/MSM466 just with an ath10k qca9890 or qca9880. (I thought it was qca9890 looking at FCC for MRLBB-1303 but lspci and iw are saying qca9880). They're both 3x3:3 802.11ac cards.

PCI layout is as follows:

0000:00:00.0 PCI bridge: Freescale Semiconductor Inc P1020E (rev 11)
0000:01:00.0 Network controller: Qualcomm Atheros QCA986x/988x 802.11ac Wireless Network Adapter
0001:02:00.0 PCI bridge: Freescale Semiconductor Inc P1020E (rev 11)
0001:03:00.0 Network controller: Qualcomm Atheros AR93xx Wireless Network Adapter (rev 01)

All that's needed is is adding kmod-ath10k-ct ath10k-board-qca9888 ath10k-firmware-qca988x-ct to your msm460 build on firmware-selector and you're good. Per the MSM thread your product ID is in colubris-bid if you want to differentiate between your different models after flashing.

Of note is you probably want to do this with a factory reset as colubris_bid might not be stable otherwise, per the MSM support thread from another user. i.e. the mac address locations change in colubris BID whilst DTS is hardcoded memory locations.

I'll eventually try to send a patch through to the mailing list.

2

qca9880 and qca9890 are basically the same, software-side, the later is just the higher quality industrial-spec variant of the former consumer variant. Differences include wider temperature ranges, stricter binning and calibration.

1 Like
3

Thanks! Of note in my patch is I also had to add compatible = "hpe,560","hpe,msm460"; as I reused the bootloader for msm460.

Unsure whether I was meant to use + DEVICE_PACKAGES := kmod-ath10k-ct ath10k-board-qca9888 ath10k-firmware-qca988x-ct or + DEVICE_PACKAGES := kmod-ath10k-ct ath10k-firmware-qca988x-ct but at least something that "works for me" is on the mailing list now =P

Also of note is that I failed to tftp boot when I added more packages. I guess it's because the initramfs gets larger than 8M? But a normal squashfs install worked fine.

edit:
Also of note is that i found wifi scans only worked on the non ct firmware. otherwise the whole whole card dies. I did some wireless performance testing and I get ~400mbit with a 2SS client down and ~600mbit up on a 2ss client on 80MHz channels on both ct and non ct firmware. So my patches had ct firmware but I'll probably be running non-ct firmware on mine.