From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:42106)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jan.kiszka@web.de>) id 1SiMdQ-0000ov-ON
	for qemu-devel@nongnu.org; Sat, 23 Jun 2012 05:28:05 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <jan.kiszka@web.de>) id 1SiMdP-00022N-6O
	for qemu-devel@nongnu.org; Sat, 23 Jun 2012 05:28:04 -0400
Received: from mout.web.de ([212.227.17.11]:63733)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jan.kiszka@web.de>) id 1SiMdO-00022H-Sq
	for qemu-devel@nongnu.org; Sat, 23 Jun 2012 05:28:03 -0400
Message-ID: <4FE58C20.4020803@web.de>
Date: Sat, 23 Jun 2012 11:28:00 +0200
From: Jan Kiszka <jan.kiszka@web.de>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig408C8CBAB532B4FD8B502267"
Subject: [Qemu-devel] MMIO coalescing of the i82378 bridge
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/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: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: =?ISO-8859-1?Q?Andreas_F=E4rber?= <andreas.faerber@web.de>, =?ISO-8859-1?Q?Herv=E9_Poussineau?= <hpoussin@reactos.org>
Cc: qemu-devel <qemu-devel@nongnu.org>

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig408C8CBAB532B4FD8B502267
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi all,

just stumbled over the memory_region_set_coalescing in pci_i82378_init:
What ISA devices are affected by this? It looks a bit strange to me as
the MMIO requests are apparently mapped on PIO requests, and we don't
have PIO coalescing on x86. Depending on the target device on PREP, this
may have some unexpected side effects. Or is only framebuffer memory
addressed this way?

Jan


--------------enig408C8CBAB532B4FD8B502267
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk/ljCAACgkQitSsb3rl5xTh3QCgzQffAdnL3yoexL/Frp/lMXRR
VCYAoI+UFWZeGuo86modH4EIuvkxw4yQ
=+TsX
-----END PGP SIGNATURE-----

--------------enig408C8CBAB532B4FD8B502267--