From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 6/7] support/scripts/qemu-boot-*: gitlab tests for Qemu
Date: Sun, 27 Oct 2019 15:34:03 +0100 [thread overview]
Message-ID: <20191027153403.18feefeb@windsurf.dhcp.lyon.intranet> (raw)
In-Reply-To: <c1aa9ebc-3717-d53b-bd0f-5f41c28730ff@smile.fr>
On Sun, 27 Oct 2019 15:32:00 +0100
Romain Naour <romain.naour@smile.fr> wrote:
> > For the x86_64 case, maybe we should simply rename board/qemu/x86_64 to
> > board/qemu/x86-64, so that it matches the other directories, where we
> > have the same name as the defconfig, with just the _ replaced by -.
> > This would entirely remove those special conditions.
>
> Instead of renaming this directory and using the name of the defconfig file to
> search for the right readme.txt containing the qemu command line to use.
>
> We can instead add a comment in the defconfig
>
> $ cat qemu_aarch64_virt_defconfig
> # Use the Qemu command line from board/qemu/arm-vexpress/readme.txt to start Qemu.
>
> or if we use a script launch.sh to start qemu (as suggested in the previous
> patch review)
>
> # Use the script from board/qemu/arm-vexpress/launch.sh to start Qemu.
>
> Doing so, we don't have a naming rule between defconfig file and board/qemu
> directory.
Yes, why not. Could be useful to point people at the readme.txt or
launch.sh script.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-10-27 14:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-05 16:53 [Buildroot] [PATCH v2 0/7] gitlab Qemu runtime testing Jugurtha BELKALEM
2019-05-05 16:53 ` [Buildroot] [PATCH v2 1/7] package/qemu: enable nios2 support for host-qemu Jugurtha BELKALEM
2019-05-31 6:13 ` Thomas Huth
2019-08-02 21:52 ` Thomas Petazzoni
2019-05-05 16:53 ` [Buildroot] [PATCH v2 2/7] package/qemu: enable sparc64 " Jugurtha BELKALEM
2019-05-31 6:14 ` Thomas Huth
2019-08-02 21:53 ` Thomas Petazzoni
2019-05-05 16:53 ` [Buildroot] [PATCH v2 3/7] package/qemu: remove comment about sh64 Jugurtha BELKALEM
2019-05-31 6:17 ` Thomas Huth
2019-08-02 21:53 ` Thomas Petazzoni
2019-05-05 16:53 ` [Buildroot] [PATCH v2 4/7] configs/qemu-*: add host-qemu-system Jugurtha BELKALEM
2019-08-02 21:53 ` Thomas Petazzoni
2019-08-03 13:38 ` Bernd Kuhls
2019-05-05 16:53 ` [Buildroot] [PATCH v2 5/7] board/qemu/*/launch.sh: add qemu launch script Jugurtha BELKALEM
2019-08-02 21:58 ` Thomas Petazzoni
2019-10-27 16:44 ` Romain Naour
2019-10-27 16:52 ` Thomas Petazzoni
2019-10-27 17:59 ` Romain Naour
2019-10-27 18:15 ` Thomas Petazzoni
2019-10-27 19:15 ` Romain Naour
2019-05-05 16:53 ` [Buildroot] [PATCH v2 6/7] support/scripts/qemu-boot-*: gitlab tests for Qemu Jugurtha BELKALEM
2019-08-02 22:24 ` Thomas Petazzoni
2019-10-27 14:32 ` Romain Naour
2019-10-27 14:34 ` Thomas Petazzoni [this message]
2019-05-05 16:53 ` [Buildroot] [PATCH v2 7/7] gitlab.yml.in*: enable Qemu gitlab testing Jugurtha BELKALEM
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=20191027153403.18feefeb@windsurf.dhcp.lyon.intranet \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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