Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 7 Jun 1999 21:31:34 +0200 (CEST)
From:      Soren Schmidt <sos@freebsd.dk>
To:        jedgar@fxp.org (Chris D. Faulhaber)
Cc:        mike@smith.net.au, junichi@junichi.org, hackers@FreeBSD.ORG
Subject:   Re: wfd.c and ATAPI Zip
Message-ID:  <199906071931.VAA06379@freebsd.dk>
In-Reply-To: <Pine.BSF.4.10.9906071458370.15515-100000@pawn.primelocation.net> from "Chris D. Faulhaber" at "Jun 7, 1999  3: 4:33 pm"

next in thread | previous in thread | raw e-mail | index | archive | help
It seems Chris D. Faulhaber wrote:
> 
> I have an off-brand (NEC) Zip Drive with:
>      <IOMEGA  ZIP 100       ATAPI       Floppy/12.A>
> which does have buggy firmware; I also have another one with:
>      <IOMEGA  ZIP 100       ATAPI/13.A>
> that has no problem when I remove the 64 block limitation.
> 
> In this case, I would use strncmp instead of strcmp to test the first 27
> characters.
> 
> So what you are saying is that we are limiting all Zip drives instead of
> being based solely on firmware revision?  Any reason for that?

Hmm, well in the atapi-fd driver in the new ata/atapi system I only
check for !strncmp(atp->atapi_parm->model, "IOMEGA  ZIP", 11) which
is even more pessimistic. However the overhead added here is small
compared to the general speed of the ZIP drive, so its not a problem.

-Søren


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?199906071931.VAA06379>