All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Hartensveld <richardh@infopact.nl>
To: "William J. Earl" <wje@fir.engr.sgi.com>
Cc: Alex deVries <adevries@engsoc.carleton.ca>,
	Jeremy John Welling <jwelling@engin.umich.edu>,
	linux@cthulhu.engr.sgi.com
Subject: Re: challenge s boots linux
Date: Fri, 25 Sep 1998 00:42:21 +0200	[thread overview]
Message-ID: <360ACACD.5533F8CA@infopact.nl> (raw)
In-Reply-To: 199809241644.JAA13188@fir.engr.sgi.com

William J. Earl wrote:

> Alex deVries writes:
> ...
>  > But, i've been thinking for awhile that an Indigo2 port would be the next
>  > box to target... i suppose there's no harm in looking at both machines
>  > concurrently.
>  >
>  > Getting docs on the Indigo2 would be quite important for a successful
>  > port, though.  That would require SGI's help, and I can see them being a
>  > lot more open to it if we got the Indy completely supported first.
> ...
>
>      Except for the EISA slots, Indigo2 is pretty close to Indy.  They run
> the same IRIX kernel binary.  The graphics are more of an issue, since most
> Indigo2 systems use something other than Newport ("XL") graphics.  It might
> be possible for Linux to get by using the very basic microcode downloaded by
> the PROM for XZ and other microcoded graphics cards, but I have not had time
> to research the interface presented.
>

If i'll get my indigo2 with extreme gfx back to work, i'll see how far i can
come with a kernel that usesa serial terminal for it's output. (no gfx card
needed there).

But first get my crosscompiler to work properly ;]

Richard

  reply	other threads:[~1998-09-24 22:39 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
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 [this message]
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=360ACACD.5533F8CA@infopact.nl \
    --to=richardh@infopact.nl \
    --cc=adevries@engsoc.carleton.ca \
    --cc=jwelling@engin.umich.edu \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=wje@fir.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 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.