| commit | adcd740341dbd58eb94a8c2885c171ce9eb8677c | |
| author | Matthew Wilcox <matthew@wil.cx> | |
| Mon, 12 Oct 2009 14:24:30 +0000 (12 08:24 -0600) | ||
| committer | Tony Luck <tony.luck@intel.com> | |
| Tue, 13 Oct 2009 17:44:42 +0000 (13 10:44 -0700) | ||
| tree | 99cbbea95dc9864b3d39e12180ad8dcdeeabc04c | treesnapshot (tar.gz zip) |
| parent | dec1798f81f7e8a299734bdc29197ae77bf08018 | commitdiff |
[IA64] Require SAL 3.2 in order to do extended config space ops
We had assumed that SAL firmware would return an error if it didn't
understand extended config space. Unfortunately, the SAL on the SGI 750
doesn't do that, it panics the machine. So, condition the extended PCI
config space accesses on SAL revision 3.2.
Signed-off-by: Matthew Wilcox <willy@linux.intel.com>
Tested-by: Brad Spengler <spender@grsecurity.net>
Signed-off-by: Tony Luck <tony.luck@intel.com>
We had assumed that SAL firmware would return an error if it didn't
understand extended config space. Unfortunately, the SAL on the SGI 750
doesn't do that, it panics the machine. So, condition the extended PCI
config space accesses on SAL revision 3.2.
Signed-off-by: Matthew Wilcox <willy@linux.intel.com>
Tested-by: Brad Spengler <spender@grsecurity.net>
Signed-off-by: Tony Luck <tony.luck@intel.com>
| arch/ia64/pci/pci.c | diffblobblamehistory |