From: Giorgio <giorgio.nicole@arcor.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: configure the mac address of an eth device
Date: Sun, 24 May 2020 13:57:08 +0200 [thread overview]
Message-ID: <69ca4999-4cf0-f20a-5d7a-93e470338bf4@arcor.de> (raw)
Hi,
I'm working with an arm som with an imx7d soc on it.
The som also has an eeprom with some module specific manufacturer parameters
like two MAC address, for eth0 and eth1, a module description string or a module
serial number.
I've now added some code to my board.c to extract the strings from the eeprom and now
I need to actually configure the MAC addresses from them, to avoid barebox choose
random ones when it needs the eth's.
What is the proper way to do this ?
giorgio
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2020-05-24 11:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-24 11:57 Giorgio [this message]
2020-05-24 18:27 ` Ladislav Michl
2020-05-25 6:01 ` Sascha Hauer
2020-05-26 15:54 ` Giorgio Dal Molin
2020-06-02 6:20 ` 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=69ca4999-4cf0-f20a-5d7a-93e470338bf4@arcor.de \
--to=giorgio.nicole@arcor.de \
--cc=barebox@lists.infradead.org \
/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