From: Dave Peverley <dpeverley@mpc-data.co.uk>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Ethernet and detecting MAC addresses
Date: Wed, 07 Apr 2004 12:18:04 +0100 [thread overview]
Message-ID: <4073E36C.8000901@mpc-data.co.uk> (raw)
AFAICT from the source I'm using (1.0.2) none of the ethernet drivers
bother with detecting their own MAC address (if available) and rather
rely on hard/soft coded addresses. Is this an intentional by design, or
just something unimplemented as yet? If this is something I can implement
for our board here, does anyone have pointers for where is best to splice
it in without upsetting anyone? :-) I already have a really untidy rough
and ready hack that we use internally to do this that works, but I'd like
to implement properly if possible.
Best Wishes,
Dave Peverley
---------------------------------------------------------------------------
Dave Peverley, Software Engineer, MPC Data Limited.
Phone : [+44] (0) 1225 868 228 Web : http://www.mpc-data.co.uk
next reply other threads:[~2004-04-07 11:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 11:18 Dave Peverley [this message]
2004-04-07 13:09 ` [U-Boot-Users] Ethernet and detecting MAC addresses Wolfgang Denk
2004-04-07 14:26 ` Dave Peverley
2004-04-07 13:48 ` Marius Groeger
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=4073E36C.8000901@mpc-data.co.uk \
--to=dpeverley@mpc-data.co.uk \
--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