From: Hayes Wang <hayeswang@realtek.com>
To: Kai Heng Feng <kai.heng.feng@canonical.com>,
"Mario.Limonciello@dell.com" <Mario.Limonciello@dell.com>
Cc: David Miller <davem@davemloft.net>,
Jakub Kicinski <jakub.kicinski@netronome.com>,
"pmalani@chromium.org" <pmalani@chromium.org>,
"grundler@chromium.org" <grundler@chromium.org>,
"<David.Chen7@dell.com>" <David.Chen7@Dell.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] r8152: Add MAC passthrough support to new device
Date: Wed, 15 Jan 2020 07:04:03 +0000 [thread overview]
Message-ID: <2eddafe6b9694a288013c3af41321ce5@realtek.com> (raw)
In-Reply-To: <430A264A-27E0-489D-B7B1-8E78AAD528D7@canonical.com>
Kai Heng Feng [mailto:kai.heng.feng@canonical.com]
> Sent: Wednesday, January 15, 2020 2:40 PM
[...]
> >> Device 0xa387 also supports MAC passthrough, therefore add it to the
> >> whitelst.
> >
> > Have you confirmed whether this product ID is unique to the products that
> > support this feature or if it's also re-used in other products?
>
> This is unique for Lenovo product.
>
> >
> > For Dell's devices there are very specific tests that make sure that this
> > feature only applies on the products it is supposed to and nothing else
> > (For example RTL8153-AD checks variant as well as effuse value)
> > (Example two: RTL8153-BND is a Dell only part).
>
> Hayes, do you know how macpassthru on Lenovo dock works?
I don't sure about it.
The Dell's devices use the VID/PID of Realtek, so they have another way
to check which devices support macpassthru.
The Lenovo use their VID/PID, so I guess they only check VID/PID.
Best Regards,
Hayes
next prev parent reply other threads:[~2020-01-15 7:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 4:41 [PATCH] r8152: Add MAC passthrough support to new device Kai-Heng Feng
2020-01-14 7:51 ` Prashant Malani
2020-01-14 8:03 ` Kai-Heng Feng
2020-01-14 8:23 ` Oliver Neukum
2020-01-14 9:22 ` Kai-Heng Feng
2020-01-14 20:33 ` Mario.Limonciello
2020-01-15 6:40 ` Kai Heng Feng
2020-01-15 7:04 ` Hayes Wang [this message]
2020-01-15 6:19 ` Hayes Wang
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=2eddafe6b9694a288013c3af41321ce5@realtek.com \
--to=hayeswang@realtek.com \
--cc=David.Chen7@Dell.com \
--cc=Mario.Limonciello@dell.com \
--cc=davem@davemloft.net \
--cc=grundler@chromium.org \
--cc=jakub.kicinski@netronome.com \
--cc=kai.heng.feng@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pmalani@chromium.org \
/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).