From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC][DFU] Unification of dfu_alt_info alt settings description + command execution
Date: Thu, 18 Jul 2013 06:17:48 +0200 [thread overview]
Message-ID: <201307180617.48259.marex@denx.de> (raw)
In-Reply-To: <51E6715B.3040807@denx.de>
Dear Heiko Schocher,
> Hello Lukasz,
>
> Am 16.07.2013 17:35, schrieb Lukasz Majewski:
> > Dear All,
> >
> > Since DFU usage at u-boot is spreading to different device types (MMC,
> > NAND), file systems, raw partitions, ubi, etc, I think that it is a
> > good moment to unify and structure the form of dfu_alt_info environment
> > variable.
>
> Full Ack!
>
> > Proposed new format for single dfu entity:
> >
> > NAME | Type | Device | Dev_num | Dev_part | FS | start | size |
> >
> > where:
> >
> > Name - name of the alt setting (as seen by dfu-util -l)
> > Type - description of the image (raw, file, img, command [*])
> > Device - physical device on which data are stored (mmc, nand, "-")
> > Dev_num - number of the device - it is possible to store data via DFU
> >
> > on several devices of the same type.
> >
> > Dev_part - number of partitions on the device.
>
> Should this be "number of the partition on the device"
>
> You mean here the mtd partition for storing, right?
>
> > FS - information about file system on the device (fat,
> >
> > ext2/ext4, ubi).
> >
> > start - start offset from the beginning of the Device (byte or LBA
> >
> > number addressed)
> >
> > size - maximal number of blocks to be stored on the Device
> >
> > (expressed with Bytes of LBA number) (protection from
> > overwriting the whole device)
> >
> > Example:
> Maybe dummy questions ...
>
> > NAME | Type | Device | Dev_num | Dev_part | FS | start | size |
> > ----------------------------------------------------------------------
> > u-boot | raw | mmc | 0 | "-" [**] | "-" | 0x80 | 0x100 |
> > uImage | file | mmc | 0 | 2 | ext4 | "-" | "-" |
>
> Is this enough information? Where to store the uImage file on the ext4
> partition?
>
> > root.img | img | mmc | 0 | 5 | "-" | "-" | "-" |
>
> img means here: getting an image and storing it on the mtd partition
> "Dev_part" if start and size are marked with "-", beginning
> on start of the partition?
>
> Wouldn't it be better to use here mtd partition names instead
> numbers for "Dev_part"?
>
> What if "start" and "size" are filled with values for the "Type" "img"?
> Or is this forbidden for the "Type" "img"?
>
> > root.img | raw | mmc | 0 | "-" | "-" | 0x1000| 0x4000|
> >
> > u-boot | raw | nand | 0 | "-" | "-" | 0x100 | 0x100 |
> > uImage | file | nand | 0 | 3 | ubi | "-" | "-" |
>
> s/uImage/rootfs.img ? s/file/img ?
>
> For the FS "ubi" we need to specify, how to burn this into nand.
> I think we have no "ubi format" command.
Try "nand write.trimffs" to write UBI images produced with ubinize .
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-07-18 4:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 15:35 [U-Boot] [RFC][DFU] Unification of dfu_alt_info alt settings description + command execution Lukasz Majewski
2013-07-16 21:27 ` Tormod Volden
2013-07-16 21:46 ` Lukasz Majewski
2013-07-17 10:26 ` Heiko Schocher
2013-07-17 14:34 ` Lukasz Majewski
2013-07-17 17:32 ` Tormod Volden
2013-07-18 5:36 ` Heiko Schocher
2013-07-18 7:13 ` Lukasz Majewski
2013-07-18 4:17 ` Marek Vasut [this message]
2013-07-18 5:16 ` Heiko Schocher
2013-07-18 8:09 ` Wolfgang Denk
2013-07-18 15:10 ` Marek Vasut
2013-07-19 4:45 ` Heiko Schocher
2013-07-19 13:55 ` Marek Vasut
2013-07-18 16:39 ` Tom Rini
2013-07-18 17:30 ` Michael Cashwell
2013-07-18 20:17 ` Lukasz Majewski
2013-07-18 22:33 ` Tom Rini
2013-08-23 10:07 ` Lukasz Majewski
2013-10-31 17:25 ` Lukasz Majewski
2013-10-31 20:32 ` Wolfgang Denk
2013-10-31 21:20 ` Lukasz Majewski
2013-10-31 23:11 ` Wolfgang Denk
2013-11-04 6:52 ` Lukasz Majewski
2013-11-01 6:15 ` Heiko Schocher
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=201307180617.48259.marex@denx.de \
--to=marex@denx.de \
--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