All of lore.kernel.org
 help / color / mirror / Atom feed
From: Janghyub Seo <jhyub06@gmail.com>
To: Heiner Kallweit <hkallweit1@gmail.com>, nic_swsd@realtek.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] r8169: Add device 10ec:8162 to driver r8169
Date: Tue, 26 Oct 2021 06:47:26 +0000	[thread overview]
Message-ID: <1635230304726.3600358701.2992435442@gmail.com> (raw)
In-Reply-To: <ab517ec9-4930-474f-eb7e-34548afd5aaa@gmail.com>



On Tuesday 26 October 2021 05:27:55 AM (+09:00), Heiner Kallweit wrote:

 > On 25.10.2021 16:55, Janghyub Seo wrote:
 > >
 > > This patch makes the driver r8169 pick up device Realtek Semiconductor 
Co.
 > > , Ltd. Device [10ec:8162].
 > >
 >
 > Interesting that still new PCI ID's are assigned. Can you post the 
output
 > of dmesg | grep r8169 ? I'd be interested to know which chip version 
this is.
Yes, this is my output:
[    9.367868] libphy: r8169: probed
[    9.368507] r8169 0000:03:00.0 eth0: RTL8125B, 04:42:1a:85:c8:87, XID 
641, IRQ 71
[    9.368515] r8169 0000:03:00.0 eth0: jumbo features [frames: 9194 bytes, 
tx checksumming: ko]
[    9.802815] r8169 0000:03:00.0 enp3s0: renamed from eth0
[    9.867245] RTL8226B_RTL8221B 2.5Gbps PHY r8169-0-300:00: attached PHY 
driver (mii_bus:phy_addr=r8169-0-300:00, irq=MAC)
[   10.060719] r8169 0000:03:00.0 enp3s0: Link is Down
[   12.747165] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow 
control rx

 > What kind of system is this?

It's a laptop computer, specifically `ASUS ROG Zephyrus G15 GA503QE`.


  reply	other threads:[~2021-10-26  6:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-25 14:55 [PATCH] r8169: Add device 10ec:8162 to driver r8169 Janghyub Seo
2021-10-25 20:27 ` Heiner Kallweit
2021-10-26  6:47   ` Janghyub Seo [this message]
2021-10-26  1:01 ` Jakub Kicinski
2021-10-26  6:52   ` Janghyub Seo

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=1635230304726.3600358701.2992435442@gmail.com \
    --to=jhyub06@gmail.com \
    --cc=hkallweit1@gmail.com \
    --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 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.