Home
PCI latency behavior for selected I/O Devices
When people first started looking into the PCI latency settings on their PCs, they discovered that
while some motherboard BIOS allowed the PCI latency to be set to a specific value, the device drivers for
the devices would often set to their own preferred value on startup, making the PCI latency setting for a
device impossible to control without a program such as Double Dawg. This leads to the natural question: "How do
the device drivers handle the PCI latency settings?"
Martin Walker of SOS Magazine asked SOS forum members to perform some
experiments to determine how the drivers for their devices manipulated the PCI latency setting,
and he did some testing with his own gear as well. He has graciously provided us with this summary of the
latency-setting behavior of some popular I/O devices.
DEVICES THAT ADOPT THE DEFAULT BIOS OR MOTHERBOARD VALUE:
GRAPHICS CARDS
- Matrox G400 (except if default is 32, when it's forced to 64)
- Matrox G450 (except if deefault is 32 or 248, when it's forced to 64)
- Matrox G550 (except if default is 32, when it's forced to 64)
- Matrox P750
SOUNDCARDS
- Emu 0404
- Emu 1820M
- ESI Juli@
- C-Media CMI8738 motherboard soundchip
- M Audio Audiophile 2496 (2 reports)
- M Audio Delta 44
- Turtle Beach Santa Cruz
- Yamaha SW1000XG
DEVICES THAT FORCE THEIR OWN PCI LATENCY TIMER VALUE:
GRAPHICS CARDS
- 255 ATI Radeon 9000
- 255 ATI Radeon Mobility M9
- 248 Creative TNT2 Video
- 248 GeForce MX440
SOUNDCARDS
- 255 RME HDSP Multiface (also reported at 248)
- 192 Echo Mia
- 192 Echo Mia MIDI
- 192 Echo Indigo io
- 128 Universal Audio UAD-1 (except 255 in version 2.0, default in version 2.1)
- 0 Marian Marc X