From: Greg Ungerer <gregungerer@westnet.com.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: gerg@snapgear.com, 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, 08 Jun 2012 19:10:55 +1000 [thread overview]
Message-ID: <4FD1C19F.4020400@westnet.com.au> (raw)
In-Reply-To: <CAMuHMdWO2HsAP1Xe3cPbHAdUZsY4FyzgXFqy1Aud=ThGs2N=Mg@mail.gmail.com>
On 06/08/2012 05:19 PM, Geert Uytterhoeven wrote:
> On Fri, Jun 8, 2012 at 7:43 AM,<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.
>>
>> Signed-off-by: Greg Ungerer<gerg@uclinux.org>
>
> I'll add this to my tree, as it depends on the other
> CPU_HAS_NO_UNALIGNED patches.
Thanks Geert!
Regards
Greg
> --
> 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
> --
> To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2012-06-08 9:11 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 [this message]
2012-06-08 10:39 ` Philippe De Muyter
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=4FD1C19F.4020400@westnet.com.au \
--to=gregungerer@westnet.com.au \
--cc=geert@linux-m68k.org \
--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 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.