public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Nick Craig-Wood <ncw1@axis.demon.co.uk>
Cc: Paul Symons <PaulS@paradigmgeo.com>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: kernel oops 2.4.24
Date: Wed, 14 Jan 2004 05:27:43 +0000	[thread overview]
Message-ID: <20040114052743.GD23845@redhat.com> (raw)
In-Reply-To: <20040113185948.GA17867@axis.demon.co.uk>

On Tue, Jan 13, 2004 at 06:59:48PM +0000, Nick Craig-Wood wrote:

 > > I am trying to run Gentoo on this hardware, and have had problems from the
 > > start, with respect to compiling things like Gentoo. The hardware is a
 > > little bit of an oddity, because i read that it is classed as i686, yet it
 > > doesn't support the cmov opcode. All my compile optimisations have been at
 > > best i586 as a result.
 > 
 > I wonder if you are thinking of the Nehemiah (the C3 mark 2) rather
 > than the Samuel which is on that board.  As far as I'm aware its only
 > safe to use i386 code and that is what we've been using very
 > succesfully (with a Debian/stable installation).

Samuel (and all other pre-Nehemiah CPUs) can run i586 just fine.
As the original poster said, they're i686 with missing CMOV extension,
which in gcc-speak, is i586.

		Dave


  parent reply	other threads:[~2004-01-14  5:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13 11:44 kernel oops 2.4.24 Paul Symons
2004-01-13 18:59 ` Nick Craig-Wood
2004-01-13 19:13   ` David Rees
2004-01-14  8:23     ` Kernel oopses both 2.4.24 and 2.6.1 Roger Abrahamsson
2004-01-14  5:27   ` Dave Jones [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-14  9:36 kernel oops 2.4.24 Paul Symons

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=20040114052743.GD23845@redhat.com \
    --to=davej@redhat.com \
    --cc=PaulS@paradigmgeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncw1@axis.demon.co.uk \
    /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