Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/6][v2] Add some intel-specific tune files, and related fixes
Date: Mon, 07 Nov 2011 14:31:53 -0800	[thread overview]
Message-ID: <4EB85C59.9080905@linux.intel.com> (raw)
In-Reply-To: <cover.1320697346.git.tom.zanussi@intel.com>

On 11/07/2011 12:28 PM, tom.zanussi@intel.com wrote:
> From: Tom Zanussi<tom.zanussi@intel.com>
>
> This patchset adds some new tune files for corei7, ivb, and atom.
>
> The corei7 and atom were build- and boot-tested on sugarbay (with
> corei7-avx), jasperforest (corei7), crownbay, fri2, fishriver (atom).
> The ivb is one I'll be using for new Ivy Bridge development and
> hasn't been tested yet, but will be needed for that.
>
> This patchset also contains a few patches for packages that had build
> problems with the corei7-avx tuning.  The python and gmp packages had
> problems because they tried to execute target code on the host and caused
> illegal instruction errors.  The libzypp failed compilation because of
> the hyphens in the tune name (corei7-avx).
>
> v2: do it using create-pull-request, fix subject on python patch
>
> The following changes since commit 28940eb97d835b45ecbf832f25e94fc1574f25a1:
>    Koen Kooi (1):
>          lighttpd 1.4.29: rename index.html to avoid clashes with DL_DIR
>
> are available in the git repository at:
>
>    git://git.yoctoproject.org/poky-contrib.git tzanussi/newtune-v0
>    http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=tzanussi/newtune-v0
>
Tom,

Thank you, this makes it much easier to pull and merge into the testing 
branch that I work with.

Sau!

> Tom Zanussi (6):
>    tune-corei7: Add tune file for Intel Core i7 machines
>    tune-ivb: Add tune file for Intel Ivy Bridge machines
>    machine/include/tune-atom.inc: add atom-specific settings
>    gmp_5.0.2: Set CC_FOR_BUILD to BUILD_CC
>    libzypp: fix mishandling of hyphenated arches
>    python: skip setup.py 'import check' when cross-compiling
>
>   meta/conf/machine/include/tune-atom.inc            |   26 +++++++++++++++++-
>   meta/conf/machine/include/tune-corei7.inc          |   17 ++++++++++++
>   meta/conf/machine/include/tune-ivb.inc             |   11 ++++++++
>   .../python/setup_py_skip_cross_import_check.patch  |   27 ++++++++++++++++++++
>   meta/recipes-devtools/python/python_2.7.2.bb       |    5 +++
>   meta/recipes-extended/libzypp/libzypp_git.bb       |    8 +++---
>   meta/recipes-support/gmp/gmp_5.0.2.bb              |    3 +-
>   7 files changed, 90 insertions(+), 7 deletions(-)
>   create mode 100644 meta/conf/machine/include/tune-corei7.inc
>   create mode 100644 meta/conf/machine/include/tune-ivb.inc
>   create mode 100644 meta/recipes-devtools/python/python/setup_py_skip_cross_import_check.patch
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>



      parent reply	other threads:[~2011-11-07 22:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-07 20:28 [PATCH 0/6][v2] Add some intel-specific tune files, and related fixes tom.zanussi
2011-11-07 20:28 ` [PATCH 1/6] tune-corei7: Add tune file for Intel Core i7 machines tom.zanussi
2011-11-07 20:28 ` [PATCH 2/6] tune-ivb: Add tune file for Intel Ivy Bridge machines tom.zanussi
2011-11-07 20:28 ` [PATCH 3/6] machine/include/tune-atom.inc: add atom-specific settings tom.zanussi
2011-11-07 20:28 ` [PATCH 4/6] gmp_5.0.2: Set CC_FOR_BUILD to BUILD_CC tom.zanussi
2011-11-07 20:28 ` [PATCH 5/6] libzypp: fix mishandling of hyphenated arches tom.zanussi
2011-11-07 20:28 ` [PATCH 6/6] python: skip setup.py 'import check' when cross-compiling tom.zanussi
2011-11-07 22:31 ` Saul Wold [this message]

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=4EB85C59.9080905@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox