Date: Wed, 06 Oct 2004 12:56:06 -0700 From: Nate Lawson <nate@root.org> To: "M. Warner Losh" <imp@bsdimp.com> Cc: jhb@FreeBSD.org Subject: Re: cvs commit: src/sys/i386/pci pci_bus.c Message-ID: <41644DD6.1070200@root.org> In-Reply-To: <20041006.132655.78073866.imp@bsdimp.com> References: <200410060722.i967MwsJ014694@repoman.freebsd.org> <200410061054.42956.jhb@FreeBSD.org> <41644490.3050005@root.org> <20041006.132655.78073866.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
M. Warner Losh wrote: > In message: <41644490.3050005@root.org> > Nate Lawson <nate@root.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41644DD6.1070200>