From owner-freebsd-hackers Tue May 4 20:48: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id 48FB414D2B for ; Tue, 4 May 1999 20:47:58 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id VAA01260; Tue, 4 May 1999 21:38:05 -0600 (MDT) Date: Tue, 4 May 1999 21:38:05 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199905050338.VAA01260@narnia.plutotech.com> To: Nick Hibma Cc: hackers@FreeBSD.org Subject: Re: CAM: devices without path X-Newsgroups: pluto.freebsd.hackers In-Reply-To: User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you wrote: > > What extra calls are needed to remove the path as well as the devices if > a CAM controller disappears? I haven't gone through and verified that a manual detach of a SIM is possible yet. I figured I'd cross that bridge once the configuration framework was up to the task, and I'm not sure it quite is yet. I'll be able to look into this in more detail in another week or so. > Currently I do the following > > static void > umass_cam_detach(umass_softc_t *sc) > { > /* Detach from CAM layer > * XXX do we need to delete the device first? > */ > At a minimum, you need to additionally perform an AC_LOST_DEVICE async notification so that the peripheral drivers detach. > xpt_free_path(sc->path); > xpt_bus_deregister(cam_sim_path(sc->sim)); > cam_sim_free(sc->sim, /*free_devq*/TRUE); > } -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message