On Mon, 24 Jan 2005 08:10:07 -0500
Thor Lancelot Simon <tls@rek.tjls.com> wrote:

> The upshot of a rather strange recent thread in netbsd-help (titled
> "got drivers?") was that, at least on some PCI alphas, neither SRM
> nor our MD PCI code set devices' latency timers at all.  A user had
> a machine with two tulips, a pciide, and a QL1040 -- only the 1040
> worked reliably, because the isp driver explicitly whacks the latency
> timer value to 0x40 if it finds it at 0x00.
> 
> The user adjusted the pciide driver to set the latency timer to 0x40
> and all of a sudden he could use the disk and talk on the network at
> the same time without losing packets.
> 
> If SRM isn't going to set the latency timer it seems to me we ought to;
> and not in every device driver, either!
> 
> -- 
>  Thor Lancelot Simon	                                      tls@rek.tjls.com
> 
> "The inconsistency is startling, though admittedly, if consistency is to be
>  abandoned or transcended, there is no problem."		- Noam Chomsky
> 
> 

hi,

FYI, I reported a similar problem recently:

http://mail-index.netbsd.org/port-alpha/2005/01/13/0000.html

I patched the MI driver(works for me) but really the MD code should
handle this as a few people suggested.

Also, it turns out this problem has been known since
at least 1998. 'Guess it's time to get it pathed once and for all?

http://mail-index.netbsd.org/port-alpha/1998/08/25/0000.html

Tobias