public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Simon Arlott <simon@arlott.org>
To: Dave Jones <davej@redhat.com>, Kyle McMartin <kyle@mcmartin.ca>,
	Mark de Vries <mark@asphyx.net>,
	linux-kernel@vger.kernel.org
Subject: Re: Which CPU for VIA C7/Esther?
Date: Mon, 12 Feb 2007 23:46:46 +0000	[thread overview]
Message-ID: <45D0FC66.5030205@simon.arlott.org.uk> (raw)
In-Reply-To: <20070212201635.GD10697@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1506 bytes --]

On 12/02/07 20:16, Dave Jones wrote:
> On Mon, Feb 12, 2007 at 02:14:41PM -0500, Kyle McMartin wrote:
>  > On Mon, Feb 12, 2007 at 06:37:38PM +0100, Mark de Vries wrote:
>  > > I've been googeling for about an hour now and can't find an answer to:
>  > > What type of CPU should I select when compiling a recent 2.6 kernel if I
>  > > have a VIA Esther CPU?
>  > 
>  > > stepping        : 9
>  > 
>  > config MVIAC3_2
>  >         bool "VIA C3-2 (Nehemiah)"
>  >         help
>  >           Select this for a VIA C3 "Nehemiah". Selecting this enables usage
>  >           of SSE and tells gcc to treat the CPU as a 686.
>  >           Note, this kernel will not boot on older (pre model 9) C3s.
>  > 
>  > Is the one you want, I believe.
> 
> The C7 doesn't seem to care much which you optimise it for.
> Any of the 686 options should work just fine, but MVIAC3_2 is no
> worse than any of the others.
> 

MVIAC3_2 doesn't enable X86_GOOD_APIC, try M686 (Pentium-Pro) - but that won't enable MMX and SSE (via -march=c3-2).
These CPUs support SSE2 too... there should probably be an option for C7 that passes 686/mmx/sse/sse2 to gcc. (The c3-2 option could even cause gcc to alter code for the C3-2 that's not necessary for the C7, but I've not checked what else gcc does with -march=c3-2).

Also, for the C7 you'll want CRYPTO_DEV_PADLOCK_* (Hardware Crypto Devices, Support for VIA PadLock ACE) and HW_RANDOM_VIA (VIA HW Random Number Generator support).

-- 
Simon Arlott


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 829 bytes --]

  reply	other threads:[~2007-02-12 23:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-12 17:37 Which CPU for VIA C7/Esther? Mark de Vries
2007-02-12 19:14 ` Kyle McMartin
2007-02-12 20:16   ` Dave Jones
2007-02-12 23:46     ` Simon Arlott [this message]
2007-02-12 23:59       ` Dave Jones

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=45D0FC66.5030205@simon.arlott.org.uk \
    --to=simon@arlott.org \
    --cc=6bc04bda904655a1b91hgkso0000m4ev@thunder.lp0.eu \
    --cc=davej@redhat.com \
    --cc=kyle@mcmartin.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@asphyx.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