Date: Thu, 11 Jan 2001 17:17:17 +0000 (GMT) From: Nick Hibma <n_hibma@calcaphon.com> To: j mckitrick <jcm@FreeBSD-uk.eu.org> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: scsi and PS2 mode parallel port programming Message-ID: <Pine.BSF.4.20.0101111714540.1786-100000@henny.webweaving.org> In-Reply-To: <20010111171117.A323@dogma.freebsd-uk.eu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> 2. In the list of scsi error codes, 0x00 is no error, and the defacto
> errors start with 0x02. However, in PS2 mode, when asked for status, the
> zip drive returns 0x01. If I ignore any byte with this bit set, the drive
> seems to work okay, but this is a crude and potentially risky fix. Is there
> any way to find out what this actually means? Could it just be a stray bit?
> Or is it an additional scsi status that should be handled? I *believe* PS2
> mode quit working for parallel port zips after a commit to the cam/scsi
> system Dec 1999, but I am not familiar with that code, so I didn't know
> where to start looking.
Could you point a date (or date range) when that commit to CAM was? I'm
vaguely familiar with it and more than willing to help.
Where does the 0x01 come from? From the drive or from the drivers?
> I am very interested in contributing my meager skills to the BSD effort in
> this manner, but I need a little help getting pointed in the right
> direction. Thanks in advance for any help anyone can offer.
-hackers is probably the best place for these questions if you want to
try and find a person with the necessary skills.
Nick
--
Qube Software, Ltd. Private:
n_hibma@qubesoft.com n_hibma@webweaving.org
n_hibma@freebsd.org
http://www.qubesoft.com/ http://www.etla.net/~n_hibma/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.20.0101111714540.1786-100000>