From: Greg Ungerer <gerg@snapgear.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@vger.kernel.org, uclinux-dev@uclinux.org,
Greg Ungerer <gerg@uclinux.org>
Subject: Re: [PATCH 1/2] m68knommu: create config options for CPU classes
Date: Mon, 6 Jun 2011 11:49:53 +1000 [thread overview]
Message-ID: <4DEC3241.6060807@snapgear.com> (raw)
In-Reply-To: <BANLkTikuR5tNe=CQS9qCOJHGkKUWKmO-rw@mail.gmail.com>
Hi Geert,
On 03/06/11 21:15, Geert Uytterhoeven wrote:
> On Fri, Jun 3, 2011 at 08:43,<gerg@snapgear.com> wrote:
>> From: Greg Ungerer<gerg@uclinux.org>
>>
>> There are 3 families of CPU core types that we support in the m68knommu
>> architecture branch. They are
>>
>> . traditional 68000
>> . CPU32 (which is a 68020 core derivitive without MMU)
>
> derivative ... and without bitfield instructions.
My spelling never was too good :-)
I'll fix up the comment and add mention of bitfields.
>> . ColdFire
>
>> It will be useful going forward to have a CONFIG_ option defined for
>> each type. We already have one for ColdFire (CONFIG_COLDFIRE), so add
>> for the other 2 families, CONFIG_M68000 and CONFIG_MCPU32.
>
> I'm wondering whether it would help to have Kconfig symbols for the
> instruction capabilities as well.
> Then you have to document these capabilities in the kconfig definition only,
> and can use single (e.g.) #ifdef CONFIG_CPU_HAS_BITFIELDS tests everywhere
> else, instead of duplicating the logic at every #ifdef.
Yes, that sounds like a reasonable idea. I won't add them in this patch
though. I'll add it to the bitops.h merge patch - which is the only
one that would be effected/helped by a bitfield Kconfig option right
now.
Thanks
Greg
>> Signed-off-by: Greg Ungerer<gerg@uclinux.org>
>> ---
>> áarch/m68k/Kconfig.nommu | á 52 ++++++++++++++++++++++++++++++++++++++++------
>> á1 files changed, 45 insertions(+), 7 deletions(-)
>>
>> diff --git a/arch/m68k/Kconfig.nommu b/arch/m68k/Kconfig.nommu
>> index fc98f9b..b004dc1 100644
>> --- a/arch/m68k/Kconfig.nommu
>> +++ b/arch/m68k/Kconfig.nommu
>> @@ -14,6 +14,33 @@ config GENERIC_CLOCKEVENTS
>> á á á ábool
>> á á á ádefault n
>>
>> +config M68000
>> + á á á bool
>> + á á á help
>> + á á á á The Freescale (was Motorola) 68000 CPU is the first generation of
>> + á á á á the well known M68K family of processors. The CPU core as well as
>> + á á á á being available as a stand alone CPU was also used in many
>> + á á á á System-On-Chip devices (eg 68328, 68302, etc). It does not contain
>> + á á á á a paging MMU.
>> +
>> +config MCPU32
>> + á á á bool
>> + á á á help
>> + á á á á The Freescale (was then Motorola) CPU32 is a CPU core that is
>> + á á á á based on the 68020 processor. For the most part it is used in
>
> without bitfield instructions.
>
>> + á á á á System-On-Chip parts, and does not contain a paging MMU.
>
> Gr{oetje,eeting}s,
>
> á á á á á á á á á á á á Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> á á á á á á á á á á á á á áá áá -- Linus Torvalds
>
>
>
--
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: gerg@snapgear.com
SnapGear Group, McAfee PHONE: +61 7 3435 2888
8 Gardner Close FAX: +61 7 3217 5323
Milton, QLD, 4064, Australia WEB: http://www.SnapGear.com
next prev parent reply other threads:[~2011-06-06 1:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 6:43 [PATCH 0/2] m68knommu: fix cpu optimization conditionals gerg
2011-06-03 6:43 ` gerg
2011-06-03 6:43 ` [PATCH 1/2] m68knommu: create config options for CPU classes gerg
2011-06-03 11:15 ` Geert Uytterhoeven
2011-06-06 1:49 ` Greg Ungerer [this message]
2011-06-10 3:56 ` Greg Ungerer
2011-06-12 9:36 ` Geert Uytterhoeven
2011-06-23 1:35 ` Greg Ungerer
2011-06-03 6:43 ` [PATCH 2/2] m68k: use kernel processor defines for conditional optimizations gerg
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=4DEC3241.6060807@snapgear.com \
--to=gerg@snapgear.com \
--cc=geert@linux-m68k.org \
--cc=gerg@uclinux.org \
--cc=linux-m68k@vger.kernel.org \
--cc=uclinux-dev@uclinux.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