public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] qemu-x86 issues
Date: Tue, 18 Oct 2016 09:19:59 -0400	[thread overview]
Message-ID: <20161018131959.GZ18591@bill-the-cat> (raw)
In-Reply-To: <CAEUhbmWvC3zVubycUy8W8UCVx6W7ZLvRG1CE7b39XyV8yp0Ghw@mail.gmail.com>

On Tue, Oct 18, 2016 at 10:36:41AM +0800, Bin Meng wrote:
> Hi Tom,
> 
> On Sat, Oct 15, 2016 at 7:32 AM, Tom Rini <trini@konsulko.com> wrote:
> > Hey guys,
> >
> > After making Stephen's scripts work with qemu today, I've started
> > testing out what platforms I can test out via qemu.  I've found two
> > problems with qemu-x86.  First, there's a real problem with the network.
> > I run qemu with "-nographic -cpu qemu32 -netdev
> > user,id=net0,tftp=/tftpboot -device e1000,netdev=net0" so that I can
> > tftpboot things in and I'm getting crc32 mismatches.
> >
> 
> I just tried QEMU v2.6.1 with u-boot.rom built from the master head,
> but did not see such issue.

Ah, I think I see it now.  We can't use 0x0 as where to load stuff to
and the tests default to 0x0 if you don't provide an address rather than
$loadaddr.  I'll see about changing the tests.

> > Second, the sleep command is not at all accurate.  It's returning the 3
> > second test in less than 1 second.
> 
> Typical emulation target issue :) Did you see similar issue on other
> QEMU platform with U-Boot?

So this one is interesting.  I see the same failure for MIPS/PPC for the
qemu targets we have as well.  I don't see this under QEMU for the ARM
targets that I'm emulating.  I suspect there's some common problem on
the U-Boot side as also don't see this on the VMs I have running under
qemu nor when I boot the kernelci rootfs from U-Boot.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20161018/b48c198b/attachment.sig>

  reply	other threads:[~2016-10-18 13:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-14 23:32 [U-Boot] qemu-x86 issues Tom Rini
2016-10-18  2:36 ` Bin Meng
2016-10-18 13:19   ` Tom Rini [this message]
2016-10-18 13:35     ` Tom Rini
2016-10-19  3:18       ` Bin Meng
2016-10-19 12:03         ` Tom Rini
2016-12-03 11:09         ` Pavel Machek

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=20161018131959.GZ18591@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