From owner-cvs-all@FreeBSD.ORG Wed Oct 6 20:00:34 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 B67BE16A4CE; Wed, 6 Oct 2004 20:00:34 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id D0B1843D39; Wed, 6 Oct 2004 20:00:11 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id i96Ju7UQ028279 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 6 Oct 2004 12:57:01 -0700 Message-ID: <41644DD6.1070200@root.org> Date: Wed, 06 Oct 2004 12:56:06 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "M. Warner Losh" References: <200410060722.i967MwsJ014694@repoman.freebsd.org> <200410061054.42956.jhb@FreeBSD.org> <41644490.3050005@root.org> <20041006.132655.78073866.imp@bsdimp.com> In-Reply-To: <20041006.132655.78073866.imp@bsdimp.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org cc: jhb@FreeBSD.org Subject: Re: cvs commit: src/sys/i386/pci pci_bus.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: Wed, 06 Oct 2004 20:00:34 -0000 M. Warner Losh wrote: > In message: <41644490.3050005@root.org> > Nate Lawson writes: > : >> Hoewver, for CardBus bridges (cbb), they rarely get the resources > : >> allocated by the BIOS, and this patch helps them greatly. Typically > : >> the 'bad Vcc' messages are caused by this problem. > : > > : > We really should be looking at the SMAP to find out what the real limits of > : > PCI space are I think since I think the SMAP includes an entry for PCI memory > : > mapped I/O. > : > : YES! More integrated SMAP awareness is especially important as more > : complex configs appear with different levels of reservation for upper > : memory besides just "reserved" or "available". > > However, the current SMAP definition is about useless since it doesn't > tell us directly what we need to know. Well, it will give us an idea > of what we can exclude, but that still leaves a gap between 'all > that's excluded' and 'all that the host bridge passes'. Sure, I can't remember the exact changes, I just remember that SMAP is going to be used soon for a lot more than just "BIOS reserved" and "available" memory resources. This is due to the changing notion of the line between OS and BIOS. -- Nate