From owner-freebsd-hackers Fri Jul 7 08:24:08 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA15863 for hackers-outgoing; Fri, 7 Jul 1995 08:24:08 -0700 Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA15857 for ; Fri, 7 Jul 1995 08:23:54 -0700 Received: (from dfr@localhost) by minnow.render.com (8.6.9/8.6.9) id QAA16527; Fri, 7 Jul 1995 16:22:59 +0100 Date: Fri, 7 Jul 1995 16:22:58 +0100 (BST) From: Doug Rabson To: Simon Marlow cc: "Serge V.Vakulenko" , davidg@root.com, hackers@freebsd.org Subject: Re: Beta version of IDE CD-ROM driver ready In-Reply-To: <199507071457.HAA15126@freefall.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hackers-owner@freebsd.org Precedence: bulk On Fri, 7 Jul 1995, Simon Marlow wrote: > > > > Hmm... I did not try the second controller yet... > > > > > > Probably, you have a drive which does not interrupt before > > > gettin a packet command. The driver of version 1.0 does not handle > > > this properly. > > > > I am getting this behaviour on wcd0 (I don't have any IDE disks at all). > > Is there a quick hack I can use to get past the probe? > > I did some investigation, and it seems that the reset operation isn't > completing properly, so it times out. As a hack, I changed the line > (in wd.c) > > if (wdreset(du) != 0 && (DELAY(RECOVERYTIME), wdreset(du)) != 0) > goto nodevice; > > to carry on even if the reset timed out. > > This gets the controller probed, and you can also get the CDROM > attached. There are more problems, however: the extra interrupt that > is supposed to happen as a result of the attach operation never comes, > and the driver won't start any operations because it thinks the > controller is active. > > So I modified wd.c again to not expect this interrupt from wdc1, but > things still don't work (it seems no interrupts are coming from the > controller, I have no idea why). > > Perhaps someone who knows more than me about this stuff can help? :-) Yea, I got this far when I hacked on it again this morning. I now get "controller busy" type messages when I open the device and the process hangs, sleeping on "atareq". -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 251 4411 FAX: +44 171 251 0939