From: Trent Piepho <trent.piepho@igorinstitute.com>
To: Michael Grzeschik <m.grzeschik@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH] net/eth: read default mac-address default from dts
Date: Tue, 15 Jun 2021 13:32:26 -0700 [thread overview]
Message-ID: <CAMHeXxNpR01tPQ-M2-Oj8S4s9QxS-i7Vw+H3ED1NH8uO9rZekQ@mail.gmail.com> (raw)
In-Reply-To: <20210615153223.9329-1-m.grzeschik@pengutronix.de>
Once upon a time, it was common for kernel dts files to be booted with
u-boot to include an all zero mac address property, since u-boot could
not unpack/pack the fdt. It could only find an existing property and
change bytes already present, thus adding a blank mac address to be
patched. Barebox has a much better fdt fixup system and does not need
this.
But maybe these blank mac address properties are still there in some
of the dts files, which mostly come from the kernel dts sources?
Might be worth ignoring an all zero address rather than calling it
found.
Unless of_get_mac_address() already includes such logic in a way that works ok?
On Tue, Jun 15, 2021 at 12:49 PM Michael Grzeschik
<m.grzeschik@pengutronix.de> wrote:
>
> Since we have the functino of_get_mac_address we can
> use it to set the default mac address vom the dts.
>
> Signed-off-by: Michael Grzeschik <m.grzeschik@pengutronix.de>
> ---
> net/eth.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/net/eth.c b/net/eth.c
> index 84f99d3aa8..baebf89d89 100644
> --- a/net/eth.c
> +++ b/net/eth.c
> @@ -11,6 +11,7 @@
> #include <net.h>
> #include <dma.h>
> #include <of.h>
> +#include <of_net.h>
> #include <linux/phy.h>
> #include <errno.h>
> #include <malloc.h>
> @@ -431,6 +432,14 @@ int eth_register(struct eth_device *edev)
> if (!ret)
> found = 1;
>
> + if (!found && edev->parent) {
> + const u8 *maddr = of_get_mac_address(edev->parent->device_node);
> + if (maddr) {
> + memcpy(ethaddr, maddr, ETH_ALEN);
> + found = 1;
> + }
> + }
> +
> if (!found) {
> ret = edev->get_ethaddr(edev, ethaddr);
> if (!ret)
> --
> 2.29.2
>
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2021-06-15 22:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 15:32 Michael Grzeschik
2021-06-15 20:32 ` Trent Piepho [this message]
2021-06-21 6:42 ` Ahmad Fatoum
2021-06-15 17:17 Michael Grzeschik
2021-06-16 7:14 ` Sascha Hauer
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=CAMHeXxNpR01tPQ-M2-Oj8S4s9QxS-i7Vw+H3ED1NH8uO9rZekQ@mail.gmail.com \
--to=trent.piepho@igorinstitute.com \
--cc=barebox@lists.infradead.org \
--cc=m.grzeschik@pengutronix.de \
/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