From: "Mark Brown" <broonie@kernel.org>
To: kernelci@groups.io, khilman@baylibre.com
Cc: Atish Patra <Atish.Patra@wdc.com>,
"drew@beagleboard.org" <drew@beagleboard.org>,
"palmer@dabbelt.com" <palmer@dabbelt.com>,
"david.abdurachmanov@sifive.com" <david.abdurachmanov@sifive.com>,
"raj.khem@gmail.com" <raj.khem@gmail.com>,
Alistair Francis <Alistair.Francis@wdc.com>,
Corentin Labbe <clabbe@baylibre.com>,
Lakshmipathi Ganapathi <lakshmipathi.ganapathi@collabora.co.uk>
Subject: Re: Improve kernelci setup for RISC-V
Date: Thu, 2 Jul 2020 12:24:00 +0100 [thread overview]
Message-ID: <20200702112400.GC4483@sirena.org.uk> (raw)
In-Reply-To: <7hsgeaixcl.fsf@baylibre.com>
[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]
On Wed, Jul 01, 2020 at 05:17:46PM -0700, Kevin Hilman wrote:
> Atish Patra <Atish.Patra@wdc.com> writes:
> > But Alistair & khem (cc'd) expressed interest to add OE to kernelci as
> > well. Can you share some pointers on what needs to be done ?
> The main tricky/annoying part with yocto is that builds are per-board,
> where as we like to build rootfs images per-arch. Maybe there's a way
> to build an arch-generic yocto rootfs using a qemu target or something,
> though.
That definitely works well, I'm doing a lot of my testing with a setup
like that - just ignore the kernel that yocto builds and use the rest of
the rootfs. Once you start to get further up the stack it can be an
issue but for most things KernelCI is covering now it's fine. The only
gotcha I'm aware of is if there's architecture variants that are binary
incompatible (like moving to v7 on arm) you need to pick one that's
suitable for everything that'll use the image.
> OTOH, I'm not quite sure what we would gain by using yocto instead of
> debian? Are there more packages for yocto available than for debian
> currently?
I'd expect it's the other way around TBH.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-07-02 11:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3c2cba2849caa6ea0116611c1da3268b41432b76.camel@wdc.com>
2020-07-02 0:17 ` Improve kernelci setup for RISC-V Kevin Hilman
2020-07-02 7:02 ` Atish Patra
2020-07-02 7:12 ` David Abdurachmanov
2020-07-02 13:19 ` David Abdurachmanov
2020-07-02 14:50 ` Aurelien Jarno
2020-07-02 14:55 ` Colin Ian King
2020-07-02 14:49 ` Aurelien Jarno
2020-07-02 18:15 ` Karsten Merker
2020-07-02 18:25 ` Kevin Hilman
2020-07-02 20:15 ` Manuel A. Fernandez Montecelo
2020-07-08 23:31 ` Manuel A. Fernandez Montecelo
2020-07-09 6:52 ` Lakshmipathi Ganapathi
2020-07-02 20:19 ` Alistair Francis
2020-07-02 15:49 ` Khem Raj
2020-07-02 11:24 ` Mark Brown [this message]
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=20200702112400.GC4483@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Alistair.Francis@wdc.com \
--cc=Atish.Patra@wdc.com \
--cc=clabbe@baylibre.com \
--cc=david.abdurachmanov@sifive.com \
--cc=drew@beagleboard.org \
--cc=kernelci@groups.io \
--cc=khilman@baylibre.com \
--cc=lakshmipathi.ganapathi@collabora.co.uk \
--cc=palmer@dabbelt.com \
--cc=raj.khem@gmail.com \
/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.