From: Kalle Valo <kvalo@codeaurora.org>
To: Ben Greear <greearb@candelatech.com>
Cc: ath11k@lists.infradead.org
Subject: Re: Board file for Hastings chip
Date: Wed, 16 Sep 2020 17:26:15 +0300 [thread overview]
Message-ID: <87v9gdiyrc.fsf@codeaurora.org> (raw)
In-Reply-To: <bc6d563b-9467-6a6e-adfd-ab94239a0ef0@candelatech.com> (Ben Greear's message of "Tue, 18 Aug 2020 16:53:58 -0700")
Ben Greear <greearb@candelatech.com> writes:
> After copying the firmware into place, I get a bit further, but there does not appear
> to be a board file available in ath11k-firmware repo for this chip. Anyone know
> next steps to get this working?
I know this is too late for you, but for the archives I sent
instructions few days back:
http://lists.infradead.org/pipermail/ath11k/2020-September/000320.html
--
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
prev parent reply other threads:[~2020-09-16 14:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 23:53 Board file for Hastings chip Ben Greear
2020-09-16 14:26 ` 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=87v9gdiyrc.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=greearb@candelatech.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox