From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-mips@linux-mips.org
Subject: Re: SGI O2 Prom modification
Date: Wed, 8 Sep 2004 14:13:33 +0200 [thread overview]
Message-ID: <20040908121333.GA6985@lug-owl.de> (raw)
In-Reply-To: <413E9931.8060605@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]
On Wed, 2004-09-08 01:31:29 -0400, Kumba <kumba@gentoo.org>
wrote in message <413E9931.8060605@gentoo.org>:
> Glenn Barry wrote:
> >My question is about the possibility of someone helping out with
> >modifying the O2's PROM to recognise the RM7900 CPU from PMC-Sierra.
>
> Modifying the binary is most assuredly way more difficult than gaining
> access to ip32PROM source and modifying it directly (and solving license
> issues). The level of change to the binary needed to make the ip32PROM
I'd not bet my a** on that. Modifying the binary firmware has got a
long, but rare, history. I remeber hacked PROM images for VAXen to
support larger SCSI disks. As long as you don't require a detailled CPU
detection, that should be possible. Hardcoding some values isn't all
thaaat hard. Making it correctly (preserving the formerly running
detection code for other CPUs) is a bit harder, of course :-)
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-09-08 12:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 4:04 SGI O2 Prom modification Glenn Barry
2004-09-08 5:31 ` Kumba
2004-09-08 5:46 ` Glenn Barry
2004-09-08 21:17 ` Robin H. Johnson
2004-09-08 21:36 ` Glenn Barry
2004-09-08 12:13 ` Jan-Benedict Glaw [this message]
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=20040908121333.GA6985@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-mips@linux-mips.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.