From: Chuanhong Guo <gch981213@gmail.com>
To: Felix Matouschek <felix@matouschek.org>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>, linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd: spinand: Add support for XTX XT26G0xA
Date: Thu, 7 Apr 2022 15:09:43 +0800 [thread overview]
Message-ID: <CAJsYDVJ7e4zagG9Yvu5r8dQn++ta9TpetC6YHzq4S-GBFEBABQ@mail.gmail.com> (raw)
In-Reply-To: <c1387c1949a8ec705116f5ee8a73fa35979aa196.camel@matouschek.org>
Hi!
On Thu, Apr 7, 2022 at 12:20 AM Felix Matouschek <felix@matouschek.org> wrote:
> The data-sheet says that only offsets 801H to 807H can be used for user
> data and are not covered by ECC (offset 800H is reserved for the bad
> block mark).
>
> The remaining 16 bytes from offset 830H to 83FH are read-only when ECC
> is enabled, so they are of no use? Can you please advise if there is
> something I can change?
According to page 30 of the datasheet[0], the 64Byte OOB layout is:
8 bytes: OOB not protected by ECC
40 bytes: OOB protected by ECC
16 bytes: ECC parity data
so your OOB layout should be:
ECC:
region->offset = 48;
region->length = 16;
Free:
/* Reserve 1 byte for the BBM. */
region->offset = 1;
region->length = 47;
[0]: https://pese.oss-cn-shenzhen.aliyuncs.com/pdfs/2005251034_XTX-XT26G01AWSEGA_C558841.pdf
--
Regards,
Chuanhong Guo
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2022-04-07 7:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 21:29 [PATCH] mtd: spinand: Add support for XTX XT26G0xA Felix Matouschek
2022-04-04 8:41 ` Miquel Raynal
2022-04-06 16:16 ` Felix Matouschek
2022-04-07 7:09 ` Chuanhong Guo [this message]
2022-04-07 7:50 ` Miquel Raynal
2022-04-08 16:22 ` Felix Matouschek
-- strict thread matches above, loose matches on Subject: below --
2021-07-02 19:52 Felix Matouschek
2021-12-22 11:27 ` Felix Matouschek
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=CAJsYDVJ7e4zagG9Yvu5r8dQn++ta9TpetC6YHzq4S-GBFEBABQ@mail.gmail.com \
--to=gch981213@gmail.com \
--cc=felix@matouschek.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.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 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.