From: Li Yang <leoli@motorola.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: jffs2+mtd+big endian problem
Date: 05 Feb 2004 11:07:33 +0800 [thread overview]
Message-ID: <1075950453.12044.7.camel@Gundam> (raw)
In-Reply-To: <1074583969.14499.100.camel@imladris.demon.co.uk>
Thank you. I got it.
In drivers/mtd/chips/sharp.c line 362
There is a hard coded cpu_to_le32 swap, which caused the swap issue.
I have tried to use Jedec_probe instead of sharp driver, but it always
recognizes my sharp flash as Intel flash, they have the same vendor id
and product id. Ugly. And then something goes wrong. So I have to
stick to the obsoleted sharp driver. Thank you for the continued help.
--
Li Yang <leoli@motorola.com>
Metrowerks
next prev parent reply other threads:[~2004-02-05 3:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 8:43 jffs2+mtd+big endian problem Li Yang-r58472
2004-01-19 9:17 ` David Woodhouse
2004-01-19 9:48 ` Joakim Tjernlund
2004-01-19 10:58 ` Li Yang
2004-01-19 11:04 ` David Woodhouse
2004-01-20 4:20 ` Li Yang
2004-01-20 7:32 ` David Woodhouse
2004-02-04 8:11 ` Li Yang
2004-02-05 3:07 ` Li Yang [this message]
2004-02-05 7:00 ` David Woodhouse
2004-02-05 9:02 ` Li Yang
2004-02-05 9:27 ` David Woodhouse
2004-02-05 9:59 ` Li Yang
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=1075950453.12044.7.camel@Gundam \
--to=leoli@motorola.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.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