All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Justin Carlson <justin@cs.cmu.edu>
Cc: Carsten Langgaard <carstenl@mips.com>, linux-mips@oss.sgi.com
Subject: Re: 64-bit kernel
Date: Wed, 19 Jun 2002 11:32:44 +0200	[thread overview]
Message-ID: <20020619113244.B22048@dea.linux-mips.net> (raw)
In-Reply-To: <1024416198.1166.1.camel@xyzzy.rlson.org>; from justin@cs.cmu.edu on Tue, Jun 18, 2002 at 09:03:18AM -0700

On Tue, Jun 18, 2002 at 09:03:18AM -0700, Justin Carlson wrote:

> On Tue, 2002-06-18 at 05:33, Carsten Langgaard wrote:
> > I don't know if anymore has a interest in the 64-bit kernel, but I just
> > found this bug (see patch below).
> > It would be nice to know, how many are interested in the 64-bit kernel
> > and who actually got something running.
> > So please rise you voice.
> 
> Been running 64-bit stuff here, but nothing even remotely fpu intensive.
> It's quite possible we'd never run into this case.

At this time probably most 64-bit kernels are running on a certain 64-bit
CPU with it's hardware fp disabled so nobody ever saw this one.

  Ralf

  reply	other threads:[~2002-06-19  9:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-18 12:33 64-bit kernel Carsten Langgaard
2002-06-18 16:03 ` Justin Carlson
2002-06-19  9:32   ` Ralf Baechle [this message]
2002-06-19 11:07     ` Carsten Langgaard
2002-06-19 11:13       ` Ralf Baechle
2002-06-18 17:52 ` Jun Sun
2002-06-19  9:01 ` Ralf Baechle
2002-06-19  9:28 ` Ralf Baechle
  -- strict thread matches above, loose matches on Subject: below --
2002-08-06 12:05 Carsten Langgaard
2002-08-06 23:14 ` 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=20020619113244.B22048@dea.linux-mips.net \
    --to=ralf@oss.sgi.com \
    --cc=carstenl@mips.com \
    --cc=justin@cs.cmu.edu \
    --cc=linux-mips@oss.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.