From: Kalle Valo <kvalo@codeaurora.org>
To: Skorpy <skorpy@darmstadt.ccc.de>
Cc: ath10k@lists.infradead.org
Subject: Re: ath10k-firmware: QCA4019 hw1.0: Add ZyXEL WRE6606 specific BDFs
Date: Mon, 08 Oct 2018 15:40:26 +0300 [thread overview]
Message-ID: <87a7noehmt.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <f3c6b7e4-4e02-e341-03b0-e5fe4b7c4b8d@darmstadt.ccc.de> (skorpy@darmstadt.ccc.de's message of "Thu, 28 Jun 2018 20:45:59 +0200")
Skorpy <skorpy@darmstadt.ccc.de> writes:
> This is a set of board.bin files for the ZyXEL WRE6606 Router [0],
> 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 IPQ4018 based board [0]
> - one QCA40xx radio is used as 2.4GHz radio
> - one QCA40xx radio is used as 5GHz 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 from the factory
> - Boardfiles also included in the vendor firmware image of the NBG6617
>
> * 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=24,variant=ZyXEL-WRE6606
>
> + bus=ahb,bmi-chip-id=0,bmi-board-id=25,variant=ZyXEL-WRE6606
>
> * sha256sum of each new board file to add
> - bus=ahb,bmi-chip-id=0,bmi-board-id=24,variant=ZyXEL-WRE6606
> has sha256sum:
> 1aeae4981217b63883e20ecbab6380aff404985485bf1e881fb0fc874f2a0883
>
> - bus=ahb,bmi-chip-id=0,bmi-board-id=25,variant=ZyXEL-WRE6606
> has sha256sum:
> 469e81fd2593cba442c0d810ce92309bb92eaa42bbddbbbf4ec051fabd345ecf
>
> * 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")
>
> Kind regards,
> Magnus Frühling
>
> [0] <https://wikidevi.com/wiki/ZyXEL_WRE6606>
>
> [1] <https://wireless.wiki.kernel.org/en/users/drivers/ath10k/boardfiles>
I don't see any board files, did you forget to attach them or is it a
problem on my end?
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2018-10-08 12:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 20:06 ath10k-firmware: QCA4019 hw1.0: Add ZyXEL WRE6606 specific BDFs Skorpy
2018-06-27 15:48 ` Kalle Valo
2018-06-28 18:45 ` Skorpy
2018-10-08 12:40 ` Kalle Valo [this message]
2018-10-10 12:07 ` Kalle Valo
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=87a7noehmt.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=skorpy@darmstadt.ccc.de \
/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.