From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 6/9] board/qemu: add post-image script for gitlab qemu testing
Date: Mon, 10 Feb 2020 15:41:33 +0100 [thread overview]
Message-ID: <20200210154133.2bfdee65@windsurf> (raw)
In-Reply-To: <f049e76f-b96a-b355-1597-b7fda6412afe@smile.fr>
Hello,
On Mon, 10 Feb 2020 14:47:59 +0100
Romain Naour <romain.naour@smile.fr> wrote:
> > Why is this script copied a zillion times? This looks like a
> > maintenance nightmare. Why not put it in board/qemu/, and have a single
> > script used by all configurations ?
>
> I'm not sure if we should share the same post-image script for several boards.
Why so? We already do that for NXP platforms for example.
> It's not clear how we should maintain theses scripts in board directory.
>
> For example for genimage (post-image.sh) :
> board/lego/ev3/post-image.sh
> board/grinn/liteboard/post-image.sh
> board/nexbox/a95x/post-image.sh
>
> This is the same script.
> Maybe we need something board/common/post-image.sh ?
>
> For Qemu board, maybe add the script in board/qemu/common/post-image.sh.
Yes, or just board/qemu/post-image.sh is sufficient.
> There is also a special case for sh4, so I'll add a second script to add
> "-serial stdio -display none" instead of "-display none"
No, just make a small condition in your script:
case ${defconfig} in
qemu_sh4_defconfig)
do something here
;;
esac
and that's it.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-02-10 14:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-09 18:03 [Buildroot] [PATCH v4 0/9] gitlab Qemu runtime testing Romain Naour
2020-02-09 18:03 ` [Buildroot] [PATCH v4 1/9] configs/qemu_ppc_mac99_defconfig: add usual comments for Kconfig symbols Romain Naour
2020-02-10 2:32 ` Joel Stanley
2020-02-16 21:22 ` Peter Korsgaard
2020-02-09 18:03 ` [Buildroot] [PATCH v4 2/9] configs/qemu_pcc_mac99: build host-qemu for runtime testing Romain Naour
2020-02-10 2:31 ` Joel Stanley
2020-02-16 21:23 ` Peter Korsgaard
2020-02-09 18:03 ` [Buildroot] [PATCH v4 3/9] configs/qemu_m68k_q800: remove host-qemu Romain Naour
2020-02-09 18:12 ` Romain Naour
2020-02-09 18:49 ` Romain Naour
2020-02-16 21:24 ` Peter Korsgaard
2020-02-09 18:03 ` [Buildroot] [PATCH v4 4/9] configs/qemu{x86, x86_64}: add a serial console Romain Naour
2020-02-16 21:28 ` Peter Korsgaard
2020-02-09 18:03 ` [Buildroot] [PATCH v4 5/9] board/qemu: add defconfig file name as tag before the qemu command line Romain Naour
2020-02-10 13:08 ` Thomas Petazzoni
2020-02-10 13:37 ` Romain Naour
2020-02-10 14:40 ` Thomas Petazzoni
2020-02-09 18:03 ` [Buildroot] [PATCH v4 6/9] board/qemu: add post-image script for gitlab qemu testing Romain Naour
2020-02-10 13:09 ` Thomas Petazzoni
2020-02-10 13:47 ` Romain Naour
2020-02-10 14:41 ` Thomas Petazzoni [this message]
2020-02-10 13:13 ` Thomas Petazzoni
2020-02-10 13:49 ` Romain Naour
2020-02-09 18:03 ` [Buildroot] [PATCH v4 7/9] configs/qemu*: use the post-image script with "$(BR2_DEFCONFIG)" as argument Romain Naour
2020-02-09 18:03 ` [Buildroot] [PATCH v4 8/9] support/scripts/boot-qemu-image.py: boot Qemu images with Qemu-system Romain Naour
2020-02-09 18:03 ` [Buildroot] [PATCH v4 9/9] gitlab.yml.in*: enable Qemu gitlab testing Romain Naour
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=20200210154133.2bfdee65@windsurf \
--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