Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux@cthulhu.engr.sgi.com
Subject: Re: Indy Documentation
Date: Mon, 15 May 2000 00:04:54 +0200	[thread overview]
Message-ID: <20000515000454.A6575@lug-owl.de> (raw)
In-Reply-To: <20000513183248.C1279@paradigm.rfc822.org>; from flo@rfc822.org on Sat, May 13, 2000 at 06:32:48PM +0200

[-- Attachment #1: Type: text/plain, Size: 2320 bytes --]

On Sat, May 13, 2000 at 06:32:48PM +0200, Florian Lohoff wrote:
> On Sat, May 13, 2000 at 06:21:56AM -0700, Ulf Carlsson wrote:
> > Subject: Indy Documentation
> 
> Someday somebody might be interested in doing more work
> for the Indigo and then there is no documentation avail.

Doing "more" work for Indigo? Well, what work has actually be done up to
now to support linux on this (okay, quite old...) box?

- The R3k is supported by gcc (I think R3000 support is mainly used for
  the DECStations?)
- Glibc2.2 will be available in near future and hopefully fully
  functional;)

But:

- No kernel support so far (okay, one try to make it run, but this 
  resulted in an exception right after tftp'ing the kernel image to
  the machine)

Personally I'd like to do work on an Indigo as I got one, but it seems
to only be a no-documentation-available problem. (I remember I got some
email address of a woman working at SGI I should have contacted a week
or two ago...).

I'd love to sign a 1US$/year contract with SGI as Flo suggested, but
this doesn't ease (nor solve) the problem. Even if I would get some
sources from eg Irix5.2 (to figure out the bootstrap process) I wouldn't
be allowed to use it in GPL'ed work because of parts being licensed
from other companies;(

However, there were some documents found. Save them. Save them at a
very save place as they might disappear which is somewhat "normal"
for documentation;) Maybe there will (at some certain time) be someone
at SGI who has got enough spare time to evaluate docs and sources.
Maybe licensed parts can be removed without removing all necessary
infos to build a kernel for Indigos. This would be equal to what
IBM does to their JFS (with one difference: Indigos are equal to 
a mid-class 486, JFS is even today a first-class fs). This unfortunately
requires menwork and so it is costly;( I also think that is isn't
really cheap to port XFS, as well. But porting XFS is a step forward, 
making Indigos is kind of nostalgic...

MfG, JBG

-- 
Fehler eingestehen, Größe zeigen: Nehmt die Rechtschreibreform zurück!!!
/* Jan-Benedict Glaw <jbglaw@lug-owl.de> -- +49-177-5601720 */
keyID=0x8399E1BB fingerprint=250D 3BCF 7127 0D8C A444 A961 1DBD 5E75 8399 E1BB
	...und aus aktuellem Anlaß:	ILOVEYOU, Linux!

[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]

  parent reply	other threads:[~2000-05-14 22:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-13 13:21 Indy Documentation Ulf Carlsson
2000-05-13 13:42 ` Guido Guenther
2000-05-14  6:08   ` Florian Lohoff
2000-05-13 16:32 ` Florian Lohoff
2000-05-14 18:58   ` Geert Uytterhoeven
2000-05-15 21:23     ` Ralf Baechle
2000-05-16 10:08       ` Florian Lohoff
2000-05-16 16:40         ` Ralf Baechle
     [not found]           ` <Pine.GSO.3.96.1000517124358.24276C-100000@delta.ds2.pg.gda.pl>
2000-05-17 16:06             ` Ralf Baechle
2000-05-16 17:17         ` Nancy Bigham
2000-05-17 11:39           ` Florian Lohoff
2000-05-14 22:04   ` Jan-Benedict Glaw [this message]
2000-05-13 23:46 ` Alan Cox
2000-05-13 23:46   ` Alan Cox
2000-05-15 18:22 ` Ulf Carlsson
2000-05-15 19:19   ` Guido Guenther
  -- strict thread matches above, loose matches on Subject: below --
2000-05-16 11:02 Kevin D. Kissell
2000-05-16 11:02 ` Kevin D. Kissell

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=20000515000454.A6575@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=linux@cthulhu.engr.sgi.com \
    /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