On behalf of the Linaro Infrastructure team I'm pleased to announce the release of Linaro Image Tools 0.4.4.
Linaro Image Tools offer a set of tools for use with Linaro images.
Highlights of this release: * Support for EfikaMX boards has been added * Support for i.MX53 LOCO board has been added * Support for SMDKV310 board has been added * Usage of sudo has been made optional * Changes to partition alignment * The original boot script is stored in the boot partition * Improvements to the btrfs support * Support for multiple kernel have been added, in particular for i.MX53, i.MX51 and OMAP4; also properly fixes U8500 * RAM size on Panda has been increased * Support for device tree binaries has been added
The source tarball is available from: https://launchpad.net/linaro-image-tools/trunk/0.4.4
Thanks,
Mattias Backman
Hello.
The ST-Ericsson Snowball has an eMMC that need a first partition of unknown type to make room for some files that the SoC needs in order to boot. We boot up to u-boot here, and then proceeds either to the internal eMMC or to the SD card, in both cases with the standard boot and root partitions as created by Linaro-Media-Create.
When creating images, this first partition is needed for the option --image_file, but should not be created for the option --mmc.
We'd like to use the --mmc option to distinguish between these two cases: 3 partitions vs. 2 partitions.
Some time ago however, I heard a discussion about removing the -mmc option?
Alternatives:
1) The --mmc option stays and keeps it semantics. We depend on it as a distinguisher. 2) The --mmc option goes away as we know it, but just drops its parameter and is from now on used as a distinguisher for the two cases (I am assuming that others can have similar needs) 3) The --mmc option goes away, and --dev <device> gets a second, user-defined option --dev <device> <whatever>
BR, Tony Mansson
On 3 May 2011 09:32, Tony MANSSON tony.xpt.mansson@stericsson.com wrote:
The ST-Ericsson Snowball has an eMMC that need a first partition of unknown type to make room for some files that the SoC needs in order to boot. We boot up to u-boot here, and then proceeds either to the internal eMMC or to the SD card, in both cases with the standard boot and root partitions as created by Linaro-Media-Create.
When creating images, this first partition is needed for the option --image_file, but should not be created for the option --mmc.
This sounds like you would end up with different results from: * using "--mmc" to write directly to a card * using "--image_file" and then copying the image to card with dd
That would be very confusing and a bad idea I think, but perhaps I'm misunderstanding?
-- PMM
On Tue, May 3, 2011 at 10:32 AM, Tony MANSSON tony.xpt.mansson@stericsson.com wrote:
I think that this is what you mean: https://bugs.launchpad.net/linaro-image-tools/+bug/744449 and would let l-m-c only create images with the option of writing it to mmc.
The support for different SD layouts in hwpacks in in this spec which I'll be working on now: https://wiki.linaro.org/Platform/Specs/11.05/HardwarePacksV2. At least I guess the proposed field partition_layout would support what you want to do.
Thanks,
Mattias
On Tue, May 03, 2011, Tony MANSSON wrote:
We'd like to use the --mmc option to distinguish between these two cases: 3 partitions vs. 2 partitions.
(This would be counter-intuitive as other pointed out)
For now, until Hwpackv2 are implemented, you could propose a new flag indicating the image type, or abuse --dev to offer snowball-mmc and snowball-emmc --dev/BoardConfig implementations.