On 31 July 2014 14:44, Ryan Harkin ryan.harkin@linaro.org wrote:
Hi there,
Do any of you fine people fancy talking to Liam at ARM about how to get a new board set up in LAVA and about what he has to do?
You can go direct to him or I can loop you into the email chain if you let me know who to put in the firing line ;-)
The linaro-validation mailing list is the best place: Linaro Validation linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation.
Hi Ryan, apologies I know you’re probably not the right person, but I’m hoping you can put us in contact with the right guy.
... mailing list.
What I wanted to know (any maybe use TC2 as an example) is what s/w is required to me running on a target platform for LAVA to work?
Do you need Linux running, do you need DVFS, power gating supported etc.
LAVA being written by Linaro is heavily based around the Linux kernel, so a kernel image with a CI loop outside LAVA to build new kernels is going to be the first thing. DVFS is not required, unless if the test writer (you) is going to want results relating to DVFS. Similar with power gating. Hardware wise, a serial connection is absolute - and it needs to not be interrupted or cause bootloader interference when the board is hard reset remotely. (LAVA will pull the power without warning and without using any on-board support from time to time. The board must react smoothly to these resets.) If all you are doing is booting a kernel, that is all that LAVA stipulates. To do more complex testing, some amount of writeable media connectivity, working ethernet support, a distribution with POSIX compatibility and a command line shell are going to be useful. LAVA developers don't write the tests for the boards in LAVA, those will need to be designed and tested by whoever wants the test results. Everything else that may become necessary is down to what tests need to run on the board.
Hi Liam,
If I understand correctly, you’re asking what needs to be on the target device.
For Versatile Express platforms we have usually run them as what we call “LAVA Master Image” type devices. What this essentially means is that there is a known good bootable image and rootfs on some external storage. Test images are then deployed to test boot and test rootfs partitions by LAVA. Look in git://git.linaro.org/lava/master-image-scripts.git to see how we create master images, and look for the lava-partiton-disk script which gets run the first time a master image is booted.
If your device supports TFTP boot, then all that needs to happen is that you create the boot stanza in the appropriate device config. Look in git://git.linaro.org/lava/lava-lab.git and look under validation.linaro.org/lava/device-types/wg.conf for an example (that one is for Juno).
I’ve copied in Dean and Basil from ARM who have a lot of in-house experience with deploying devices into LAVA.
Thanks
Dave
On 31 Jul 2014, at 15:02, Neil Williams neil.williams@linaro.org wrote:
On 31 July 2014 14:44, Ryan Harkin ryan.harkin@linaro.org wrote:
Hi there,
Do any of you fine people fancy talking to Liam at ARM about how to get a new board set up in LAVA and about what he has to do?
You can go direct to him or I can loop you into the email chain if you let me know who to put in the firing line ;-)
The linaro-validation mailing list is the best place: Linaro Validation linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation.
Hi Ryan, apologies I know you’re probably not the right person, but I’m hoping you can put us in contact with the right guy.
... mailing list.
What I wanted to know (any maybe use TC2 as an example) is what s/w is required to me running on a target platform for LAVA to work?
Do you need Linux running, do you need DVFS, power gating supported etc.
LAVA being written by Linaro is heavily based around the Linux kernel, so a kernel image with a CI loop outside LAVA to build new kernels is going to be the first thing. DVFS is not required, unless if the test writer (you) is going to want results relating to DVFS. Similar with power gating. Hardware wise, a serial connection is absolute - and it needs to not be interrupted or cause bootloader interference when the board is hard reset remotely. (LAVA will pull the power without warning and without using any on-board support from time to time. The board must react smoothly to these resets.) If all you are doing is booting a kernel, that is all that LAVA stipulates. To do more complex testing, some amount of writeable media connectivity, working ethernet support, a distribution with POSIX compatibility and a command line shell are going to be useful. LAVA developers don't write the tests for the boards in LAVA, those will need to be designed and tested by whoever wants the test results. Everything else that may become necessary is down to what tests need to run on the board.
--
Neil Williams
neil.williams@linaro.org http://www.linux.codehelp.co.uk/
linaro-validation mailing list linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation
Hi Dave,
Alan informed me about it and I am liasing with Liam now. Will definitely come back if any specific help needed from LAVA team for Liam's requirements.
Thanks Basil Eljuse...
-----Original Message----- From: Dave Pigott [mailto:dave.pigott@linaro.org] Sent: 01 August 2014 10:30 To: Liam Dillon Cc: ryan.harkin@linaro.org; Liam Dillon; Linaro Validation; Dean Arnold; Basil Eljuse Subject: Re: [Linaro-validation] LAVA and s/w requirements
Hi Liam,
If I understand correctly, you're asking what needs to be on the target device.
For Versatile Express platforms we have usually run them as what we call "LAVA Master Image" type devices. What this essentially means is that there is a known good bootable image and rootfs on some external storage. Test images are then deployed to test boot and test rootfs partitions by LAVA. Look in git://git.linaro.org/lava/master-image-scripts.git to see how we create master images, and look for the lava-partiton-disk script which gets run the first time a master image is booted.
If your device supports TFTP boot, then all that needs to happen is that you create the boot stanza in the appropriate device config. Look in git://git.linaro.org/lava/lava-lab.git and look under validation.linaro.org/lava/device-types/wg.conf for an example (that one is for Juno).
I've copied in Dean and Basil from ARM who have a lot of in-house experience with deploying devices into LAVA.
Thanks
Dave
On 31 Jul 2014, at 15:02, Neil Williams neil.williams@linaro.org wrote:
On 31 July 2014 14:44, Ryan Harkin ryan.harkin@linaro.org wrote:
Hi there,
Do any of you fine people fancy talking to Liam at ARM about how to get a new board set up in LAVA and about what he has to do?
You can go direct to him or I can loop you into the email chain if you let me know who to put in the firing line ;-)
The linaro-validation mailing list is the best place: Linaro Validation linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation.
Hi Ryan, apologies I know you're probably not the right person, but I'm hoping you can put us in contact with the right guy.
... mailing list.
What I wanted to know (any maybe use TC2 as an example) is what s/w is required to me running on a target platform for LAVA to work?
Do you need Linux running, do you need DVFS, power gating supported etc.
LAVA being written by Linaro is heavily based around the Linux kernel, so a kernel image with a CI loop outside LAVA to build new kernels is going to be the first thing. DVFS is not required, unless if the test writer (you) is going to want results relating to DVFS. Similar with power gating. Hardware wise, a serial connection is absolute - and it needs to not be interrupted or cause bootloader interference when the board is hard reset remotely. (LAVA will pull the power without warning and without using any on-board support from time to time. The board must react smoothly to these resets.) If all you are doing is booting a kernel, that is all that LAVA stipulates. To do more complex testing, some amount of writeable media connectivity, working ethernet support, a distribution with POSIX compatibility and a command line shell are going to be useful. LAVA developers don't write the tests for the boards in LAVA, those will need to be designed and tested by whoever wants the test results. Everything else that may become necessary is down to what tests need to run on the board.
--
Neil Williams
neil.williams@linaro.org http://www.linux.codehelp.co.uk/
linaro-validation mailing list linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590 ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782
linaro-validation@lists.linaro.org
-
Basil Eljuse -
Dave Pigott -
Neil Williams