On 12/05/2012 07:47 AM, Antonio Terceiro wrote:
On Wed, Dec 05, 2012 at 02:24:50PM +0100, Alexander Sack wrote:
On Wed, Dec 5, 2012 at 1:34 PM, Antonio Terceiro
For physical boards, however, currently the partitions corresponding to
those parts are populated directly from the build tarballs
({boot,system,userdata}.tar.bz2 etc). In this case, if the hwpack file
is going to be a new input to this process, we would need to know what
has to be done with that hwpack file.  As I understand from
https://wiki.linaro.org/AndroidHardwarePacksV3, the hwpack file seems to
contain stuff that is going to be used to create u-boot scripts and the
like, right?


On high level, I would guess its just another argument to lamc ... and
then I would expect lamc bails out if it detects an image is of the
new format but we dont pass a hwpack and the other way around (e.g.
you pass hwpack, but the image doesnt announce that it supports the
new format.

My point was: lamc is *only* used for creating a single image file for
fastmodels. For physical boards running master images, the dispatcher
*does not* run lamc at all, what means it should probably mimic
whatever lamc does with the hwpack file

When we have SD muxe, then we might use lamc for all devices, but
until then the dispatcher would have to be taught what to do with the
hwpack file.

Antonio is correct. For our "master devices" which account for probably 90% of our Android jobs, we do our own special stuff with tarballs. So we have options:

1) change nothing - assuming the {boot,system,userdata}.tar.bz2 still have everything. sounds unlikely

2) change our master device logic to do whatever new process is required

3) extend our prebuilt image support to android (we currently only do pre-built images for ubuntu)

Question: with this new hwpack - it sounds like we'll now need to be given 4 parameters (hwpack, boot, system, and userdata)?

_______________________________________________
linaro-validation mailing list
[email protected]
http://lists.linaro.org/mailman/listinfo/linaro-validation

Reply via email to