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 22:08:03 -0500 [thread overview]
Message-ID: <38E2C513.F3A37159@embeddededge.com> (raw)
In-Reply-To: 20000330024703.3E3C0355E8@elph.research.canon.com.au
Graham Stoney wrote:
> Sure, but there's only provision for a single MAC address in the bd_t
> struct,
The board descriptor is unique to every board configuration. I have
some boards with three MACs, three unique Ethernet addresses, and the
bd_t has three Ethernet entries. That's the "right" way. My latest
change to the RPX Classic is to define two Ethernet addresses, and
these are assigned in the 'embed_config.c' functions. The FEC just
always chooses the second one (board specific index).
> ....... Otherwise the MAC address the ROM monitor tells
> you about is different to the one the FEC uses.
That is now irrelevant. The ROM monitor on the RPX boards is going
to be significantly different within weeks. It will only use the
Ethernet address and the 10 Mbit SCC Ethernet.
> True, it just seemed to me to be a better default for other vendors...
The example will now be in the embedded configuration functions. Load
your choice of Ethernet addresses there, and the FEC driver is just
built with which to select. This further flows into the 8260 port
which can support multiple Fast Ethernet controllers.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-03-30 3:08 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
2000-03-30 2:47 ` Graham Stoney
2000-03-30 3:08 ` Dan Malek [this message]
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=38E2C513.F3A37159@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).