From: Dan Brown <dan_brown@ieee.org>
To: Zeri Virgo <zerivirgo@infocell-its.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [UPDATE] DOCBoot support for NFTL-based DOC2000
Date: Wed, 06 Apr 2005 12:29:07 -0400 [thread overview]
Message-ID: <42540E53.8080109@ieee.org> (raw)
In-Reply-To: <4253F6C2.1080105@infocell-its.com>
Zeri Virgo wrote:
> mtd.type = MTD_NANDFLASH
> mtd.flags = MTD_CLEAR_BITS | MTD_ERASEABLE | MTD_OOB | MTD_ECC
> mtd.size = 67108864 (64M)
> mtd.erasesize = 16384 (16K)
> mtd.oobblock = 512
> mtd.oobsize = 16
> mtd.ecctype = (unknown ECC type - new MTD API maybe?)
> regions = 0
Looks fine.
> This may be useless, but I did a nanddump of the first 0x208000 bytes.
> 0x00 to 0xff -> data
>
> Then each of the following chunks of data (ie, not chunks of ff) are
> preceeded by OOB Data
> (eg,
> OOB Data: 36 7f eb 1f 3b aa ff ff ff ff ff ff ff ff ff ff
> 0x000000200: 0e cd...)
>
> 0x200 to 0x2ff -> data
> 0x400 to 0x43a -> data
> 0x600 to 0x629 -> data
> 0x800 to 0x8ff -> data
> 0xa00 to 0xa75 -> data
>
> Then a large chunk (1144949 bytes)
> 0xc00 to 0x119075 -> data
>
> Some mysterious OOB Data before 0x119200, though no normal data
> following it.
>
> Then the rest is blank.
Sounds right, at first glance. The OOB data actually follows each block
(perhaps that's just a terminology issue :) )
-Dan
next prev parent reply other threads:[~2005-04-06 16:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-29 21:06 [UPDATE] DOCBoot support for NFTL-based DOC2000 Dan Brown
2005-03-31 15:50 ` Zeri Virgo
2005-03-31 20:35 ` Dan Brown
2005-04-01 1:33 ` Zeri Virgo
2005-04-01 2:13 ` Dan Brown
2005-04-04 15:05 ` Zeri Virgo
2005-04-04 18:04 ` Dan Brown
2005-04-05 12:00 ` Zeri Virgo
2005-04-05 19:51 ` Dan Brown
2005-04-06 12:13 ` Zeri Virgo
2005-04-06 12:29 ` Zeri Virgo
2005-04-06 13:12 ` Dan Brown
2005-04-06 14:48 ` Zeri Virgo
2005-04-06 16:29 ` Dan Brown [this message]
2005-04-06 18:23 ` Dan Brown
2005-04-07 14:27 ` Dan Brown
2005-04-07 21:45 ` Zeri Virgo
2005-04-08 15:41 ` Dan Brown
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=42540E53.8080109@ieee.org \
--to=dan_brown@ieee.org \
--cc=linux-mtd@lists.infradead.org \
--cc=zerivirgo@infocell-its.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