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 15:21:35 -0400 [thread overview]
Message-ID: <20130527192135.GX17119@bill-the-cat> (raw)
In-Reply-To: <51A1B522.2050405@denx.de>
On Sun, May 26, 2013 at 09:09:22AM +0200, Heiko Schocher wrote:
[snip]
> Ah, looking in drivers/dfu/dfu_mmc.c, they use dfu->layout
> for switching between DFU_RAW_ADDR, DFU_FS_FAT, DFU_FS_EXT4...
>
> After all ... should we add a DFU_UBI and add this to
> drivers/dfu/dfu_nand.c?
Yes, I think we should be able to adapt dfu_nand to support raw
(current) and UBI (which will need a little further handling so you can
update per UBI container). In MMC (and there's examples in trats and
am335x_evm) we say <name> ext4/fat/part/raw device#/start_blk part#/end_blk.
I would imagine, but testing and implementation might show a better way,
we do UBI as <name> ubi ubiN volume-name, ie:
rootfs ubi ubi0 rootfs
user ubi ubi0 user-data
and so forth, and augment dfu_nand.c with UBI knowledge, ala dfu_mmc and
fat/ext knowledge.
--
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/32a73a89/attachment.pgp>
next prev parent reply other threads:[~2013-05-27 19:21 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
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 [this message]
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=20130527192135.GX17119@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