From: Brendan J Simon <brendan.simon@bigpond.com>
To: mtd <mtd@infradead.org>
Subject: MTD: linux-2.4.0-test9 on a PowerPC board.
Date: Wed, 24 Jan 2001 17:30:31 +1100 [thread overview]
Message-ID: <3A6E7687.9070200@bigpond.com> (raw)
My company has a custom PowerPC board with a DOC2000 (8MB) on it. I am
trying to get linux-2.4.0-test9 running on it with the MTD drivers. We
think the DOC was detected initially but it seems that NFTL media header
has been blown away. I think this happened when we tried to write to it
or format the device.
Trying to debug things we have noticed that some of the data returned
has the bytes swapped. It seems the NUM ERASE UNITS is returning 0xFA03
where as it should be returning 0x03FA. It looks like an endian
problem. Is the DOC code endian neutral ?? Will the endian problems be
rampant throughout the code or will it be confined to a few places ??
Has anyone used a DOC on a PowerPC processor or other big endian
architecture ??
Thanks for any help,
Brendan Simon.
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next reply other threads:[~2001-01-25 6:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-24 6:30 Brendan J Simon [this message]
2001-01-25 8:54 ` MTD: linux-2.4.0-test9 on a PowerPC board David Woodhouse
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=3A6E7687.9070200@bigpond.com \
--to=brendan.simon@bigpond.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