cvs commit: src/sys/dev/pci pci_pci.c
imp at bsdimp.com
Fri Feb 18 22:37:25 GMT 2005
From: Bernd Walter <ticso at cicely12.cicely.de>
Subject: Re: cvs commit: src/sys/dev/pci pci_pci.c
Date: Fri, 18 Feb 2005 22:46:55 +0100
> On Fri, Feb 18, 2005 at 05:35:03PM +0000, Warner Losh wrote:
> > imp 2005-02-18 17:35:03 UTC
> > FreeBSD src repository
> > Modified files:
> > sys/dev/pci pci_pci.c
> > Log:
> > For the I/O port case, we need to set ok to 1 if we have what looks
> > like a valid range. We already do this in the memory case (although
> > the code there is somewhat different than the I/o case because we have
> > to deal with different kinds of memory). Since most laptops don't
> > have non-subtractive bridges, this wasn't seen in practice.
> Does that mean we do check ranges on pci bridges?
Yes. And we have been for a long time.
> I can remember having troubles with alpha systems where io ranges in
> PCI chips behind PCI-PCI bridges looked valid by themself, but in fact
> no IO range is configured on bridges.
Yes. And we've been dealing with the newer subtractively decoded
bridges for a long time as well too :-)
long time == since before 5.3 :-)
More information about the cvs-src