Hi Alex, You are right. I didn't define a clear scope for what I wanted to validate. Apologies about that imprecision.
If possible, I'd like to divide the validation process into three stages 1. The system has a clean boot up process 2. The system is tested using a C-based benchmark (e.g. SPEC CPU2006) 3. The system is validated using a more complex set of testbench frameworks (e.g. http://www.phoronix-test-suite.com/)) My immediate goal is to accomplish stages 1 and 2. Considering the stages listed above, what steps would I need to follow? I appreciate your help. On Tue, Jun 12, 2018 at 4:37 AM, Alexander Kanavin <alex.kana...@gmail.com> wrote: > You start by defining 'works'. It can be anything from quickly > building an image and booting it on the target hardware to see a login > prompt, to running a massive test suite and achieving 100% pass rate. > > Alex > > 2018-06-12 2:14 GMT+03:00 Ricardo Ramirez <o...@ieee.org>: > > Thanks for the reply, Khem! > > > > What steps should I follow to be able to verify the build I put together > for > > SPARCv9 works (or doesn't)? > > > > I realize it is a pretty non-conventional (newbie like) question but I'd > > like to follow a methodological procedure to validate the build. > > > > I appreciate your answer. > > > > -R > > > > On Mon, Jun 11, 2018 at 5:41 PM, Khem Raj <raj.k...@gmail.com> wrote: > >> > >> Hi Ricardo > >> > >> On 6/10/18 7:06 PM, Ricardo Ramirez wrote: > >>> > >>> Hi David, > >>> > >>> Thanks for the prompt reply! > >>> > >>> My question was a follow up of Khem's inquire (posted on 2014-05-02) > >>> > >>> https://lists.yoctoproject.org/pipermail/yocto/2014-May/019387.html > >>> > >> > >> this reply still holds as of today. > >> > >>> Using the links you sent me, I found that the old OE-Classic branch > >>> supports sparc32 but didn't see any sparc64 > >>> > >>> http://layers.openembedded.org/layerindex/oe-classic/recipes/ > >>> > >>> As such, I'd like to know what steps I need to follow in order to > enable > >>> a SPARCv9 machine in Yocto. > >>> > >> > >> We support arm/aarch64/mips/mips64/ppc/ppc64/riscv64/x86/x86_64 for > major > >> arches in OE-Core, we also carry patches to support SH4 but do not test > >> actively for it. sparc support is in there atleast I see basic > constructs > >> are there. Its should be possible to build upon that easily. But it > will not > >> work out of box to set your expectations right. > >> > >>> I appreciate your answer. > >>> > >>> -R > >>> > >>> > >>> On Sun, Jun 10, 2018 at 7:17 PM, Reyna, David < > david.re...@windriver.com > >>> <mailto:david.re...@windriver.com>> wrote: > >>> > >>> Hi Ricardo,____ > >>> > >>> __ __ > >>> > >>> If you are asking about the list of MACHINE types that Yocto > Project > >>> supports, then the best place to look is in the Layer Index:____ > >>> > >>> __ __ > >>> > >>> https://layers.openembedded.org/layerindex/branch/master/layers/ > >>> > >>> <https://layers.openembedded.org/layerindex/branch/master/layers/>____ > >>> > >>> __ __ > >>> > >>> Click on the “Machines” tab, click on the “Search” tab with or > >>> without a search value, and see the glorious list.____ > >>> > >>> __ __ > >>> > >>> The same goes for supported layers, recipes, classes, and distro > >>> values.____ > >>> > >>> __ __ > >>> > >>> You can change the “Branch” value to see the MACHINE’s per > >>> release.____ > >>> > >>> __ __ > >>> > >>> - David Reyna____ > >>> > >>> __ __ > >>> > >>> *From:*yocto-boun...@yoctoproject.org > >>> <mailto:yocto-boun...@yoctoproject.org> > >>> [mailto:yocto-boun...@yoctoproject.org > >>> <mailto:yocto-boun...@yoctoproject.org>] *On Behalf Of *Ricardo > >>> Ramirez > >>> *Sent:* Sunday, June 10, 2018 5:07 PM > >>> *To:* yocto@yoctoproject.org <mailto:yocto@yoctoproject.org> > >>> *Subject:* Re: [yocto] Target CPU architectures that Yocto Project > >>> Support____ > >>> > >>> __ __ > >>> > >>> Hi,____ > >>> > >>> __ __ > >>> > >>> Naive question from a newbie. How can this be achieved? I'd > >>> appreciate if you could please shed some light on what steps need > to > >>> be followed?____ > >>> > >>> __ __ > >>> > >>> Thanks in advance,____ > >>> > >>> __ __ > >>> > >>> -R____ > >>> > >>> > >>> > > > > > > -- > > _______________________________________________ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto > > >
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto