From owner-freebsd-current@FreeBSD.ORG Tue Mar 24 15:07:51 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 253091065677 for ; Tue, 24 Mar 2009 15:07:51 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.freebsd.org (Postfix) with ESMTP id EC8628FC08 for ; Tue, 24 Mar 2009 15:07:50 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id 59E502FAA93; Tue, 24 Mar 2009 11:07:50 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute2.internal (MEProxy); Tue, 24 Mar 2009 11:07:50 -0400 X-Sasl-enc: BlUCePLKzMguj2xRelLzZVuYAJLt1wJNwc0zyGMJ15uD 1237907269 Received: from empiric.lon.incunabulum.net (unknown [81.168.51.182]) by mail.messagingengine.com (Postfix) with ESMTPSA id B9E8F2E1A5; Tue, 24 Mar 2009 11:07:49 -0400 (EDT) Message-ID: <49C8F744.4020405@FreeBSD.org> Date: Tue, 24 Mar 2009 15:07:48 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.19 (X11/20090126) MIME-Version: 1.0 To: freebsd-current@freebsd.org, Mars G Miro References: <200903191126.15390.jhb@freebsd.org> <200903201242.09167.jhb@freebsd.org> <20090324114648.GC3329@stlux503.dsto.defence.gov.au> In-Reply-To: <20090324114648.GC3329@stlux503.dsto.defence.gov.au> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: sk/msk no more X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Mar 2009 15:07:51 -0000 Wilkinson, Alex wrote: > 0n Fri, Mar 20, 2009 at 12:42:08PM -0400, John Baldwin wrote: > > >mcfg is a mechanism for doing faster PCI config access using a memory mapped window. > > As opposed to what ? > As opposed to bit-banging all PCI configuration space accesses through a couple of low ISA I/O space ports (PCI Configuration Mechanism #1... in the PCI SIG specs.) :-) For years PCI was an x86/Intel only thing, architectures which don't have this notion of ISA I/O port space have used memory mapped windows like this for years. cheers, BMS