From owner-freebsd-scsi Fri Apr 27 10: 0:59 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 28E5237B423 for ; Fri, 27 Apr 2001 10:00:52 -0700 (PDT) (envelope-from gibbs@scsiguy.com) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.2/8.9.3) with ESMTP id f3RH01s35435; Fri, 27 Apr 2001 11:00:28 -0600 (MDT) (envelope-from gibbs@scsiguy.com) Message-Id: <200104271700.f3RH01s35435@aslan.scsiguy.com> To: Joerg Wunsch Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: sa(4) jamming In-Reply-To: Your message of "Fri, 27 Apr 2001 10:48:55 MDT." <200104271649.f3RGmts35017@aslan.scsiguy.com> Date: Fri, 27 Apr 2001 11:00:01 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >That depends on whether the sa driver relies on any settings (mode >page or otherwise) that are invalidated by a reset, but aren't >restored when the bus reset async event occurs. Just to be more clear here, it is the peripheral driver's responsibility to restore any of this state if it needs to. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message