linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <w.sang@pengutronix.de>
To: "Albrecht Dreß" <albrecht.dress@arcor.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Weird 5200/mtd-ram problem
Date: Mon, 25 May 2009 23:47:18 +0200	[thread overview]
Message-ID: <20090525214718.GA8152@pengutronix.de> (raw)
In-Reply-To: <1243273283.3328.0@antares>

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


> A word or long copy of 0x0055aaff with U-Boot works fine, but a byte  
> copy filled the whole ram with 0x0000aaaa.  The reason is apparently  
> that the chip is attached to the local bus in 16-bit mode, which is  
> incompatible with byte accesses.  However, the Local Bus doesn't provide 
> "low byte" or "high byte" indicators in non-muxed mode.  How is this 
> supposed to work then?

Hmm, as I feared... we were bitten by this, too:

http://thread.gmane.org/gmane.linux.drivers.mtd/21521

There is no generic solution yet :(

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

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

  parent reply	other threads:[~2009-05-25 21:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-20 14:13 Weird 5200/mtd-ram problem Albrecht Dreß
2009-05-20 14:23 ` Gary Thomas
2009-05-20 19:36   ` Albrecht Dreß
2009-05-20 19:59     ` Gary Thomas
2009-05-20 20:01 ` Wolfram Sang
2009-05-25 17:41   ` Albrecht Dreß
2009-05-25 18:11     ` Wolfgang Denk
2009-05-25 21:47     ` Wolfram Sang [this message]
2009-05-27 19:54       ` [Solved/Patch Question] " Albrecht Dreß
2009-05-28  3:10         ` Jon Smirl

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=20090525214718.GA8152@pengutronix.de \
    --to=w.sang@pengutronix.de \
    --cc=albrecht.dress@arcor.de \
    --cc=linuxppc-dev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).