From owner-freebsd-scsi Thu Aug 15 14:12:36 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA23189 for freebsd-scsi-outgoing; Thu, 15 Aug 1996 14:12:36 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA23181; Thu, 15 Aug 1996 14:12:33 -0700 (PDT) Message-Id: <199608152112.OAA23181@freefall.freebsd.org> To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-scsi@freebsd.org, count@key.hole.fi (Bror 'Count' Heinola) Subject: Re: Pioneer CD changer problem In-reply-to: Your message of "Thu, 15 Aug 1996 21:44:38 +0200." <199608151944.VAA01875@uriah.heep.sax.de> Date: Thu, 15 Aug 1996 14:12:33 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >The timeouts in the existing driver are way too short to properly >handle CD changers. I've got a Nakamichi on loan to test and fix >this, but defered all my CD-ROM work until Justin's changes are in the >tree to avoid massively diverging drivers. The current way of timeout >handling sucks rocks, all timeouts are wild guesses, and there's no >way to centrally maintain them. Each and every call to >scsi_scsi_cmd() specifies its own idea of what timeout might be >appropriate. Do you have any ideas on handling this better? Has anyone researched if there is any kind of status information we can retrieve so we can dynamically adjust timeout length? The SCSI layer is in dire need of a better error recovery strategy as well, and the timeout issue is part of that. Perhaps we can start tossing around ideas on how we should solve these problems? >-- >cheers, J"org > >joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE >Never trust an operating system you don't have sources for. ;-) -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations ===========================================