From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:39611) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R8alP-0008SJ-9F for qemu-devel@nongnu.org; Tue, 27 Sep 2011 12:44:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1R8alN-0005W4-Eh for qemu-devel@nongnu.org; Tue, 27 Sep 2011 12:44:11 -0400 Received: from mx1.redhat.com ([209.132.183.28]:65457) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R8alN-0005Vs-4W for qemu-devel@nongnu.org; Tue, 27 Sep 2011 12:44:09 -0400 Message-ID: <4E81FD53.7070006@redhat.com> Date: Tue, 27 Sep 2011 19:44:03 +0300 From: Avi Kivity MIME-Version: 1.0 References: <4E7A828A.3030404@codemonkey.ws> <4E7F366F.9060501@redhat.com> <4E7F5B62.1090307@redhat.com> <4E804F20.2090007@redhat.com> <4E80B3EF.3070202@redhat.com> <4E80B535.1030804@redhat.com> <4E818A5A.6000605@redhat.com> <4E819012.6090100@redhat.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [FYI] Soft feature freeze for 1.0 is 10/15 (three weeks away) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Blue Swirl Cc: qemu-devel On 09/27/2011 07:39 PM, Blue Swirl wrote: > > > > Well, it's not that easy. As the other mapping is part of an ordinary BAR, > > you need to setup the device (at least PCI_COMMAND and PCI_BASE_ADDRESS_0) > > so it responds to memory requests, and also enable the bridge. > > > > We could hack it by having a low-priority mapping at 0x80013000, but it > > seems wrong. Maybe the firmware should configure that BAR first? What > > happens on real hardware? > > In this message I seem to confess that the address is arbitrary and in > the subsequent messages the overlap with PCI region is also discussed. > http://lists.nongnu.org/archive/html/qemu-devel/2009-01/msg00542.html > > Maybe the address of macio should be fixed as Laurent suggested. I'll leave it up to you - I'm out of my depth here. Meanwhile I suggest applying the pci alias patch - the bug is independent of the vga issue. -- error compiling committee.c: too many arguments to function