From owner-freebsd-scsi Sat Jul 1 23:51:51 1995 Return-Path: freebsd-scsi-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA18861 for freebsd-scsi-outgoing; Sat, 1 Jul 1995 23:51:51 -0700 Received: from bunyip.cc.uq.oz.au (bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id XAA18855 ; Sat, 1 Jul 1995 23:51:49 -0700 Received: from cc.uq.oz.au by bunyip.cc.uq.oz.au id <25110-0@bunyip.cc.uq.oz.au>; Sun, 2 Jul 1995 16:51:40 +1000 Received: from netfl15a.devetir.qld.gov.au by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) with ESMTP id QAA12577; Sun, 2 Jul 1995 16:56:01 +1000 Received: from localhost by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) id GAA01310; Sun, 2 Jul 1995 06:53:07 GMT Message-Id: <199507020653.GAA01310@netfl15a.devetir.qld.gov.au> X-Mailer: exmh version 1.6 4/21/95 To: current@freebsd.org, scsi@freebsd.org Subject: Calling sequence for SCSI operations Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 02 Jul 1995 16:53:07 +1000 From: Stephen Hocking Sender: freebsd-scsi-owner@freebsd.org Precedence: bulk I'm in the process of finding out why the -current seagate.c driver does not work with Future Domain TMC-885 controllers and was wondering if anyone could tell me exactly what happens when things start up after the kernel is loaded. At the moment I'm getting a bunch of arbitration timeout and it refuses to see any of the drives. I do know, from my work with the 2.0R driver, that it can't cope with allowing disconnects. Stephen I do not speak for the Worker's Compensation Board of Queensland - They don't pay me enough for that!