From owner-freebsd-scsi@FreeBSD.ORG Tue Feb 8 22:15:20 2005 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9134616A4CE; Tue, 8 Feb 2005 22:15:20 +0000 (GMT) Received: from msgbas9x.lvld.agilent.com (msgbas9x.lvld.agilent.com [192.25.144.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6561043D2F; Tue, 8 Feb 2005 22:15:20 +0000 (GMT) (envelope-from chuck_tuffli@agilent.com) Received: from relcos2.cos.agilent.com (relcos2.cos.agilent.com [130.29.152.237]) by msgbas9x.lvld.agilent.com (Postfix) with ESMTP id 7A3C31FC9; Tue, 8 Feb 2005 15:15:17 -0700 (MST) Received: from wlvdvs01.lvld.agilent.com (wlvdvs01.lvld.agilent.com [148.5.6.4]) by relcos2.cos.agilent.com (Postfix) with ESMTP id BABA225F; Tue, 8 Feb 2005 15:15:19 -0700 (MST) Received: from rtl.rose.agilent.com ([130.30.179.189]) by wlvdvs01.lvld.agilent.com with InterScan Messaging Security Suite; Tue, 08 Feb 2005 15:15:18 -0700 Received: from [141.184.129.212] (cos1nai129212.cos.agilent.com [141.184.129.212])ESMTP id OAA22956; Tue, 8 Feb 2005 14:15:15 -0800 (PST) Received: from 127.0.0.1 (AVG SMTP 7.0.300 [265.8.6]); Tue, 08 Feb 2005 14:15:47 -0800 Message-ID: <42093A11.9040403@agilent.com> Date: Tue, 08 Feb 2005 14:15:45 -0800 From: Chuck Tuffli User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dan Nelson References: <4208F618.3000400@freebsd.org> <20050208214956.GA3104@dan.emsphone.com> In-Reply-To: <20050208214956.GA3104@dan.emsphone.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-scsi@freebsd.org cc: Scott Long Subject: Re: how CAM/HBA probe for devices? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Feb 2005 22:15:20 -0000 Dan Nelson wrote: ... > The fibre-channel drivers (isp,mpt) must have been the first to have > hit this problem; do they do the same thing as atapicam? If memory serves, the FC drivers take the results from loop/fabric discovery and then map each discovered device to a target_id. During boot, the driver stalls/sleeps waiting for discovery to complete before completing to the CAM. Later on if the loop/fabric changes, the user would need to force a re-scan to pick up the new devices. -- Chuck Tuffli Agilent Technologies