public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: "Phil Endecott" <phil_wueww_endecott@chezphil.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Mention Intel Atom in Kconfig.cpu
Date: Mon, 13 Oct 2008 09:18:48 -0400	[thread overview]
Message-ID: <20081013091848.7dcdaaac@infradead.org> (raw)
In-Reply-To: <87zll8r86h.fsf@basil.nowhere.org>

On Mon, 13 Oct 2008 14:28:06 +0200
Andi Kleen <andi@firstfloor.org> wrote:

> "Phil Endecott" <phil_wueww_endecott@chezphil.org> writes:
> 
> > Am I right in thinking that CONFIG_MCORE2 is the correct choice for
> > an Intel Atom? 
> 
> No, Atom is completely different from a Core2.
> 
> Right now 586 or 686 is a reasonable choice.

actually 586 is completely wrong.

Core2 instruction set with tune=generic is still the best to set.

-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  reply	other threads:[~2008-10-13 13:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-13 10:58 [PATCH] Mention Intel Atom in Kconfig.cpu Phil Endecott
2008-10-13 12:13 ` [PATCH] Mention Intel Atom in Kconfig.cpu (less garbled this time) Phil Endecott
2008-10-13 15:36   ` J.A. Magallón
2008-10-13 12:28 ` [PATCH] Mention Intel Atom in Kconfig.cpu Andi Kleen
2008-10-13 13:18   ` Arjan van de Ven [this message]
2008-10-13 13:30     ` Andi Kleen
2008-10-13 13:30       ` Arjan van de Ven
2008-10-13 13:53         ` Andi Kleen
2008-10-13 14:02         ` Adrian Bunk
2008-10-13 14:17           ` Arjan van de Ven
2008-10-13 19:22             ` Phil Endecott

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=20081013091848.7dcdaaac@infradead.org \
    --to=arjan@infradead.org \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phil_wueww_endecott@chezphil.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox