netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hayes Wang <hayeswang@realtek.com>
To: <dwmw2@infradead.org>, <ben@decadent.org.uk>
Cc: <romieu@fr.zoreil.com>, <netdev@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	Hayes Wang <hayeswang@realtek.com>
Subject: [PATCH firmware] rtl_nic: update firmware for RTL8168G
Date: Wed, 11 Jul 2012 20:10:03 +0800	[thread overview]
Message-ID: <1342008603-1279-1-git-send-email-hayeswang@realtek.com> (raw)
In-Reply-To: <1341878937.25597.309.camel@deadeye.wl.decadent.org.uk>

File: rtl_nic/rtl8168g-1.fw
Version: 0.0.2

Change the ocp_base of linux driver to OCP_STD_PHY_BASE after setting
firmware. The firmware would modify the ocp_base, and that results the
driver uses the wrong ocp_base to access standard phy after setting
firmware.

Signed-off-by: Hayes Wang <hayeswang@realtek.com>
---
 WHENCE                |    2 +-
 rtl_nic/rtl8168g-1.fw |  Bin 4272 -> 4272 bytes
 2 files changed, 1 insertion(+), 1 deletion(-)

diff --git a/WHENCE b/WHENCE
index 1fb7951..f46c842 100644
--- a/WHENCE
+++ b/WHENCE
@@ -1817,7 +1817,7 @@ File: rtl_nic/rtl8106e-1.fw
 Version: 0.0.1
 
 File: rtl_nic/rtl8168g-1.fw
-Version: 0.0.1
+Version: 0.0.2
 
 Licence:
  * Copyright © 2011, Realtek Semiconductor Corporation
diff --git a/rtl_nic/rtl8168g-1.fw b/rtl_nic/rtl8168g-1.fw
index dace1ea98c66de08107ee0857d8a8680d57d7898..bc03a5d28fd07d99a6cc89aa115d8ef8942629a6 100644
GIT binary patch
delta 78
zcmdm>xIs~u0SJmpax4tZEYfui;|=r-^o$e?%=HZo^$m?cl0c9E#6m0#40#iERoN}A
WOw6oI3^qo33-CB_$u|JyzyJVS1PxdK

delta 78
zcmdm>xIs~u0SJmpax4tZEYfui;|=r-^b8dY%=C>c^$m?cl0c9E#DXjg3}F*>RoTs~
Qj7)%NW2CnL4@eRQ08i5lSO5S3

-- 
1.7.10.4

  reply	other threads:[~2012-07-11 12:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-09  3:11 [PATCH firmware 1/4] rtl_nic: update firmware for RTL8168F Hayes Wang
2012-07-09  3:11 ` [PATCH firmware 2/4] rtl_nic: update firmware for RTL8411 Hayes Wang
2012-07-09 23:58   ` Ben Hutchings
2012-07-09  3:11 ` =? ?q?=5BPATCH=20firmware=203/4=5D=20rtl=5Fnic=3A=20add=20new=20firmware=20for=20RTL8106E?= Hayes Wang
2012-07-09 10:33   ` Jan Ceuleers
2012-07-10  0:08   ` [PATCH firmware 3/4] rtl_nic: add new firmware for RTL8106E Ben Hutchings
2012-07-09  3:11 ` =? ?q?=5BPATCH=20firmware=204/4=5D=20rtl=5Fnic=3A=20add=20new=20firmware=20for=20RTL8168G?= Hayes Wang
2012-07-10  0:08   ` [PATCH firmware 4/4] rtl_nic: add new firmware for RTL8168G Ben Hutchings
2012-07-11 12:10     ` Hayes Wang [this message]
2012-07-19  0:59       ` [PATCH firmware] rtl_nic: update " Ben Hutchings
2012-07-09 23:58 ` [PATCH firmware 1/4] rtl_nic: update firmware for RTL8168F Ben Hutchings
  -- strict thread matches above, loose matches on Subject: below --
2012-10-23  7:02 [PATCH firmware] rtl_nic: update firmware for RTL8168G Hayes Wang
2012-10-30 20:37 ` Ben Hutchings
2013-02-06 15:18 Hayes Wang
2013-02-18  3:28 ` Ben Hutchings

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=1342008603-1279-1-git-send-email-hayeswang@realtek.com \
    --to=hayeswang@realtek.com \
    --cc=ben@decadent.org.uk \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=romieu@fr.zoreil.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).