Date: Tue, 08 Feb 2005 15:26:02 -0700 From: Scott Long <scottl@freebsd.org> To: Chuck Tuffli <chuck_tuffli@agilent.com> Cc: Dan Nelson <dnelson@allantgroup.com> Subject: Re: how CAM/HBA probe for devices? Message-ID: <42093C7A.3000704@freebsd.org> In-Reply-To: <42093A11.9040403@agilent.com> References: <E1CyYUO-0003tg-IT@cs1.cs.huji.ac.il> <4208F618.3000400@freebsd.org> <20050208214956.GA3104@dan.emsphone.com> <42093A11.9040403@agilent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Chuck Tuffli wrote: > 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. > That sounds about right. I couldn't remember exactly what the exsting drivers handle, so i was just playing it safe. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42093C7A.3000704>