From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>, qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Eduardo Habkost <ehabkost@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Wainer dos Santos Moschetta <wainersm@redhat.com>,
qemu-arm@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>,
Aleksandar Markovic <amarkovic@wavecomp.com>,
Cleber Rosa <crosa@redhat.com>
Subject: Re: [PATCH 2/2] tests/acceptance/integratorcp: Verify Tux is displayed on framebuffer
Date: Sat, 1 Feb 2020 08:24:51 +0100 [thread overview]
Message-ID: <31738ee9-1c2f-0c30-8651-a05e01b7914d@redhat.com> (raw)
In-Reply-To: <20200131211102.29612-3-f4bug@amsat.org>
On 31/01/2020 22.11, Philippe Mathieu-Daudé wrote:
> Add a test that verifies the Tux logo is displayed on the framebuffer.
>
> We simply follow the OpenCV "Template Matching with Multiple Objects"
> tutorial, replacing Lionel Messi by Tux:
> https://docs.opencv.org/4.2.0/d4/dc6/tutorial_py_template_matching.html
What a cool idea :-)
If you like, there are some more images with Tux in the QEMU advent
calendar 2018 which you could use for testing the framebuffer:
https://www.qemu-advent-calendar.org/2018/download/day13.tar.xz
https://www.qemu-advent-calendar.org/2018/download/day15.tar.xz
https://www.qemu-advent-calendar.org/2018/download/day16.tar.xz
https://www.qemu-advent-calendar.org/2018/download/day19.tar.xz
These two use a slightly different tux:
https://www.qemu-advent-calendar.org/2018/download/day09.tar.xz
https://www.qemu-advent-calendar.org/2018/download/day11.tar.xz
And day 22 (MIPS64) and 23 (SPARC64) use a framebuffer, too, but they
seem to be broken with the current version from the git master branch.
Thomas
next prev parent reply other threads:[~2020-02-01 7:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 21:11 [PATCH 0/2] tests/acceptance/integratorcp: Verify Tux is displayed on framebuffer Philippe Mathieu-Daudé
2020-01-31 21:11 ` [PATCH 1/2] tests/acceptance: Extract boot_integratorcp() from test_integratorcp() Philippe Mathieu-Daudé
2020-02-01 7:06 ` Thomas Huth
2020-02-11 10:08 ` Philippe Mathieu-Daudé
2020-02-03 14:00 ` Wainer dos Santos Moschetta
2020-01-31 21:11 ` [PATCH 2/2] tests/acceptance/integratorcp: Verify Tux is displayed on framebuffer Philippe Mathieu-Daudé
2020-02-01 7:24 ` Thomas Huth [this message]
2020-02-03 14:05 ` Wainer dos Santos Moschetta
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=31738ee9-1c2f-0c30-8651-a05e01b7914d@redhat.com \
--to=thuth@redhat.com \
--cc=amarkovic@wavecomp.com \
--cc=crosa@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=f4bug@amsat.org \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=wainersm@redhat.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;
as well as URLs for NNTP newsgroup(s).