From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ng1qK-0003lN-KK for qemu-devel@nongnu.org; Fri, 12 Feb 2010 15:10:24 -0500 Received: from [199.232.76.173] (port=37796 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ng1qK-0003kL-1b for qemu-devel@nongnu.org; Fri, 12 Feb 2010 15:10:24 -0500 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1Ng1qJ-00084b-9P for qemu-devel@nongnu.org; Fri, 12 Feb 2010 15:10:24 -0500 Received: from mail-px0-f203.google.com ([209.85.216.203]:64482) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Ng1qI-00084X-UT for qemu-devel@nongnu.org; Fri, 12 Feb 2010 15:10:23 -0500 Received: by pxi41 with SMTP id 41so1887703pxi.27 for ; Fri, 12 Feb 2010 12:10:21 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <20100212133434.GI11930@valinux.co.jp> References: <20100212023134.GC11930@valinux.co.jp> <20100212125457.GH21947@redhat.com> <20100212133434.GI11930@valinux.co.jp> From: Blue Swirl Date: Fri, 12 Feb 2010 22:10:01 +0200 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: [Qemu-devel] Re: [PATCH] pci: introduce get_info_quirk callback. List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Isaku Yamahata Cc: qemu-devel@nongnu.org, "Michael S. Tsirkin" On Fri, Feb 12, 2010 at 3:34 PM, Isaku Yamahata wrote: > On Fri, Feb 12, 2010 at 02:54:59PM +0200, Michael S. Tsirkin wrote: >> On Fri, Feb 12, 2010 at 11:31:34AM +0900, Isaku Yamahata wrote: >> > This patch fixes 525e05147d5a3bdc08caa422d108c1ef71b584b5 >> > by introducing device specific get_info_quirk callback. >> > It wrongly assumes that pci host bridge class device has >> > header type of pci-pci bridge. But this isn't always true. >> > In fact i440fx pci host bridge has header type of normal device, >> > hence it breaks i440fx and other pci host bridges. >> > The right fix is that header type should be checked, instead of device class. >> > >> > The change set's purpose is to show PBM pci host bridge >> > info which doesn't conform to PCI specification. >> >> So, PBM has header type PCI_HEADER_TYPE_NORMAL >> but all config space is in bridge format? > > Some of registers is in bridge format. > To be honest, I don't know whether all or some. > Blue seems to want bus numbers registers at least. > > http://lists.gnu.org/archive/html/qemu-devel/2010-02/msg00519.html I'm not so sure anymore, I'll have to check this in the weekend. Perhaps there was some other problem with bus numbering or OpenBIOS PCI programming which resulted in the need to program PRIMARY/ SECONDARY/SUBORDINATE bus values for host bridge. Does it make any sense to use anything other than bus 0 for PCI bus attached to host bridge?