Searched hist:a0ca9909609470ad779b9b9cc68ce96e975afff7 (Results 1 – 3 of 3) sorted by relevance
| /openbmc/linux/arch/x86/pci/ |
| H A D | mmconfig_64.c | diff a0ca9909609470ad779b9b9cc68ce96e975afff7 Mon Jan 14 16:31:09 CST 2008 Ivan Kokshaysky <ink@jurassic.park.msu.ru> 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>
|
| H A D | mmconfig_32.c | diff a0ca9909609470ad779b9b9cc68ce96e975afff7 Mon Jan 14 16:31:09 CST 2008 Ivan Kokshaysky <ink@jurassic.park.msu.ru> 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>
|
| H A D | mmconfig-shared.c | diff a0ca9909609470ad779b9b9cc68ce96e975afff7 Mon Jan 14 16:31:09 CST 2008 Ivan Kokshaysky <ink@jurassic.park.msu.ru> 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>
|