Abhishek Kumar writes:
> Board data files wrapped inside board-2.bin files are
> identified based on a combination of bus architecture,
> chip-id, board-id or variants. Here is one such example
> of a BDF entry in board-2.bin file:
> bus=snoc,qmi-board-id=67,qmi-chip-id=320,variant=GO_
> It i
Kalle Valo writes:
>> static int ath10k_core_fetch_board_data_api_n(struct ath10k *ar,
>>const char *boardname,
>> - const char *fallback_boardname1,
>> - const char *fal
Abhishek Kumar writes:
> Board data files wrapped inside board-2.bin files are
> identified based on a combination of bus architecture,
> chip-id, board-id or variants. Here is one such example
> of a BDF entry in board-2.bin file:
> bus=snoc,qmi-board-id=67,qmi-chip-id=320,variant=GO_
> It i
Replying again ...
Thanks for the review Jeff, I have replied below and will address
these comments in next iteration. I will wait for a day more to get
some more reviews and collectively make the change.
On Mon, May 9, 2022 at 10:22 AM Jeff Johnson wrote:
>
> On 5/8/2022 7:26 PM, Abhishek Kumar
On 5/8/2022 7:26 PM, Abhishek Kumar wrote:
Board data files wrapped inside board-2.bin files are
identified based on a combination of bus architecture,
chip-id, board-id or variants. Here is one such example
of a BDF entry in board-2.bin file:
bus=snoc,qmi-board-id=67,qmi-chip-id=320,variant=GO_X
