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: Wed, 20 May 2009 22:01:35 +0200 [thread overview]
Message-ID: <20090520200135.GB13287@pengutronix.de> (raw)
In-Reply-To: <14558983.1242828785546.JavaMail.ngmail@webmail10.arcor-online.net>
[-- Attachment #1: Type: text/plain, Size: 479 bytes --]
> For the test I created a "pattern file" which is filled with the unsigned
> long 0x0055aaff. Using the Abatron BDI3000, I can write the pattern file to
> the ram and re-read it without problems. The same applies to u-boot (write
> ram via tftp, dump contents).
Does it work with byte, word and long accesses?
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-05-20 20:01 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 [this message]
2009-05-25 17:41 ` Albrecht Dreß
2009-05-25 18:11 ` Wolfgang Denk
2009-05-25 21:47 ` Wolfram Sang
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=20090520200135.GB13287@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).