From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33)
	id 1BY981-00019u-CS
	for qemu-devel@nongnu.org; Wed, 09 Jun 2004 15:52:53 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33)
	id 1BY97z-00017y-GK
	for qemu-devel@nongnu.org; Wed, 09 Jun 2004 15:52:52 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.33) id 1BY97z-00017Q-3D
	for qemu-devel@nongnu.org; Wed, 09 Jun 2004 15:52:51 -0400
Received: from [193.252.22.26] (helo=mwinf0503.wanadoo.fr)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1BY97B-0004P6-Aa
	for qemu-devel@nongnu.org; Wed, 09 Jun 2004 15:52:01 -0400
Received: from bellard.org (ATuileries-112-1-3-149.w81-48.abo.wanadoo.fr
	[81.48.134.149])
	by mwinf0503.wanadoo.fr (SMTP Server) with ESMTP id 951E0680043E
	for <qemu-devel@nongnu.org>; Wed,  9 Jun 2004 21:52:00 +0200 (CEST)
Message-ID: <40C76AF5.6060801@bellard.org>
Date: Wed, 09 Jun 2004 21:54:29 +0200
From: Fabrice Bellard <fabrice@bellard.org>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: Re: NE2K PCI and Windows 98SE & Cirrus Logic
References: <001801c44d31$2b1291b0$0401a8c0@putte2k>
	<20040608131418.N1510@edinburgh.cisco.com>
In-Reply-To: <20040608131418.N1510@edinburgh.cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.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.gnu.org/pipermail/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: qemu-devel@nongnu.org

Derek Fawcus wrote:
> On Tue, Jun 08, 2004 at 10:18:22AM +0200, Mike Nordell wrote:
> 
>>I'm still curious why 32MB is claimed in the pci_register_io_region call,
>>even that it only has got 4MB.
> 
> 
> Because that what's the hardware does - actually,  from memory I thought
> this family only claimed 16M.
> 
> The reason for the larger size is given in the datasheet - it's multiple
> mapped copies of the RAM so as top have automatic byteswapping.  So something
> to beware of if this device is used under the PPC emulation.

32M is correct: 16M are mapped for the frame buffer in various 
endiannesses and 16M for the bitblt engine data access (in 5446 rev B).

Fabrice.