From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] travis: Wire Xilinx Versal Virt platform
Date: Wed, 26 Dec 2018 09:29:28 -0500 [thread overview]
Message-ID: <20181226142928.GV8702@bill-the-cat> (raw)
In-Reply-To: <CAEUhbmU9gWY1-UP0mwibz=7sQOj=asPTc9RwWC5oqgpBDs_5eQ@mail.gmail.com>
On Thu, Dec 20, 2018 at 04:30:19PM +0800, Bin Meng wrote:
> Hi Michal,
>
> On Thu, Dec 20, 2018 at 4:17 PM Michal Simek <michal.simek@xilinx.com> wrote:
> >
> > On 20. 12. 18 9:09, Bin Meng wrote:
> > > On Thu, Dec 20, 2018 at 3:55 PM Michal Simek <michal.simek@xilinx.com> wrote:
> > >>
> > >> Test Xilinx Versal Virt platform running on the v3.1.0 Qemu.
> > >>
> > >> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
> > >> ---
> > >>
> > >> Patch needs to be applied when this PR is merged.
> > >> https://github.com/swarren/uboot-test-hooks/pull/21
> > >>
> > >> ---
> > >> .travis.yml | 8 ++++++++
> > >> 1 file changed, 8 insertions(+)
> > >>
> > >> diff --git a/.travis.yml b/.travis.yml
> > >> index 6e4b4ba0a34a..e14e6987e4cf 100644
> > >> --- a/.travis.yml
> > >> +++ b/.travis.yml
> > >> @@ -454,6 +454,14 @@ matrix:
> > >> QEMU_TARGET="arm-softmmu"
> > >> TEST_PY_ID="--id qemu"
> > >> BUILDMAN="^zynq_zc702$"
> > >> + - name: "test/py xilinx_versal_virt"
> > >> + env:
> > >> + - TEST_PY_BD="xilinx_versal_virt"
> > >> + TEST_PY_TEST_SPEC="not sleep"
> > >> + QEMU_TARGET="aarch64-softmmu"
> > >> + QEMU_VERSION="v3.1.0"
> > >> + TEST_PY_ID="--id qemu"
> > >> + BUILDMAN="^xilinx_versal_virt$"
> > >
> > > Can we turn on 3.1.0 for all QEMU targets?
> >
> > I expected this question.
> > First of all I wanted to enable an option to be able to wire whatever
> > version. Even sha1 for not released version.
> >
> > I think we can try to test v3.1.0 qemu version for all boards but I will
> > let Tom to decide is we can move or not.
> >
>
> Yes, please try to test that. If everything is good, I see no reason
> not using it.
Yes, I would also like to move everyone up to v3.1.0 and also having the
version we use be spelled out will help with future reproducibility.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20181226/0e56a4ae/attachment.sig>
next prev parent reply other threads:[~2018-12-26 14:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 7:55 [U-Boot] [PATCH 1/2] travis: Setup QEMU_VERSION as variable Michal Simek
2018-12-20 7:55 ` [U-Boot] [PATCH 2/2] travis: Wire Xilinx Versal Virt platform Michal Simek
2018-12-20 8:09 ` Bin Meng
2018-12-20 8:17 ` Michal Simek
2018-12-20 8:30 ` Bin Meng
2018-12-26 14:29 ` Tom Rini [this message]
2019-01-03 8:00 ` Michal Simek
2019-01-03 13:39 ` Tom Rini
2019-01-04 1:29 ` Bin Meng
2019-01-04 3:01 ` Tom Rini
2019-01-07 12:18 ` Michal Simek
2019-01-07 12:28 ` Tom Rini
2019-01-07 12:46 ` Michal Simek
2019-01-07 16:57 ` Alexander Graf
2019-01-07 17:13 ` Tom Rini
2019-01-07 20:15 ` Alexander Graf
2019-01-07 22:59 ` Tom Rini
2019-01-07 23:05 ` Stephen Warren
2019-01-15 7:07 ` Michal Simek
2019-01-15 8:54 ` Alexander Graf
2019-01-15 8:56 ` Michal Simek
2019-01-15 8:58 ` Alexander Graf
2019-01-16 13:10 ` Tom Rini
2019-01-16 14:21 ` Michal Simek
2018-12-20 8:08 ` [U-Boot] [PATCH 1/2] travis: Setup QEMU_VERSION as variable Bin Meng
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=20181226142928.GV8702@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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