From owner-aic7xxx Fri Jan 18 10:21: 1 2002 Delivered-To: aic7xxx@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 4A74D37B417 for ; Fri, 18 Jan 2002 10:20:59 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.6/8.11.5) with ESMTP id g0IIKrx36234; Fri, 18 Jan 2002 11:20:53 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200201181820.g0IIKrx36234@aslan.scsiguy.com> To: Alexey Zhuravlev Cc: AIC7xxx@FreeBSD.ORG Subject: Re: question about aic7xxx In-Reply-To: Your message of "Fri, 18 Jan 2002 21:12:15 +0300." <20020118211215.486c6b00.alexey@udm.ru> Date: Fri, 18 Jan 2002 11:20:53 -0700 From: "Justin T. Gibbs" Sender: owner-aic7xxx@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Is there the way to know last events and messages related to that tag >in aic7xxx ? Depending on the type of card you are using, you could record additional state in the "status packet" of that transactions control block. This would require modification of the firmware and a bit of thought about which bytes are available to be used for this purpose. Due to time contraints on our U320 driver schedule, I can't commit time in the near future to add these kinds of diagnostics. As far as the "last message seen", it should have been a disconnect message as that transaction is on the disconnected list. Trasactions are removed from the disconnection list on a reselection and are only added to the disconnect list when that message is seen. The firware waits for bus free after a disconnect message and will complain if it doesn't see one before the next REQ to it on the bus. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe aic7xxx" in the body of the message