diff options
author | Ivan Kokshaysky <ink@jurassic.park.msu.ru> | 2008-01-14 17:31:09 -0500 |
---|---|---|
committer | Linus Torvalds <torvalds@woody.linux-foundation.org> | 2008-02-10 12:52:45 -0800 |
commit | a0ca9909609470ad779b9b9cc68ce96e975afff7 (patch) | |
tree | af1ce8cdf6e927e25ad92869849456916e236fbf /arch/x86/pci/legacy.c | |
parent | 7cf712db6087342e5e7e259d3883a7b5ac3212d1 (diff) | |
download | kernel_samsung_smdk4412-a0ca9909609470ad779b9b9cc68ce96e975afff7.zip kernel_samsung_smdk4412-a0ca9909609470ad779b9b9cc68ce96e975afff7.tar.gz kernel_samsung_smdk4412-a0ca9909609470ad779b9b9cc68ce96e975afff7.tar.bz2 |
PCI x86: always use conf1 to access config space below 256 bytes
Thanks to Loic Prylli <loic@myri.com>, who originally proposed
this idea.
Always using legacy configuration mechanism for the legacy config space
and extended mechanism (mmconf) for the extended config space is
a simple and very logical approach. It's supposed to resolve all
known mmconf problems. It still allows per-device quirks (tweaking
dev->cfg_size). It also allows to get rid of mmconf fallback code.
Signed-off-by: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Signed-off-by: Matthew Wilcox <willy@linux.intel.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'arch/x86/pci/legacy.c')
0 files changed, 0 insertions, 0 deletions