From: Aaron Ma <aaron.ma@canonical.com>
To: Hayes Wang <hayeswang@realtek.com>,
"Limonciello, Mario" <Mario.Limonciello@amd.com>,
Henning Schild <henning.schild@siemens.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
Kai-Heng Feng <kai.heng.feng@canonical.com>,
Andrew Lunn <andrew@lunn.ch>, Oliver Neukum <oneukum@suse.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"tiwai@suse.de" <tiwai@suse.de>
Subject: Re: [PATCH 1/3 v3] net: usb: r8152: Check used MAC passthrough address
Date: Thu, 27 Jan 2022 16:13:24 +0800 [thread overview]
Message-ID: <e52f8155-61a8-0cea-b96c-a05b83cdfff9@canonical.com> (raw)
In-Reply-To: <5b94f064bd5c48589ea856f68ac0e930@realtek.com>
On 1/27/22 16:06, Hayes Wang wrote:
> I don't think the feature of MAC passthrough address is maintained
> by Realtek. Especially, there is no uniform way about it. The
> different companies have to maintain their own ways by themselves.
>
> Realtek could provide the method of finding out the specific device
> for Lenovo. You could check USB OCP 0xD81F bit 3. For example,
>
> ocp_data = ocp_read_byte(tp, MCU_TYPE_USB, USB_MISC_1);
> if (tp->version == RTL_VER_09 && (ocp_data & BIT(3))) {
> /* This is the RTL8153B for Lenovo. */
> }
>
May I use the code from Realtek Outbox driver to implement the MAPT?
If so, allow me to write a patch and send here to review.
Thanks,
Aaron
> Best Regards,
> Hayes
next prev parent reply other threads:[~2022-01-27 8:13 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 15:14 [PATCH 1/3 v3] net: usb: r8152: Check used MAC passthrough address Aaron Ma
2022-01-05 15:14 ` [PATCH 2/3] net: usb: r8152: Set probe mode to sync Aaron Ma
2022-01-05 15:33 ` Greg KH
2022-01-05 15:14 ` [PATCH 3/3] net: usb: r8152: remove unused definition Aaron Ma
2022-01-05 15:34 ` Greg KH
2022-01-05 15:31 ` [PATCH 1/3 v3] net: usb: r8152: Check used MAC passthrough address Greg KH
2022-01-05 15:57 ` Henning Schild
2022-01-05 17:30 ` Andrew Lunn
2022-01-05 17:40 ` Henning Schild
2022-01-05 21:49 ` Oliver Neukum
2022-01-05 22:27 ` Andrew Lunn
2022-01-06 2:10 ` Kai-Heng Feng
2022-01-06 13:27 ` Andrew Lunn
2022-01-07 2:01 ` Kai-Heng Feng
2022-01-07 2:31 ` Jakub Kicinski
2022-01-10 3:32 ` Kai-Heng Feng
2022-01-10 16:51 ` Jakub Kicinski
2022-01-11 1:51 ` Kai-Heng Feng
2022-01-11 14:57 ` Limonciello, Mario
2022-01-11 16:26 ` Jakub Kicinski
2022-01-11 16:33 ` Limonciello, Mario
2022-01-11 16:43 ` Jakub Kicinski
2022-01-11 16:54 ` Limonciello, Mario
2022-01-11 17:06 ` Jakub Kicinski
2022-01-11 17:10 ` Limonciello, Mario
2022-01-12 19:21 ` Henning Schild
2022-01-12 19:27 ` Limonciello, Mario
2022-01-13 3:23 ` Aaron Ma
2022-01-27 2:51 ` Aaron Ma
2022-01-27 8:06 ` Hayes Wang
2022-01-27 8:13 ` Aaron Ma [this message]
2022-01-27 8:42 ` Hayes Wang
2022-01-27 12:53 ` Andrew Lunn
2022-01-07 13:32 ` Andrew Lunn
2022-01-10 3:39 ` Kai-Heng Feng
2022-01-10 11:39 ` Oliver Neukum
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=e52f8155-61a8-0cea-b96c-a05b83cdfff9@canonical.com \
--to=aaron.ma@canonical.com \
--cc=Mario.Limonciello@amd.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=hayeswang@realtek.com \
--cc=henning.schild@siemens.com \
--cc=kai.heng.feng@canonical.com \
--cc=kuba@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=tiwai@suse.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 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).