| Summary: | Support image flash methods and communication methods with DUT | ||
|---|---|---|---|
| Product: | [QA/Testing] Runtime Testing | Reporter: | Cathy Shen <cathy.shen> |
| Component: | general | Assignee: | Benjamin Esquivel <benjamin.esquivel> |
| Status: | VERIFIED OBSOLETE | QA Contact: | Jose Perez C <jose.perez.carranza> |
| Severity: | enhancement | ||
| Priority: | Medium+ | CC: | alexandru.c.georgescu, benjamin.esquivel, costin.c.constantin, leonardo.sandoval.gonzalez |
| Version: | 2.1 | ||
| Target Milestone: | 2.3 M1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
| Bug Depends on: | |||
| Bug Blocks: | 10604 | ||
|
Description
Cathy Shen
2015-10-11 13:41:54 UTC
Hi Cathy, Please provide more info on what "controller" means. For this: "support kinds of image flash methods" you refer to image deployment on DUT? For the communication methods, that is clear. Thank you, Costin Controller is referring to the classes defined in oeqa/targetcontrol.py. runner use it to flash image to DUT, communicate with DUT, etc. changed back to new Moving this bug to Edwin and also targeting a single image flash method and single communication protocol for the re-do of the device automation. Looks not feasible for 2.2. Please let us know if you have a strong requirement on this one otherwise will be moved to future/2.3. This is a master bug and must be splitted. Edwin, please work with Anibal to do this. this is a feature required for having bug 10604 completed. Benjamin needs to validate the initial requirements and compare with current supported features. The flashing part is taken care by the AFT[1] and the communication methods are still going to be simply over ssh and obtain logging via the serial console. This bug is obsoleted by work being done in bug 10604 |