Hello everyone, I start replying from the last email.
On Wed, Dec 5, 2012 at 4:33 PM, Andy Doan <[email protected]> wrote: > > 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 They should have everything as usual: with this kind of hwpack (it is just a configuration file) we are passing parameters that right now are stored in the code of l-a-m-c. Parameters that we are extracting and storing in configuration files. > 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)? In the beginning, and for a while, we will keep the old behavior (no need to pass the hwpack configuration file), but yes, in the future it will be necessary to pass also the hwpack on the command line to l-a-m-c (I think l-a-m-c needs the "dev" target as well, so it should be 5 parameters). So it might be good to start "porting" the jobs/tasks that call l-a-m-c directly. -- Milo Casagrande Infrastructure Engineer Linaro.org <www.linaro.org> │ Open source software for ARM SoCs _______________________________________________ linaro-validation mailing list [email protected] http://lists.linaro.org/mailman/listinfo/linaro-validation
