From: Juergen Beisert <jbe@pengutronix.de>
To: linux-mtd@lists.infradead.org
Cc: Ravi Vasarla <ravi.vasarla@sasken.com>
Subject: Re: DOC2000 flash: Do I miss something?
Date: Mon, 23 Mar 2009 11:21:21 +0100 [thread overview]
Message-ID: <200903231121.21801.jbe@pengutronix.de> (raw)
In-Reply-To: <022F54DCE6CCCD45A5F9DF0B0B7BFEEB063562407E@EXGMBX01.sasken.com>
Hi,
On Montag, 23. März 2009, Ravi Vasarla wrote:
> Kindly check the DOC2000 driver which is available under -> Device
> Drivers-> Memory Technology Devices (MTD)-> Memory Technology Device (MTD)
> support (MTD [=m])-> NAND Flash Device Drivers (Which has recommanded too).
> The below error message due to the way old doc driver implemented.
Ups. With the new driver it seems to work now. Didn't look into the NAND
submenu, yet.
[...]
DiskOnChip found at 0xd8000
DiskOnChip 2000 responds to DWORD access
Detected 1 chips per floor.
NAND device: Manufacturer ID: 0x98, Chip ID: 0x73 (Toshiba NAND 16MiB 3,3V
8-bit)
ECC error scanning DOC at 0x10000
Found DiskOnChip ANAND Media Header at 0x10000
ECC error scanning DOC at 0x14000
Found DiskOnChip ANAND Media Header at 0x14000
DataOrgID = ANAND
NumEraseUnits = 1020
FirstPhysicalEUN = 4
FormattedSize = 16334848
UnitSizeFactor = 255
Bad block table at page 129, version 0x55
Bad block table at page 161, version 0x55
Found alias of DOC at 0xd8000 to 0xda000
Possible DiskOnChip at 0xe2000 failed TOGGLE test, dropping.
[...]
Looks better now ;-)
Thank you very much.
Regards,
Juergen
next prev parent reply other threads:[~2009-03-23 10:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 7:52 DOC2000 flash: Do I miss something? Juergen Beisert
2009-03-23 9:44 ` Ravi Vasarla
2009-03-23 10:21 ` Juergen Beisert [this message]
2009-03-23 19:29 ` Juergen Beisert
2009-03-24 6:46 ` Ravi Vasarla
2009-03-24 7:00 ` Ravi Vasarla
2009-03-24 12:49 ` Juergen Beisert
2009-03-24 13:07 ` Ravi Vasarla
2009-03-24 14:00 ` Juergen Beisert
2009-03-24 16:03 ` Ravi Vasarla
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=200903231121.21801.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=ravi.vasarla@sasken.com \
/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