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 17:59:27 +0800 [thread overview]
Message-ID: <1075975166.28252.72.camel@Gundam> (raw)
In-Reply-To: <1075973239.786.6179.camel@hades.cambridge.redhat.com>
On Thu, 2004-02-05 at 17:27, David Woodhouse wrote:
> On Thu, 2004-02-05 at 17:02 +0800, Li Yang wrote:
> > Search for id:(ff89 ffaa) interleave(2) type(2)
> > Search for id:(ff89 ffaa) interleave(2) type(2)
> > Search for id:(ff89 ffaa) interleave(2) type(2)
> > Search for id:(ff89 ffaa) interleave(2) type(2)
> > Search for id:(ff89 ffaa) interleave(2) type(2)
> > Search for id:(89 aa) interleave(2) type(1)
>
> The 'sharp.c' driver handles four 8-bit chips in parallel. Your probes
> above aren't _looking_ for that. Did you enable the advanced CFI options
> and then disable 4-way interleave?
Oh, yes. I enabled the advanced CFI options, but not the CFI geometry
selection. Because I saw there is a BIG_ENDIAN_BYTE option under it,
maybe I was a little bit too nervous about the endian setting. =) I
will try again without the advanced CFI options.
>
> > MTD jedec_match(): Check fit 0x00000000 + 0x00200000 = 0x00200000
> > MTD jedec_match(): check unlock addrs 0x0555 0x02aa
> > MTD jedec_match(): check ID's disappear when not in ID mode
> > MTD jedec_match(): return to ID mode
> > MTD jedec_probe_chip(): matched device 0x89,0xaa unlock_addrs: 0x0555
> > 0x02aa
> > Found: Intel I28F016S3
> > Flash SIMM: Found 2 x8 devices at 0x0 in 32-bit mode
> > Probe at addr_unlock2(0x00400000 + 0xc0185aac) past the end of the
> > map(0x007fffff)
>
> That's odd too. What is that pointer doing in addr_unlock2? Possibly not
> relevant though.
They are just baffling numbers to me.
--
Li Yang <leoli@motorola.com>
Metrowerks
prev parent reply other threads:[~2004-02-05 9:57 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
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 [this message]
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=1075975166.28252.72.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.