public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
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:02:50 +0800	[thread overview]
Message-ID: <1075971769.28245.60.camel@Gundam> (raw)
In-Reply-To: <1075964435.12587.2.camel@imladris.demon.co.uk>

On Thu, 2004-02-05 at 15:00, David Woodhouse wrote:
> On Thu, 2004-02-05 at 11:07 +0800, Li Yang wrote:
> > 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.
> 
> Hmmm. I'd feel happier if you were to identify the 'something' which
> goes wrong. I was just about to remove the sharp driver from the tree on
> the basis that it's obsolete.
XXXXXXXX flash device: 800000 at fe000000
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)
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)
Using word write method
mtd: Giving out device 0 to Flash SIMM
Using XXXXXXXX partition definition
Creating 4 MTD partitions on "Flash SIMM":
0x00000000-0x00600000 : "JFFS"
mtd: partition "JFFS" extends beyond the end of device "Flash SIMM" --
size truncated to 0x400000
mtd: Giving out device 1 to JFFS
0x00600000-0x00700000 : "uImage"
mtd: partition "uImage" is out of reach -- disabled
mtd: Giving out device 2 to uImage
0x00700000-0x00740000 : "u-boot"
mtd: partition "u-boot" is out of reach -- disabled
mtd: Giving out device 3 to u-boot
0x00740000-0x00780000 : "u-boot env"
mtd: partition "u-boot env" is out of reach -- disabled
mtd: Giving out device 4 to u-boot env


> 
> Could it be as simple as disabling the erase suspend?

The Flash SIMM is 8M byte, but it is probed to be 4M only.

-- 
Li Yang <leoli@motorola.com>
Metrowerks

  reply	other threads:[~2004-02-05  9:01 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 [this message]
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=1075971769.28245.60.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