From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=35485 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OJR7G-0006IU-5j
	for qemu-devel@nongnu.org; Tue, 01 Jun 2010 09:02:47 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <galibert@dspnet.fr>) id 1OJR75-0005ky-14
	for qemu-devel@nongnu.org; Tue, 01 Jun 2010 09:02:45 -0400
Received: from dspnet.fr ([188.165.44.67]:52618)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <galibert@dspnet.fr>) id 1OJR74-0005i0-Sp
	for qemu-devel@nongnu.org; Tue, 01 Jun 2010 09:02:34 -0400
Date: Tue, 1 Jun 2010 15:02:10 +0200
From: Olivier Galibert <galibert@pobox.com>
Subject: Re: [SeaBIOS] [Qemu-devel] Re:  SMBIOS strings
Message-ID: <20100601130210.GA12448@dspnet.fr>
References: <4BFFE03F.40606@redhat.com> <20100528154402.GB3604@redhat.com>
	<4C0365F8.2070703@redhat.com> <20100531075030.GB22291@redhat.com>
	<019522D4DB3546ECB35EA6CC5D5FD069@FSCPC>
	<m3wrujz57a.fsf@blackfin.pond.sub.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <m3wrujz57a.fsf@blackfin.pond.sub.org>
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: Markus Armbruster <armbru@redhat.com>
Cc: seabios@seabios.org, QEMU Developers <qemu-devel@nongnu.org>, Sebastian Herbszt <herbszt@gmx.de>

On Tue, Jun 01, 2010 at 07:34:33AM +0200, 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?

Not easily, that process trips when the total number of changes goes
over a fixed value.

  OG.