Subject: Re: kern/22869: Slave IDE drive not detected
To: Charles M. Hannum <abuse@spamalicious.com>
From: Manuel Bouyer <bouyer@antioche.lip6.fr>
List: netbsd-bugs
Date: 09/22/2003 17:41:16
On Mon, Sep 22, 2003 at 02:26:33PM +0000, Charles M. Hannum wrote:
> 
> > detecting the ghosting *before the reset* should't speed up the reset.
> > If we have only one master, it will also handle registers read for the
> > slave and both drives will appear ready at the same time.
> 
> I'm not sure what difference you think that makes.  Since we're
> (typically) reading a status of all-0s at that point, the reset does

We should get the contents of the drive 0 registers, not all 0.

> complete quickly, but we still try sending a command to the bogus
> drive 1 and time out.

I can't see how we can differentiate a real drive from a bogus one
exept by sending a command, as we will read the same values from registers,
whatever drive is selected, when there is only one drive.

Now, a command send to drive 1, when there's only one master, shoud not time
out, it should be aborted immediatly by the drive. If it times out maybe
we have a problem with the code sending the command.

--
Manuel Bouyer, LIP6, Universite Paris VI.           Manuel.Bouyer@lip6.fr
     NetBSD: 24 ans d'experience feront toujours la difference
--