From owner-freebsd-current Sun Nov 22 15:42:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26899 for freebsd-current-outgoing; Sun, 22 Nov 1998 15:42:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26877 for ; Sun, 22 Nov 1998 15:42:16 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id QAA08681; Sun, 22 Nov 1998 16:34:05 -0700 (MST) Date: Sun, 22 Nov 1998 16:34:05 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199811222334.QAA08681@narnia.plutotech.com> To: gfm@mira.net (Graham Menhennitt) cc: current@FreeBSD.ORG Subject: Re: Adaptec 1542B still not detected X-Newsgroups: pluto.freebsd.current In-Reply-To: <3659842e.234385067@mira.net> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-BETA (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <3659842e.234385067@mira.net> you wrote: > I just updated my 3.0-current system via cvsup. A kernel built with the > latest still fails to detect my Adaptec 1542B. I reported this a couple of > weeks ago and even posted a fix. Could somebody please make a patch and > commit it. The patch is inappropriate as it won't necessarily solve the problem on all machines (loop is CPU speed dependant). 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. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message