public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Segmented RAM, big userspace.
Date: Tue, 13 Dec 2011 14:00:18 -0600	[thread overview]
Message-ID: <4EE7AED2.3090508@freescale.com> (raw)
In-Reply-To: <20111213160810.GA27440@build.ihdev.net>

On 12/13/2011 10:08 AM, Sergey Lapin wrote:
> It is possible to flash filesystems in parts, but for this to work
> these are needed to be properly split. This raises a problem of
> bad blocks - writing previous piece might end not where you expect it to
> end, but a few blocks later. Hand-handling this case is too error-prone.

Use a separate partition for each chunk.  Each partition should have
extra space for as many bad blocks as you reasonably anticipate in that
partition.  The start address of each partition is fixed, regardless of
the number of bad blocks in previous partitions.

-Scott

      parent reply	other threads:[~2011-12-13 20:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-13 16:08 [U-Boot] Segmented RAM, big userspace Sergey Lapin
2011-12-13 16:24 ` Wolfgang Denk
2011-12-13 16:51   ` Sergey Lapin
2011-12-13 18:14     ` Wolfgang Denk
2011-12-13 20:00 ` Scott Wood [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=4EE7AED2.3090508@freescale.com \
    --to=scottwood@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