[U-Boot] [RFC][DFU] Unification of dfu_alt_info alt settings description + command execution

[Lukasz Majewski]

Hi Wolfgang,

> Dear Lukasz,
> 
> In message <20131031182541.3a3020c6 at amdc308.digital.local> you wrote:
> > 
> > As a follow up from u-boot's mini-summit at ELCE 2013, I would like
> > to once again share the new format of dfu_alt_info env variable
> > (for those who couldn't attend).
> > 
> > dfu_alt_info_cleanup:
> > 
> >     |---+-------------+-------------+---------+----------------------|
> >     |   | <dev_name>: | <alt_name>, | <type>  | extra
> > params         |
> > |---+-------------+-------------+---------+----------------------|
> > | 1 | mmc0:       | rootfs,     | part;   | -                    |
> > | 2 | mmc0:       | uImage,     | file,   | part, dir;           |
> > | 3 | nand0:      | u-boot.bin, | raw,    | start, size;         |
> > | 4 | mmc0:       | u-boot.bin, | raw,    | start_lba, size_lba; |
> > | 5 | ram0:       | uImage,     | ram,    | start, size;         |
> > | 6 | ubi0:       | kernel0,    | raw;    | -                    |
> > |---+-------------+-------------+---------+----------------------|
> > | 7 | cmd:        | cmd,        | cmd;    | -                    |
> 
> Why can we not have a common format for all media supporting the "raw"
> type?  I mean, why can we not also use "start, size" for mmc?  It
> should be trivial to convert into a LBA number.

I think, that I could do better with this table.

What I have meant, is that the "raw" extra parameters are the same in
both cases. The interpretation of start and size (if they are LBA or
"normal" addresses) depends on the <dev_name>.


> 
> Best regards,
> 
> Wolfgang Denk
> 

Best regards,
Lukasz Majewski
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20131031/3abb1002/attachment.pgp>