From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] qemu: Update defconfigs to Linux 4.19.16
Date: Wed, 13 Feb 2019 08:46:07 +0100 [thread overview]
Message-ID: <20190213084607.55ef5dc9@windsurf> (raw)
In-Reply-To: <d93f0671-7695-1604-272d-4145a4ad2182@smile.fr>
Hello,
On Tue, 12 Feb 2019 23:21:48 +0100
Romain Naour <romain.naour@smile.fr> wrote:
> > Actually, maybe it would make sense for those qemu defconfigs to be
> > runtime tested as part of the .gitlab-ci.yml that is in Buildroot
> > itself ?
>
> Actually we discussed about that with Gerome. Maybe we needs something like in
> toolchain-builder project that retrieve the Qemu command line from the
> readme.txt file present in each board/qemu/<target>/readme.txt.
It already works like this. In the build.sh script:
# Extract Qemu command from readme.txt
test_qemu_cmd=$(grep qemu-system ${buildroot_dir}/board/qemu/${test_board_dir}/readme.txt)
and then further tweaks to build the Qemu command line.
> > with some additional commands to see if it is a qemu defconfig, and if
> > it is, run it under Qemu.
>
> Maybe we should use host-qemu build by Buildroot instead of qemu from the host
> distribution. Some Qemu configs (ex aarch64) requires a recent qemu version.
Yes, we could use host-qemu if needed.
> Gerome, tested the network device emulation by trying to login to the target
> using ssh. But we are not sure what was the network test used by [1] (ping, ssh,
> iperf etc...).
I'm not sure it matters a lot: just test if network support is working,
ping or ssh is enough. I believe in the cases where network was not
working, it was simply not working at all.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-02-13 7:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 22:14 [Buildroot] [PATCH] qemu: Update defconfigs to Linux 4.19.16 Gerome Burlats
2019-02-07 8:41 ` Thomas Petazzoni
2019-02-12 22:21 ` Romain Naour
2019-02-13 7:46 ` Thomas Petazzoni [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=20190213084607.55ef5dc9@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 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.