From: Nicolai Buchwitz <nb@tipi-net.de>
To: zjzhao@edatec.cn
Cc: hayeswang@realtek.com, andrew+netdev@lunn.ch,
linux-usb@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] r8152: add vendor/device ID for CoreChips SR9900
Date: Sat, 13 Jun 2026 16:57:54 +0200 [thread overview]
Message-ID: <588cf92dc4ca2b8199f5c80915207468@tipi-net.de> (raw)
In-Reply-To: <20260613090154.1975753-1-zjzhao@edatec.cn>
On 13.6.2026 11:01, zjzhao@edatec.cn wrote:
> From: zjzhao-eda <zjzhao@edatec.cn>
>
> The CoreChips SR9900 (0x0fe6:0x9900) is a USB 2.0 10/100
> Ethernet adapter. Testing shows it works correctly with the
> r8152 driver, reaching wire speed (94 Mbps) with zero packet
> loss on both TCP and UDP.
Do you know how they differ to the other CoreChip devices (eg.
drivers/net/usb/sr9800.c and others)?
>
> Tested on Raspberry Pi, including hotplug and extended data
> transfer.
>
> Signed-off-by: zjzhao-eda <zjzhao@edatec.cn>
> ---
> drivers/net/usb/r8152.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/usb/r8152.c b/drivers/net/usb/r8152.c
> index d61074178279..ea1733e3619c 100644
> --- a/drivers/net/usb/r8152.c
> +++ b/drivers/net/usb/r8152.c
> @@ -10062,6 +10062,7 @@ static const struct usb_device_id
> rtl8152_table[] = {
> { USB_DEVICE(VENDOR_ID_DELL, 0xb097) },
> { USB_DEVICE(VENDOR_ID_ASUS, 0x1976) },
> { USB_DEVICE(VENDOR_ID_TRENDNET, 0xe02b) },
> + { USB_DEVICE(0x0fe6, 0x9900) },
Instead of hardcoded 0x0fe6, please add a proper VENDOR_ID define in
include/linux/usb/r8152.h
> {}
> };
Thanks
Nicolai
prev parent reply other threads:[~2026-06-13 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-13 9:01 [PATCH] r8152: add vendor/device ID for CoreChips SR9900 zjzhao
2026-06-13 12:52 ` Nicolai Buchwitz
2026-06-13 14:57 ` Nicolai Buchwitz [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=588cf92dc4ca2b8199f5c80915207468@tipi-net.de \
--to=nb@tipi-net.de \
--cc=andrew+netdev@lunn.ch \
--cc=hayeswang@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=zjzhao@edatec.cn \
/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