aboutsummaryrefslogtreecommitdiffstats
path: root/arch
diff options
context:
space:
mode:
authorBrice Goglin <brice@myri.com>2007-01-10 23:15:29 -0800
committerLinus Torvalds <torvalds@woody.osdl.org>2007-01-11 18:18:20 -0800
commit47a4d5be7c50b2e9b905abbe2b97dc87051c5a44 (patch)
treeeac7cb4258e1d3c5e5db7d6c0ea8d1c017661852 /arch
parente5e5673f828623e58a401862b33173591faaeaff (diff)
downloadkernel_samsung_smdk4412-47a4d5be7c50b2e9b905abbe2b97dc87051c5a44.zip
kernel_samsung_smdk4412-47a4d5be7c50b2e9b905abbe2b97dc87051c5a44.tar.gz
kernel_samsung_smdk4412-47a4d5be7c50b2e9b905abbe2b97dc87051c5a44.tar.bz2
[PATCH] increment pos before looking for the next cap in __pci_find_next_ht_cap
While testing 2.6.20-rc3 on a machine with some CK804 chipsets, we noticed that quirk_nvidia_ck804_msi_ht_cap() was not detecting HT MSI capabilities anymore. It is actually caused by the MSI mapping on the root chipset being the 2nd HT capability in the chain. pci_find_ht_capability() does not seem to find anything but the first HT cap correctly, because it forgets to increment the position before looking for the next cap. The following patch seems to fix it. At least, this proves that having a ttl is good idea since the machine would have been stucked in an infinite loop if we didn't have a ttl :) We have to pass pos + PCI_CAP_LIST_NEXT to __pci_find_next_cap_ttl to get the next HT cap instead of the same one again. Signed-off-by: Brice Goglin <brice@myri.com> Signed-off-by: Andrew J. Gallatin <gallatin@myri.com> Cc: Greg KH <greg@kroah.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions