From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Mon,  5 Oct 1998 09:38:08 -0400
From: jmk@plan9.bell-labs.com jmk@plan9.bell-labs.com
Subject: [9fans] 9fs and 1542
Topicbox-Message-UUID: 834a11a0-eac8-11e9-9e20-41e7f4b1d025
Message-ID: <19981005133808.3EzD8eT0ct98rMyqGSAx4nI7N1M5DFOqltnXmfcwr3U@z>

I'll echo the concerns about termination and also to double-check
the kernel is correctly determining the cpu speed for delay loops.

That said, I've looked at the Plan9 fs scsiprobe routine and I'd just
take out the loop, turning

	status = 0;
	for(t = 0; t < 3; t++) {
		status = testur(ctlr, d);
		if(status == 0x6000)
			break;
	}

into

	status = testur(ctlr, d);

I don't know why the loop is there, it's probably a hangover
from some buggy hardware in the distant past - some of this code
dates from a Unibus controller on a Vax-11/750 - the current fs code
doesn't do this. The loop shouldn't cause any problems, but it
might be interacting with some marginal hardware problem.

--jim