From: Andrew Lunn <andrew@lunn.ch>
To: Mario_Limonciello@Dell.com
Cc: gregkh@linuxfoundation.org, hayeswang@realtek.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-usb@vger.kernel.org, pali.rohar@gmail.com,
anthony.wong@canonical.com
Subject: Re: [PATCH v2] r8152: Add support for setting MAC to system's Auxiliary MAC address
Date: Thu, 2 Jun 2016 21:09:46 +0200 [thread overview]
Message-ID: <20160602190946.GL15379@lunn.ch> (raw)
In-Reply-To: <ae0f974692814260bb9f2f2cf4af6450@ausx13mpc124.AMER.DELL.COM>
On Thu, Jun 02, 2016 at 07:04:32PM +0000, Mario_Limonciello@Dell.com wrote:
> > -----Original Message-----
> > From: Andrew Lunn [mailto:andrew@lunn.ch]
> > Sent: Thursday, June 2, 2016 2:03 PM
> > To: Limonciello, Mario <Mario_Limonciello@Dell.com>
> > Cc: gregkh@linuxfoundation.org; hayeswang@realtek.com; linux-
> > kernel@vger.kernel.org; netdev@vger.kernel.org; linux-
> > usb@vger.kernel.org; pali.rohar@gmail.com; anthony.wong@canonical.com
> > Subject: Re: [PATCH v2] r8152: Add support for setting MAC to system's
> > Auxiliary MAC address
> >
> > > > And you want to check this for all Dell devices? Please be model
> > > > specific, I doubt a bunch of Dell servers wants to run this code...
> > > >
> > >
> > > Tracking model specific is really going to turn into a giant list never ending
> > list.
> > > To drill down more specifically, I can match on chassis too.
> >
> > Does Dell happen to use its own USB Vendor ID for the USB device in
> > the dock? You could go at this problem from the other direction if it
> > does have a unique vendor ID.
> >
> > Andrew
>
> Unfortunately it's not a Dell specific VID/PID. I'm asking around to find out
> if there is something else identifiable about this dock's NIC (maybe that r8152
> can query).
lsusb -v
I assume there is a USB hub in the dock, maybe that has a Dell VID?
Going one level up the USB tree hierarchy should not be too hard.
Andrew
next prev parent reply other threads:[~2016-06-02 19:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 16:58 [PATCH v2] r8152: Add support for setting MAC to system's Auxiliary MAC address Mario Limonciello
2016-06-02 16:58 ` Mario Limonciello
2016-06-02 17:48 ` Greg KH
2016-06-02 18:32 ` Mario_Limonciello
2016-06-02 19:02 ` Andrew Lunn
2016-06-02 19:04 ` Mario_Limonciello
2016-06-02 19:09 ` Andrew Lunn [this message]
2016-06-03 14:44 ` Mario_Limonciello
2016-06-03 2:01 ` Greg KH
2016-06-03 15:10 ` Mario_Limonciello
2016-06-03 9:43 ` Hayes Wang
2016-06-03 15:08 ` Mario_Limonciello
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=20160602190946.GL15379@lunn.ch \
--to=andrew@lunn.ch \
--cc=Mario_Limonciello@Dell.com \
--cc=anthony.wong@canonical.com \
--cc=gregkh@linuxfoundation.org \
--cc=hayeswang@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pali.rohar@gmail.com \
/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).