From: Alice Hennessy <ahennessy@mvista.com>
To: mtd@infradead.org, ahennessy@mvista.com
Subject: Big Endian issues
Date: Tue, 28 Nov 2000 15:44:06 -0800 [thread overview]
Message-ID: <3A244346.12F3235B@mvista.com> (raw)
In-Reply-To: 3A14638F.8EBE29DA@mvista.com
Hello all,
I need some advice regarding my big endian arch (ppc). I am using
cfi_cmdset_0002.c and there is
a built-in assumption that words will be swapped when reading and writing to
a little endian device.
This assumption is present in cfi_build_cmd and in cfi_probe_new_chip. Both
of these (in my configuration)
use map->write32 and map->read32 when dealing with commands and status
words. This seems reasonable.
In dealing with data, however, map->write32 is used in writes but
map->copy_from is used in reads.
So, the assumption I assume is that map->copy_from will also swap bytes.
But in my environment,
map->copy_from (memcpy_fromio) doesn't swap bytes. I don't think it needs to
if we make use of
map->copy_to (memcpy_toio) when writing data (in amd_write_val and in the
immediate data check). In this case, copy_from and copy_to functions just
need to be consistent.
Any opinions? Anyone else get this to work with big endian?
Is a change needed in my memcpy_fromio?
Alice
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2000-11-28 23:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-16 19:41 Big Endian/Little Endian headache in cfi_cmdset_0002.c mark.langsdorf
2000-11-16 22:09 ` Nicolas Pitre
2000-11-16 22:45 ` Alice Hennessy
2000-11-28 23:44 ` Alice Hennessy [this message]
2000-11-29 2:59 ` Big Endian issues Nicolas Pitre
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=3A244346.12F3235B@mvista.com \
--to=ahennessy@mvista.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