From: "Kevin Hilman" <khilman@baylibre.com>
To: kernelci@groups.io, Santiago.Esteban@microchip.com, info@kernelci.org
Subject: Re: Microchip KernelCi contributions
Date: Mon, 06 Jul 2020 11:20:26 -0700 [thread overview]
Message-ID: <7hr1to4iad.fsf@baylibre.com> (raw)
In-Reply-To: <3c193c7e-c13d-5740-8d11-4dca5be528ef@microchip.com>
Hi Santiago,
<Santiago.Esteban@microchip.com> writes:
> I'm Santiago Esteban, SW Engineer at Microchip. I'm leading the effort
> for continuous integration of our Linux developments. We are setting up
> the infrastructure for CI in a board farm containing several boards.
> We would like to contribute to the KernelCI effort with build and test
> data. Hopefully, as our knowledge increases we will be able to help in
> some other ways.
>
>
> How should I prodeed?
How is your lab currently setup? Are you using LAVA? If not, can you
tell us a bit more about how your lab is setup? What kind of hardware
you're testing?
If using LAVA, getting integrated into KernelCI is pretty straight
forward.
Some pre-requisites:
- boards can boot an upstream Linux kernel using an upstream defconfig,
(minimum: boot to a serial-console shell using a ramdisk)
- LAVA device-types for your boards are submitted upstream to the LAVA
project
>From there, with a basic LAVA setup/working, we just add your lab to our
list of labs[1] and then add your device-types in your lab to our list
of devices[2].
For kernelci.org to be able to submit jobs to your LAVA lab, you'll need
to create a `kernel-ci` user, setup an auth token and share that token
with us. Any boards that the kernel-ci LAVA user has access to,
kernelci.org will have access to.
Hope that helps get you started,
Kevin
[1] https://github.com/kernelci/kernelci-core/blob/master/lab-configs.yaml
[2] https://github.com/kernelci/kernelci-core/blob/master/test-configs.yaml
next prev parent reply other threads:[~2020-07-06 18:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 10:20 Microchip KernelCi contributions Santiago.Esteban
2020-07-06 18:20 ` Kevin Hilman [this message]
2020-07-20 12:11 ` santiago.esteban
2020-07-20 15:14 ` Guillaume Tucker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7hr1to4iad.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=Santiago.Esteban@microchip.com \
--cc=info@kernelci.org \
--cc=kernelci@groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.