public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: linux-mtd@lists.infradead.org
Subject: Re: [U-Boot] U-Boot and UBI
Date: Tue, 19 Aug 2008 18:35:23 +0200	[thread overview]
Message-ID: <ly8wut9d4k.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: 1218633636.10489.43.camel@localhost.localdomain

Josh Boyer <jwboyer@linux.vnet.ibm.com> writes:

>> Yes, we should make a u-boot within one block size since flash
>> only guarantees the first one block as bad block free. e.g.,
>> exactly (128KiB - 2KiB) size if OneNAND case.
>> For this, we need to code or size optimization.  If this is
>> solved, we can use flash as bad block free device with UBI.
>
> An alternative to that is to have a very small IPL that loads
> U-Boot to DRAM as the SPL.

Yes; our implementation of such an IPL (for PXA320) can be found
at

   https://www.cvg.de/people/ensc/elito-mobm320-0.0.4.tar.bz2

This allows to jump into an image either located in a 'bootloader'
volume (which contains U-Boot) or in a 'kernel' image.

Latter is faster (by about 3-5 seconds plus the duplicate UBI
scan within U-Boot) which can make a difference as the IPL itself
needs 3.5 seconds to scan a 1GiB NAND :(


> That would require some relocatable support in U-Boot.

Depends on the system resp. how U-Boot was built (e.g. set its
TEXTADDR so that it does not conflict with the IPL).


Enrico

      reply	other threads:[~2008-08-19 16:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-08 18:26 U-Boot and UBI Josh Boyer
2008-08-08 22:58 ` [U-Boot] " Wolfgang Denk
2008-08-11  5:18   ` Kyungmin Park
2008-08-11  6:42     ` Wolfgang Denk
2008-08-11 12:13     ` Josh Boyer
2008-08-11 20:02     ` Stefan Roese
2008-08-12 10:25       ` Kyungmin Park
2008-08-12 11:11         ` Stefan Roese
2008-08-12 23:34           ` Kyungmin Park
2008-08-13 13:20             ` Josh Boyer
2008-08-19 16:35               ` Enrico Scholz [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=ly8wut9d4k.fsf@ensc-virt.intern.sigma-chemnitz.de \
    --to=enrico.scholz@sigma-chemnitz.de \
    --cc=linux-mtd@lists.infradead.org \
    /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