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
There are 2 ways to integrate them: 1. Include the git in all the manifest and specify the right hwpack in device.mk and copy it to boot directory from common code.
2. Commit individual configs to each of the board specific repository like device/linaro/origen, specify the same in device.mk and copy it to boot directory from common code.
The advantage of second approach is that we don't need to maintain one more repository and the config will be maintained closely to the device.
Regards, Vishal
Hi, both approaches work for me -- I'd tend to prefer 2. for the reasons you've already mentioned.
ttyl bero
On 17 January 2013 11:34, Vishal Bhoj vishal.bhoj@linaro.org 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
There are 2 ways to integrate them:
- Include the git in all the manifest and specify the right hwpack in
device.mk and copy it to boot directory from common code.
- Commit individual configs to each of the board specific repository like
device/linaro/origen, specify the same in device.mk and copy it to boot directory from common code.
The advantage of second approach is that we don't need to maintain one more repository and the config will be maintained closely to the device.
Regards, Vishal
On 17 January 2013 04:34, Vishal Bhoj vishal.bhoj@linaro.org 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
There are 2 ways to integrate them:
- Include the git in all the manifest and specify the right hwpack in
device.mk and copy it to boot directory from common code.
- Commit individual configs to each of the board specific repository like
device/linaro/origen, specify the same in device.mk and copy it to boot directory from common code.
Seem good to me. You could reuse:
LINARO_BUILD_SPEC=
..and do it like we did the howtos.
The advantage of second approach is that we don't need to maintain one more repository and the config will be maintained closely to the device.
Regards, Vishal
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).
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/confi...
Regards, Vishal
-- Tixy
On Thu, 2013-01-17 at 19:05 +0530, Vishal Bhoj wrote:
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.
As I hoped :-)
This is the format which we have for vexpress: https://github.com/MiloCasagrande/android-hwpacks/blob/master/vexpress/confi...
I'd already looked at that. Hopefully it means when I get some spare time (ha!) I could tidyup vexpress and possibly remove all that boot.scr generation and the extra dummy u-boot we build. (I was put off this before because of the painful process for hacking l-a-m-c.
linaro-android@lists.linaro.org
-
Bernhard Rosenkränzer -
Jon Medhurst (Tixy) -
Vishal Bhoj -
Zach Pfeffer