On Sunday 20 November 2005 11:04 pm, M. Warner Losh wrote: > In message: <20051120042536.E72D816A421_at_hub.freebsd.org> > > wpaul_at_freebsd.org (Bill Paul) writes: > : Our PCI code > : then comes along and enables all of the devices but doesn't necessarily > : update the base address registers on some of them, which has the effect > : of mapping one of the PCI devices at physical address 0. > > Actually, that bug has been fixed in recent versions of > FreeBSD-current, and should be fixed in 6.0. I recall merging changes > to 6.0 just before the release. The problem was that the host bridge > wasn't properly setting a range. If that's not the case, then I'd > like to know about it... No, the bug was fixed, but that wasn't the fix. The fix was to bail out earlier if a BAR's base was 0 and not enable IO or MEM decoding unless a BAR had a valid base (where 0 and 0xfffffff are both invalid bases). -- John Baldwin <jhb_at_FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.orgReceived on Mon Nov 21 2005 - 17:16:57 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:48 UTC