From: Eugene Surovegin <ebs@ebshome.net>
To: Brian Hawley <bhawley@luminex.com>
Cc: Wolfgang Denk <wd@denx.de>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Ebony Board, PPC440GP and NFS panics
Date: Wed, 19 May 2004 15:44:48 -0700 [thread overview]
Message-ID: <20040519224447.GE13351@gate.ebshome.net> (raw)
In-Reply-To: <4.2.2.20040519143346.04c41220@bhawley.mailhost.luminex.com>
On Wed, May 19, 2004 at 02:34:29PM -0700, Brian Hawley wrote:
> At 03:11 PM 5/19/04 -0700, Eugene Surovegin wrote:
>
> >inird option has nothing to do with MAC address. MAC address is read by
> >ebony.c directly from OpenBIOS VPD area (see ebony.c::ebony_setup_arch())
> >regardless whether initrd is enabled or not.
> >
> >Probably, you have erased this area on your box.
>
> I don't think so, it always appears correct when I print the
> environment variables in uboot.
This is irrelevant, ebony.c doesn't know about u-boot.
> It also appears to be correct when the
> IBM boot prom displays the emac parameters.
It's possible that after you did something with OpenBIOS, e.g. rebuilt it, VPD
area moved to some other place. Or probably you have an old or new boot loader
:)
ebony.h uses hardcoded addresses:
/* Macros to get at Ebony VPD info */
#define EBONY_VPD_BASE 0x00000001fffffe00ULL
#define EBONY_VPD_SIZE 0x24
#define EBONY_NA0_OFFSET 0x0c
#define EBONY_NA1_OFFSET 0x18
#define EBONY_NA0_ADDR(base) (base + EBONY_NA0_OFFSET)
#define EBONY_NA1_ADDR(base) (base + EBONY_NA1_OFFSET)
P.S. There is another possible solution for your problems, you can hire somebody
who knows this stuff.
I bet there are people here who are available. Just send a message to the list
with appropriate subject :)
Eugene.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-05-19 22:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-18 1:49 ELDK help Jack Liu
2004-05-18 7:31 ` Wolfgang Denk
2004-05-18 16:32 ` Ebony Board, PPC440GP and NFS panics Brian Hawley
2004-05-19 7:23 ` Gerhard Jaeger
2004-05-19 16:13 ` Brian Hawley
2004-05-19 17:37 ` Mark Chambers
2004-05-19 17:09 ` Brian Hawley
2004-05-19 17:59 ` Wolfgang Denk
2004-05-19 17:16 ` Brian Hawley
2004-05-19 19:54 ` Wolfgang Denk
2004-05-19 19:36 ` Brian Hawley
2004-05-19 21:04 ` Eugene Surovegin
2004-05-19 20:24 ` Brian Hawley
2004-05-19 21:19 ` Eugene Surovegin
2004-05-19 20:52 ` Brian Hawley
2004-05-19 22:11 ` Eugene Surovegin
2004-05-19 21:27 ` Brian Hawley
2004-05-19 21:34 ` Brian Hawley
2004-05-19 22:44 ` Eugene Surovegin [this message]
2004-05-19 22:19 ` Ebony Board, PPC440GP and NFS time out Brian Hawley
2004-05-19 23:42 ` Eugene Surovegin
2004-05-19 23:09 ` Brian Hawley
2004-05-20 0:19 ` Eugene Surovegin
2004-05-19 23:40 ` Brian Hawley
2004-05-19 20:01 ` Ebony Board, PPC440GP and NFS panics Brian Hawley
[not found] ` <Your message of "Wed, 19 May 2004 10:16:29 PDT." <4.2.2.20040519101456.0509d340@bhawley.mailhost.luminex.com>
[not found] ` <4.2.2.20040519123513.05074da0@bhawley.mailhost.luminex.com >
2004-05-19 20:14 ` Ebony Board, PPC440GP and Ramdisk Brian Hawley
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=20040519224447.GE13351@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=bhawley@luminex.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=wd@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;
as well as URLs for NNTP newsgroup(s).