From: Ralf Baechle <ralf@oss.sgi.com>
To: Keith M Wesolowski <wesolows@chem.unr.edu>
Cc: Stockli Reto <stockli@geo.umnw.ethz.ch>, linux-mips@oss.sgi.com
Subject: Re: R10000 SGI O2
Date: Fri, 16 Feb 2001 17:59:02 -0800 [thread overview]
Message-ID: <20010216175902.C2233@bacchus.dhis.org> (raw)
In-Reply-To: <20010213190716.A29070@chem.unr.edu>; from wesolows@chem.unr.edu on Tue, Feb 13, 2001 at 07:07:16PM -0800
On Tue, Feb 13, 2001 at 07:07:16PM -0800, Keith M Wesolowski wrote:
> > For not repeating here what has already been done:
> > Has anyone ever tried the same before and what are the problems to
> > encounter? I will most likely boot from a bootp linux server. Is there a
> > chance that I get a console on my O2 or do I only have a serial
> > connection.
>
> There is no chance whatever that you will get anything. If you want
> to have any chance at all of getting this to work I would recommend
> you ask Harald for his latest patch; it provides some level of support
> for r5k-based IP32 (O2) systems. r10k O2 suffers from the same
> cache-noncoherency problem as r10k I2 does, and to the best of my
> knowledge nobody has ever really tried to even boot one.
>
> Not to discourage you at all...there's just a lot of work to do.
It's really hard work to do. R12000 O2s however should be much easier to
do; the processor feature which causes so much grief in the O2 can be
disabled there.
Ralf
next prev parent reply other threads:[~2001-02-17 2:00 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 [this message]
2001-02-19 8:49 ` Stockli Reto
2001-02-21 6:12 ` Ralf Baechle
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=20010216175902.C2233@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