Date: Wed, 25 Nov 1998 12:36:31 -0700 From: "Justin T. Gibbs" <gibbs@narnia.plutotech.com> To: Warner Losh <imp@village.org> Cc: gfm@mira.net (Graham Menhennitt), current@FreeBSD.ORG Subject: Re: Adaptec 1542B still not detected Message-ID: <199811251943.MAA06556@pluto.plutotech.com> In-Reply-To: Your message of "Wed, 25 Nov 1998 12:15:58 MST." <199811251915.MAA26254@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>In message <199811222334.QAA08681@narnia.plutotech.com> "Justin T. Gibbs" writ >es: >: The patch is inappropriate as it won't necessarily solve the problem >: on all machines (loop is CPU speed dependant). > >I've fixed this by using DELAY. But we have no way of knowing how long of a wait is enough. >: I've been meening >: to re-examine the aha probe code to see if we even need to look at >: the geometry register. A better approach may be to try an extended >: command and succeed the probe only if it fails. This requires the >: ability to recovery from an invalid command in the driver and >: ensuring that this works on all aha models. Ping me later in the >: week and I should have something for you to test. > >I've tried that in the aha probe, but it locks up some cards (none of >the ones that I have, but others that people have reported to me). This makes no sense considering that in the GENERIC kernel the bt probe occurs before the aha probe and the bt probe will cause an extended setup command to go to the aha (assuming it shows up as having a geometry register). I would suspect that we aren't clearing the invalid command status properly if sending an extended setup command doesn't work. Which cards had problems with the extended setup command? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199811251943.MAA06556>