Hi
Another 2014.04 planning blueprint. A trivial two-hour blueprint with great potential for future usage.
A copy of the description:
Currently all boards we are interested in have a working mmc controller. SD specification defines the CID register that contains per-card unique identification numbers. The actual syntax of the register is irrelevant but if made available from the master image could be used to track and identify SD cards in a particular lava installation.
A master image could detect when a post-first-boot image was copied to another card (thus breaking uniqueness of first-boot-uuid). LAVA device manager could track the wear of each card even if it was moved from board to board without explicit notification done manually by the system administrator. The device manager could also track SD card performance as experienced by different devices in different master images. This could be used as basis for additional argument to timeout expressions it dispatcher jobs.
See more (work items) at:
https://blueprints.launchpad.net/lava-master-image-scripts/+spec/master-imag...
Thanks ZK
On Mon, 26 Mar 2012 20:47:15 +0200, Zygmunt Krynicki zygmunt.krynicki@linaro.org wrote:
Hi
Another 2014.04 planning blueprint. A trivial two-hour blueprint with great potential for future usage.
A copy of the description:
Currently all boards we are interested in have a working mmc controller. SD specification defines the CID register that contains per-card unique identification numbers. The actual syntax of the register is irrelevant but if made available from the master image could be used to track and identify SD cards in a particular lava installation.
A master image could detect when a post-first-boot image was copied to another card (thus breaking uniqueness of first-boot-uuid). LAVA device manager could track the wear of each card even if it was moved from board to board without explicit notification done manually by the system administrator. The device manager could also track SD card performance as experienced by different devices in different master images. This could be used as basis for additional argument to timeout expressions it dispatcher jobs.
See more (work items) at:
https://blueprints.launchpad.net/lava-master-image-scripts/+spec/master-imag...
Interesting, I didn't know about that. At the very least, we should get lava-test or something to include it in the metadata about the tests it runs.
Cheers, mwh
linaro-validation@lists.linaro.org