From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=60861 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PXoar-0004nX-JF
	for qemu-devel@nongnu.org; Wed, 29 Dec 2010 00:29:14 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <stefanha@gmail.com>) id 1PXoad-0004GB-PV
	for qemu-devel@nongnu.org; Wed, 29 Dec 2010 00:29:01 -0500
Received: from mail-wy0-f173.google.com ([74.125.82.173]:57038)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <stefanha@gmail.com>) id 1PXoad-0004Fj-Km
	for qemu-devel@nongnu.org; Wed, 29 Dec 2010 00:28:47 -0500
Received: by wyg36 with SMTP id 36so10884392wyg.4
	for <qemu-devel@nongnu.org>; Tue, 28 Dec 2010 21:28:46 -0800 (PST)
MIME-Version: 1.0
In-Reply-To: <035B2B8A-3932-4B90-8EA5-D95D3E2F4467@dlh.net>
References: <AANLkTi=LqDt1FvzvQEdRYdkqWAFjjeDpNStcB8Zf7YLh@mail.gmail.com>
	<035B2B8A-3932-4B90-8EA5-D95D3E2F4467@dlh.net>
Date: Wed, 29 Dec 2010 05:28:46 +0000
Message-ID: <AANLkTimgfHQdGNX-c8=gMOKiL0xg8ePiLgmtPYuVWn1g@mail.gmail.com>
From: Stefan Hajnoczi <stefanha@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: [Qemu-devel] Re: [PATCH] pc: move port 92 stuff back to pc.c from
	pckbd.c
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: Peter Lieven <pl@dlh.net>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel <qemu-devel@nongnu.org>

On Tue, Dec 28, 2010 at 9:45 PM, Peter Lieven <pl@dlh.net> wrote:
> What happens if I set the A20 Gate via the keyboard controller and then r=
ead its status via ioport 0x92? This doesn't work, or does it?
> What was wrong reading the A20 via
>
> int ioport_get_a20(void)
> {
> =A0 =A0return ((first_cpu->a20_mask >> 20) & 1);
> }
>
> every time ioport 0x92 or the keyobard outport is read?

I wonder the same thing.

Also, stashing the uint8_t output value away is not migration-friendly
at the moment?

Stefan