From: Roland Dreier <roland@topspin•com>
To: "Brian Padalino" <bpadalino@perigee•com>
Cc: <linuxppc-embedded@lists•linuxppc.org>
Subject: Re: PPCBoot on Ebony board
Date: 16 Jul 2003 07:45:17 -0700 [thread overview]
Message-ID: <52u19mr0n6.fsf@topspin.com> (raw)
In-Reply-To: <DGEEIPOFGGPOACEFBGGCOEHCCAAA.bpadalino@perigee.com>
Brian> I found the flash programmer utility, but I am actually a
Brian> bit scared to flash the flash with the version of PPCBoot
Brian> that I made. I am working without a JTAG interface, so
Brian> flashing using JTAG is out of the question, and how would I
Brian> re-flash if the PPCBoot binary I have doesn't work
Brian> properly? Is the board running out of EEPROM right now
Brian> with the IBM Open Shell always there? I have sifted
Brian> through the documentation a bit, but haven't found a
Brian> straight answer as to exactly how the board is setup right
Brian> out of the box.
The Ebony OpenBIOS runs out of the socketed EEPROM on the board. Just
pop the current EEPROM, put a sticker on it that says "Original
Bootloader" and use a new EEPROM for PPCBoot testing.
- Roland
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-07-16 14:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 4:32 [RFC] consistent_sync and non L1 cache line aligned buffers Eugene Surovegin
2003-07-15 15:46 ` Tom Rini
2003-07-15 16:20 ` Eugene Surovegin
2003-07-15 16:25 ` Tom Rini
2003-07-15 16:17 ` Matt Porter
2003-07-15 16:27 ` Eugene Surovegin
2003-07-15 18:11 ` PPCBoot on Ebony board Brian Padalino
2003-07-15 21:32 ` Chris Zimman
2003-07-16 11:59 ` Brian Padalino
2003-07-16 14:29 ` Chris Zimman
2003-07-16 15:39 ` Brian Padalino
2003-07-16 14:45 ` Roland Dreier [this message]
2003-07-15 23:51 ` [RFC] consistent_sync and non L1 cache line aligned buffers Matt Porter
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=52u19mr0n6.fsf@topspin.com \
--to=roland@topspin$(echo .)com \
--cc=bpadalino@perigee$(echo .)com \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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