All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Albrecht Dreß" <albrecht.dress@arcor.de>
To: linuxppc-dev@lists.ozlabs.org
Subject: Re: Problem with memcpy on ppc8536
Date: Fri, 19 Jun 2009 19:28:12 +0200	[thread overview]
Message-ID: <1245432500.3294.0@antares> (raw)
In-Reply-To: <4A3BC58A.7050408@missinglinkelectronics.com> (from lorenz@missinglinkelectronics.com on Fri Jun 19 19:06:18 2009)

[-- Attachment #1: Type: text/plain, Size: 717 bytes --]

Am 19.06.09 19:06 schrieb(en) Lorenz Kolb:
> Could you please try the following patch, I am quite sure that  
> checking for > 4 was accidentially done within io.c instead of >= 4  
> as if it's 4 we still can copy a 32-bit word. Some hardware might not  
> be happy about 8-bit accesses...

I submitted the same patch a while ago, see  
<http://lists.ozlabs.org/pipermail/linuxppc-dev/2009-May/072582.html>  
and  
<http://lists.ozlabs.org/pipermail/linuxppc-dev/2009-June/073065.html>,  
maybe you can add a tested/revied for it?

If it is a problem with *byte* accesses, you might want to have a look  
at  
<http://lists.ozlabs.org/pipermail/linuxppc-dev/2009-June/072903.html>.

Best, Albrecht.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2009-06-19 17:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <71DEA556544D7A4F9C6848402D8184340C4A13__24467.8549039692$1245370891$gmane$org@usi01.ultsol.local>
2009-06-19 17:04 ` Problem with memcpy on ppc8536 Lorenz Kolb
2009-06-19 17:06 ` Lorenz Kolb
2009-06-19 17:28   ` Albrecht Dreß [this message]
2009-06-19 17:51   ` Wolfram Sang
2009-06-18 20:33 Fahd Abidi
2009-06-19  4:42 ` Liu Dave-R63238

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=1245432500.3294.0@antares \
    --to=albrecht.dress@arcor.de \
    --cc=linuxppc-dev@lists.ozlabs.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.