From owner-freebsd-stable@FreeBSD.ORG Thu Jul 23 05:53:22 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2F01C106566C for ; Thu, 23 Jul 2009 05:53:22 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.freebsd.org (Postfix) with ESMTP id 8B0108FC16 for ; Thu, 23 Jul 2009 05:53:21 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (eugen@localhost [127.0.0.1]) by www.svzserv.kemerovo.su (8.13.8/8.13.8) with ESMTP id n6N5rISI072887; Thu, 23 Jul 2009 13:53:18 +0800 (KRAST) (envelope-from eugen@www.svzserv.kemerovo.su) Received: (from eugen@localhost) by www.svzserv.kemerovo.su (8.13.8/8.13.8/Submit) id n6N5rHMO072886; Thu, 23 Jul 2009 13:53:17 +0800 (KRAST) (envelope-from eugen) Date: Thu, 23 Jul 2009 13:53:17 +0800 From: Eugene Grosbein To: Sagara Wijetunga Message-ID: <20090723055317.GA72627@svzserv.kemerovo.su> References: <20090722022027.12059.qmail@us1.tomahawkonline.net> <20090722142033.GA13316@svzserv.kemerovo.su> <20090723001338.27858.qmail@us1.tomahawkonline.net> <20090723035900.GA67095@svzserv.kemerovo.su> <20090723021418.29042.qmail@us1.tomahawkonline.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090723021418.29042.qmail@us1.tomahawkonline.net> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: SCSI device not created upon a CF card plug in X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jul 2009 05:53:22 -0000 On Thu, Jul 23, 2009 at 10:14:18AM +0800, Sagara Wijetunga wrote: > If you conversant in this area, could you help us to identify what is/are > the exact function/s in which program/s to look into identify the media > insertion activity, so that we can generate relevant devd event. No, I'm not. In your position I would study the device specs - does it generate hardware event in case of media change in first place? If yes, I'd read sources of umass driver to see how it generates events for single flash device and add such event for reader's media change. If not, there should be polling anyway. Eugene Grosbein