From: John Rigby <jrigby@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ADS5121 NAND driver
Date: Wed, 29 Oct 2008 17:24:09 -0600 [thread overview]
Message-ID: <4908F099.80207@freescale.com> (raw)
In-Reply-To: <20081029231504.0941783420FE@gemini.denx.de>
Wolfgang Denk wrote:
> Dear John Rigby,
>
> In message <1225313050-31063-1-git-send-email-jrigby@freescale.com> you wrote:
>
>> ADS5121 rev4 / MPC5121e rev2 only
>>
>> Only tested with:
>> 2K page size
>> 8 bit device width
>>
>> This controller treats 2K pages as 4 512 byte pages
>> and the hw ecc is over the combined 512 byte main
>> area and the first 7 bytes of the spare area.
>>
>> The hw ecc is stored in the last 9 bytes of the
>> spare area.
>>
>> This all means the the spare area can not be written
>> separately from the main. This means unmodified JFFS2
>> will not work.
>>
>
> Hm... then what exactly is this good for? If we cannot use it with
> the normal Linux code I see little use cases for such a driver?
>
We have gone over this before offline. It works great for UBIFS. It
also works with JFFS2 if you teach JFFS2 to leave the OOB area alone,
though there have been reports that there are still issues.
My 5121 linux tree has the two patches necessary for JFFS2 to work, but
I would recommend using UBIFS.
It is useful in u-boot because you may want to use u-boot to write a
UBIFS image to NAND.
> Best regards,
>
> Wolfgang Denk
>
>
prev parent reply other threads:[~2008-10-29 23:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1225256829-10536-1-git-send-email-jrigby@freescale.com>
2008-10-29 20:44 ` [U-Boot] [PATCH] ADS5121 NAND driver John Rigby
2008-10-29 21:28 ` [U-Boot] [PATCH v2] " Scott Wood
2008-10-29 23:37 ` John Rigby
2008-10-30 9:22 ` Wolfgang Denk
2008-10-31 15:44 ` Scott Wood
2008-10-29 23:15 ` [U-Boot] [PATCH] " Wolfgang Denk
2008-10-29 23:24 ` John Rigby [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=4908F099.80207@freescale.com \
--to=jrigby@freescale.com \
--cc=u-boot@lists.denx.de \
/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