From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=57865 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OJK7b-0007YY-IG
	for qemu-devel@nongnu.org; Tue, 01 Jun 2010 01:34:40 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <armbru@redhat.com>) id 1OJK7a-0002ZS-3R
	for qemu-devel@nongnu.org; Tue, 01 Jun 2010 01:34:39 -0400
Received: from mx1.redhat.com ([209.132.183.28]:51877)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <armbru@redhat.com>) id 1OJK7Z-0002ZM-S6
	for qemu-devel@nongnu.org; Tue, 01 Jun 2010 01:34:38 -0400
From: Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] Re: [SeaBIOS] SMBIOS strings
References: <4BFFE03F.40606@redhat.com> <20100528154402.GB3604@redhat.com>
	<4C0365F8.2070703@redhat.com> <20100531075030.GB22291@redhat.com>
	<019522D4DB3546ECB35EA6CC5D5FD069@FSCPC>
Date: Tue, 01 Jun 2010 07:34:33 +0200
In-Reply-To: <019522D4DB3546ECB35EA6CC5D5FD069@FSCPC> (Sebastian Herbszt's
	message of "Mon, 31 May 2010 22:38:03 +0200")
Message-ID: <m3wrujz57a.fsf@blackfin.pond.sub.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Sebastian Herbszt <herbszt@gmx.de>
Cc: Jes Sorensen <Jes.Sorensen@redhat.com>, seabios@seabios.org, QEMU Developers <qemu-devel@nongnu.org>, Gleb Natapov <gleb@redhat.com>

"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?