Date: Thu, 24 Mar 2005 12:07:28 +0100 From: Bernd Walter <ticso@cicely12.cicely.de> To: John Baldwin <jhb@freebsd.org> Cc: Julian Elischer <julian@elischer.org> Subject: Re: Reattach/redetect allways connected umass device - is it possible ? Message-ID: <20050324110727.GX53520@cicely12.cicely.de> In-Reply-To: <77e48641fc04164b4c81cce75c42a38b@FreeBSD.org> References: <1110800717.1296.19.camel@localhost> <200503231411.46948.jhb@FreeBSD.org> <20050323154642.J37251@sasami.jurai.net> <42421D8D.5060502@elischer.org> <20050323205841.N37251@sasami.jurai.net> <77e48641fc04164b4c81cce75c42a38b@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 23, 2005 at 11:05:04PM -0500, John Baldwin wrote: > > On Mar 23, 2005, at 9:00 PM, Matthew N. Dodd wrote: > > >On Wed, 23 Mar 2005, Julian Elischer wrote: > >>eject should imply a detach.. > >>i.e. I think your patch should call the detach code from the eject > >>code. > > > >Eject is for devices that support removable media. > > So are flash memory sticks ejectable media from a slot in a laptop that > never goes away? Seems like it should be an ejectable media to me. > *shrug* Flash disks are just standard direct access disk drives with exchangeable media. You have the same kind of trouble with MO, ZIP or any other removeable media devices. The problem is neither the device nor cam. It is GEOM that needs a trigger for rereading the new media. I can't imagine any device related brokenness that a CAM disconnect, which is a kernel internal thing, could work around. And no - If I issue an eject I want the drive to eject the media and nothing else, but since most flash drives have no motor eject this command can't physically do what is expected anyway. A CAM detach would be fine, but for general use - not for this case. -- B.Walter BWCT http://www.bwct.de bernd@bwct.de info@bwct.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050324110727.GX53520>