linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arend Van Spriel <arend.vanspriel@broadcom.com>
To: yhchuang@realtek.com, jwboyer@kernel.org
Cc: linux-firmware@kernel.org, linux-wireless@vger.kernel.org,
	Larry.Finger@lwfinger.net, briannorris@chromium.org
Subject: Re: [PATCH v2 2/2] rtw88: RTL8822C: add WoW firmware v7.3
Date: Wed, 7 Aug 2019 11:33:15 +0200	[thread overview]
Message-ID: <3307e4b7-c92d-e1d2-b896-26e45fb69a9b@broadcom.com> (raw)
In-Reply-To: <1565167700-22501-2-git-send-email-yhchuang@realtek.com>



On 8/7/2019 10:48 AM, yhchuang@realtek.com wrote:
> From: Yan-Hsuan Chuang <yhchuang@realtek.com>
> 
> Add WoW firmware to support entering Wake on WirelessLAN mode
> 
> Signed-off-by: Yan-Hsuan Chuang <yhchuang@realtek.com>
> ---
> 
> v1 -> v2
>     * update WHENCE file for new added firmware
> 
>   WHENCE                    |   1 +
>   rtw88/rtw8822c_wow_fw.bin | Bin 0 -> 138720 bytes
>   2 files changed, 1 insertion(+)
>   create mode 100755 rtw88/rtw8822c_wow_fw.bin

Just wondering: Is this a good approach? What firmware should distros 
pick? Is there a trade-off affecting other wifi functionality when using 
WoW firmware?

Regards,
Arend

  reply	other threads:[~2019-08-07  9:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-07  8:48 [PATCH v2 1/2] rtw88: RTL8822C: update rtw8822c_fw.bin to v7.3 yhchuang
2019-08-07  8:48 ` [PATCH v2 2/2] rtw88: RTL8822C: add WoW firmware v7.3 yhchuang
2019-08-07  9:33   ` Arend Van Spriel [this message]
2019-08-07  9:53     ` Tony Chuang
2019-08-07 10:15       ` Arend Van Spriel
2019-08-07 16:20         ` Josh Boyer

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=3307e4b7-c92d-e1d2-b896-26e45fb69a9b@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=briannorris@chromium.org \
    --cc=jwboyer@kernel.org \
    --cc=linux-firmware@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=yhchuang@realtek.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;
as well as URLs for NNTP newsgroup(s).