Warner Losh e5baeed6a6 MFp4: When doing lazy allocation, it turns out that we need to record the ... actual resource values we received from the system rather than the range we requested. Since we request a range starting at 0, we would record that number. Later, since this == 0, we'd allocate again. However, we wouldn't write the new resource into the BAR. This resulted in a resource leak as well as a BAR that couldn't access the resource at all since rman_get_start, et al, were wrong. MFC After: 1 week (assuming RELENG_6 is open for business)		2005-10-29 05:52:17 +00:00
..
eisa_pci.c
fixup_pci.c
ignore_pci.c
isa_pci.c	Don't save and restore the ELCR register across suspend and resume for	2005-09-29 15:00:09 +00:00
pci_if.m
pci_pci.c	fix CardBus issue for Compaq R3000 series laptop	2005-08-26 23:39:44 +00:00
pci_private.h
pci_user.c	For FreeBSD 4 binaries, when trying to read from a device that does	2005-08-26 01:00:19 +00:00
pci.c	MFp4: When doing lazy allocation, it turns out that we need to record the	2005-10-29 05:52:17 +00:00
pcib_if.m
pcib_private.h
pcireg.h	Use symbolic name rather thanhard coding the cap pointer offset for	2005-10-29 05:49:06 +00:00
pcivar.h	Allow one to access the cached values for CMDREG, CACHELNSZ, MINGNT,	2005-09-11 03:22:03 +00:00