From: Dan Malek <dan@netx4.com>
To: Graham Stoney <greyham@research.canon.com.au>
Cc: LinuxPPC Embedded Mailing List <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Tiny fix to fec.c for RPX boards using only fast ethernet
Date: Wed, 29 Mar 2000 20:38:21 -0500 [thread overview]
Message-ID: <38E2B00D.E65880E7@embeddededge.com> (raw)
In-Reply-To: 20000330001115.4B3FF5067E@brixi.research.canon.com.au
Graham Stoney wrote:
> .... Unfortunately, it isn't desirable if the
> SCC port isn't being used, because it still renumbers the FEC MAC address from
> the one in the board info structure.
Why don't you want this? Ethernet addresses are supposed to be assigned
to MACs. It's not a good idea to have a MAC appear at different addresses.
This is why it always assigns the same address.
> ..... It also makes the decision non-board-specific, so other boards
> with dual FEC & SCC ports benefit too:
That's not good either. I know how EP assigns Ethernet addresses, so
I can do this. Manufacturers are supposed to supply Ethernet addresses
for every MAC they support. The "right" way is to have multiple, known
unique addresses assigned to boards that have multiple MACs. Other
boards may (should) require different assignment methods.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-03-30 1:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-30 0:11 Tiny fix to fec.c for RPX boards using only fast ethernet Graham Stoney
2000-03-30 1:38 ` Dan Malek [this message]
2000-03-30 2:47 ` Graham Stoney
2000-03-30 3:08 ` Dan Malek
2000-03-30 7:04 ` 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=38E2B00D.E65880E7@embeddededge.com \
--to=dan@netx4.com \
--cc=greyham@research.canon.com.au \
--cc=linuxppc-embedded@lists.linuxppc.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).