From: Stuart Longland <stuartl@vrt.com.au>
To: u-boot@lists.denx.de
Subject: [U-Boot] Silly question regarding mx28_adjust_mac and MAC OUIs?
Date: Tue, 22 Jul 2014 12:54:56 +1000 [thread overview]
Message-ID: <53CDD280.3040306@vrt.com.au> (raw)
Hi all,
Apoligies if this has been asked before. I'm very new to U-Boot, and
did look around but found nothing on the topic.
I've been doing some porting of U-Boot to a board based around a
Freescale i.MX286 CPU. So far thing are working, but I was wondering
how one specifies the MAC OUI?
As I understand it on this platform, the hardware "fuses" only store the
lower 32-bits of the MAC, with the upper 16-bits intended to be
hardcoded into device firmware. Looking through U-Boot, I see this is
done in mx28_adjust_mac (arch/arm/cpu/arm926ejs/mxs/mxs.c +237).
If I wanted to set a different OUI, is there a way to specify an
alternate one without patching mx28_adjust_mac directly?
Regards,
--
Stuart Longland
Systems Engineer
_ ___
\ /|_) | T: +61 7 3535 9619
\/ | \ | 38b Douglas Street F: +61 7 3535 9699
SYSTEMS Milton QLD 4064 http://www.vrt.com.au
reply other threads:[~2014-07-22 2:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=53CDD280.3040306@vrt.com.au \
--to=stuartl@vrt.com.au \
--cc=u-boot@lists.denx.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