From: Ralf Baechle <ralf@linux-mips.org>
To: Markos Chandras <markos.chandras@imgtec.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] MIPS: Kconfig: microMIPS and SmartMIPS are mutually exclusive
Date: Tue, 3 Jun 2014 11:34:34 +0200 [thread overview]
Message-ID: <20140603093434.GQ17197@linux-mips.org> (raw)
In-Reply-To: <1401785177-7904-1-git-send-email-markos.chandras@imgtec.com>
On Tue, Jun 03, 2014 at 09:46:17AM +0100, Markos Chandras wrote:
> Warning: the 32-bit microMIPS architecture does not support the `smartmips'
> extension
> arch/mips/kernel/entry.S:90: Error: unrecognized opcode `mtlhx $24'
> [...]
> arch/mips/kernel/entry.S:109: Error: unrecognized opcode `mtlhx $24'
>
> Link: https://dmz-portal.mips.com/bugz/show_bug.cgi?id=1021
> Reviewed-by: Steven J. Hill <Steven.Hill@imgtec.com>
> Signed-off-by: Markos Chandras <markos.chandras@imgtec.com>
> ---
> arch/mips/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig
> index 2fe8e60..ffde3d6 100644
> --- a/arch/mips/Kconfig
> +++ b/arch/mips/Kconfig
> @@ -2063,7 +2063,7 @@ config ARCH_PHYS_ADDR_T_64BIT
> def_bool 64BIT_PHYS_ADDR
>
> config CPU_HAS_SMARTMIPS
> - depends on SYS_SUPPORTS_SMARTMIPS
> + depends on SYS_SUPPORTS_SMARTMIPS && !CPU_MICROMIPS
> bool "Support for the SmartMIPS ASE"
> help
> SmartMIPS is a extension of the MIPS32 architecture aimed at
From a user's perspective that's a bit quirky; a user has to first
disable CPU_MICROMIPS before he can enable CPU_HAS_SMARTMIPS. So I
think this should become a choice statement.
Ralf
WARNING: multiple messages have this Message-ID (diff)
From: Ralf Baechle <ralf@linux-mips.org>
To: Markos Chandras <markos.chandras@imgtec.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] MIPS: Kconfig: microMIPS and SmartMIPS are mutually exclusive
Date: Tue, 3 Jun 2014 11:34:34 +0200 [thread overview]
Message-ID: <20140603093434.GQ17197@linux-mips.org> (raw)
Message-ID: <20140603093434.UJPMnY13rDNndm5WWd6dwi0CpfeUxOnhnKNTr7WZ6gA@z> (raw)
In-Reply-To: <1401785177-7904-1-git-send-email-markos.chandras@imgtec.com>
On Tue, Jun 03, 2014 at 09:46:17AM +0100, Markos Chandras wrote:
> Warning: the 32-bit microMIPS architecture does not support the `smartmips'
> extension
> arch/mips/kernel/entry.S:90: Error: unrecognized opcode `mtlhx $24'
> [...]
> arch/mips/kernel/entry.S:109: Error: unrecognized opcode `mtlhx $24'
>
> Link: https://dmz-portal.mips.com/bugz/show_bug.cgi?id=1021
> Reviewed-by: Steven J. Hill <Steven.Hill@imgtec.com>
> Signed-off-by: Markos Chandras <markos.chandras@imgtec.com>
> ---
> arch/mips/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig
> index 2fe8e60..ffde3d6 100644
> --- a/arch/mips/Kconfig
> +++ b/arch/mips/Kconfig
> @@ -2063,7 +2063,7 @@ config ARCH_PHYS_ADDR_T_64BIT
> def_bool 64BIT_PHYS_ADDR
>
> config CPU_HAS_SMARTMIPS
> - depends on SYS_SUPPORTS_SMARTMIPS
> + depends on SYS_SUPPORTS_SMARTMIPS && !CPU_MICROMIPS
> bool "Support for the SmartMIPS ASE"
> help
> SmartMIPS is a extension of the MIPS32 architecture aimed at
next prev parent reply other threads:[~2014-06-03 9:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 8:46 [PATCH] MIPS: Kconfig: microMIPS and SmartMIPS are mutually exclusive Markos Chandras
2014-06-03 8:46 ` Markos Chandras
2014-06-03 9:34 ` Ralf Baechle [this message]
2014-06-03 9:34 ` Ralf Baechle
2014-06-03 9:45 ` Markos Chandras
2014-06-03 9:45 ` Markos Chandras
2014-06-03 11:18 ` Maciej W. Rozycki
2014-06-03 12:24 ` Ralf Baechle
2014-06-03 13:56 ` Maciej W. Rozycki
2014-07-21 7:46 ` [PATCH v2] MIPS: Kconfig: Add choice symbol to select microMIPS or SmartMIPS Markos Chandras
2014-07-21 7:46 ` Markos Chandras
2014-10-08 13:28 ` Markos Chandras
2014-10-08 13:28 ` Markos Chandras
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=20140603093434.GQ17197@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=markos.chandras@imgtec.com \
/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