From: Ralf Baechle <ralf@oss.sgi.com>
To: <nick@snowman.net>
Cc: cgut@calpoly.edu, linux-mips@oss.sgi.com
Subject: Re: Linux on Origin 200 (newbie)
Date: Wed, 21 Feb 2001 07:46:38 +0100 [thread overview]
Message-ID: <20010221074638.B7335@bacchus.dhis.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0102202007480.19261-100000@ns>; from nick@snowman.net on Tue, Feb 20, 2001 at 08:08:03PM -0500
On Tue, Feb 20, 2001 at 08:08:03PM -0500, nick@snowman.net wrote:
> Yes. It may or may not work . It does not work on my O200.
Latest theory is that we have a problem which is related to different
versions of various chips of the system. When it's actually running on
an Origin 200 / 2000 then it's also very reliable.
Aside of that the current list of open bugs for the Origin 200 / 2000 is:
- we don't have FPU emulation code
- the performance of the ioc3-eth driver is weak to say the least
- ioc3-eth doesn't handle autonegotiation correctly
- the binary compatibility code for running 32-bit apps is less than perfect.
- we crash on systems with more than 64 processors. Yes dudes, that's
tested on real world hardware :-)
Ralf
WARNING: multiple messages have this Message-ID (diff)
From: Ralf Baechle <ralf@oss.sgi.com>
To: nick@snowman.net
Cc: cgut@calpoly.edu, linux-mips@oss.sgi.com
Subject: Re: Linux on Origin 200 (newbie)
Date: Wed, 21 Feb 2001 07:46:38 +0100 [thread overview]
Message-ID: <20010221074638.B7335@bacchus.dhis.org> (raw)
Message-ID: <20010221064638.vYmk04aY53cBFCrPLHk0j8AQzeiEXKt9o4qCc7mhkgs@z> (raw)
In-Reply-To: <Pine.LNX.4.21.0102202007480.19261-100000@ns>; from nick@snowman.net on Tue, Feb 20, 2001 at 08:08:03PM -0500
On Tue, Feb 20, 2001 at 08:08:03PM -0500, nick@snowman.net wrote:
> Yes. It may or may not work . It does not work on my O200.
Latest theory is that we have a problem which is related to different
versions of various chips of the system. When it's actually running on
an Origin 200 / 2000 then it's also very reliable.
Aside of that the current list of open bugs for the Origin 200 / 2000 is:
- we don't have FPU emulation code
- the performance of the ioc3-eth driver is weak to say the least
- ioc3-eth doesn't handle autonegotiation correctly
- the binary compatibility code for running 32-bit apps is less than perfect.
- we crash on systems with more than 64 processors. Yes dudes, that's
tested on real world hardware :-)
Ralf
next prev parent reply other threads:[~2001-02-21 12:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-18 18:58 redhat 7.0 ppopov
2001-02-20 6:49 ` David Jez
2001-02-20 20:56 ` Ralf Baechle
2001-02-21 0:24 ` Pete Popov
2001-02-21 0:57 ` Linux on Origin 200 (newbie) cgut
2001-02-21 1:03 ` Mike McDonald
2001-02-21 1:08 ` nick
2001-02-21 6:46 ` Ralf Baechle [this message]
2001-02-21 6:46 ` Ralf Baechle
2001-02-21 7:12 ` redhat 7.0 Ralf Baechle
2001-03-07 9:06 ` Carsten Langgaard
2001-03-07 13:01 ` ppopov
2001-03-08 11:13 ` Carsten Langgaard
2001-03-09 18:55 ` David Jez
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=20010221074638.B7335@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=cgut@calpoly.edu \
--cc=linux-mips@oss.sgi.com \
--cc=nick@snowman.net \
/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