All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RESEND PATCH 2/2] net: rtl8169: Support RTL-8168h/8111h
Date: Tue, 16 Apr 2019 18:20:30 +0200	[thread overview]
Message-ID: <20190416162030.13590-2-thierry.reding@gmail.com> (raw)
In-Reply-To: <20190416162030.13590-1-thierry.reding@gmail.com>

From: Thierry Reding <treding@nvidia.com>

This version of the RTL-8168 is present on some development boards and
is compatible with this driver. Add support for identifying this version
of the chip so that U-Boot won't complain about it being unknown.

Signed-off-by: Thierry Reding <treding@nvidia.com>
---
 drivers/net/rtl8169.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/net/rtl8169.c b/drivers/net/rtl8169.c
index 27e27b34176b..bc052e72564b 100644
--- a/drivers/net/rtl8169.c
+++ b/drivers/net/rtl8169.c
@@ -257,6 +257,7 @@ static struct {
 	{"RTL-8168/8111g",	0x4c, 0xff7e1880,},
 	{"RTL-8101e",		0x34, 0xff7e1880,},
 	{"RTL-8100e",		0x32, 0xff7e1880,},
+	{"RTL-8168h/8111h",	0x54, 0xff7e1880,},
 };
 
 enum _DescStatusBit {
-- 
2.21.0

  reply	other threads:[~2019-04-16 16:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-16 16:20 [U-Boot] [RESEND PATCH 1/2] net: rtl8169: Implement ->hwaddr_write() callback Thierry Reding
2019-04-16 16:20 ` Thierry Reding [this message]
2019-04-16 16:36   ` [U-Boot] [RESEND PATCH 2/2] net: rtl8169: Support RTL-8168h/8111h Joe Hershberger
2019-05-14 20:03   ` [U-Boot] " Joe Hershberger
2019-04-16 16:36 ` [U-Boot] [RESEND PATCH 1/2] net: rtl8169: Implement ->hwaddr_write() callback Joe Hershberger
2019-04-25 13:31   ` Thierry Reding
2019-04-25 13:47     ` Joe Hershberger
2019-05-09 21:15     ` Joe Hershberger
2019-05-14 20:03 ` [U-Boot] " Joe Hershberger

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=20190416162030.13590-2-thierry.reding@gmail.com \
    --to=thierry.reding@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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.