public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Philippe De Muyter <phdm@macqel.be>
To: gerg@snapgear.com
Cc: linux-m68k@vger.kernel.org, uclinux-dev@uclinux.org,
	Greg Ungerer <gerg@uclinux.org>
Subject: Re: [PATCH] m68knommu: allow ColdFire CPUs to use unaligned accesses
Date: Fri, 8 Jun 2012 12:39:31 +0200	[thread overview]
Message-ID: <20120608103931.GA26964@frolo.macqel> (raw)
In-Reply-To: <1339134180-13630-1-git-send-email-gerg@snapgear.com>

On Fri, Jun 08, 2012 at 03:43:00PM +1000, gerg@snapgear.com wrote:
> From: Greg Ungerer <gerg@uclinux.org>
> 
> All current ColdFire CPUs are able to support unaligned memory accesses.
> So remove the CONFIG_CPU_HAS_NO_UNALIGNED option selection for ColdFire.
> 
> It seems that the current restriction was inherrited from the early non-MMU
> support for the basic 68000 proecssors - which do not support unaligned
> accesses.

It seems that the first ColdFires needed the restriction :

I read in the "MCF5200 ColdFire Family Programmer’s Reference Manual" :

The ColdFire processor default configuration supports word- and
longword-sized operand references on 0-modulo-2 and 0-modulo-4
addresses, respectively. All other references are defined as
misaligned accesses. Any attempt to access a misaligned operand
generates an address-error exception, unless the optional hardware
module for handling misalignment is present. This misalignment
module converts any misaligned operand references into a series
of aligned bus cycles to access the data. The existence of the
misalignment module is implementation-dependent and is documented
in the appropriate ColdFire user’s manual.

Philippe

  parent reply	other threads:[~2012-06-08 10:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-08  5:43 [PATCH] m68knommu: allow ColdFire CPUs to use unaligned accesses gerg
2012-06-08  7:19 ` Geert Uytterhoeven
2012-06-08  9:10   ` Greg Ungerer
2012-06-08 10:39 ` Philippe De Muyter [this message]
2012-06-08 12:19   ` Greg Ungerer
2012-06-08 13:35     ` Philippe De Muyter
2012-06-12  2:25       ` Greg Ungerer
2012-06-12  7:26         ` Philippe De Muyter
2012-06-12 20:27           ` Geert Uytterhoeven
2012-06-13  0:27             ` 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=20120608103931.GA26964@frolo.macqel \
    --to=phdm@macqel.be \
    --cc=gerg@snapgear.com \
    --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