On 17 January 2013 18:57, Jon Medhurst (Tixy) <tixy@linaro.org> wrote:

On Thu, 2013-01-17 at 16:04 +0530, Vishal Bhoj wrote:
> Hi,
>
> I am about to integrate the hwpack support into our android builds.
> Currently the configs are hosted at :
> https://github.com/MiloCasagrande/android-hwpacks

Are they intended to replace the current boot.tar.bz2?

Currently, vexpress puts all the versions of UEFI, U-Boot and
device-trees in that boot tarball, so if that's going, then the vexpress
android-hwpack will need serious modification.

Alternatively, if the current boot tarball is unaffected then that is OK
and the vexpress hwpack is irrelevant as it doesn't provide anything
that is required for users, apart from possibly the 'fat_size: 16'. (I
would need to double check my assertion though if we wanted to delete
the contents of the vexpress config).

The hwpack term is a little confusing here. Its just a config file describing the boot arguments to be used to generate the boot.scr. All the hardcodings from l-a-m-c are moved into the config file and l-a-m-c will use it to create boot.scr. It will not affect existing files in boottarball.

This is the format which we have for vexpress:

https://github.com/MiloCasagrande/android-hwpacks/blob/master/vexpress/config

Regards,

Vishal

--
Tixy