public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Brad Boyer <flar@allandria.com>
To: Luis Alves <ljalvs@gmail.com>
Cc: linux-m68k@vger.kernel.org, uclinux-dev@uclinux.org, gerg@uclinux.org
Subject: Re: [PATCH 1/1] Changes for 68000 code integration.
Date: Fri, 27 Apr 2012 00:33:55 -0700	[thread overview]
Message-ID: <20120427073355.GA28132@cynthia.pants.nu> (raw)
In-Reply-To: <1335481717-8652-1-git-send-email-ljalvs@gmail.com>

On Fri, Apr 27, 2012 at 12:08:37AM +0100, Luis Alves wrote:
> diff --git a/arch/m68k/Kconfig.cpu b/arch/m68k/Kconfig.cpu
> index 8a9c767..2abac0f 100644
> --- a/arch/m68k/Kconfig.cpu
> +++ b/arch/m68k/Kconfig.cpu
> @@ -32,26 +32,33 @@ endchoice
>  
>  if M68KCLASSIC
>  
> -config M68000
> +
> +config M68XXX
>  	bool
>  	select CPU_HAS_NO_BITFIELDS
>  	select CPU_HAS_NO_MULDIV64
>  	select GENERIC_CSUM
>  	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.
> +	  Common features for the first generation of M68K CPUs. It
> +	  includes the original MC68000 and CPU32 core.
> +
>  
>  config MCPU32
>  	bool
> -	select CPU_HAS_NO_BITFIELDS
> +	select M68XXX
>  	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
>  	  System-On-Chip parts, and does not contain a paging MMU.

I believe this misrepresents the CPU32 feature set. According to the old
paper copy I have of the Motorola CPU32 reference manual, the only
unimplemented instructions relative to the 68020 are these:

1) Bit field instructions
2) Module call/return
3) RMW instructions (CAS/CAS2)
4) Coprocessor instructions
5) BCD instructions

The 64 bit MUL and DIV variants are explicitly listed in the instruction set.

The CPU32 is also missing some (but not all) of the addressing modes
which were added with the 68020.

I haven't worked with any of these chips in a long time, but the CPU32
is quite a bit newer and more complicated than a 68000 or 68010. I
did a project based on a 68332 about 15 years ago and still have all
the printed reference manuals for that particular chip.

	Brad Boyer
	flar@allandria.com

  parent reply	other threads:[~2012-04-27  7:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <MC68000 integration>
2012-04-26 23:08 ` [PATCH 1/1] Changes for 68000 code integration Luis Alves
2012-04-27  6:43   ` Greg Ungerer
2012-04-27  6:55     ` Geert Uytterhoeven
2012-04-27  7:33   ` Brad Boyer [this message]
     [not found]     ` <CAGj5WxDCYXOX9Jw2zRxxb0NBJnnKkQTWj03FeY+u35EsfuiHjQ@mail.gmail.com>
2012-04-27 14:16       ` Luis Alves
2012-04-27 14:06   ` Greg Ungerer
2012-04-27 14:30     ` Luis Alves
2012-04-28 13:02       ` Greg Ungerer

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=20120427073355.GA28132@cynthia.pants.nu \
    --to=flar@allandria.com \
    --cc=gerg@uclinux.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=ljalvs@gmail.com \
    --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