All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Add Intel Core 2 machine support (prescott and nocona)
Date: Mon, 20 Aug 2007 14:10:15 -0700	[thread overview]
Message-ID: <46CA0337.9050709@gmail.com> (raw)
In-Reply-To: <c384c5ea0708201339j44462d85o286bbb548b256aec@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Leon Woestenberg wrote:
> Hello,
> 
> I would like to add support for Intel's Core 2 processors, in both 32
> and 64 bit mode.
> 
> I am wondering what namespace to use for the PACKAGE ARCHs?
> 
> Given all the options[*], I think "x86-prescott" and "x86_64-nocona"
> are suitable:
> 
> x86_64-prescott= x86_32-core = x86_32-core2
> x86_64-nocona = x86_64-core2
> 
> The naming is a bit to long to suite my taste, maybe prescott and
> nocona are enough?
> 
> I would like some input on this before I commit anything and pollute
> the namespace.
> 
> Regards,

I would suggest just add conf/machine/core2.conf and another
conf/machine/tune-core2.inc file to have the special gcc flags.  I would
not add it as a separate arch but stick with x86. To me it sounds more
confusing to have x86 and core separated out into two different basic
arches.

Just my 2 cents.

- -Khem

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGygM3HnJKy6V6em4RAnk4AJ0Xw4JlBqos/8xA60x59GkAbOYvhwCffGm+
AMhMc3UVpCmd1qTCmlVT570=
=ES0x
-----END PGP SIGNATURE-----



  reply	other threads:[~2007-08-20 21:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-20 20:39 Add Intel Core 2 machine support (prescott and nocona) Leon Woestenberg
2007-08-20 21:10 ` Khem Raj [this message]
2007-08-20 21:52   ` Leon Woestenberg
2007-08-21  8:04     ` Richard Purdie
2007-08-22 17:59       ` Leon Woestenberg
2007-08-22 18:03         ` Leon Woestenberg

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=46CA0337.9050709@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-devel@lists.openembedded.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.