From owner-freebsd-current@FreeBSD.ORG Mon Apr 26 18:27:01 2004 Return-Path: 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 7313516A4CE for ; Mon, 26 Apr 2004 18:27:01 -0700 (PDT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 11D3543D5A for ; Mon, 26 Apr 2004 18:27:01 -0700 (PDT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id F02E872DF0; Mon, 26 Apr 2004 18:27:00 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id ED74572DBF; Mon, 26 Apr 2004 18:27:00 -0700 (PDT) Date: Mon, 26 Apr 2004 18:27:00 -0700 (PDT) From: Doug White To: Julian Elischer In-Reply-To: Message-ID: <20040426182459.D27442@carver.gumbysoft.com> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: "Vyacheslav I. Ivanchenko" cc: current@freebsd.org cc: Nate Lawson Subject: Re: Trouble with EHCI controller and USB Flash Disk. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Apr 2004 01:27:01 -0000 On Wed, 21 Apr 2004, Julian Elischer wrote: > > > I have problems with mine USB2.0 Mobile Disk III and EHCI controller. > > > (http://www.twinmos.com/flash/flash_p_usb20_mobile3.htm) > > > > > > When I try to use EHCI controller, my system finds out > > > the device /dev/da0, but does not find out the > > > device /dev/da0s1. > > > > > > With UHCI controller no problem. > > > > Since it works with UHCI, it's likely an EHCI problem. Unfortunately, I > > don't know much about EHCI so I'm moving this to -current. > > The ehci driver has quite a few problems. > It workd in some cases but not in others. > I have not yet isolated what the defining factor is. I think EHCI has a tendency to drop transactions. I got umass really confused a few weeks back by attaching one usb key to ehci and a low key to uhci and trying to do stuff on both keys at once. The transaction sequence #s got off-by-one and never recovered (due to a bug in umass), but the txn shouldn't have disappeared in the first place. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org