public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Ian Campbell <ijc+uboot@hellion.org.uk>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] sunxi_nand_spl: Be smarter about where to look for backup u-boot.bin
Date: Mon, 21 Sep 2015 13:19:04 +0100	[thread overview]
Message-ID: <1442837944.10338.70.camel@hellion.org.uk> (raw)
In-Reply-To: <55FFE8FC.1070309@redhat.com>

On Mon, 2015-09-21 at 13:24 +0200, Hans de Goede wrote:
> Hi,
> 
> On 21-09-15 12:22, Ian Campbell wrote:
> > On Sun, 2015-09-20 at 15:39 -0400, Hans de Goede wrote:
> > > We know when u-boot is written to its own partition, in this case the
> > > layout always is:
> > > 
> > > eb 0 spl
> > > eb 1 spl-backup
> > > eb 2 u-boot
> > > eb 3 u-boot-backup
> > > 
> > > eb: erase-block
> > > 
> > > So if we cannot load u-boot from its primary offset we know exactly
> > > where
> > > to look for it.
> > 
> > Is it worth noting here (or perhaps in a code comment?) that the code
> > currently assumes that the first four ebs are of uniform size?
> 
> The eraseblock size is a property of the nand, given a certain nand chip,
> all eraseblocks on that chip always have the same size.

So they never have "boot erase zones" at either the start or end, which
divide one of the erase zones into more fine-grained sizes?

e.g. it used to be the case with NOR that with, say, a 128KB device you
would have zones of 3x32K, 1x16K, 2x8K or something like that rather than
simply 4x32K.

They don't do this with NAND then?

Ian.

  reply	other threads:[~2015-09-21 12:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-20 19:39 [U-Boot] [PATCH v2] sunxi_nand_spl: Be smarter about where to look for backup u-boot.bin Hans de Goede
2015-09-21 10:22 ` Ian Campbell
2015-09-21 11:24   ` Hans de Goede
2015-09-21 12:19     ` Ian Campbell [this message]
2015-09-21 13:19       ` Hans de Goede
2015-09-21 13:44         ` Ian Campbell

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=1442837944.10338.70.camel@hellion.org.uk \
    --to=ijc+uboot@hellion.org.uk \
    --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