From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:55953) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R46R5-0003nw-VL for qemu-devel@nongnu.org; Thu, 15 Sep 2011 03:32:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1R46R4-0005xs-V8 for qemu-devel@nongnu.org; Thu, 15 Sep 2011 03:32:39 -0400 Received: from mx1.redhat.com ([209.132.183.28]:7713) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R46R4-0005xb-Ky for qemu-devel@nongnu.org; Thu, 15 Sep 2011 03:32:38 -0400 Message-ID: <4E71AA08.8060100@redhat.com> Date: Thu, 15 Sep 2011 10:32:24 +0300 From: Avi Kivity MIME-Version: 1.0 References: <4E6E2BDC.3060702@siemens.com> <4E6F10DD.6060606@siemens.com> <6BA6355D-D77A-40F4-A8C4-61901A926E71@suse.de> <4E6F1BAF.2000105@siemens.com> <2A74238E-5C89-444B-9DB9-4B380D182AC3@suse.de> <4E6F3FB8.6060705@siemens.com> <4E7053A3.8090508@redhat.com> <4E706303.9040502@redhat.com> <4E7063D9.3040803@siemens.com> <4E70645D.8050100@redhat.com> <4E7064BA.1050700@siemens.com> <58B7465A-925F-4732-A557-AB57BEFCD64B@suse.de> <4E706763.8020706@redhat.com> <14B02BB3-FFB5-4B67-B0AC-6E6A9806AE0E@suse.de> <4E710BAB. 6060705@redhat.com> <4E7111BB.107 0608@twiddle.net> <219F7C53-89AB-4824-B78C-E31E99E3A50C@suse.de> <1316049883.455.178.camel@pa! sglop> In-Reply-To: <1316049883.455.178.camel@pasglop> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v3 5/6] vga: Use linear mapping + dirty logging in chain 4 memory access mode List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Benjamin Herrenschmidt Cc: Anthony Liguori , Jan Kiszka , qemu-devel Developers , Alexander Graf , Blue Swirl , =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= , Gerd Hoffmann , Richard Henderson On 09/15/2011 04:24 AM, Benjamin Herrenschmidt wrote: > On Wed, 2011-09-14 at 23:41 +0200, Alexander Graf wrote: > > On 14.09.2011, at 22:42, Richard Henderson wrote: > > > > > On 09/14/2011 01:35 PM, Alexander Graf wrote: > > > > > >>> Can you explain what the memory map looks like from the hardware > > point of view? > > >> > > >> If you can tell me where to find out :). I seriously have zero > > experience in VGA mapping - and it sounds as if Blue has a pretty good > > idea what's going on. > > > > > > He's not interested in the VGA bits, but in the PPC board bits. > > > How are addresses forwarded from the main system bus to the > > > PCI host bridge, for instance? > > > > Yeah, and what I'm trying to tell you is that I know about as much > > about the g3 beige as you do. However, Ben might now a bit more here. > > Let's ask him :). > > Can I have a bit of context please ? :-) What does the memory map regarding a pci vga card looks like? Right now it looks like some BAR has collided with the legacy vga range at 0xa0000 (maped to 0x8000a0000) or such. What is supposed to be where? -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.