From: "C.Newport" <crn@netunix.com>
To: sparclinux@vger.kernel.org
Subject: Re: socal
Date: Thu, 01 Jan 2004 02:57:21 +0000 [thread overview]
Message-ID: <200401010257.21123.crn@netunix.com> (raw)
In-Reply-To: <200312311429.26841.awirtz@novapointe.com>
On Thursday 01 January 2004 2:41 am, Pete Zaitcev wrote:
> On Thu, Jan 01, 2004 at 02:06:56AM +0000, C.Newport wrote:
> > The E3500 can boot from fcal, so the required code is in the OBP.
> > You could probably hack up a driver by calling the OBP code.
>
> Anything can boot from the SOCAL card, even sun4d. In fact it's
> exactly the same FCode, and even more - it's exactly the same binary
> image! The build procedure for the Sunfire OBP builds an FCode as
> if it were for the card, then incorporates it into OBP as a binary
> with a little od(1) and ld(1) magic.
>
> Calling OBP driver is probably not a good idea, it's beyond
> slow. It's glacial. Also, its error recovery is not stellar.
> I hardened it a bit when I took over from Ping, but there are
> limits to what you could do to FCode. I advise against it.
Agreed, I was thinking in terms of a temporary driver as an aid
to understanding how to build a production version.
next prev parent reply other threads:[~2004-01-01 2:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-31 22:29 socal Aaron Wirtz
2003-12-31 23:07 ` socal C.Newport
2003-12-31 23:18 ` socal Keith M Wesolowski
2003-12-31 23:19 ` socal Aaron Wirtz
2003-12-31 23:26 ` socal Keith M Wesolowski
2003-12-31 23:35 ` socal Pete Zaitcev
2003-12-31 23:43 ` socal Aaron Wirtz
2003-12-31 23:43 ` socal Pete Zaitcev
2003-12-31 23:49 ` socal Aaron Wirtz
2003-12-31 23:57 ` socal Aaron Wirtz
2004-01-01 0:54 ` socal C.Newport
2004-01-01 1:26 ` socal C.Newport
2004-01-01 1:34 ` socal Aaron Wirtz
2004-01-01 2:06 ` socal C.Newport
2004-01-01 2:41 ` socal Pete Zaitcev
2004-01-01 2:57 ` C.Newport [this message]
2004-01-01 3:10 ` socal Aaron Wirtz
2004-01-06 3:06 ` socal Aaron Wirtz
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=200401010257.21123.crn@netunix.com \
--to=crn@netunix.com \
--cc=sparclinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.