ath10k-firmware: QCA4019 hw1.0: Add GL.iNet GL-B1300 specific BDFs
kvalo at codeaurora.org
Thu Apr 19 07:40:24 PDT 2018
Dongming Han <workspace4hdm at gmail.com> writes:
> Tying to upstream BDFs of GL.iNet GL-B1300 to ath10k-firmware.
> This router uses two changed BDFs based on
> boardData_1_0_IPQ4019_Y9803_wifi0.bin & boardData_1_0_IPQ4019_Y9803_wifi1.bin.
> We changed BDF for target power of both BDFs and FEM control parameter
> antCtrlCommon2_G_0_0 of boardData_1_0_IPQ4019_Y9803_wifi0.
> I'm not quite sure if ath10k driver need to add these two changed BDF
> to work properly
> for this board.
> I think the ART data is made based on BDF. Maybe the antCtrlCommon logic
> and target power parameter is passed to driver by ART but not BDF?
> That way we're all happier no need to mantain these change. Please advise.
> Now to the questions from the wiki page :
> * description for what hardware this is:
> - it is a IPQ4028 based router. More information 
> * origin of the board file (did you create it yourself or where you
> - we create it. Can also be extracted from manufacturer firmware.
> * ids to be used with the board file (ATH10K_BD_IE_BOARD_NAME in ath10k)
> - bus=ahb,bmi-chip-id=0,bmi-board-id=16,variant=GL-B1300
> sha256sum: 34d5b821826aad1699666ec95df19a1767245ab424068161275a7ace947eedee
> - bus=ahb,bmi-chip-id=0,bmi-board-id=17,variant=GL-B1300
> sha256sum: d0abd802b3d04b51f4a40883157e86b1ff3a204c660d0aa3365ae8e55f625a3e
> * attach the actual board file (board.bin)
> - The name of the files are equal to the id string in the board-2.bin
> (minus the ".bin")
Added now, please check:
1 board image(s) added, 0 changed, 0 deleted, 18 in total
1 board image(s) added, 0 changed, 0 deleted, 19 in total
More information about the ath10k