From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] dfu: dfu and UBI Volumes
Date: Mon, 27 May 2013 16:41:27 -0400 [thread overview]
Message-ID: <20130527204127.GY17119@bill-the-cat> (raw)
In-Reply-To: <7E1B5EF8-454B-4AD4-A49F-D5752EA7036C@antoniou-consulting.com>
On Mon, May 27, 2013 at 07:29:02PM +0300, Pantelis Antoniou wrote:
> Hi
>
> On May 27, 2013, at 7:25 PM, Wolfgang Denk wrote:
>
> > Dear Heiko Schocher,
> >
> > In message <51A30F34.7030603@denx.de> you wrote:
> >>
> >> But how to handle a raw nand partition and a ubi partition on one
> >> nand?
> >>
> >> If ubi is a new dfu interface, somebody must start dfu on u-boot
> >> with "dfu nand .." or "dfu ubi .." dependent on which partition
> >> has to be updated ... before using dfu-util on the host side ...
> >> and start dfu-util for the correct partition...
> >>
> >> This seems not really userfriendly to me ... if I have to use the
> >
> > Indeed, this makes no sense and breaks the whole concept of DFU to be
> > able to download a sinlge firmware image with one, simple command.
> >
> >> Is ubi really a "interface" as nand or mmc ... ?
> >
> > No, it is not. It could be considered a "partition type" at best.
> >
> >>> Looks like it's simple enough; erase (but don't step over the wear counters)
> >>> , write (but skip over the wear counters).
> >>
> >> Yep, or load the complete image in ram, and write it with "ubi write ..."
> >
> > Not "or". When dealing with UBI volumes, then "ubi write" (or the
> > equivalent C API) is the way to go.
> >
> >
>
> I pretty much agree. UBI looks like it's partition type.
>
> BTW, the whole point of DFU is not to store your image in RAM at all.
> There are very few systems that have that much RAM.
This _may_ be the hard part for UBI. When doing raw block writes for
NAND/MMC, we're able to write them out quickly and thus support images
larger than RAM. But for filesystems we don't support that notion in
general for write and so limit ourselves to 8MiB or so files. Fine for
the most part, but not fine for UBI. It's possible that we can support
this on UBI easier than we can on filesystems, but I just don't know.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20130527/2f384bf4/attachment.pgp>
next prev parent reply other threads:[~2013-05-27 20:41 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 16:39 [U-Boot] dfu: dfu and UBI Volumes Heiko Schocher
2013-05-24 16:42 ` Pantelis Antoniou
2013-05-24 17:12 ` Tom Rini
2013-05-26 7:09 ` Heiko Schocher
2013-05-27 7:02 ` Lukasz Majewski
2013-05-27 7:28 ` Heiko Schocher
2013-05-27 7:35 ` Pantelis Antoniou
2013-05-27 7:45 ` Heiko Schocher
2013-05-27 16:25 ` Wolfgang Denk
2013-05-27 16:29 ` Pantelis Antoniou
2013-05-27 20:41 ` Tom Rini [this message]
2013-05-27 21:25 ` Wolfgang Denk
2013-05-27 23:37 ` Tom Rini
2013-05-28 5:50 ` Wolfgang Denk
2013-05-28 15:01 ` Tom Rini
2013-05-28 15:05 ` Pantelis Antoniou
2013-05-28 16:31 ` Benoît Thébaudeau
2013-05-28 16:43 ` Pantelis Antoniou
2013-05-28 16:43 ` Benoît Thébaudeau
2013-05-28 16:53 ` Pantelis Antoniou
2013-05-28 17:23 ` Tom Rini
2013-05-28 21:01 ` Wolfgang Denk
2013-05-28 21:16 ` Tom Rini
2013-05-29 4:35 ` Heiko Schocher
2013-05-29 12:09 ` Tom Rini
2013-05-28 3:42 ` Heiko Schocher
2013-05-28 5:55 ` Wolfgang Denk
2013-05-28 15:35 ` Tom Rini
2013-05-28 4:10 ` Heiko Schocher
2013-05-27 19:21 ` Tom Rini
2013-05-28 4:04 ` Heiko Schocher
2013-05-28 5:58 ` Wolfgang Denk
2013-05-28 6:24 ` Heiko Schocher
2013-05-28 16:00 ` Tom Rini
2013-05-24 18:41 ` Wolfgang Denk
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=20130527204127.GY17119@bill-the-cat \
--to=trini@ti.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