From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Cc: 'Gleb Natapov' <gleb@redhat.com>, 'Sebastian Herbszt' <herbszt@gmx.de>
Subject: Re: [Qemu-devel] RE: [Bochs-developers] [PATCH v3 1/6] Move PIC initialization out ofline to save space in post code area.
Date: Thu, 13 Nov 2008 14:00:45 -0600 [thread overview]
Message-ID: <491C876D.3010003@codemonkey.ws> (raw)
In-Reply-To: <004d01c945c4$2a561180$7f023480$@com>
Stanislav Shwartsman wrote:
> Done.
>
Gleb,
What's the status of this patch series? Are there particular patches
that haven't made it into upstream Bochs yet that requiring
refactoring? Are there things that we should take in the bios.diff?
Until the Bochs folks get around to applying?
Regards,
Anthony Liguori
> -----Original Message-----
> From: Sebastian Herbszt [mailto:herbszt@gmx.de]
> Sent: Thursday, November 13, 2008 2:10 AM
> To: Gleb Natapov; bochs-developers@lists.sourceforge.net; Stanislav
> Shwartsman
> Cc: qemu-devel@nongnu.org
> Subject: Re: [Bochs-developers] [PATCH v3 1/6] Move PIC initialization out
> ofline to save space in post code area.
>
> Gleb Natapov wrote:
>
>> There are only a couple of bytes left in post area.
>>
>> Signed-off-by: Gleb Natapov <gleb@redhat.com>
>> ---
>>
>> bios/rombios.c | 48 ++++++++++++++++++++++++++----------------------
>> 1 files changed, 26 insertions(+), 22 deletions(-)
>>
>
> Stanislav, please apply this one.
>
> - Sebastian
>
>
>
>
next prev parent reply other threads:[~2008-11-13 20:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-10 9:11 [Qemu-devel] [PATCH v3 0/6] Support for S3 ACPI state (suspend to memory) in BIOS Gleb Natapov
2008-11-10 9:11 ` [Qemu-devel] [PATCH v3 1/6] Move PIC initialization out of line to save space in post code area Gleb Natapov
2008-11-13 0:10 ` [Qemu-devel] Re: [Bochs-developers] [PATCH v3 1/6] Move PIC initialization out ofline " Sebastian Herbszt
2008-11-13 19:15 ` [Qemu-devel] " Stanislav Shwartsman
2008-11-13 20:00 ` Anthony Liguori [this message]
2008-11-14 9:47 ` Gleb Natapov
2008-11-14 20:36 ` [Qemu-devel] RE: [Bochs-developers] [PATCH v3 1/6] Move PICinitialization " Sebastian Herbszt
2008-11-10 9:11 ` [Qemu-devel] [PATCH v3 2/6] Add S3 state to DSDT. Handle resume event in the BIOS Gleb Natapov
2008-11-15 17:43 ` [Qemu-devel] Re: [Bochs-developers] [PATCH v3 2/6] Add S3 state to DSDT. Handleresume " Sebastian Herbszt
2008-11-15 17:56 ` Gleb Natapov
2008-11-10 9:11 ` [Qemu-devel] [PATCH v3 3/6] Preserve memory content during SMM init Gleb Natapov
2008-11-10 9:11 ` [Qemu-devel] [PATCH v3 4/6] Execute rombios32 code from rom address 0xe0000 Gleb Natapov
2008-11-10 9:11 ` [Qemu-devel] [PATCH v3 5/6] Don't use unreserved memory in BIOS Gleb Natapov
2008-11-13 0:43 ` [Qemu-devel] Re: [Bochs-developers] [PATCH v3 5/6] Don't use unreserved memory inBIOS Sebastian Herbszt
2008-11-13 7:41 ` Gleb Natapov
2008-11-10 9:12 ` [Qemu-devel] [PATCH v3 6/6] Don't power down vga card on entering S3 state Gleb Natapov
2008-11-10 12:07 ` Glauber Costa
2008-11-10 13:28 ` Gleb Natapov
2008-11-10 20:25 ` [Qemu-devel] Re: [Bochs-developers] [PATCH v3 6/6] Don't power down vga card onentering " Sebastian Herbszt
2008-11-10 21:20 ` Gleb Natapov
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=491C876D.3010003@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=gleb@redhat.com \
--cc=herbszt@gmx.de \
--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).