From owner-freebsd-usb@FreeBSD.ORG  Fri Jan  6 05:21:29 2006
Return-Path: <owner-freebsd-usb@FreeBSD.ORG>
X-Original-To: freebsd-usb@freebsd.org
Delivered-To: freebsd-usb@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 1D61A16A41F;
	Fri,  6 Jan 2006 05:21:29 +0000 (GMT)
	(envelope-from dgilbert@daveg.ca)
Received: from ox.eicat.ca (ox.eicat.ca [66.96.30.35])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C841343D46;
	Fri,  6 Jan 2006 05:21:28 +0000 (GMT)
	(envelope-from dgilbert@daveg.ca)
Received: by ox.eicat.ca (Postfix, from userid 66)
	id C9C0311B4E; Fri,  6 Jan 2006 00:21:27 -0500 (EST)
Received: by canoe.dclg.ca (Postfix, from userid 101)
	id D05EC1A0A96; Fri,  6 Jan 2006 00:21:19 -0500 (EST)
From: David Gilbert <dgilbert@dclg.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <17341.65102.980006.14057@canoe.dclg.ca>
Date: Fri, 6 Jan 2006 00:21:18 -0500
To: freebsd-current@freebsd.org, freebsd-usb@freebsd.org
X-Mailer: VM 7.17 under 21.4 (patch 18) "Social Property" XEmacs Lucid
Cc: 
Subject: Disappearing memory
X-BeenThere: freebsd-usb@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: FreeBSD support for USB <freebsd-usb.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-usb>,
	<mailto:freebsd-usb-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-usb>
List-Post: <mailto:freebsd-usb@freebsd.org>
List-Help: <mailto:freebsd-usb-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-usb>,
	<mailto:freebsd-usb-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Jan 2006 05:21:29 -0000

For some time, my answer to disappearing memory has been to always
unplug the USB device before removing (or inserting different) memory
cards.  The issue is that they seem to not signal the USB
infrastructure that they have been ejected, and thus the operating
system doesn't know.  In fact, most "x in 1" card readers --- ones
that read many types of memory --- actually attach a bunch of disks
with zero blocks in addition to attaching the memory card you have
inserted --- as if they have the capability of simutaneously handling
all different kinds of memory (although they often don't).

So this seems like an acceptable solution.  Until now.

Now that I have a Dell 2405 flat panel display on my desk (gorgeous,
BTW), I have a permanently attached cluster of memory card slots.
Sure ... I can grope around behind things, find the usb cord for the
monitor, but that's very ungraceful and ends up unplugging any other
USB devices that go through the monitor (thus causing all kinds of
trouble).

So I set about tonight to see if I could convince camcontrol to
realize that one of the previously full disks was now empty again.  It
doesn't seem that I can.

Maybe what we need is 'usbcontrol' ... allowing us to reset (or at
least reset the OSs idea of) one usb device.

Dave.

-- 
============================================================================
|David Gilbert, Independent Contractor.       | Two things can be          |
|Mail:       dave@daveg.ca                    |  equal if and only if they |
|http://daveg.ca                              |   are precisely opposite.  |
=========================================================GLO================