From owner-cvs-all@FreeBSD.ORG Sun Dec 12 15:25:55 2004 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 146BC16A4CE; Sun, 12 Dec 2004 15:25:55 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8636E43D2D; Sun, 12 Dec 2004 15:25:54 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iBCFSMCG034712; Sun, 12 Dec 2004 08:28:23 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41BC62ED.10700@freebsd.org> Date: Sun, 12 Dec 2004 08:25:33 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= References: <200412060827.iB68RAmE058040@repoman.freebsd.org> In-Reply-To: X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: cvs-src@freebsd.org cc: src-committers@freebsd.org cc: cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/i386/pci pci_cfgreg.c X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Dec 2004 15:25:55 -0000 Dag-Erling Smørgrav wrote: > Scott Long writes: > >> Modified files: >> sys/i386/pci pci_cfgreg.c >> Log: >> Add support for the memory-mapped PCI Express configuration mechanism. > > > What about amd64? Are these platforms really so different that the > PCI configuration code can't be shared between them? > > DES AMD64 will be done via a single direct-mapped window instead of a pool of temporary mappings. There also seems to be at least one amd64 chipset that requires information contained in ACPI in order to work, and it's something that I didn't consider until after I had done the i386 side. So once I have it figured out, I'll commit it. Scott