Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Sean Nyekjaer <sean@geanix.com>,
	openembedded-core@lists.openembedded.org,
	Richard Purdie <richard.purdie@linuxfoundation.org>,
	martin.jansa@gmail.com
Subject: Re: [OE-core] runqemu: ahci option
Date: Thu, 11 Jan 2024 13:14:45 +0200	[thread overview]
Message-ID: <ZZ_NpSCvzbInt8hy@nuoska> (raw)
In-Reply-To: <CANNYZj8DSe-qb+U2CniuBEM3hahJz3+7W3MBVro3fs=O0mNFoQ@mail.gmail.com>

Hi,

On Thu, Jan 11, 2024 at 11:42:58AM +0100, Alexander Kanavin wrote:
> Generally runqemu is inteded for  (and tested with) specifically
> qemux86_64 MACHINE (or any other qemu* machine). So if testing your
> particular target bootloader with qemu isn't actually important, you
> can rebuild the image for qemux86_64, and in that configuration there
> is no bootloader: qemu boots the kernel directly.

True, yocto has a lot of history with the assumption that every board even with
common and compatible SoC's needs a specific machine configuration.

I think this is a bit too old fashioned and would like to move towards generic and
compatible builds where a single binary build works on a large number of instruction
set compatible SoCs and boards.

Thus I'd be happy to have qemu testing part of this and the hard coded assumptions of
qemu configs to be removed or made optional so that they can be overwritten
if needed. So patches welcome :)

Cheers,

-Mikko


      reply	other threads:[~2024-01-11 11:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-11  7:59 [OE-core] runqemu: ahci option Sean Nyekjaer
2024-01-11 10:42 ` Alexander Kanavin
2024-01-11 11:14   ` Mikko Rapeli [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=ZZ_NpSCvzbInt8hy@nuoska \
    --to=mikko.rapeli@linaro.org \
    --cc=alex.kanavin@gmail.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=sean@geanix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox