ReleaseEngineering/Projects/PandaBoards: Difference between revisions
Jump to navigation
Jump to search
(Created page with "== What is the goal? == * To have a testing automation for Android 3.0 and/or Android 4.0 == What does mobile need/know? == == What does the a-team need/know? == == What does ...") |
No edit summary |
||
| Line 1: | Line 1: | ||
== What is the goal? == | == What is the goal? == | ||
* To have a testing automation for Android | * To have a testing automation for Android 4.0 | ||
* To enable us to test NEON support (a graphics subsystem these cards have) | |||
* To test a different chipset architecture than the tegras (Tegra is largely a dying platform in mobile space) | |||
* To test on android 4.0 | |||
* To have a mobilie automation platform that is more reliable and easier to flash than the tegras (less IT management cost) | |||
* To have a mobile platform that is faster than the tegras | |||
== What does mobile need/know? == | == What does mobile need/know? == | ||
== What does the a-team need/know? == | == What does the a-team need/know? == | ||
* How do we do flashing of these devices so that you can flash with all required software from the get-go | |||
* Does it run through our test systems without dying? | |||
* How much faster is it than a tegra? | |||
== What does IT need/know? == | == What does IT need/know? == | ||
| Line 10: | Line 18: | ||
== What does releng need/know? == | == What does releng need/know? == | ||
Point of contact: armenzg | Point of contact: armenzg | ||
* a panda board | * a panda board | ||
* hook up the panda-board to the automation | * hook up the panda-board to the automation | ||
* know if the setup is the same as tegras (SUT agent, foopies) | * know if the setup is the same as tegras (SUT agent, foopies) | ||
** ''clint:'' Exact same setup. | |||
* what suites are going to be run on it | * what suites are going to be run on it | ||
** ''clint:'' Everything we run on the tegras | |||
* imaging process | * imaging process | ||
** Ateam to define | |||
* ordering schedule | * ordering schedule | ||
* how many boards? | * how many boards? | ||
| Line 21: | Line 31: | ||
** ordering these many boards is simply ridiculous for manufacturers | ** ordering these many boards is simply ridiculous for manufacturers | ||
* do they have to be racked in haxxor? | * do they have to be racked in haxxor? | ||
** ''clint:'' No. These are wired devices, no reason to use haxxor for this. | |||
== Roadmap/Timeline == | == Roadmap/Timeline == | ||
Revision as of 02:35, 8 February 2012
What is the goal?
- To have a testing automation for Android 4.0
- To enable us to test NEON support (a graphics subsystem these cards have)
- To test a different chipset architecture than the tegras (Tegra is largely a dying platform in mobile space)
- To test on android 4.0
- To have a mobilie automation platform that is more reliable and easier to flash than the tegras (less IT management cost)
- To have a mobile platform that is faster than the tegras
What does mobile need/know?
What does the a-team need/know?
- How do we do flashing of these devices so that you can flash with all required software from the get-go
- Does it run through our test systems without dying?
- How much faster is it than a tegra?
What does IT need/know?
What does releng need/know?
Point of contact: armenzg
- a panda board
- hook up the panda-board to the automation
- know if the setup is the same as tegras (SUT agent, foopies)
- clint: Exact same setup.
- what suites are going to be run on it
- clint: Everything we run on the tegras
- imaging process
- Ateam to define
- ordering schedule
- how many boards?
- do we really know if the model we follow is scalable?? does the tegra model work?
- ordering these many boards is simply ridiculous for manufacturers
- do they have to be racked in haxxor?
- clint: No. These are wired devices, no reason to use haxxor for this.
Roadmap/Timeline
TBD