[lkml]   [1998]   [Sep]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: PCI_LATENCY_TIMER brain-damage in net drivers.
   Date: Sat, 26 Sep 1998 11:17:18 +0200 (MET DST)
From: Gerard Roudier <>

The only text part of this code states about 10 being an
unreasonnable value and the code forces the maximum value 255 when
the actual value is less than 10.

Yes I saw and understood all of your mail, no need to repeat.

I am just saying why some are there for more legitimate reasons than
others. I think it's all crap too :-)

Just so I can be quoted with a specific example, from some version of
3c59x.c I have sitting around in the Cobalt kernel tree (v0.99C):

/* Get and check the latency values. On the 3c590 series
the latency timer must be set to the maximum value to avoid
data corruption that occurs when the timer expires during
a transfer -- a bug in the Vortex chip only. */
u8 new_latency = (device&0xff00) == 0x5900 ? 248 : 32;

David S. Miller

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:44    [W:0.071 / U:3.396 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site