From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [Qemu-devel] KVM call minutes for Feb 8 Date: Thu, 10 Feb 2011 15:00:05 +0200 Message-ID: <4D53E155.5000807@redhat.com> References: <4D526D0D.9020507@codemonkey.ws> <4D52A86A.1030407@codemonkey.ws> <4D52F20A.7070009@codemonkey.ws> <4D539800.3070802@codemonkey.ws> <20110210090748.GD673@redhat.com> <4D53BD22.1040800@redhat.com> <20110210111354.GA21681@redhat.com> <4D53DF42.4030700@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Gleb Natapov , Chris Wright , kvm@vger.kernel.org, qemu-devel@nongnu.org, Markus Armbruster , Blue Swirl To: Anthony Liguori Return-path: Received: from mx1.redhat.com ([209.132.183.28]:22272 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752913Ab1BJNAT (ORCPT ); Thu, 10 Feb 2011 08:00:19 -0500 In-Reply-To: <4D53DF42.4030700@codemonkey.ws> Sender: kvm-owner@vger.kernel.org List-ID: On 02/10/2011 02:51 PM, Anthony Liguori wrote: > On 02/10/2011 12:13 PM, Gleb Natapov wrote: >> >> Which spec? Even in this discussion we completely mixed different >> things. 440FX is not a chipset. > > Yes, it is. It's a single silicon package with a defined pinout. If > you don't believe me, re-read the spec. > > It's a MCM with the PIIX3 being internally connected. The connection > between the i440fx and PIIX3 happens to be PCI but that's not always > the case. Sometimes it's a proprietary bus. Aren't they two distinct chips, together comprising the chip-set? One (the northbridge) converts the system bus to PCI + some extra wires, the other (southbridge) bridges PCI to ISA and contains some embedded ISA devices. IIRC there are some wires between them that are not PCI. -- error compiling committee.c: too many arguments to function