From: Gerd Hoffmann <kraxel@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PULL 0/3] Update seabios to 1.7.4
Date: Tue, 04 Feb 2014 09:17:36 +0100 [thread overview]
Message-ID: <1391501856.15480.4.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <52F09936.9090407@msgid.tls.msk.ru>
On Di, 2014-02-04 at 11:39 +0400, Michael Tokarev wrote:
> 03.02.2014 18:45, Gerd Hoffmann wrote:
> > Hi,
> >
> > Sorry for the delay folks, totally forgot that one.
> > Here is the seabios update to 1.7.4 final.
>
> FWIW, we updated seabios in Debian testing (with qemu 1.7), and
> now there are several bugs filed in Debian BTS, at least:
>
> http://bugs.debian.org/737142
> http://bugs.debian.org/736902
>
> (this last one is a bit messy, all branches/combinations produce
> different results, and it isn't exactly stable).
Dunno what 737142 is. 736902 looks like something with ram detection.
Would be interesting to know whenever the blobs from this pull request
are failing too. If so a seabios log would be helpful.
cheers,
Gerd
next prev parent reply other threads:[~2014-02-04 8:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 14:45 [Qemu-devel] [PULL 0/3] Update seabios to 1.7.4 Gerd Hoffmann
2014-02-03 14:45 ` [Qemu-devel] [PATCH 1/3] roms: remove explicit MAKEFLAGS from recursive make invocations Gerd Hoffmann
2014-02-03 14:45 ` [Qemu-devel] [PATCH 2/3] Update seabios submodule to 1.7.4 Gerd Hoffmann
2014-02-03 14:45 ` [Qemu-devel] [PATCH 3/3] Update seabios binaries " Gerd Hoffmann
2014-02-04 7:39 ` [Qemu-devel] [PULL 0/3] Update seabios " Michael Tokarev
2014-02-04 8:17 ` Gerd Hoffmann [this message]
2014-02-04 11:31 ` Michael Tokarev
2014-02-04 10:21 ` Michael Tokarev
2014-02-04 11:03 ` Gerd Hoffmann
2014-02-04 11:18 ` Michael Tokarev
2014-02-08 13:12 ` Peter Maydell
2014-02-17 11:56 ` Peter Maydell
2014-02-17 13:17 ` Gerd Hoffmann
2014-02-17 13:23 ` Peter Maydell
2014-02-18 13:21 ` Peter Maydell
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=1391501856.15480.4.camel@nilsson.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
/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).