From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] u-boot wear-levelling?
Date: Wed, 7 Feb 2007 12:42:27 +0100 [thread overview]
Message-ID: <200702071242.28297.sr@denx.de> (raw)
In-Reply-To: <8bf247760702070331u54ebb37cgb41c28a4be080fc2@mail.gmail.com>
On Wednesday 07 February 2007 12:31, Ram wrote:
> Does u-boot nand write support wear levelling techniques?.
No.
> If so, how it is done?.
Not at all.
> Does it matain any information on how many writes have taken place
> to a particular page?.
No.
U-Boot has no fs write support for NAND (like JFFS2 or YAFFS2). The images can
only be written as binary images. It is not intended for very frequent write
access like file systems do. For this you have the fs drivers in Linux.
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk
Office: Kirchenstr. 5, D-82194 Groebenzell, Germany
=====================================================================
prev parent reply other threads:[~2007-02-07 11:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 11:31 [U-Boot-Users] u-boot wear-levelling? Ram
2007-02-07 11:42 ` Stefan Roese [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=200702071242.28297.sr@denx.de \
--to=sr@denx.de \
--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