From owner-freebsd-scsi Wed Sep 30 08:43:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA20743 for freebsd-scsi-outgoing; Wed, 30 Sep 1998 08:43:16 -0700 (PDT) (envelope-from owner-freebsd-scsi@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 IAA20729 for ; Wed, 30 Sep 1998 08:43:14 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id JAA24139; Wed, 30 Sep 1998 09:36:14 -0600 (MDT) Date: Wed, 30 Sep 1998 09:36:14 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199809301536.JAA24139@narnia.plutotech.com> To: torstenb@vmunix.org cc: scsi@FreeBSD.ORG Subject: Re: Command Linking Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-BETA (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you wrote: > Well, I can read the firmware from the drive and write it to a file. The > problem starts when I start to write the new firmware. Due to the physio > problem I have to upload the firmware in 64k parts with the WRITE BUFFER > command. After each WRITE BUFFER the drive sends a MSG_LINK_CMD_COMPLETE > (0x0a) and the scsi system can't handle it: Do you have to load the firmware using a series of linked commands instead of unlinked commands? I had no intention of supporting this feature in the aic7xxx driver and it would probably require some additional tweaking to the SCSI transport layer to make it work. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message