From: mentor <mentor@0192ed92-7a03-0410-a25b-9323aeb14dbd>
Date: Mon, 8 Oct 2007 12:02:22 +0000 (+0000)
Subject: Significantly lower the PCI_LATENCY_TIMER value that we were setting. This is essenti... 
X-Git-Url: http://git.ozo.com/?a=commitdiff_plain;h=11f13a175232058fcf877a2b09b2a4c6536a8df9;p=madwifi%2F.git

Significantly lower the PCI_LATENCY_TIMER value that we were setting. This is essentially hte total time we are allowed to hold onto the PCI bus, before we see if anyone else wants a go. Higher means better throuhgput at the expense of the latency of other devices, and vice versa.

This value is roughly around the value that other devices are setting. The previous value appeared to be stupidly high.

This may solve some interactivity problems and machine performance issues.


git-svn-id: http://madwifi-project.org/svn/madwifi/trunk@2732 0192ed92-7a03-0410-a25b-9323aeb14dbd
---

diff --git a/ath/if_ath_pci.c b/ath/if_ath_pci.c
index 828122b..45a833c 100644
--- a/ath/if_ath_pci.c
+++ b/ath/if_ath_pci.c
@@ -155,7 +155,7 @@ ath_pci_probe(struct pci_dev *pdev, const struct pci_device_id *id)
 	 * set it to the value used by other systems.  It may be worth
 	 * tweaking this setting more.
 	 */
-	pci_write_config_byte(pdev, PCI_LATENCY_TIMER, 0xa8);
+	pci_write_config_byte(pdev, PCI_LATENCY_TIMER, 0x60);
 
 	pci_set_master(pdev);