[Automated-testing] [Openembedded-architecture] Yocto Project LTS Proposal/Discussion

Adrian Bunk bunk at stusta.de
Sat Oct 26 12:37:13 PDT 2019


On Sat, Oct 26, 2019 at 10:34:44AM -0400, Rich Persaud wrote:
>...
> To avoid YP users assuming that YP and/or the upstream kernel has done hardware testing for YP LTS, we may want to document specific testing actions that are expected from YP LTS users.  E.g. should YP downstreams work directly with CKI via the Linux Foundation, to pool hardware test results?  Should they report hw test results to other YP LTS users?

Aren't the testing actions expected from YP LTS users the same as for
any other YP user?

My understanding is that the hardware support provided by YP is just an 
example BSP mainly used by YP, and real-world project get their hardware 
support either from a 3rd party layer or from 3rd party git trees.
 
>... 
> If we are able to attract contributions, could we eventually associate YP LTS external test results with public BSP definitions and hardware model/revision numbers?

Isn't this more a topic for the 3rd party BSP layers that are actually 
providing this hardware support?

> Rich

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed



More information about the automated-testing mailing list