netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kai-Heng Feng <kai.heng.feng@canonical.com>
To: Oliver Neukum <oneukum@suse.com>
Cc: David Miller <davem@davemloft.net>,
	Hayes Wang <hayeswang@realtek.com>,
	Jakub Kicinski <jakub.kicinski@netronome.com>,
	Prashant Malani <pmalani@chromium.org>,
	Grant Grundler <grundler@chromium.org>,
	Mario Limonciello <mario.limonciello@dell.com>,
	David Chen <david.chen7@dell.com>,
	"open list:USB NETWORKING DRIVERS" <linux-usb@vger.kernel.org>,
	"open list:NETWORKING DRIVERS" <netdev@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] r8152: Add MAC passthrough support to new device
Date: Tue, 14 Jan 2020 17:22:39 +0800	[thread overview]
Message-ID: <A3D0DBA9-7014-48BF-8001-6F34EC2200B1@canonical.com> (raw)
In-Reply-To: <1578990223.15925.0.camel@suse.com>



> On Jan 14, 2020, at 16:23, Oliver Neukum <oneukum@suse.com> wrote:
> 
> Am Dienstag, den 14.01.2020, 12:41 +0800 schrieb Kai-Heng Feng:
>> Device 0xa387 also supports MAC passthrough, therefore add it to the
>> whitelst.
> 
> Hi,
> 
> this list is getting longer and longer. Isn't there a way to do
> this generically? ACPI?

ACPI only provides the MAC address, to write the MAC to r8152 it still requires hardware support.
So we need to use whitelist here, not all r8152 support this feature.

Kai-Heng

> 
> 	Regards
> 		Oliver
> 


  reply	other threads:[~2020-01-14  9:22 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 [this message]
2020-01-14 20:33 ` Mario.Limonciello
2020-01-15  6:40   ` Kai Heng Feng
2020-01-15  7:04     ` Hayes Wang
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=A3D0DBA9-7014-48BF-8001-6F34EC2200B1@canonical.com \
    --to=kai.heng.feng@canonical.com \
    --cc=davem@davemloft.net \
    --cc=david.chen7@dell.com \
    --cc=grundler@chromium.org \
    --cc=hayeswang@realtek.com \
    --cc=jakub.kicinski@netronome.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mario.limonciello@dell.com \
    --cc=netdev@vger.kernel.org \
    --cc=oneukum@suse.com \
    --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).