All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ANN] U-Boot v2016.09 is released
Date: Fri, 16 Sep 2016 10:12:35 +0200	[thread overview]
Message-ID: <3c1484b8-a78d-ff94-c418-a15ed1ab4a42@monstr.eu> (raw)
In-Reply-To: <20160915112404.GI8156@bill-the-cat>

On 15.9.2016 13:24, Tom Rini wrote:
> On Wed, Sep 14, 2016 at 11:32:07PM +0200, Daniel Schwierzeck wrote:
>> Hi Tom,
>>
>> Am 12.09.2016 um 18:21 schrieb Tom Rini:
>>>
>>> Another thing I'd like to call out, and ask for a little help with too
>>> is automated testing.  The framework in test/py/test.py can be used on
>>> real hardware and Stephen Warren has been doing a good job having things
>>> run on Tegra boards.  You can see his scripts here[1].  I've setup
>>> locally some of my boards (some TI, RPi3, A20-OLinuXino-Lime2) and I'm
>>> looking at adding more still, so long as I can update U-Boot in a way
>>> that does not involve the console.  You can see my scripts here[2] and
>>> I'm cleaning things up and pushing them back up to Stephen.  But there's
>>> always more to do and test.  Is anyone else out there running this on
>>> real hardware, or would like to set this up?  Has anyone out there
>>> gotten this hooked up with qemu?
>>>
>>
>> I have scripts for running tests on MIPS Malta in Qemu [1]. Currently
>> the only non-working tests are test_sleep and test_net_tftpboot on Malta
>> 64Bit.
>>
>> I think it's possible to create a generic ConsoleQemu class but I hadn't
>> time yet to try this.
>>
>> [1] https://github.com/danielschwierzeck/u-boot-test-hooks
> 
> Ah cool.  I think between that and what Michal sent me off-list throwing
> together some helper scripts to fit into Stephens hook scripts should be
> doable.  The only thing I'm not sure about, wrt doing a class is the
> amount of flags that qemu needs (and how much they vary) compared with
> sandbox.  Thanks!
> 

It is just the same style how to get a console out of qemu.

Some sort of integration can be good but the most problematic part
to decide what qemu version to use and if permit also out of tree qemu, etc.
But having a guidance how to do it would be good.

Thanks,
Michal


-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Xilinx Microblaze
Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP SoCs


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160916/f4d86aa5/attachment.sig>

  reply	other threads:[~2016-09-16  8:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-12 16:21 [U-Boot] [ANN] U-Boot v2016.09 is released Tom Rini
2016-09-12 16:43 ` Michal Simek
2016-09-12 16:58 ` Lukasz Majewski
2016-09-13  5:49 ` Heiko Schocher
2016-09-14 13:44   ` Tom Rini
2016-09-13  6:58 ` Wolfgang Denk
2016-09-14 21:32 ` Daniel Schwierzeck
2016-09-15 11:24   ` Tom Rini
2016-09-16  8:12     ` Michal Simek [this message]
2016-09-19 16:07 ` [U-Boot] [ANN] U-Boot v2016.09.01 " Tom Rini
2016-09-19 16:43   ` Fabio Estevam
2016-09-19 17:01     ` Tom Rini
2016-09-20 16:32       ` Fabio Estevam

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=3c1484b8-a78d-ff94-c418-a15ed1ab4a42@monstr.eu \
    --to=monstr@monstr.eu \
    --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.