From owner-freebsd-current Wed Sep 30 16:49:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA28553 for freebsd-current-outgoing; Wed, 30 Sep 1998 16:49:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA28495 for ; Wed, 30 Sep 1998 16:49:30 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id JAA23414; Thu, 1 Oct 1998 09:48:48 +1000 Date: Thu, 1 Oct 1998 09:48:48 +1000 From: Bruce Evans Message-Id: <199809302348.JAA23414@godzilla.zeta.org.au> To: karl@Denninger.Net, toasty@home.dragondata.com Subject: Re: Long IDE probes? Cc: bright@hotjobs.com, current@FreeBSD.ORG, dnelson@emsphone.com, tom@uniserve.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >To shed some light.... This is all according to the ATA specs: > >We throw a hardware reset. > >The device must set the BSY flag within 400ns, after RESET- is turned off. >If we can see BSY, the device is there. We should be able to stop at this >point, as suposedly this is a yes/no test for a device being present. > >However, after this, we're supposed to do some magic, then the device has 31 >seconds to respond. > >Possibly there are some rogue devices/chipsets out there that fool the >driver with the BSY test, and so we're forced to wait for the full 31 >seconds for the reply? We're supposed to wait 31 seconds for the drives to become unbusy. We actually only wait only 10 seconds (for each drive IIRC). With the current (poorly organised) probe logic, the correct wait time of 31 seconds would give a delay of > 2 minutes when no drives are attached. This should not be surprising. The BIOS also takes minute(s) to time out if it is misconfigured. >Not sure, but that's what the 'standard' is. Do you prefer SCSI, where there is no standard timeout, and the OS guesses that 15 seconds is enough? Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message