From: "Michał Pecio" <michal.pecio@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: mario_limonciello@dell.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, linux-usb@vger.kernel.org,
anthony.wong@canonical.com
Subject: Re: [PATCH v6 RESEND] r8152: Add support for setting pass through MAC address on RTL8153-AD
Date: Tue, 12 Jul 2016 09:02:48 +0200 [thread overview]
Message-ID: <20160712090248.7b5633e5@sauron> (raw)
In-Reply-To: <20160711.194246.742914205682079488.davem@davemloft.net>
> From: Mario Limonciello <mario_limonciello@dell.com>
> Date: Mon, 11 Jul 2016 19:58:04 -0500
>
> > The RTL8153-AD supports a persistent system specific MAC address.
> > This means a device plugged into two different systems with host
> > side support will show different (but persistent) MAC addresses.
> >
> > This information for the system's persistent MAC address is burned
> > in when the system HW is built and available under \_SB.AMAC in the
> > DSDT at runtime.
> >
> > This technology is currently implemented in the Dell TB15 and WD15
> > Type-C docks. More information is available here:
> > http://www.dell.com/support/article/us/en/04/SLN301147
> >
> > Signed-off-by: Mario Limonciello <mario_limonciello@dell.com>
>
> Applied.
Hi,
Isn't it possible that the same ACPI name could be used for other
vendor-specific extensions on other laptops and that r8152 will now
wreak havoc there?
Regards,
MP
next prev parent reply other threads:[~2016-07-12 7:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 0:58 [PATCH v6 RESEND] r8152: Add support for setting pass through MAC address on RTL8153-AD Mario Limonciello
2016-07-12 2:42 ` David Miller
2016-07-12 7:02 ` Michał Pecio [this message]
2016-07-12 15:04 ` Mario_Limonciello
[not found] ` <5a304b784fe747aea4de6b69fb12a767-uCoIPMzyhkttLtSlb8FIwwVY21JRvFwKV6yJEvX+wlw@public.gmane.org>
2016-07-13 6:23 ` Michał Pecio
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=20160712090248.7b5633e5@sauron \
--to=michal.pecio@gmail.com \
--cc=anthony.wong@canonical.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mario_limonciello@dell.com \
--cc=netdev@vger.kernel.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).