linux-firmware.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@kernel.org>
To: Hayes Wang <hayeswang@realtek.com>
Cc: Linux Firmware <linux-firmware@kernel.org>,
	 Realtek linux nic maintainers <nic_swsd@realtek.com>,
	netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH linux-firmware] rtl_nic: update firmware of RTL8153C
Date: Mon, 30 Aug 2021 20:27:00 -0400	[thread overview]
Message-ID: <CA+5PVA47g24XAj7b3KiaqiG=D-mf0QH5UQ154mrEQDAbwkWZTg@mail.gmail.com> (raw)
In-Reply-To: <20210819125822.6899-380-nic_swsd@realtek.com>

Applied and pushed out.

josh

On Thu, Aug 19, 2021 at 8:59 AM Hayes Wang <hayeswang@realtek.com> wrote:
>
> - rtl8153c-1 v2 08/19/21:
>     1. Update the firmware of RTL_FW_USB.
>     2. Set bp_en_addr of RTL_FW_PLA to 0xfc48.
>
> Signed-off-by: Hayes Wang <hayeswang@realtek.com>
> ---
>  rtl_nic/rtl8153c-1.fw | Bin 816 -> 832 bytes
>  1 file changed, 0 insertions(+), 0 deletions(-)
>
> diff --git a/rtl_nic/rtl8153c-1.fw b/rtl_nic/rtl8153c-1.fw
> index 5c3d1c468e5307c588ff347b57f7d0ca719f8341..e2b5d74f8c051a8bb4eefc1d742388701b5aa015 100644
> GIT binary patch
> delta 224
> zcmdnMc7QFxq>sDKZB4b|<Az(|@`4U4KkRudH|HMLs{d=u6wf>_xLs6|V_|4&oUCi8
> zP-diHV4-hlsc&S+00&G!)(1ugh6DzNXKH^K7I^&OXVCb=!f;OER*VV98|jIO(k=|w
> z&odbr7#YSJ7#kYJ2l<$p8(KQXr{xzVr^b5(#}_1)Bxf)PJg9sy{lUx!3mz<bu;jtA
> z2P+<|da&lfx(6E`Y<jTe!M2UtB^d=A5*j=jJ(@fmI+zYI?D`-*`2wTN<X=oWf<Ol_
> UZ~%!228JI%S2TD`He~t_0AJNrX#fBK
>
> delta 205
> zcmX@Wwt+29E63&t=i_A6`yHVR7j3>jOG|o#lN`&Y>ir?+Rwn(mK}97w7KWzA$-0IL
> zWrhj{#`?yF`bLHfaKHp)Jz!*Dh+trNruK(nfyW<q28}<=4CfSX#h7qROq8|*D!6{0
> zF*MjIJ|M9qIV0XVKP5H3xGc}u*u<Qn`@g`0$_LXQ%zQBW!Q2P)A1r*Z_`%W#%O9+K
> vu=>H;2kRef+_+zoaq>GxvC01!*?`zcn1KOk8v_T#${#>08!RR}GW`bt*oI66
>
> --
> 2.31.1
>

      reply	other threads:[~2021-08-31  0:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-19 12:58 [PATCH linux-firmware] rtl_nic: update firmware of RTL8153C Hayes Wang
2021-08-31  0:27 ` Josh Boyer [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='CA+5PVA47g24XAj7b3KiaqiG=D-mf0QH5UQ154mrEQDAbwkWZTg@mail.gmail.com' \
    --to=jwboyer@kernel.org \
    --cc=hayeswang@realtek.com \
    --cc=linux-firmware@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nic_swsd@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).