summaryrefslogtreecommitdiffstats
path: root/sys/dev/asr/asr.c
diff options
context:
space:
mode:
authorimp <imp@FreeBSD.org>2004-04-21 20:19:56 +0000
committerimp <imp@FreeBSD.org>2004-04-21 20:19:56 +0000
commitec1a4689236bc43ad97c0a482fe26e79a065f86f (patch)
tree91507a08465c2c3f7f8b9827c872b601620e6dc2 /sys/dev/asr/asr.c
parent144cdd3d4018667dc2f3c725749e61bcfdd1b30d (diff)
downloadFreeBSD-src-ec1a4689236bc43ad97c0a482fe26e79a065f86f.zip
FreeBSD-src-ec1a4689236bc43ad97c0a482fe26e79a065f86f.tar.gz
ata devices in legacy are special, and we must treat them as such.
While I would have prefered to have a solution that didn't move knowledge of this into the pci layer. However, this is literally the only exception that's listed in the PCI standard to the usual way of decoding BARs. atapci devices in legacy mode now ignore the first 4 bars and hard code the values to the legacy ide values (well, for each of the controllers that are in legacy mode). The 5th bar is handled normally. Remove the zero bar handling. zero bars should be ignored at all other times, and since we handle that specially, we don't need the older workaround.
Diffstat (limited to 'sys/dev/asr/asr.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud