public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Tim Bowman <tbowman@emware.com>
To: mtd mailing list <mtd@infradead.org>
Subject: RPX Classic/Lite and byte ordering
Date: Mon, 02 Apr 2001 14:40:10 -0600	[thread overview]
Message-ID: <3AC8E3AA.3BFCCE50@emware.com> (raw)

Original message:

> I am having trouble with an Embeddded Planet RPX board.  The mtd layer
> seems to be reversing the data by double words.  If I write (then cat)
> some text, every double word is reversed.  I can use a cramfs file
> system, but I have to reverse the dwords myself before writing it to
> flash, then everything works fine.  JFFS and other file systems
> obviously don't work, since the data is written by mtd in the wrong
> order.  I am doing everything on big-endian machines (PowerPC).

I have tried all of the query ordering options in the kernel config, and
even tried changing just the read, and then just the write in
cfi-endian.h to order words and double words, to no avail.  I have the
latest code for both the bk kernel and the cvs mtd.

Eric B. suggested:
"You might want to take a look at .../include/mtd/cfi_endian.h and
be sure you are using __raw_writeb and friends. "

The rpxlite layer seems to be using memcpy_fromio, writeb, writew, etc,
not __raw_writeb.  Should these be replaced with the raw versions?

Finally, could this have something to do with flash interleave?  I am
relatively new at this low-level stuff, but if the interleave is 4 for
the RPX, then I could see how every 4 bytes might be reversed.  The
specific board I am using is a CLCC_E with 8M flash.

Thanks


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

             reply	other threads:[~2001-04-02 20:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-02 20:40 Tim Bowman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-02 20:52 RPX Classic/Lite and byte ordering Tim Bowman
2001-04-03  1:16 ` Brendan J Simon
2001-04-03  0:42   ` mferrell
2001-03-30 17:43 Tim Bowman

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=3AC8E3AA.3BFCCE50@emware.com \
    --to=tbowman@emware.com \
    --cc=mtd@infradead.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