From: Andrew Lunn <andrew@lunn.ch>
To: Tao Ren <taoren@fb.com>
Cc: Jakub Kicinski <jakub.kicinski@netronome.com>,
Samuel Mendoza-Jonas <sam@mendozajonas.com>,
"David S . Miller" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
William Kennington <wak@google.com>,
Joel Stanley <joel@jms.id.au>
Subject: Re: [PATCH net-next] net/ncsi: allow to customize BMC MAC Address offset
Date: Thu, 8 Aug 2019 15:32:09 +0200 [thread overview]
Message-ID: <20190808133209.GB32706@lunn.ch> (raw)
In-Reply-To: <806a76a8-229a-7f24-33c7-2cf2094f3436@fb.com>
> Let me prepare patch v2 using device tree. I'm not sure if standard
> "mac-address" fits this situation because all we need is an offset
> (integer) and BMC MAC is calculated by adding the offset to NIC's
> MAC address. Anyways, let me work out v2 patch we can discuss more
> then.
Hi Tao
I don't know BMC terminology. By NICs MAC address, you are referring
to the hosts MAC address? The MAC address the big CPU is using for its
interface? Where does this NIC get its MAC address from? If the BMCs
bootloader has access to it, it can set the mac-address property in
the device tree.
Andrew
next prev parent reply other threads:[~2019-08-08 13:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 0:21 [PATCH net-next] net/ncsi: allow to customize BMC MAC Address offset Tao Ren
2019-08-07 18:25 ` Jakub Kicinski
2019-08-07 18:41 ` Andrew Lunn
2019-08-08 4:48 ` Tao Ren
2019-08-08 13:32 ` Andrew Lunn [this message]
2019-08-08 19:02 ` Tao Ren
2019-08-08 21:16 ` Andrew Lunn
2019-08-08 22:26 ` Tao Ren
2019-08-08 23:03 ` Andrew Lunn
2019-08-09 5:29 ` Tao Ren
[not found] ` <10079A1AC4244A41BC7939A794B72C238FCE0E03@fmsmsx104.amr.corp.intel.com>
[not found] ` <bc9da695-3fd3-6643-8e06-562cc08fbc62@linux.intel.com>
2019-08-13 16:31 ` Terry Duncan
[not found] ` <faa1b3c9-9ba3-0fff-e1d4-f6dddb60c52c@fb.com>
2019-08-13 20:54 ` Terry Duncan
2019-08-14 0:22 ` Terry Duncan
[not found] ` <CH2PR15MB3686B3A20A231FC111C42F40A3D20@CH2PR15MB3686.namprd15.prod.outlook.com>
2019-08-13 21:15 ` Terry Duncan
-- strict thread matches above, loose matches on Subject: below --
2019-08-07 17:36 Vijay Khemka
2019-08-08 4:51 ` [PATCH " Tao Ren
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=20190808133209.GB32706@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=joel@jms.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=sam@mendozajonas.com \
--cc=taoren@fb.com \
--cc=wak@google.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