From owner-freebsd-scsi Sat Jan 25 10:07:55 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA10477 for freebsd-scsi-outgoing; Sat, 25 Jan 1997 10:07:55 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA10470 for ; Sat, 25 Jan 1997 10:07:48 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0voCVq-00031I-00; Sat, 25 Jan 1997 11:07:34 -0700 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Subject: Re: Question about the scsi sub system. Cc: scsi@freebsd.org In-reply-to: Your message of "Sat, 25 Jan 1997 18:34:05 +0100." References: Date: Sat, 25 Jan 1997 11:07:34 -0700 From: Warner Losh Message-Id: Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message J Wunsch writes: : Move the START UNIT command earlier in the sdopen() function. I've : already did this for the `cd' and `od' driver, and at least in the : latter case, it works fine. (I'm running the `od' driver with an : automatic spindown at odclose().) I noticed that in the sd and cd drivers, the start unit command are placed in the same location, relative to eachother. Is this in your private copy? In a branch that I'm missing? Anyway, I'm going to try moving scsi_start_unit() to before the scsi_test_unit_ready() call and see if that helps or not. Thanks for the suggestion! Warner