All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: David Bauer <mail@david-bauer.net>
Cc: ath10k@lists.infradead.org
Subject: Re: ath10k-firmware: QCA4019 hw1.0: Add Aruba AP-303 specific BDFs
Date: Fri, 21 Jan 2022 15:34:46 +0200	[thread overview]
Message-ID: <87a6fpdxft.fsf@kernel.org> (raw)
In-Reply-To: <8d42b55b-b4d4-5156-dc85-524b8cabd29d@david-bauer.net> (David Bauer's message of "Fri, 3 Apr 2020 02:14:54 +0200")

David Bauer <mail@david-bauer.net> writes:

> this is a set of board.bin files for the Aruba AP-303,
> which I wish to be added to the ath10k-firmware repository.
>
> As per the current "Submitting board files" guidelines [1]:
>
> * description for what hardware this is:
>   - it is a IPQ4029 based board
>     - one QCA40xx radio is used as 2.4 GHz radio
>     - one QCA40xx radio is used as 5 GHz radio
>
> * origin of the board file (did you create it yourself or where you
>   downloaded)
>   - all files were extracted from official vendor firmware which was on
> the device
>
> * ids to be used with the board file (ATH10K_BD_IE_BOARD_NAME in ath10k)
>   - qca4019 hw1.0
>     + bus=ahb,bmi-chip-id=0,bmi-board-id=20,variant=Aruba-AP-303
>     + bus=ahb,bmi-chip-id=0,bmi-board-id=21,variant=Aruba-AP-303
> * sha256sum of each new board file to add
>   - bus=ahb,bmi-chip-id=0,bmi-board-id=20,variant=Aruba-AP-303.bin
>     - deeeee5b1408681c68699d068eea297aa970a64fef4f04ad4fc30413e186d67f
>   - bus=ahb,bmi-chip-id=0,bmi-board-id=21,variant=Aruba-AP-303.bin
>     - b636eb18ed7c2df6a6f2567009bf95c7c2252feea146b4f05d8757514fe1d6e1
>
> * 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")

Thanks, added to QCA4019/hw1.0/board-2.bin:

New:
bus=ahb,bmi-chip-id=0,bmi-board-id=21,variant=Aruba-AP-303
bus=ahb,bmi-chip-id=0,bmi-board-id=20,variant=Aruba-AP-303

Changed:


Deleted:

2 board image(s) added, 0 changed, 0 deleted, 73 in total

https://github.com/kvalo/ath10k-firmware/commit/46a4f4a7165fc0ed51abfa70fb3713791c394026

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

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

      reply	other threads:[~2022-01-21 13:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-03  0:14 ath10k-firmware: QCA4019 hw1.0: Add Aruba AP-303 specific BDFs David Bauer
2022-01-21 13:34 ` Kalle Valo [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a6fpdxft.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath10k@lists.infradead.org \
    --cc=mail@david-bauer.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.