From: Stanislaw Gruszka <sgruszka-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Lorenzo Bianconi
<lorenzo.bianconi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org,
linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-firmware-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
nbd-Vt+b4OUoWG0@public.gmane.org
Subject: Re: [PATCH v2] linux-firmware: add firmware for mt76x2u
Date: Mon, 30 Jul 2018 14:16:20 +0200 [thread overview]
Message-ID: <20180730121618.GA1993@redhat.com> (raw)
In-Reply-To: <20180728103857.1458-1-lorenzo.bianconi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On Sat, Jul 28, 2018 at 12:38:57PM +0200, Lorenzo Bianconi wrote:
> Add binary firmware for MT76x2u based devices
>
> Signed-off-by: Lorenzo Bianconi <lorenzo.bianconi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> ---
> Changes since v1:
> - move bin files in mediatek folder
> - use LICENCE.mediatek as licence file
> ---
> WHENCE | 12 ++++++++++++
> mediatek/mt7662u.bin | Bin 0 -> 91412 bytes
> mediatek/mt7662u_rom_patch.bin | Bin 0 -> 20686 bytes
Seems this location will also require change in the driver
to look into mediatek subdirectory for the firmware.
Stanislaw
next prev parent reply other threads:[~2018-07-30 12:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-28 10:38 [PATCH v2] linux-firmware: add firmware for mt76x2u Lorenzo Bianconi
[not found] ` <20180728103857.1458-1-lorenzo.bianconi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-07-30 11:21 ` Josh Boyer
2018-07-30 12:16 ` Stanislaw Gruszka [this message]
[not found] ` <20180730121618.GA1993-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-07-30 12:19 ` Lorenzo Bianconi
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=20180730121618.GA1993@redhat.com \
--to=sgruszka-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=linux-firmware-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=lorenzo.bianconi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=nbd-Vt+b4OUoWG0@public.gmane.org \
--cc=sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
/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.