All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>,
	Kevin O'Connor <kevin@koconnor.net>,
	Paolo Bonzini <pbonzini@redhat.com>
Cc: Phil Dennis-Jordan <phil@philjordan.eu>,
	seabios@seabios.org,
	"qemu-devel@nongnu.org qemu-devel" <qemu-devel@nongnu.org>,
	Programmingkid <programmingkidx@gmail.com>,
	Phil Dennis-Jordan <lists@philjordan.eu>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [SeaBIOS] Commit 77af8a2b95b79699de650965d5228772743efe84 breaks Windows 2000 support
Date: Fri, 28 Jul 2017 08:57:51 +0200	[thread overview]
Message-ID: <1501225071.10943.3.camel@redhat.com> (raw)
In-Reply-To: <70092179-8b4b-8f6d-50bc-df95ad2649be@redhat.com>

  Hi,

> It's a good goal.
> 
> I apologize for forgetting the context, but what exactly was the
> argument against:
> 
> - splitting modern ACPI generation from ancient ACPI generation (so
> that
> we can assign separate maintainers to ancient vs. modern),
> 
> - restricting ancient ACPI generation to old machine types?

I think this is the only sensible solution for 2.10:  Have "pc" provide
a rev1 FADT and "q35" provide a rev3 FADT.

Or just revert the rev3 FADT patch and try again in the 2.11 devel
cycle.

We are in qemu freeze and we don't even have a clear plan yet how to
implement the "RSDT points to rev1 and XSDT points to rev3" thing,
which IMO is a clear indicator that it isn't 2.10 material.

Beside that I'll be in my summer vacation next three weeks, so I can't
take care to create a seabios 1.10.3 release and update qemu ...

cheers,
  Gerd

  reply	other threads:[~2017-07-28  6:57 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-20 16:40 [Qemu-devel] Commit 77af8a2b95b79699de650965d5228772743efe84 breaks Windows 2000 support Programmingkid
2017-07-20 19:29 ` Phil Dennis-Jordan
2017-07-21  0:00   ` Programmingkid
2017-07-21  9:06   ` Igor Mammedov
2017-07-21  9:11     ` Phil Dennis-Jordan
2017-07-21  9:23     ` Daniel P. Berrange
2017-07-21 12:34       ` Igor Mammedov
2017-07-21 18:29         ` Phil Dennis-Jordan
2017-07-25 16:14           ` Laszlo Ersek
2017-07-25 16:23             ` Paolo Bonzini
2017-07-25 17:10               ` Paolo Bonzini
2017-07-25 21:25                 ` Phil Dennis-Jordan
2017-07-26  8:53                   ` Paolo Bonzini
2017-07-26 11:42                     ` Laszlo Ersek
2017-07-26 12:06                       ` Paolo Bonzini
2017-07-25 22:01                 ` [Qemu-devel] [SeaBIOS] " Kevin O'Connor
2017-07-26  7:20                   ` Paolo Bonzini
2017-07-26 19:12                     ` Kevin O'Connor
2017-07-26 20:21                       ` Paolo Bonzini
2017-07-27  8:39                         ` Gerd Hoffmann
2017-07-27 12:26                           ` Paolo Bonzini
2017-07-27 14:59                         ` Kevin O'Connor
2017-07-27 17:46                           ` Laszlo Ersek
2017-07-28  6:57                             ` Gerd Hoffmann [this message]
2017-07-26 13:08               ` [Qemu-devel] " Igor Mammedov
2017-07-26 13:10                 ` Paolo Bonzini
2017-07-26 13:30                   ` Igor Mammedov
2017-07-26 13:33                     ` Paolo Bonzini
2017-07-26 13:43                       ` Igor Mammedov
2017-07-26 14:04                         ` Daniel P. Berrange
2017-07-26 16:13                           ` Michael S. Tsirkin
2017-07-26 13:57                     ` Michael S. Tsirkin
2017-07-24 12:45     ` Gerd Hoffmann
2017-07-24 16:43     ` John Snow
2017-07-24 17:30       ` Programmingkid
2017-07-21  9:20   ` Daniel P. Berrange
2017-07-21  9:46     ` Igor Mammedov
2017-07-21 10:39       ` Phil Dennis-Jordan
2017-07-21 10:50       ` BALATON Zoltan
2017-07-21 11:46         ` Phil Dennis-Jordan
2017-07-21 17:17           ` BALATON Zoltan

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=1501225071.10943.3.camel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=kevin@koconnor.net \
    --cc=lersek@redhat.com \
    --cc=lists@philjordan.eu \
    --cc=pbonzini@redhat.com \
    --cc=phil@philjordan.eu \
    --cc=programmingkidx@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --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 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.