Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Richard Hartensveld <richardh@infopact.nl>
To: Jeremy John Welling <jwelling@engin.umich.edu>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: challenge s boots linux
Date: Thu, 24 Sep 1998 11:38:04 +0200	[thread overview]
Message-ID: <360A12FC.DC0C039F@infopact.nl> (raw)
In-Reply-To: Pine.SOL.4.02.9809240031070.6032-100000@azure.engin.umich.edu

Jeremy John Welling wrote:

> What is the next architecture sgi/linux will be ported to?  Indigo2 r4kXZ?
> What is the status of the newport Xserver? What is the best place to get
> specific hardware info?  Has anyone started on the Indy XZ graphics?

Well i've got a indigo2 r4400 with a defective motherboard, when i'm able  to
get this fixed (they're quite expensive) i'll be happy to volunteer in the
development.

Richard

  reply	other threads:[~1998-09-24  9:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-09-22 21:11 challenge s boots linux Richard Hartensveld
1998-09-22 21:01 ` Rob Lembree
1998-09-22 21:41   ` Richard Hartensveld
1998-09-23  0:24     ` Alex deVries
1998-09-23 19:22       ` Thomas Bogendoerfer
1998-09-23 20:54         ` Richard Hartensveld
1998-09-23 21:11           ` Alex deVries
1998-09-24  4:47           ` Jeremy John Welling
1998-09-24  9:38             ` Richard Hartensveld [this message]
1998-09-24 14:15             ` Alan Cox
1998-09-24 14:15               ` Alan Cox
1998-09-24 16:33             ` Alex deVries
1998-09-24 16:44               ` William J. Earl
1998-09-24 22:42                 ` Richard Hartensveld
1998-09-25  5:45               ` Cool Jeremy John Welling
1998-09-23 21:30         ` challenge s boots linux Richard Masoner
1998-09-23 23:59         ` ralf
1998-09-24  0:17           ` Richard Hartensveld
1998-09-24  0:21             ` ralf
1998-09-24  9:29           ` Thomas Bogendoerfer
1998-09-24 16:14   ` Alex deVries
1998-09-24  5:44 ` Robin Humble
1998-09-24  5:44   ` Robin Humble

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=360A12FC.DC0C039F@infopact.nl \
    --to=richardh@infopact.nl \
    --cc=jwelling@engin.umich.edu \
    --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