From owner-freebsd-scsi Wed Sep 30 12:32:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03270 for freebsd-scsi-outgoing; Wed, 30 Sep 1998 12:32:43 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from onizuka.vmunix.org (onizuka.vmunix.org [194.97.84.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA03236 for ; Wed, 30 Sep 1998 12:32:30 -0700 (PDT) (envelope-from torstenb@vmunix.org) Received: by onizuka.vmunix.org via sendmail with stdio id for ; Wed, 30 Sep 1998 21:32:03 +0200 (CEST) Message-Id: From: torstenb@vmunix.org (Torsten Blum) Subject: Re: Command Linking In-Reply-To: <199809301536.JAA24139@narnia.plutotech.com> from "Justin T. Gibbs" at "Sep 30, 98 09:36:14 am" To: gibbs@narnia.plutotech.com (Justin T. Gibbs) Date: Wed, 30 Sep 1998 21:32:03 +0200 (CEST) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Justin T. Gibbs 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? Yes, the alternative is one write buffer for the whole firmware image, which doesnt work due to the 64k physio limitation. > I had no intention of supporting this feature in the aic7xxx driver Hm, why ? -tb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message