From: Ralf Baechle <ralf@linux-mips.org>
To: David Daney <ddaney.cavm@gmail.com>
Cc: linux-mips@linux-mips.org, David Daney <david.daney@cavium.com>,
Jonas Gorski <jogo@openwrt.org>,
"Steven J. Hill" <Steven.Hill@imgtec.com>
Subject: Re: [PATCH 3/3] MIPS: Only set cpu_has_mmips if SYS_SUPPORTS_MICROMIPS
Date: Thu, 27 Jun 2013 01:55:35 +0200 [thread overview]
Message-ID: <20130626235535.GO7171@linux-mips.org> (raw)
In-Reply-To: <1369432450-13583-4-git-send-email-ddaney.cavm@gmail.com>
On Fri, May 24, 2013 at 02:54:10PM -0700, David Daney wrote:
> From: David Daney <david.daney@cavium.com>
>
> As Jonas Gorske said in his patch:
>
> Disable cpu_has_mmips for everything but SEAD3 and MALTA. Most of
> these platforms are from before the micromips introduction, so they
> are very unlikely to implement it.
>
> Reduces an -Os compiled, uncompressed kernel image by 8KiB for
> BCM63XX.
>
> This patch taks a different approach than his, we gate the runtime
> test for microMIPS by the config symbol SYS_SUPPORTS_MICROMIPS.
Sounds like a good approach also for other ASEs.
Applied.
Ralf
prev parent reply other threads:[~2013-06-26 23:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 21:54 [PATCH 0/3] MIPS: Repair some of the microMIPS patches David Daney
2013-05-24 21:54 ` [PATCH 1/3] MIPS: Declare emulate_load_store_microMIPS as a static function David Daney
2013-06-19 21:50 ` Steven J. Hill
2013-06-19 21:50 ` Steven J. Hill
2013-05-24 21:54 ` [PATCH 2/3] MIPS: Don't try to decode microMIPS branch instructions where they cannot exist David Daney
2013-06-19 21:50 ` Steven J. Hill
2013-06-19 21:50 ` Steven J. Hill
2013-05-24 21:54 ` [PATCH 3/3] MIPS: Only set cpu_has_mmips if SYS_SUPPORTS_MICROMIPS David Daney
2013-06-19 21:50 ` Steven J. Hill
2013-06-19 21:50 ` Steven J. Hill
2013-06-26 23:55 ` Ralf Baechle [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=20130626235535.GO7171@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=Steven.Hill@imgtec.com \
--cc=david.daney@cavium.com \
--cc=ddaney.cavm@gmail.com \
--cc=jogo@openwrt.org \
--cc=linux-mips@linux-mips.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.