From: Tom Rini <trini@ti.com>
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 18:33:25 -0400 [thread overview]
Message-ID: <51E86D35.7040603@ti.com> (raw)
In-Reply-To: <20130718221752.1d8ae58d@jawa>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/18/2013 04:17 PM, Lukasz Majewski wrote:
> On Thu, 18 Jul 2013 13:30:55 -0400 Michael Cashwell
> <mboards@prograde.net> wrote:
>
>> On Jul 18, 2013, at 12:39 PM, Tom Rini <trini@ti.com> wrote:
>>
>>> uImage | raw | nand | 0 | "kernel" | "-" | "-"
>>> | "-" |
>>>
>>> Since partitions provide start/size.
>>
>> I've got some WIP that pulls the alt info from a GPT partition
>> map on mmc.
>
> Extraction the part of dfu_alt_info from GPT or $partitions env
> variable (as defined at e.g. Trats) is also a good idea.
>
> The best solution would be to produce alt settings information as a
> mix of GPT layout information (extraction of part num, start
> offset, size... any more?) [*] and some predefined dfu_alt_info env
> variable. In this way we can reuse already available code (since
> GPT layout is already in place for most of targets).
>
> But what about mtd parts (Nand/ UBI)? It shall be also doable to
> extract information [*] from it. Am I correct?
Right, we support that today even in DFU.
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJR6G00AAoJENk4IS6UOR1WA9cQAKRC0fOrdoVcQyrqeAzf+ahC
y18UHlFsmS+0fVzJzc0z3m7RiUYNCFEsNMm2JFedss7xgpP7GCwMDLRcLhy4CkEW
m5hjISL/C3pJKoAbCocKcUe4TD53Vmukr+sBPwKUR2N62iRcVYCO0Ved8P/4QXUz
g+Ylc8F6C6pPXxTEi8cn8oigmZzckJqn02AjfhY474uQZvKNezM1eA6uBOAbCugM
RJYjM+AxjOeL4dNYJTQEcmLAqcQPF0KW9yxfbMYi79h09qVJTqZIyvIHVIX4XfUp
E64yh21LhuhEyKxUnMcZbvcn5RQ2CvROY2a121D+hFWCxrnLeumIA49Hz8ilVYBt
1P6qzNotUbciOr9M33pedFOziYua/0Y6Wy4f5sMqYOaCy+qhO9KnaiJe0SkOUYah
XNMZ5tVMOAhCwDhmnmLSDWfZZMl9LBzibzIsw7qPzb/ZYtwA7CEa9WSSwZVw7Zsj
jj0+/j4uis4a4UOwj1E7ui3CgiRLu7ck5vBBTJ1VJlRvdCvBknio2aJ3/ZcJaXjc
U76Aly890n4EfwlclwRpeXVGg2eObsherz6gOuWqmVmjBYuiwQAKiT7X4VnqtWmM
V6yB6VmOKO5Am9GmpaWplep8l1vJgkmWd++3kwR75NgZIgmizwIpRxG56hd+oav8
0MH2gBeO6rZo/WdnJwJS
=IYIY
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-07-18 22:33 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 [this message]
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=51E86D35.7040603@ti.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.