Send Lava-devel mailing list submissions to
        lava-devel@lists.lavasoftware.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.lavasoftware.org/mailman/listinfo/lava-devel
or, via email, send a message with subject or body 'help' to
        lava-devel-request@lists.lavasoftware.org

You can reach the person managing the list at
        lava-devel-owner@lists.lavasoftware.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Lava-devel digest..."


Today's Topics:

   1. Integration of a new device (Marcel Trattner)


----------------------------------------------------------------------

Message: 1
Date: Fri, 4 Dec 2020 10:50:08 +0000
From: Marcel Trattner <marcel.trattner@expleogroup.com>
To: "Lava-devel@lists.lavasoftware.org"
        <Lava-devel@lists.lavasoftware.org>
Cc: Alexander Wyron Wachtberger
        <alexander-wyron.wachtberger@expleogroup.com>,  Vladimir Schmidt
        <vladimir.schmidt@expleogroup.com>
Subject: [Lava-devel] Integration of a new device
Message-ID:
        <AM9PR10MB4295B7516795BD7B514C2DF7E5F10@AM9PR10MB4295.EURPRD10.PROD.OUTLOOK.COM>

Content-Type: text/plain; charset="us-ascii"

Dear LAVA-Team,

We have only recently started to use LAVA in a new project and we are now at the point of integrating a new device. As I have read in the documentation that this is the hardest part I would like to ask for some advice where to start and what to especially look out for.

The current state is that LAVA, as a master and one slave is running in two Docker containers by using the example of the following Github repository:

https://github.com/kernelci/lava-docker

After reading the documentary extensively and trying things out with qemu I'd like to try and integrate the following device:

https://www.lantronix.com/products/sa8155p-automotive-development-platform/

Our plan so far would be:
Since it has a Snapdragon processor, it's running Android and it is using fastboot for flashing, we figured we could use one of the dragonboard Device-Type templates and duplicate it for our device. But as it comes now to configuring the device dictionary and specifying the test jobs we are not so sure as how to proceed and we also don't want to damage the hardware, so we would be grateful for some help.

Here some more information:
The DUT is connected via USB and its power supply can be turned on and off by using Python scripts (When defining the power_on and power_off commands, should the scripts then be on the master or on the dispatcher? And what are all the necessary parameters for the power on/off and also the values connection_list and connection_commands?).
It is running Android with the underlying Linux configured especially for the hardware, so we would like to avoid deploying for the beginning and only run some simple shell tests to see if the connection stands.
A very simple health check has been set up here<https://paste.debian.net/1175549>, maybe you could give some feedback if that would be sufficient and how future test jobs should be altered.

Hope to hear from you soon

Best Regards,


_________________________________________________________

EMAIL LEGAL MENTION / DISCLAIMER

This message contains information that may be privileged or confidential and is the property of the Expleo Services SAS, RCS Versailles 831 178 348, located, 3 avenue des Pr?s, 78180 Montigny Le Bretonneux - France. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.

Ce message contient des informations qui peuvent ?tre privil?gi?es ou confidentielles et elles sont de la propri?t? d'Expleo Services SAS, RCS Versailles 831 178 348, situ?, 3 avenue des Pr?s, 78180 Montigny le Bretonneux-France. Il est destin? uniquement ? la personne ? qui est adress?. Si vous n'?tes pas le destinataire vis?, vous n'?tes pas autoris? ? lire, imprimer, conserver, copier, diffuser, distribuer ou utiliser ce message ou toute partie de celui-ci. Si vous recevez ce message par erreur, veuillez en avertir imm?diatement l'exp?diteur et supprimer toutes les copies de ce message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lavasoftware.org/pipermail/lava-devel/attachments/20201204/42993299/attachment-0001.htm>

------------------------------

Subject: Digest Footer

_______________________________________________
Lava-devel mailing list
Lava-devel@lists.lavasoftware.org
https://lists.lavasoftware.org/mailman/listinfo/lava-devel


------------------------------

End of Lava-devel Digest, Vol 15, Issue 1
*****************************************