From: Joe Perches <joe@perches.com>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: "David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, Jason Cooper <jason@lakedaemon.net>,
Gregory Clement <gregory.clement@free-electrons.com>,
Andrew Lunn <andrew@lunn.ch>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
Lior Amsalem <alior@marvell.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] net: mvneta: read MAC address from hardware when available
Date: Mon, 03 Jun 2013 09:52:59 -0700 [thread overview]
Message-ID: <1370278379.2025.40.camel@joe-AO722> (raw)
In-Reply-To: <1370277707-2468-1-git-send-email-thomas.petazzoni@free-electrons.com>
On Mon, 2013-06-03 at 18:41 +0200, Thomas Petazzoni wrote:
> This patch improves the logic used by the mvneta driver to find a MAC
> address for a particular interface. Until now, it was only looking at
> the Device Tree, and if no address was found, was falling back to
> generating a random MAC address.
[]
> diff --git a/drivers/net/ethernet/marvell/mvneta.c b/drivers/net/ethernet/marvell/mvneta.c
[]
> @@ -2740,6 +2748,17 @@ static int mvneta_probe(struct platform_device *pdev)
[]
> + dt_mac_addr = of_get_mac_address(dn);
> + if (dt_mac_addr && is_valid_ether_addr(dt_mac_addr))
> + memcpy(dev->dev_addr, dt_mac_addr, ETH_ALEN);
> + else {
> + mvneta_get_mac_addr(pp, hw_mac_addr);
> + if (is_valid_ether_addr(hw_mac_addr))
> + memcpy(dev->dev_addr, hw_mac_addr, ETH_ALEN);
> + else
> + eth_hw_addr_random(dev);
> + }
maybe there could be a dmesg line like:
const char *mac_from;
[...]
mac_from = "device tree"
else
[...]
mac_from = "hardware"
else
mac_from = "random"
[...]
netdev_info(dev, "Using %s mac address %pM\n",
mac_from, dev->dev_addr);
prev parent reply other threads:[~2013-06-03 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 16:41 [PATCH] net: mvneta: read MAC address from hardware when available Thomas Petazzoni
2013-06-03 16:52 ` Sergei Shtylyov
2013-06-03 16:52 ` Joe Perches [this message]
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=1370278379.2025.40.camel@joe-AO722 \
--to=joe@perches.com \
--cc=alior@marvell.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=ezequiel.garcia@free-electrons.com \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=thomas.petazzoni@free-electrons.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).