public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: u-boot@lists.denx.de, linux-mtd@lists.infradead.org
Cc: arnez@de.ibm.com, haver@vnet.ibm.com
Subject: U-Boot and UBI
Date: Fri, 08 Aug 2008 14:26:56 -0400	[thread overview]
Message-ID: <1218220016.2328.109.camel@localhost.localdomain> (raw)

Hi All,

As has been stated before by various people, IBM has added some form of
UBI support to an older version of U-Boot.  While we would love to be
able to forward port this to the latest version of U-Boot, we have
simply not found the time and don't see that being the case in the near
future.

So as an alternative, I have cleaned up the code slightly and pushed out
a version that applies to U-Boot 1.1.6.  This way there is at least some
form of code release that people can use as a reference.  I am not
pushing this for inclusion into the current U-Boot, as we are well aware
of the need for further adaptation and cleanup.

A few caveats:

- This is a quick forward port from a patched 1.1.4 tree to 1.1.6.  It
compiles for the example board (PowerPC 440EP Bamboo), but that example
code may not actually work due to the differences in how flash was read
between the code bases.  When moving to a newer U-Boot, I highly
recommend using the generic MTD interfaces.

- There might be slight differences in the UBI format that this code
base supports and what is in the upstream Linux kernel.  Comparison of
the data structures in the current kernel would be advised if you are
forward porting.

- There is no write support for UBI in this port.

- The interfaces have two methods of getting scan information.  The
first is having a bit of code that runs before U-Boot do the scan and
pass it.  The second is to have a user/script use the "ubiscan" command
to have U-Boot manually perform the scan itself.  The latter method is
likely more flexible for new boards.

All of that being said, we hope this code is useful as a guide.  I will
certainly answer questions as I can.  If for some unknown reason I find
a massive amount of spare time, I might even try to forward port it, but
that seems unlikely these days.

I would like to thank Frank Haverkamp, Thomas Gleixner, Andreas Arnez,
and Artem Bityutskiy for their work on UBI and the majority of the
U-Boot code we have.

The git tree can be found here:

git fetch git://git.infradead.org/users/jwboyer/u-boot.git ubi

http://git.infradead.org/users/jwboyer/u-boot.git?a=shortlog;h=refs/heads/ubi

josh

             reply	other threads:[~2008-08-08 18:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-08 18:26 Josh Boyer [this message]
2008-08-08 22:58 ` [U-Boot] U-Boot and UBI 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
  -- strict thread matches above, loose matches on Subject: below --
2008-07-18 12:20 U-boot " Nigel Hathaway
2008-07-30 18:00 ` Bernard Blackham
2008-07-31 11:01   ` Nigel Hathaway

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=1218220016.2328.109.camel@localhost.localdomain \
    --to=jwboyer@linux.vnet.ibm.com \
    --cc=arnez@de.ibm.com \
    --cc=haver@vnet.ibm.com \
    --cc=linux-mtd@lists.infradead.org \
    --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