From: Kevin O'Connor <kevin@koconnor.net>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: seabios@seabios.org, qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: Advise on updating SeaBIOS in stable
Date: Thu, 14 Jan 2010 08:46:37 -0500 [thread overview]
Message-ID: <20100114134637.GA11393@morn.localdomain> (raw)
In-Reply-To: <4B4E5E2B.9080300@codemonkey.ws>
On Wed, Jan 13, 2010 at 05:58:35PM -0600, Anthony Liguori wrote:
> I actually need the compiler fix to build on my laptop (F12) so I've
> included that too. Care to take a look at
> git://git.qemu.org/seabios.git stable-0.5.0? It survives some light
> testing and I'll be doing more thorough testing overnight.
I'd also include: 2ceeec9d, and 085debd9. The first fixes a binutils
oddity, and the second is a straight-forward bug fix.
> If you want to add some more and/or tag a release, I'll resync again
> before cutting 0.12.2.
>
> >If you're looking to pull in 32bit pcibios support, then I don't think
> >it would be worthwhile to rebase to a stable branch, as the 32bit
> >pcibios support is easily the biggest user visible change in v0.5.1
> >(in the sense that Linux will call 32bit pcibios if it's available).
>
> Unless there's a strong demand for it, I'd like to hold off on 32bit
> pcibios support.
That makes sense. I'll pull your branch into my tree as well.
However, I don't think I'll get time to look much closer at this until
tomorrow night.
-Kevin
next prev parent reply other threads:[~2010-01-14 13:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 19:43 [Qemu-devel] Advise on updating SeaBIOS in stable Anthony Liguori
2010-01-13 4:51 ` [Qemu-devel] " Kevin O'Connor
2010-01-13 23:58 ` Anthony Liguori
2010-01-14 6:11 ` Aurelien Jarno
2010-01-14 10:27 ` [Qemu-devel] Re: [SeaBIOS] " Gerd Hoffmann
2010-01-14 13:46 ` Kevin O'Connor [this message]
2010-01-14 14:37 ` [Qemu-devel] " Anthony Liguori
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=20100114134637.GA11393@morn.localdomain \
--to=kevin@koconnor.net \
--cc=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.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).