From: Greg Ungerer <gerg@snapgear.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Philippe De Muyter <phdm@macqel.be>,
Greg Ungerer <gerg@uclinux.org>, <linux-m68k@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] m68k: Use generic strncpy_from_user(), strlen_user(), and strnlen_user()
Date: Fri, 8 Jun 2012 14:14:00 +1000 [thread overview]
Message-ID: <4FD17C08.8030203@snapgear.com> (raw)
In-Reply-To: <m2bokvw9f1.fsf@igel.home>
On 07/06/12 23:14, Andreas Schwab wrote:
> Greg Ungerer<gerg@snapgear.com> writes:
>
>> This strikes me as odd. Maybe this has been wrong all along. I need
>> to check further but in a little testing I did today I think it may
>> well be that all ColdFire support unaligned reads and writes.
>
> The CFPRM doesn't indicate otherwise (the address error exception is
> only documented to be raised for a word index addressing mode).
Yeah, I can't find anything that says otherwise in any of the CPU
specific data sheets either. I suspect the internals of unaligned.h
have just been carried from the original non-mmu 68k support to
ColdFire.
Testing on the ColdFires I have at hand here shows unaligned reads
and writes working on all. And that includes testing with a modified
unaligned.h that allows unaligned accesses.
Geert, I'll put a patch together that changes this over. I'll make
that on top of your recent patch series.
Regards
Greg
------------------------------------------------------------------------
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:[~2012-06-08 4:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 21:33 Geert Uytterhoeven
2012-05-30 3:07 ` Greg Ungerer
2012-05-30 10:22 ` Philippe De Muyter
2012-05-30 11:20 ` Geert Uytterhoeven
2012-05-30 14:04 ` Philippe De Muyter
2012-06-05 20:57 ` Geert Uytterhoeven
2012-06-06 6:31 ` Greg Ungerer
2012-06-06 17:46 ` Geert Uytterhoeven
2012-06-07 11:10 ` Greg Ungerer
2012-06-07 13:14 ` Andreas Schwab
2012-06-08 4:14 ` Greg Ungerer [this message]
2012-06-06 13:44 ` Geert Uytterhoeven
2012-06-06 15:20 ` Philippe De Muyter
2012-05-30 14:42 ` Andreas Schwab
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=4FD17C08.8030203@snapgear.com \
--to=gerg@snapgear.com \
--cc=geert@linux-m68k.org \
--cc=gerg@uclinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=phdm@macqel.be \
--cc=schwab@linux-m68k.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
Powered by JetHome