ath10k-firmware: QCA4019 hw1.0: Add OpenMesh A42 specific BDFs

Sven Eckelmann sven.eckelmann at
Sun Jan 28 23:59:04 PST 2018

On Freitag, 26. Januar 2018 16:07:10 CET Kalle Valo wrote:
> > * bus=ahb,bmi-chip-id=0,bmi-board-id=16,variant=OM-A42
> >   - sha256sum: 
> >     10700a7ac636d57fe055e5bb4bd5f7bb3f1c282a7f25a8bb2204fc36e8c317bf
> > * bus=ahb,bmi-chip-id=0,bmi-board-id=17,variant=OM-A42
> >   - sha256sum:
> >     b3d9556894e509ac608b2e27c9169da12c63634670bb69c5ef21fb31583e7998
> I added these now:
> To make this easier I did some bigger changes in ath10k-bdencoder,
> please check carefully that I didn't break anything.

Tested it by extracting the files using the ath10k-bdencoder d278f25bc977 
(from 2017-02-10) and then calculating the sha256sum's using

    $ sha256sum bus=ahb,bmi-chip-id=0,bmi-board-id=16,variant=OM-A42.bin bus=ahb,bmi-chip-id=0,bmi-board-id=17,variant=OM-A42.bin 
    10700a7ac636d57fe055e5bb4bd5f7bb3f1c282a7f25a8bb2204fc36e8c317bf  bus=ahb,bmi-chip-id=0,bmi-board-id=16,variant=OM-A42.bin
    b3d9556894e509ac608b2e27c9169da12c63634670bb69c5ef21fb31583e7998  bus=ahb,bmi-chip-id=0,bmi-board-id=17,variant=OM-A42.bin

It was also checked that the board-2.json only had these names attached to the 
.bin files.

I did the same with my reference files and came to the same results. I am
assuming that the files must have been added correctly when the names are 
correct and the content is correct.

I have then extracted the version prior to the OM-A42 change and compared it 
to the one with OM-A42. The only difference I could find are related to the 
OM-A42. I must therefore also assume that only the relevant parts were changed 
and the other BDFs were not touched.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <>

More information about the ath10k mailing list