From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: seabios@seabios.org, QEMU Developers <qemu-devel@nongnu.org>,
Gleb Natapov <gleb@redhat.com>,
Sebastian Herbszt <herbszt@gmx.de>
Subject: Re: [Qemu-devel] Re: [SeaBIOS] SMBIOS strings
Date: Tue, 01 Jun 2010 08:05:26 +0200 [thread overview]
Message-ID: <4C04A326.3050205@redhat.com> (raw)
In-Reply-To: <m3wrujz57a.fsf@blackfin.pond.sub.org>
On 06/01/10 07:34, Markus Armbruster wrote:
> "Sebastian Herbszt" <herbszt@gmx.de> writes:
>
>> Gleb Natapov wrote:
>>> I don't care much as long as we will not have "CPU :". It looks like something
>>> that can change after BIOS upgrade, so it is hard to believe Windows
>>> will stop working because of this change.
>>
>> Maybe it could trigger the Windows activation process?
>
> Isn't that testable?
The problem there is that the number of possible combinations to test is
endless. I think older versions of windows are far more prone to such
problems than newer ones.
Cheers,
Jes
next prev parent reply other threads:[~2010-06-01 6:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 15:24 [Qemu-devel] SMBIOS strings Jes Sorensen
2010-05-28 15:44 ` [Qemu-devel] Re: [SeaBIOS] " Gleb Natapov
2010-05-31 7:32 ` Jes Sorensen
2010-05-31 7:50 ` Gleb Natapov
2010-05-31 20:38 ` Sebastian Herbszt
2010-06-01 5:34 ` Markus Armbruster
2010-06-01 6:05 ` Jes Sorensen [this message]
2010-06-01 23:57 ` [SeaBIOS] [Qemu-devel] " Kevin O'Connor
2010-06-01 13:02 ` Olivier Galibert
2010-06-01 5:36 ` [Qemu-devel] Re: [SeaBIOS] " Gleb Natapov
2010-05-29 12:49 ` Sebastian Herbszt
2010-05-31 7:33 ` Jes Sorensen
2010-05-29 16:15 ` Kevin O'Connor
2010-06-01 20:26 ` Sebastian Herbszt
2010-06-01 23:34 ` Kevin O'Connor
2010-06-02 20:35 ` Sebastian Herbszt
2010-06-02 6:44 ` Jes Sorensen
2010-06-02 21:01 ` Sebastian Herbszt
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=4C04A326.3050205@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=armbru@redhat.com \
--cc=gleb@redhat.com \
--cc=herbszt@gmx.de \
--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 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.