Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] MIPS/MIPS32 tune -> MIPS
Date: Mon, 9 Apr 2012 18:31:06 -0500	[thread overview]
Message-ID: <cover.1334014014.git.mark.hatle@windriver.com> (raw)

The following is in reference to the recent discussion about the mips32
-package- arch changing from mips to mips32.  One of the potential options
was to get rid of the previous "mips" and replace it with the mips32
definition standard.  This patch does just that.

Working with Khem, we have moved the default "mips" (32-bit) tune to be
-march=mips32 based, and produce package with the package arch of "mips".

The side effect of this work is that the prior 'mips' tune was actually
"mips1".  I don't believe that was really desired by anyone, but it is a
change.  Also there is no longer a "mips32" tune, just an include file
that automatically inherits and chooses the "mips" tune.

The following changes since commit 1a82989345fb98becb487d270fd93a5e6dffeb47:

  runqemu-internal: Add console=tty for qemuppc and NFS (2012-04-06 01:12:15 +0100)

are available in the git repository at:
  git://git.pokylinux.org/poky-contrib mhatle/mips-tune
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=mhatle/mips-tune

Mark Hatle (1):
  tune-mips32: Update the default MIPS tuning to be mips32

 meta/conf/machine/include/mips/arch-mips.inc |   13 +++++++++----
 meta/conf/machine/include/tune-mips32.inc    |   24 +-----------------------
 2 files changed, 10 insertions(+), 27 deletions(-)




             reply	other threads:[~2012-04-09 23:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-09 23:31 Mark Hatle [this message]
2012-04-09 23:31 ` [PATCH 1/1] tune-mips32: Update the default MIPS tuning to be mips32 Mark Hatle
2012-04-10 12:35   ` Phil Blundell
2012-04-10 12:37     ` Phil Blundell
2012-04-10  0:14 ` [PATCH 0/1] MIPS/MIPS32 tune -> MIPS Andreas Oberritter
2012-04-10  0:20   ` Mark Hatle

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=cover.1334014014.git.mark.hatle@windriver.com \
    --to=mark.hatle@windriver.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