From 5e83a678cc5266bc6e9e9b9866df9bad0a49e138 Mon Sep 17 00:00:00 2001 From: Michael Witten Date: Fri, 15 Jul 2011 03:25:44 +0000 Subject: [PATCH] --- yaml --- r: 263032 b: refs/heads/master c: e6b85a1f8a56d3c9db0273b7e4aaab802dc07a9b h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/Documentation/PCI/MSI-HOWTO.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/[refs] b/[refs] index 0d5694c9116d..524f3136f245 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 952df55b5a30913f4a5536b12ad09dd95c66d83f +refs/heads/master: e6b85a1f8a56d3c9db0273b7e4aaab802dc07a9b diff --git a/trunk/Documentation/PCI/MSI-HOWTO.txt b/trunk/Documentation/PCI/MSI-HOWTO.txt index 257628fdd464..2322a570beb5 100644 --- a/trunk/Documentation/PCI/MSI-HOWTO.txt +++ b/trunk/Documentation/PCI/MSI-HOWTO.txt @@ -316,7 +316,7 @@ Some bridges allow you to enable MSIs by changing some bits in their PCI configuration space (especially the Hypertransport chipsets such as the nVidia nForce and Serverworks HT2000). As with host chipsets, Linux mostly knows about them and automatically enables MSIs if it can. -If you have a bridge which Linux doesn't yet know about, you can enable +If you have a bridge unknown to Linux, you can enable MSIs in configuration space using whatever method you know works, then enable MSIs on that bridge by doing: