All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH v6 2/4] test: qemu: add qfw sandbox driver, dm tests, qemu tests
Date: Sun, 14 Mar 2021 16:22:32 -0400	[thread overview]
Message-ID: <20210314202232.GA13803@bill-the-cat> (raw)
In-Reply-To: <20210307035958.25969-3-ashe@kivikakk.ee>

On Sun, Mar 07, 2021 at 02:59:57PM +1100, Asherah Connor wrote:

> A sandbox driver and test are added for the qfw uclass, and a test in
> QEMU added for qfw functionality to confirm it doesn't break in real
> WORld use.
> 
> Signed-off-by: Asherah Connor <ashe@kivikakk.ee>
> Reviewed-by: Simon Glass <sjg@chromium.org>

A small thing, CMD_QFW needs to be disabled on sandbox_spl_defconfig (a
special config for some tests only).  A larger thing is that these tests
fail for me both locally and in CI:
https://source.denx.de/u-boot/u-boot/-/jobs/237539
https://source.denx.de/u-boot/u-boot/-/jobs/237535
https://source.denx.de/u-boot/u-boot/-/jobs/237536

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20210314/19418a3a/attachment.sig>

  reply	other threads:[~2021-03-14 20:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-07  3:59 [PATCH v6 0/4] Move qfw to DM, add Arm support Asherah Connor
2021-03-07  3:59 ` [PATCH v6 1/4] x86: qemu: move QFW to its own uclass Asherah Connor
2021-03-12  4:45   ` Simon Glass
2021-03-07  3:59 ` [PATCH v6 2/4] test: qemu: add qfw sandbox driver, dm tests, qemu tests Asherah Connor
2021-03-14 20:22   ` Tom Rini [this message]
2021-03-19  2:57     ` Asherah Connor
2021-03-07  3:59 ` [PATCH v6 3/4] qemu: add MMIO driver for QFW Asherah Connor
2021-03-12  4:45   ` Simon Glass
2021-03-07  3:59 ` [PATCH v6 4/4] qemu: arm: select QFW, MMIO on qemu-arm Asherah Connor
2021-03-12  4:45   ` Simon Glass

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=20210314202232.GA13803@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 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.