From: "Christopher Dumoulin" <cdumoulin@ics-ltd.com>
To: <linuxppc-embedded@ozlabs.org>
Subject: RE: Multiple Boards with same MAC addresses - problem.
Date: Tue, 10 Apr 2007 16:02:12 -0400 [thread overview]
Message-ID: <200704102002.l3AK240R008519@mail3.magma.ca> (raw)
In-Reply-To: <mailman.536.1176223651.26657.linuxppc-embedded@ozlabs.org>
Do you have some non-volatile memory to work with? You could store MAC
addresses for each individual board in non-volatile memory, then read the
MAC address from there each time U-Boot runs, and program your Ethernet
ports accordingly.
----------------------------------------------------------------------
Message: 1
Date: Tue, 10 Apr 2007 16:51:04 +0200
From: powerpc440 <powerpc440@googlemail.com>
Subject: Multiple Boards with same MAC addresses - problem.
To: linuxppc-embedded@ozlabs.org
Message-ID: <461BA458.2010605@googlemail.com>
Content-Type: text/plain; charset=ISO-8859-1
Hello all,
I have multiple boards, based on ppc405ep (which include on-chip two
ethernet ports). I'm configure the MAC address in u-boot and all works
great. The problem appears when I use two or more boards in one network,
because the MAC addresses are the same. Now I'm making a own u-boots for
each board, but this solution is not very comfortable.
My question is, which is the standard way to resolve such problem? I
would have only one generic u-boot. Is this possible?
Best regards,
Zhivko Yordanov
------------------------------
next parent reply other threads:[~2007-04-10 20:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.536.1176223651.26657.linuxppc-embedded@ozlabs.org>
2007-04-10 20:02 ` Christopher Dumoulin [this message]
2007-04-10 14:51 Multiple Boards with same MAC addresses - problem powerpc440
2007-04-10 15:12 ` Ben Warren
2007-04-10 19:18 ` Wolfgang Denk
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=200704102002.l3AK240R008519@mail3.magma.ca \
--to=cdumoulin@ics-ltd.com \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).