On Thu, 18 Jul 2013 13:30:55 -0400 Michael Cashwell <mboa...@prograde.net> wrote:
> On Jul 18, 2013, at 12:39 PM, Tom Rini <tr...@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? > That alt settings in DFU can be strings or numbers was handy to > allow the name to identify the partition. > > -Mike > > _______________________________________________ > U-Boot mailing list > U-Boot@lists.denx.de > http://lists.denx.de/mailman/listinfo/u-boot
signature.asc
Description: PGP signature
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
