From: Hector Martin <marcan@marcan.st>
To: Andrew Lunn <andrew@lunn.ch>, Tianhao Chai <cth451@gmail.com>
Cc: Igor Russkikh <irusskikh@marvell.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Sven Peter <sven@svenpeter.dev>,
Alyssa Rosenzweig <alyssa@rosenzweig.io>
Subject: Re: [PATCH] ethernet: aquantia: Try MAC address from device tree
Date: Mon, 29 Nov 2021 02:08:28 +0900 [thread overview]
Message-ID: <37679b8b-7a81-5605-23af-e442f9e91816@marcan.st> (raw)
In-Reply-To: <YaOvShya4kP4SRk7@lunn.ch>
On 29/11/2021 01.33, Andrew Lunn wrote:
> On Sat, Nov 27, 2021 at 08:37:33PM -0600, Tianhao Chai wrote:
>> Apple M1 Mac minis (2020) with 10GE NICs do not have MAC address in the
>> card, but instead need to obtain MAC addresses from the device tree. In
>> this case the hardware will report an invalid MAC.
>>
>> Currently atlantic driver does not query the DT for MAC address and will
>> randomly assign a MAC if the NIC doesn't have a permanent MAC burnt in.
>> This patch causes the driver to perfer a valid MAC address from OF (if
>> present) over HW self-reported MAC and only fall back to a random MAC
>> address when neither of them is valid.
>
> This is a change in behaviour, and could cause regressions. It would
> be better to keep with the current flow. Call
> aq_fw_ops->get_mac_permanent() first. If that does not give a valid
> MAC address, then try DT, and lastly use a random MAC address.
On DT platforms, it is expected that the device tree MAC will override
whatever the device thinks is its MAC address. See tg3, igb, igc, r8169,
for examples where eth_platform_get_mac_address takes precedence over
everything else.
I would not expect any other existing platform to have a MAC assigned to
the device in this way using these cards; if any platforms do, chances
are they intended it for it to be used and this patch will fix a current
bug. If some platforms out there really have bogus MACs assigned in this
way, that's a firmware bug, and we'd have to find out and add explicit,
targeted workaround code. Are you aware of any such platforms? :)
--
Hector Martin (marcan@marcan.st)
Public Key: https://mrcn.st/pub
next prev parent reply other threads:[~2021-11-28 17:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-28 2:37 Tianhao Chai
2021-11-28 16:33 ` Andrew Lunn
2021-11-28 17:08 ` Hector Martin [this message]
2021-11-30 2:32 ` Andrew Lunn
2021-11-30 4:43 ` Tianhao Chai
2021-12-02 5:10 ` Hector Martin
2021-11-29 22:11 ` Heiner Kallweit
2021-11-30 3:12 ` Tianhao Chai
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=37679b8b-7a81-5605-23af-e442f9e91816@marcan.st \
--to=marcan@marcan.st \
--cc=alyssa@rosenzweig.io \
--cc=andrew@lunn.ch \
--cc=cth451@gmail.com \
--cc=davem@davemloft.net \
--cc=irusskikh@marvell.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sven@svenpeter.dev \
/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
all inboxes | Powered by JetHome®