android hwpack config support in the build

Registered by vishal on 2012-11-22

Why?
We want to remove the hardcoded data from other components like l-a-m-c and LAVA. These hwpack will provide the necessary meta info needed to set the right bootargs to the build.

Context?
Engineering Builds rework

where will the work get put ?
It will be part of build artifact and will be used by l-a-m-c to flash the image.

Blueprint information

Status:
Complete
Approver:
vishal
Priority:
High
Drafter:
vishal
Direction:
Approved
Assignee:
vishal
Definition:
New
Series goal:
None
Implementation:
Implemented
Milestone target:
milestone icon 13.01
Started by
vishal on 2013-01-21
Completed by
vishal on 2013-01-29

Related branches

Sprints

Whiteboard

[2012/11/22 vishalbhoj] Notes here
[2013/1/15 vishalbhoj] The hwpack config will be stored as config in the boot folder of boot.tar.bz2.
[2013/1/23 vishalbhoj] the linaro-image-tools update to pick a hwpack config from boot tarball is under review. The branch proposed from MP is available here:
https://code.launchpad.net/~vishalbhoj/linaro-image-tools/hwpack-from-boottarball
[2012/1/29 vishalbhoj] The MP will be reviewed and merged by the infrastructure team.

Meta:
Roadmap id: CARD-329
Headline: android builds now support android hwpack
Acceptance: Artifacts from all the builds from android build will include a hwpack needed by the l-a-m-c for flashing the image.

(?)

Work Items

Work items:
Add the git repository containing hwpack templates into manifest: DONE
Add device specific changes to copy the hwpack templates into the boot tarball: DONE
Test the builds with new l-a-m-c tools: DONE

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.