From owner-freebsd-current@FreeBSD.ORG  Thu Oct 28 03:54:24 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 44D2316A4CE
	for <freebsd-current@freebsd.org>;
	Thu, 28 Oct 2004 03:54:24 +0000 (GMT)
Received: from soyo.zuhause.org (host153.balbrecht.real-time.com
	[65.165.41.153])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1BC6E43D39
	for <freebsd-current@freebsd.org>;
	Thu, 28 Oct 2004 03:54:24 +0000 (GMT)
	(envelope-from bruce@zuhause.org)
Received: by soyo.zuhause.org (Postfix, from userid 1001)
	id B418C4B52D; Wed, 27 Oct 2004 22:54:23 -0500 (CDT)
Message-ID: <16768.28015.665736.1361@soyo.zuhause.org>
Date: Wed, 27 Oct 2004 22:54:23 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: bruce@zuhause.mn.org
To: Mike Tancsa <mike@sentex.net>
In-Reply-To: <6.1.2.0.0.20041027143606.08a42660@64.7.153.2>
References: <6.1.2.0.0.20041027135726.02ec27c0@64.7.153.2>
	<6.1.2.0.0.20041027143606.08a42660@64.7.153.2>
X-Mailer: VM 7.17 under 21.4 (patch 14) "Reasonable Discussion" XEmacs Lucid
cc: freebsd-current@freebsd.org
Subject: Re: Lexar Jumpdrive / umass problems (solved)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Oct 2004 03:54:24 -0000

Mike Tancsa writes:
 > At 02:06 PM 27/10/2004, Mike Tancsa wrote:
 > 
 > >Hi,
 > >
 > >I am experimenting with this device on RELENG_5 (Oct 26th) ? The unit is 
 > >recognized
 > 
 > It seems turning off EHCI fixes the problem.

That's only a workaround.  Turning off EHCI means you're accessing the
device as a USB 1.1 device, with a transfer speed 1/40th of USB 2.