Alan Hoyt said:
:> It won't happen by itself, only if someone devotes serious
:> time to it. My personal feeling is that Linux on R3000
:> will not happen (there are cheaper and faster old pentium 90's
:> out there) but if someone builds it... I've been wrong before.
:Are you saying that the effort necessary to port Linux to R3000
:Indigo would be better placed elsewhere?
Everything I write below is personal views, no one appointed me
to be an official SGI spokeperson]
In a way yes ;-)
For example, I personally would be much happier if the few people
who have the ability to make such port a reality would devote their
time on more attractive, newer machines.
The real scarcity is in talent who can make things happen. There's
no scarcity in people who just "want" things to happen and voice
their wishes on various mailing lists.
If we could get talent to get involved with the SGI Intel machines
it would be IMHO more valuable; the reasons are simple:
- We can leverage the thousands of precompiled PRMs out there
rather than duplicating work
- The installed base of these systems is expected to be much
larger so the scarcity of talent with access to hardware
would likely be less grave.
- The performance and attractiveness of these machines is
- Market realities: SGI as a company may be much more inclined
to put resources on something that is not a dead product.
and we have to realize that every response even on this
friendly mailing list, is in the end paid for by SGI since
people work on company time.
There's some work going on (while no one was taking notice, the 2.2.4
kernel just got a /dev/fb implementation from Jeff Newquist) so
we can have X11 (albeit unaccelerated) running on the SGI VisWS!
People are welcome to look at the code and get involved, it is all
completely open on www.linux.sgi.com (in the Intel section).
Regarding MIPS, for similar reasons, having the Indy port 'finished'
(it is not yet really easy to get up and running) or having support
for O2s, seems (at least to me) to be much more attractive than
Again, It is not that I don't want it to happen. I'm just
asking myself, what would I (and many others) prefer to put
available talent energies on. If we don't set priorities,
we run the risk of getting lost in multiple unfinished ports
and dilute our efforts and end results.
:The final portion of my original question, is really the most
:important - are the hardware specifications/documentation available
:or are they considered proprietary?
:This issue alone is paramount since it substantially affects the "effort"
:necessary to port.
I believe Bill Earl tried to locate some very old specs but
couldn't find them (and he can correct me if I'm wrong). Indy
specs were sent (sorry I only have paper versions) to those
who have shown they are really serious and can make a difference
and asked for them. The best source for older SGI machines
data is at:
This is the best I could find on anything before my times at SGI...