All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tom 'spot' Callaway" <tcallawa@redhat.com>
To: sparclinux@vger.kernel.org
Subject: Re: Status of Ross hyperSPARC on linux-2.4.x and linux-2.6.x?
Date: Tue, 13 Jan 2004 20:06:34 +0000	[thread overview]
Message-ID: <1074024394.4990.75.camel@zorak> (raw)
In-Reply-To: <20040113204206.A988@sparky.j-son.org>

On Tue, 2004-01-13 at 13:42, christian@j-son.org wrote:
> Just a little ping for me (and anyone else).. what's the status of the
> linux kernels 2.4 and 2.6 for running Ross' hyperSPARC processors?

The code to deal with HyperSPARCs hasn't changed between 2.4 and 2.6.
There are definitely lurking bugs in the HyperSPARC implementation
(anaconda triggers a hard lock in Aurora). The kernel will boot, but its
probably not overly stable.

I honestly don't think that 2.2 (or older) has these problems resolved,
but rather that they're not as easily exposed.

Peter Jones will undoubtedly correct me if I said anything wrong here,
as he knows more about this than me.

~spot
---
Tom "spot" Callaway <tcallawa(a)redhat*com> LCA, RHCE 
Red Hat Sales Engineer || Aurora SPARC Linux Project Leader

"The author's mathematical treatment of the conception of purpose is
novel and highly ingenious, but heretical and, so far as the present
social order is concerned, dangerous and potentially subversive. Not to
be published." -- Aldous Huxley's "Brave New World"


  reply	other threads:[~2004-01-13 20:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13 19:42 Status of Ross hyperSPARC on linux-2.4.x and linux-2.6.x? christian
2004-01-13 20:06 ` Tom 'spot' Callaway [this message]
2004-01-13 20:06 ` christian
2004-01-13 20:46 ` Wiktor Wodecki
2004-01-13 20:52 ` christian
2004-01-14  1:39 ` Keith M Wesolowski

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=1074024394.4990.75.camel@zorak \
    --to=tcallawa@redhat.com \
    --cc=sparclinux@vger.kernel.org \
    /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.