From: Lukasz Majewski <l.majewski@majess.pl>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC][DFU] Unification of dfu_alt_info alt settings description + command execution
Date: Thu, 31 Oct 2013 22:20:10 +0100 [thread overview]
Message-ID: <20131031222010.082d453f@jawa> (raw)
In-Reply-To: <20131031203208.F3B5C3803F1@gemini.denx.de>
Hi Wolfgang,
> Dear Lukasz,
>
> In message <20131031182541.3a3020c6@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>
next prev parent reply other threads:[~2013-10-31 21:20 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
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 [this message]
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=20131031222010.082d453f@jawa \
--to=l.majewski@majess.pl \
--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