From: Ralf Baechle <ralf@oss.sgi.com>
To: Stockli Reto <stockli@geo.umnw.ethz.ch>
Cc: Keith M Wesolowski <wesolows@chem.unr.edu>, linux-mips@oss.sgi.com
Subject: Re: R10000 SGI O2
Date: Wed, 21 Feb 2001 07:12:09 +0100 [thread overview]
Message-ID: <20010221071209.A7335@bacchus.dhis.org> (raw)
In-Reply-To: <3A90DE28.FCDE8CB8@geo.umnw.ethz.ch>; from stockli@geo.umnw.ethz.ch on Mon, Feb 19, 2001 at 09:49:44AM +0100
Gruezi,
On Mon, Feb 19, 2001 at 09:49:44AM +0100, Stockli Reto wrote:
> Thanks Keith and Ralf for your information on running a R10000 O2 with
> Linux. I knew that the video and sound HW as well as some of the
> machine's graphics features were not supported by any linux drivers,
> because it's even hard on SGI/Irix to find useful documentation about
> this hardware! I guess this is the point why so few developers have
> programmed applications that would take advantage of the very nice
> capabilities of the machine.
You're mixing two completly different things. SGI never released hardware
programming information for the O2 to the general public. The graphics
APIs however have been published and there is a ton more good reasons to
stick with those like those APIs beying consistent beyond just the O2 and
even SGI platforms.
> So, I still would like to contribute something to the implementation of
> Linux on SGI machines and I have this O2 standing on my desk. I have
> installed and maintained some I386 based linux systems, but am not
> really into fixing kernels. As I see there's no kernel that will boot
> rightaway (with or without screen console). Let me know if the situation
> is hopeless or if I can make a step taking a current mips-kernel (any
> specific R10000-patch around there?) and start to consult R10000/ SGI O2
> manuals.
Only the mips64 kernel has R10000 support. Anyway you want to use the
mips64 kernel as an O2 can have more memory than 32-bit kernel can handle.
> It would be nice, but maybe I'm too much on the admin/user side and for
> sure I am not into developing kernels. Anyway, curious I am...
Everybody was a newbie once at a time ...
Ralf
next prev parent reply other threads:[~2001-02-21 12:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-13 16:25 R10000 SGI O2 Stockli Reto
2001-02-14 3:07 ` Keith M Wesolowski
2001-02-17 1:59 ` Ralf Baechle
2001-02-19 8:49 ` Stockli Reto
2001-02-21 6:12 ` Ralf Baechle [this message]
2001-02-22 3:23 ` Soren S. Jorvang
2001-02-23 0:04 ` Ralf Baechle
2001-02-23 0:11 ` Soren S. Jorvang
2001-02-23 1:08 ` Ralf Baechle
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=20010221071209.A7335@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=linux-mips@oss.sgi.com \
--cc=stockli@geo.umnw.ethz.ch \
--cc=wesolows@chem.unr.edu \
/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