From: Andrew Dixon <andrew.dixon@seranoa.com>
To: ppclist <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: root=/dev/nfs on sbc8260
Date: Thu, 13 Dec 2001 10:41:40 -0500 [thread overview]
Message-ID: <3C18CC34.5CF24CDA@seranoa.com> (raw)
In-Reply-To: 3C18445A.80505@embeddededge.com
Here is something very strange. In PPCBoot I set the ethernet address
to 00:a0:1e:90:15:55.
=> printenv
<snip>
ethaddr=00:a0:1e:90:15:55
<snip>
And PPCBoot uses bootp to get lots of good information about who the
board is.
Now, as I watch Linux try to come up I see the following:
eth0: FCC ENET Version 0.2, 00:a0:1e:d0:15:55
fec: Phy @ 0x1, type 0x000fd04b
Notice that the ethernet address has changed. Very odd. I assume that
this info should be passed from PPCBoot to Linux via the board info data
structure bd_t.
Has anyone else seen this before?
Thanks,
Andy
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-12-13 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-12 22:55 root=/dev/nfs on sbc8260 Andrew Dixon
2001-12-13 6:02 ` Dan Malek
2001-12-13 15:41 ` Andrew Dixon [this message]
2001-12-13 20:25 ` jtm
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=3C18CC34.5CF24CDA@seranoa.com \
--to=andrew.dixon@seranoa.com \
--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).