From owner-freebsd-scsi Tue Jan 2 8: 0:13 2001 From owner-freebsd-scsi@FreeBSD.ORG Tue Jan 2 08:00:11 2001 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by hub.freebsd.org (Postfix) with ESMTP id 5236337B400 for ; Tue, 2 Jan 2001 08:00:11 -0800 (PST) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by serenity.mcc.ac.uk with esmtp (Exim 2.05 #4) id 14DTr8-000Ozo-00 for freebsd-scsi@freebsd.org; Tue, 2 Jan 2001 16:00:10 +0000 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.11.1/8.11.1) id f02G09d28173 for freebsd-scsi@freebsd.org; Tue, 2 Jan 2001 16:00:09 GMT (envelope-from jcm) Date: Tue, 2 Jan 2001 16:00:09 +0000 From: j mckitrick To: freebsd-scsi@freebsd.org Subject: parallel port zip driver Message-ID: <20010102160009.A28117@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello all, I am working to find a problem in the parallel port zip plus driver, and I have a few questions about the scsi code above the driver. Concening the SCSI_STATUS values, csio->scsi_status seems to only have even-numbered values, according to scsi_all.h. In the process of debugging, if the zip driver returns 0x01, the scsi driver seems to choke without explaining why. There is so much code in scsi, cam, and aic7xxx that I am not sure where to look, so I thought maybe I would ask and maybe discover the problem much more quickly. jm -- ------------------------------------------------------------------------ Jonathon McKitrick -- jcm@freebsd-uk.eu.org They laugh because I'm different. I laugh because they're all the same. ------------------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message