From owner-freebsd-usb@FreeBSD.ORG Sun Dec 26 00:27:59 2004 Return-Path: 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 6536316A4CE for ; Sun, 26 Dec 2004 00:27:59 +0000 (GMT) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE40F43D49 for ; Sun, 26 Dec 2004 00:27:58 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de (cicely5.cicely.de [IPv6:3ffe:400:8d0:301:200:92ff:fe9b:20e7]) (authenticated bits=0) iBQ0RrP8017590 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Sun, 26 Dec 2004 01:27:56 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [IPv6:3ffe:400:8d0:301::12]) by cicely5.cicely.de (8.12.10/8.12.10) with ESMTP id iBQ0RNrU092296 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 26 Dec 2004 01:27:24 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.12.11/8.12.11) with ESMTP id iBQ0RNiU070079; Sun, 26 Dec 2004 01:27:23 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.12.11/8.12.11/Submit) id iBQ0RMU6070078; Sun, 26 Dec 2004 01:27:22 +0100 (CET) (envelope-from ticso) Date: Sun, 26 Dec 2004 01:27:22 +0100 From: Bernd Walter To: Darksidex Message-ID: <20041226002721.GG58581@cicely12.cicely.de> References: <41CD83E6.1010304@gmail.com> <20041225181725.GE58581@cicely12.cicely.de> <41CDEDE2.5030900@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41CDEDE2.5030900@gmail.com> X-Operating-System: FreeBSD cicely12.cicely.de 5.2-CURRENT alpha User-Agent: Mutt/1.5.6i X-Spam-Status: No, hits=-4.9 required=3.0 tests=BAYES_00 autolearn=ham version=2.64 X-Spam-Report: * -4.9 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on cicely12.cicely.de cc: freebsd-usb@freebsd.org Subject: Re: How to mount usb2 devices X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ticso@cicely.de List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Dec 2004 00:27:59 -0000 On Sat, Dec 25, 2004 at 11:46:58PM +0100, Darksidex wrote: > Bernd Walter wrote: > > >It is running high speed, because it is attached to your ehci > >controller. > >Having high throughput is another story - msdosfs is not very efficient > >with some devices - you might want to check a dd with big block sizes > >to verify if higher speed can be reached. > > > > > How can I do it? dd if=/dev/da-whatever-number-it-is of=/dev/null bs=64k You may want to test higher values for bs= too. -- B.Walter BWCT http://www.bwct.de bernd@bwct.de info@bwct.de From owner-freebsd-usb@FreeBSD.ORG Sun Dec 26 03:32:18 2004 Return-Path: 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 56A8C16A4CE for ; Sun, 26 Dec 2004 03:32:18 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75B7043D45 for ; Sun, 26 Dec 2004 03:32:17 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iBQ3TL25071216; Sat, 25 Dec 2004 20:29:22 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sat, 25 Dec 2004 20:29:52 -0700 (MST) Message-Id: <20041225.202952.80502292.imp@bsdimp.com> To: freebsd-misuser@NOSPAM.dyndns.dk, freebsd-misuser@remove-NOSPAM-to-reply.NOSPAM.dyndns.dk From: "M. Warner Losh" In-Reply-To: <200412250207.iBP27mQ40936@Mail.NOSPAM.DynDNS.dK> References: <200412242236.iBOMaig32845@Mail.NOSPAM.DynDNS.dK> <20041224.155218.123609434.imp@bsdimp.com> <200412250207.iBP27mQ40936@Mail.NOSPAM.DynDNS.dK> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: usb@freebsd.org cc: lennart@augustsson.net Subject: Re: getting vendor IDs X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Dec 2004 03:32:18 -0000 In message: <200412250207.iBP27mQ40936@Mail.NOSPAM.DynDNS.dK> Barry Bouwsma writes: : : On Fri, 24 Dec 2004 15:52:18 -0700 (MST), "M. Warner Losh" wrote: : : > : In such a case, the only thing I can see doing is to provide the : > : end-product description as part of the vendor product, for NetBSD. : > : Which will be rather a lot of work, but when you have the case of : > : some unfamiliar-to-consumer's chip in a well-known camera case, : > : I don't see an easy way to keep the descriptions short yet clear. : : > I don't understand what you are saying at all. : : Sorry, I'll try again. Since NetBSD uses these strings, I want to : make them match the device a bit more, especially for cases where : the descriptor string is deficient. That's the case with my camera, : which is just `CAMERA' according to the internal vendor string, : if I remember. But NetBSD only uses these strings if there's no driver to claim the device. Otherwise, it uses the same method as FreeBSD. : Of course, I need to look where NetBSD uses the product's string, : and where it refers to the table from usbdevs, to see where it : matters. It's not in the boot-time messages for an attached : device, though, as my uaudio vendor wasn't identified with : uaudio present in my NetBSD kernel. Yes. It is better to know and understand where NetBSD uses things before going off on assumptions. : I'm hoping to introduce coordination, to reduce the differences : between the files that make keeping up-to-date more of a hassle : than it should be. As in this case, the BSDen share a common : base (unlike, say, uaudio where there are significant differences, : or more specifically, the audio infrastructure in general), I : don't see a reason why all the BSDen can't draw from a single : source that's synchronized between them, for the data within, : that doesn't change between OSen. I think I made my point badly: NetBSD developers do not coordinate things well, so there tends to be a lot of different conventions in place. : I'm thinking of the two devices I showed earlier (mouse and uaudio : device) that were missing vendor strings, and in part a product. : If this information can't be pulled from the device itself, in : hopefully relatively few cases, my feeling is it would be good to : fall back on a database which provides more than just the vendor : and product numbers. : ums0: vendor 0x062a product 0x0000, rev 1.10/0.00, addr 4, iclass 3/1 That code is already in place. Please, go look at the code before speculating. Warner From owner-freebsd-usb@FreeBSD.ORG Sun Dec 26 03:32:34 2004 Return-Path: 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 29E4D16A4CE for ; Sun, 26 Dec 2004 03:32:34 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB6FB43D49 for ; Sun, 26 Dec 2004 03:32:33 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iBQ3U5wR071220; Sat, 25 Dec 2004 20:30:09 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sat, 25 Dec 2004 20:30:36 -0700 (MST) Message-Id: <20041225.203036.70797686.imp@bsdimp.com> To: julian@elischer.org From: "M. Warner Losh" In-Reply-To: <41CCFB49.707@elischer.org> References: <41CB38A7.5020700@vicor.com> <20041224.132339.88473596.imp@bsdimp.com> <41CCFB49.707@elischer.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: usb@freebsd.org cc: dillon@apollo.backplane.com cc: lennart@augustsson.net cc: julian@vicor.com Subject: Re: USB vendore designations.. X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Dec 2004 03:32:34 -0000 In message: <41CCFB49.707@elischer.org> Julian Elischer writes: : M. Warner Losh wrote: : > In message: <41CB38A7.5020700@vicor.com> : > Julian Elischer writes: : > : Lennart, Matt, Barry, USB hackers, : > : : > : On FreeBSD we have added vendor descriptiosn fo teh form : > : XYZ electrical corp. : > : : > : where on NetBSD the same ID may be described as "XYZ" : > : : > : Is there a reason to go one way or the other? : > : I'd rather not be different for no reason, but I'm loath to : > : just discard information. : > : : > : thoughts? : > : > Doesn't matter in FreeBSD because we don't use the vendor strings the : > way that NetBSD does. We don't[*] create large tables of them, which is : > why NetBSD reduced their length... : > : > Warner : > : > [*] well, we can with USB_VERBOSE. : > _______________________________________________ : > freebsd-usb@freebsd.org mailing list : > http://lists.freebsd.org/mailman/listinfo/freebsd-usb : > To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org" : : but there are dvices that use the definitions there to probe, so we do need the : definitions. Just the strings are not so important.. I've used the tables in the : past. I don't understand what you are saying. The strings from usbdevs are basically unused in FreeBSD. Warner From owner-freebsd-usb@FreeBSD.ORG Sun Dec 26 06:34:52 2004 Return-Path: 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 377CE16A4CE for ; Sun, 26 Dec 2004 06:34:52 +0000 (GMT) Received: from pimout1-ext.prodigy.net (pimout1-ext.prodigy.net [207.115.63.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id E039443D46 for ; Sun, 26 Dec 2004 06:34:51 +0000 (GMT) (envelope-from julian@elischer.org) Received: from [192.168.1.102] (adsl-216-100-134-143.dsl.snfc21.pacbell.net [216.100.134.143])iBQ6Yee2156320; Sun, 26 Dec 2004 01:34:44 -0500 Message-ID: <41CE5B7F.3090805@elischer.org> Date: Sat, 25 Dec 2004 22:34:39 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8a3) Gecko/20041017 X-Accept-Language: en, hu MIME-Version: 1.0 To: ticso@cicely.de References: <41CD83E6.1010304@gmail.com> <20041225181725.GE58581@cicely12.cicely.de> <41CDEDE2.5030900@gmail.com> <20041226002721.GG58581@cicely12.cicely.de> In-Reply-To: <20041226002721.GG58581@cicely12.cicely.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-usb@freebsd.org Subject: Re: How to mount usb2 devices X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Dec 2004 06:34:52 -0000 Bernd Walter wrote: > On Sat, Dec 25, 2004 at 11:46:58PM +0100, Darksidex wrote: > >>Bernd Walter wrote: >> >> >>>It is running high speed, because it is attached to your ehci >>>controller. >>>Having high throughput is another story - msdosfs is not very efficient >>>with some devices - you might want to check a dd with big block sizes >>>to verify if higher speed can be reached. >>> >>> >> >>How can I do it? > > > dd if=/dev/da-whatever-number-it-is of=/dev/null bs=64k > You may want to test higher values for bs= too. I think that there is a lot of work that can be done to speed up USB2 devices.. for example Ugen devices can be sped up by an order of magnitude with a simple set of changes. (that I will commit when I clean them up) I have to guess that the Umass driver may have similar performance problems. From owner-freebsd-usb@FreeBSD.ORG Sun Dec 26 06:39:30 2004 Return-Path: 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 8442516A4CE for ; Sun, 26 Dec 2004 06:39:30 +0000 (GMT) Received: from pimout2-ext.prodigy.net (pimout2-ext.prodigy.net [207.115.63.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1EC7143D5C for ; Sun, 26 Dec 2004 06:39:30 +0000 (GMT) (envelope-from julian@elischer.org) Received: from [192.168.1.102] (adsl-216-100-134-143.dsl.snfc21.pacbell.net [216.100.134.143])iBQ6dEGr040792; Sun, 26 Dec 2004 01:39:26 -0500 Message-ID: <41CE5C91.5060104@elischer.org> Date: Sat, 25 Dec 2004 22:39:13 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8a3) Gecko/20041017 X-Accept-Language: en, hu MIME-Version: 1.0 To: Kazuhito HONDA References: <41B8C7A9.3080306@elischer.org> <20041224.182917.607958849.kazuhito@ph.noda.tus.ac.jp> <41CD00B1.9040502@elischer.org> <20041225.230115.422452498.kazuhito@ph.noda.tus.ac.jp> In-Reply-To: <20041225.230115.422452498.kazuhito@ph.noda.tus.ac.jp> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-usb@freebsd.org Subject: Re: Hacking usb/uaudio code X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Dec 2004 06:39:30 -0000 Kazuhito HONDA wrote: > From: Julian Elischer > Subject: Re: Hacking usb/uaudio code > Date: Fri, 24 Dec 2004 21:54:57 -0800 > > >>Kazuhito HONDA wrote: >> >>>kern/75274 for merging >> >>I could commit this.. how much have you tested it? > > >>>kern/75276 for volumes >>>kern/75311 for recording >>>kern/75316 for selection of a recording sound source >> >>how much have you tested these patches? >>do they break other audio devices? > > > I usually use those patches almost every day. > But I have tested those patches by `Sound Blaster Digital Music' only. > So those patches require many test, test, test, and test > by various USB audio devices. > > I'm afraid that those patches have problems with simple devices e.g. > USB microphone or with complicated devices > which have add-processing or extension units. I am led to believe that those cases were not well supported before your patches and that your patches probably do not break them more than they were already broken. > > Kazuhito HONDA > _______________________________________________ > freebsd-usb@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-usb > To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org" From owner-freebsd-usb@FreeBSD.ORG Sun Dec 26 09:50:38 2004 Return-Path: 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 8786216A4CE for ; Sun, 26 Dec 2004 09:50:38 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A46D43D2D for ; Sun, 26 Dec 2004 09:50:38 +0000 (GMT) (envelope-from humprhey@gmail.com) Received: by rproxy.gmail.com with SMTP id c16so147041rne for ; Sun, 26 Dec 2004 01:50:37 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:x-accept-language:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=hXk1AH76fNExPlIvcL1Qp8q2PX3abMnOSr+MD/K/JvVmirRkTkYewEp9rKl7mpDALpv0rWf1O44SqtGC1NkGSXS4ifkAvm5vFlYo+R2v7hDR9LCM2wU6/HZXcZLo2Sjp4qiZQ4SFL0Yv5OmlQDwgJ39vW+i3G9sBz8HsnpW+UqA= Received: by 10.38.13.70 with SMTP id 70mr117541rnm; Sun, 26 Dec 2004 01:50:36 -0800 (PST) Received: from ?192.168.1.1? ([217.127.98.119]) by smtp.gmail.com with ESMTP id 63sm18056rna.2004.12.26.01.50.36; Sun, 26 Dec 2004 01:50:36 -0800 (PST) Message-ID: <41CE89E1.6000408@gmail.com> Date: Sun, 26 Dec 2004 10:52:33 +0100 From: Darksidex User-Agent: Mozilla Thunderbird 1.0 (X11/20041209) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-usb@freebsd.org References: <41CD83E6.1010304@gmail.com> <20041225181725.GE58581@cicely12.cicely.de> <41CDEDE2.5030900@gmail.com> <20041226002721.GG58581@cicely12.cicely.de> In-Reply-To: <20041226002721.GG58581@cicely12.cicely.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: How to mount usb2 devices X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Dec 2004 09:50:38 -0000 Bernd Walter wrote: >dd if=/dev/da-whatever-number-it-is of=/dev/null bs=64k > bs=64k -> 15mb/s bs=128k -> 15mb/s Not very fast. From owner-freebsd-usb@FreeBSD.ORG Sun Dec 26 13:17:15 2004 Return-Path: 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 E484C16A4CE for ; Sun, 26 Dec 2004 13:17:15 +0000 (GMT) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3002343D1D for ; Sun, 26 Dec 2004 13:17:15 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de (cicely5.cicely.de [IPv6:3ffe:400:8d0:301:200:92ff:fe9b:20e7]) (authenticated bits=0) iBQDH2P8050996 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Sun, 26 Dec 2004 14:17:04 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [IPv6:3ffe:400:8d0:301::12]) by cicely5.cicely.de (8.12.10/8.12.10) with ESMTP id iBQDGCrU096284 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 26 Dec 2004 14:16:13 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.12.11/8.12.11) with ESMTP id iBQDGCDX074089; Sun, 26 Dec 2004 14:16:12 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.12.11/8.12.11/Submit) id iBQDG8r9074088; Sun, 26 Dec 2004 14:16:08 +0100 (CET) (envelope-from ticso) Date: Sun, 26 Dec 2004 14:16:08 +0100 From: Bernd Walter To: Julian Elischer Message-ID: <20041226131607.GJ58581@cicely12.cicely.de> References: <41CD83E6.1010304@gmail.com> <20041225181725.GE58581@cicely12.cicely.de> <41CDEDE2.5030900@gmail.com> <20041226002721.GG58581@cicely12.cicely.de> <41CE5B7F.3090805@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41CE5B7F.3090805@elischer.org> X-Operating-System: FreeBSD cicely12.cicely.de 5.2-CURRENT alpha User-Agent: Mutt/1.5.6i X-Spam-Status: No, hits=-4.9 required=3.0 tests=BAYES_00 autolearn=ham version=2.64 X-Spam-Report: * -4.9 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on cicely12.cicely.de cc: ticso@cicely.de cc: freebsd-usb@freebsd.org Subject: Re: How to mount usb2 devices X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ticso@cicely.de List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Dec 2004 13:17:16 -0000 On Sat, Dec 25, 2004 at 10:34:39PM -0800, Julian Elischer wrote: > Bernd Walter wrote: > >On Sat, Dec 25, 2004 at 11:46:58PM +0100, Darksidex wrote: > > > >>Bernd Walter wrote: > >> > >> > >>>It is running high speed, because it is attached to your ehci > >>>controller. > >>>Having high throughput is another story - msdosfs is not very efficient > >>>with some devices - you might want to check a dd with big block sizes > >>>to verify if higher speed can be reached. > >>> > >>> > >> > >>How can I do it? > > > > > >dd if=/dev/da-whatever-number-it-is of=/dev/null bs=64k > >You may want to test higher values for bs= too. > > I think that there is a lot of work that can be done to speed up > USB2 devices.. Likely - there is still a lot that can be done even for full speed devices. > for example Ugen devices can be sped up by an order of magnitude > with a simple set of changes. (that I will commit when I clean > them up) I have to guess that the Umass driver may have similar > performance problems. So you can speed up ugen devices - sounds interesting. What is the basic idea behind? -- B.Walter BWCT http://www.bwct.de bernd@bwct.de info@bwct.de From owner-freebsd-usb@FreeBSD.ORG Sun Dec 26 13:37:05 2004 Return-Path: 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 D602F16A4CE for ; Sun, 26 Dec 2004 13:37:05 +0000 (GMT) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B7A343D1F for ; Sun, 26 Dec 2004 13:37:05 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de (cicely5.cicely.de [IPv6:3ffe:400:8d0:301:200:92ff:fe9b:20e7]) (authenticated bits=0) iBQDb1P8051645 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Sun, 26 Dec 2004 14:37:03 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [IPv6:3ffe:400:8d0:301::12]) by cicely5.cicely.de (8.12.10/8.12.10) with ESMTP id iBQDZvrU096376 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 26 Dec 2004 14:35:57 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.12.11/8.12.11) with ESMTP id iBQDZuIq074177; Sun, 26 Dec 2004 14:35:56 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.12.11/8.12.11/Submit) id iBQDZu68074176; Sun, 26 Dec 2004 14:35:56 +0100 (CET) (envelope-from ticso) Date: Sun, 26 Dec 2004 14:35:56 +0100 From: Bernd Walter To: Darksidex Message-ID: <20041226133555.GM58581@cicely12.cicely.de> References: <41CD83E6.1010304@gmail.com> <20041225181725.GE58581@cicely12.cicely.de> <41CDEDE2.5030900@gmail.com> <20041226002721.GG58581@cicely12.cicely.de> <41CE89E1.6000408@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41CE89E1.6000408@gmail.com> X-Operating-System: FreeBSD cicely12.cicely.de 5.2-CURRENT alpha User-Agent: Mutt/1.5.6i X-Spam-Status: No, hits=-4.9 required=3.0 tests=BAYES_00 autolearn=ham version=2.64 X-Spam-Report: * -4.9 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on cicely12.cicely.de cc: freebsd-usb@freebsd.org Subject: Re: How to mount usb2 devices X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ticso@cicely.de List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Dec 2004 13:37:06 -0000 On Sun, Dec 26, 2004 at 10:52:33AM +0100, Darksidex wrote: > Bernd Walter wrote: > > >dd if=/dev/da-whatever-number-it-is of=/dev/null bs=64k > > > bs=64k -> 15mb/s > bs=128k -> 15mb/s > > Not very fast. At least much faster than USB1.1, but not faster than with your msdosfs tests. It might be a limitation from your disk, from FreeBSD or from your USB-IDE converter. What can the disk deliver if connected to a plain IDE controller? -- B.Walter BWCT http://www.bwct.de bernd@bwct.de info@bwct.de From owner-freebsd-usb@FreeBSD.ORG Sun Dec 26 16:47:14 2004 Return-Path: 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 62FA716A4CE for ; Sun, 26 Dec 2004 16:47:14 +0000 (GMT) Received: from mailfe04.swip.net (mailfe04.swip.net [212.247.154.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E7A643D2F for ; Sun, 26 Dec 2004 16:47:13 +0000 (GMT) (envelope-from hselasky@c2i.net) X-T2-Posting-ID: gvlK0tOCzrqh9CPROFOFPw== Received: from mp-217-207-83.daxnet.no ([193.217.207.83] verified) by mailfe04.swip.net (CommuniGate Pro SMTP 4.2.7) with ESMTP id 255334768 for freebsd-usb@freebsd.org; Sun, 26 Dec 2004 17:47:12 +0100 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Sun, 26 Dec 2004 17:47:36 +0100 User-Agent: KMail/1.7 References: <41CB38A7.5020700@vicor.com> <41CB4BCB.1080708@elischer.org> <20041224124346.GG45586@cicely12.cicely.de> In-Reply-To: <20041224124346.GG45586@cicely12.cicely.de> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200412261747.36555.hselasky@c2i.net> Subject: Re: USB vendore designations.. X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: hselasky@c2i.net List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Dec 2004 16:47:14 -0000 On Friday 24 December 2004 13:43, Bernd Walter wrote: > On Thu, Dec 23, 2004 at 02:50:51PM -0800, Julian Elischer wrote: > > EHCI is almost ok.. except for where it REALLY SUCKS! > The EHCI manual says that QH's can be removed without stopping the HC. QH removal is done like this: set the previous QH to point to the next QH, and then set the DOORBELL bit in the EHCI command register and wait for it to clear. This is the same whether the QH is finished or cancelled, though if it is finished one might get around with a short DELAY(), hence the HC should already be skipping the QH? Currently, no driver is checking cancelled QH's, to see if they were finished after all. If the drivers did, then no information as to whether the transfers on it were completed or not, would be lost. As long as there are not so many transfers the EHCI is not that inefficient. Yours --HPS From owner-freebsd-usb@FreeBSD.ORG Sun Dec 26 16:54:40 2004 Return-Path: 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 699EA16A4CE for ; Sun, 26 Dec 2004 16:54:40 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 133A343D1D for ; Sun, 26 Dec 2004 16:54:38 +0000 (GMT) (envelope-from humprhey@gmail.com) Received: by rproxy.gmail.com with SMTP id c16so159944rne for ; Sun, 26 Dec 2004 08:54:37 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:x-accept-language:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=L65FqZqaK7k9pDAsNT4uR3RtPd2CNIaFDHN4DED4npLI5LGL7YOcY0SPFaxNsTlwhsY3iyFzDnz9ioGCdgww4E4CEfH42vNTkhPeVnK0FbuXbFMBFYzHQXbx8N7RXiJkTKVDLcP6Wi7FcBvjRLPAh3dWzMXqNVwXd0x0juGtTIs= Received: by 10.38.73.54 with SMTP id v54mr212280rna; Sun, 26 Dec 2004 08:54:37 -0800 (PST) Received: from ?192.168.1.1? ([217.127.98.119]) by smtp.gmail.com with ESMTP id 79sm327109rna.2004.12.26.08.54.36; Sun, 26 Dec 2004 08:54:37 -0800 (PST) Message-ID: <41CEED40.8030808@gmail.com> Date: Sun, 26 Dec 2004 17:56:32 +0100 From: Darksidex User-Agent: Mozilla Thunderbird 1.0 (X11/20041209) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-usb@freebsd.org References: <41CD83E6.1010304@gmail.com> <20041225181725.GE58581@cicely12.cicely.de> <41CDEDE2.5030900@gmail.com> <20041226002721.GG58581@cicely12.cicely.de> <41CE89E1.6000408@gmail.com> <20041226133555.GM58581@cicely12.cicely.de> In-Reply-To: <20041226133555.GM58581@cicely12.cicely.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: How to mount usb2 devices X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Dec 2004 16:54:40 -0000 Bernd Walter wrote: >At least much faster than USB1.1, but not faster than with your msdosfs >tests. >It might be a limitation from your disk, from FreeBSD or from your >USB-IDE converter. >What can the disk deliver if connected to a plain IDE controller? > > Connected to IDE 64k and 128K: 29mb/s I have checked my BIOS configuration, but I don't see anything unusual, and my other HD (where I have installed FBSD gives to me the same speed). Another question. Since I added ehci support in the kernel, I can't boot my fbsd box if this usb unit is powered on, it gets freeze. It isn't very important, because I can boot it without the usb unit, but if I want to reboot it from internet, I can't. Any idea? From owner-freebsd-usb@FreeBSD.ORG Sun Dec 26 18:14:01 2004 Return-Path: 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 571B916A4CE for ; Sun, 26 Dec 2004 18:14:01 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8991843D4C for ; Sun, 26 Dec 2004 18:14:00 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iBQICbMe008496; Sun, 26 Dec 2004 11:12:37 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 26 Dec 2004 11:13:08 -0700 (MST) Message-Id: <20041226.111308.79871324.imp@bsdimp.com> To: humprhey@gmail.com From: "M. Warner Losh" In-Reply-To: <41CE89E1.6000408@gmail.com> References: <41CDEDE2.5030900@gmail.com> <20041226002721.GG58581@cicely12.cicely.de> <41CE89E1.6000408@gmail.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-usb@freebsd.org Subject: Re: How to mount usb2 devices X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Dec 2004 18:14:01 -0000 In message: <41CE89E1.6000408@gmail.com> Darksidex writes: : Bernd Walter wrote: : : >dd if=/dev/da-whatever-number-it-is of=/dev/null bs=64k : > : bs=64k -> 15mb/s : bs=128k -> 15mb/s : : Not very fast. For USB that is relatively fast... The numbers are 120Mb/s, so it is clearly operating at USB2 speeds. Warner From owner-freebsd-usb@FreeBSD.ORG Sun Dec 26 20:37:45 2004 Return-Path: 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 C282116A4CE; Sun, 26 Dec 2004 20:37:45 +0000 (GMT) Received: from dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NOSPAM.dyndns.dk (84-72-30-72.dclient.hispeed.ch [84.72.30.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id BAAB043D1D; Sun, 26 Dec 2004 20:37:43 +0000 (GMT) (envelope-from bounce@NOSPAM.dyndns.dk) Received: from Mail.NOSPAM.DynDNS.dK (ipv6.NOSPAM.dyndns.dk [2002:5448:1e48:0:210:60ff:fe25:f1e5]) (8.11.6/8.11.6-SPAMMERS-DeLiGHt) with ESMTP id iBQKbWI02634 verified NO); Sun, 26 Dec 2004 21:37:40 +0100 (CET) (envelope-from bounce@NOSPAM.dyndns.dk) Received: (from beer@localhost) by Mail.NOSPAM.DynDNS.dK (8.11.6/FNORD) id iBQKbV102633; Sun, 26 Dec 2004 21:37:31 +0100 (CET) (envelope-from bounce@NOSPAM.dyndns.dk) Date: Sun, 26 Dec 2004 21:37:31 +0100 (CET) Message-Id: <200412262037.iBQKbV102633@Mail.NOSPAM.DynDNS.dK> X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: beer set sender to bounce@NOSPAM.dyndns.dk using -f X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: Processed from queue /tmp X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: Processed by beer with -C /etc/mail/sendmail.cf-LOCAL References: <200411301305.iAUD5Ot01166@Mail.NOSPAM.DynDNS.dK> From: Barry Bouwsma To: Firewire Developers , USB developers Mail-Followup-To: FreeBSD USB developers Subject: Re: Firewire/USB conflicting number of sectors for certain drives X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Barry Bouwsma List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Dec 2004 20:37:46 -0000 Happy 2004!!1! I happened to be looking at the Linux USB code and noticed their definition of quirks, and noted an interesting `FIX_CAPACITY' type of quirk that doesn't seem to be present in FreeBSD, which sounds very much like what I thought was a firewire problem (having set up my disk under USB and then failed to access the last partition with Firewire). The essence of the quirk is that the reported size with USB of some devices is 1 too large, which sounds exactly like what I am describing in the message below, which I initially posted to the firewire list. Now I think I posted the below in error, and it needs to be sent to the USB list instead, which is what I'm trying to do with this crosspost. Sorry for annoying the Firewire-fanatics with this, when it seems to be the domain of the USB-users. Here's the message, for freebsd-usb@ , and the linux code which does this is in drivers/usb/storage/ procotols.c and unusual_devs.h, for anyone who wishes to look there. thanks barry bouwsma | Date: Tue, 30 Nov 2004 14:05:24 +0100 (CET) | Message-Id: <200411301305.iAUD5Ot01166@Mail.NOSPAM.DynDNS.dK> | From: Barry Bouwsma | To: FreeBSD Firewire Developers | Subject: Firewire/USB conflicting number of sectors for certain drives | | Salut, [ ... ] | I have three different disks in front of me, all equipped with both | USB and Firewire connectors. Two of the three report a different | number of sectors -- one fewer -- when connected via firewire, than | when connected via USB1 (UHCI and apparently OHCI though I know of | access problems with the latter; have not checked against EHCI). | The third disk, however, reports the same sectors in `dmesg', and | I initially set it up connected with Firewire, while the other drives | have been set up over USB1 as the hardware which I had at hand. | | The two drives are Western Digital, hidden behind something as you | can see in the below dmesg snippets. Here the reported sectors from | them: | USB: da1: 238475MB (488397169 512 byte sectors: 255H 63S/T 30401C) | FW: da1: 238475MB (488397168 512 byte sectors: 255H 63S/T 30401C) | and | USB: da1: 190782MB (390721969 512 byte sectors: 255H 63S/T 24321C) | FW: da1: 190782MB (390721968 512 byte sectors: 255H 63S/T 24321C) | | Too bad I disklabel'ed and whatnot the disk when connected via USB, | so that any Firewire access fails to report the actual partition | where I expect to find the data (it now appears to extend beyond the | end of the disk). Hmmm. | da1s1: slice extends beyond end of disk: truncating from 488397106 to 488397105 | sectors | | The third drive -- the first one I acquired -- is a Maxtor, and does | not have this issue. I'm using kernel modules on FreeBSD 4.x, modules | built on 11.05.2004, which otherwise work splendidly, though I may have | one or two minor hacks compiled in. I haven't tried more recent source | or anything based on -current. | | | It's probably a known issue that (as you see below), the drive attached | by USB is identified by what the actual drive is, whereas when connected | via firewire, it appears to be identified as the chipset that interfaces | from firewire to the drive's ATA -- at least with my modules. | | | Here's a bit of some `dmesg' concerning the drives, although it's | not comprehensive, in case there's something to be seen below: | | exhibit 1 on usb: | umass0: ASSMANN Electronic GmbH product 0x3507, rev 2.00/0.01, addr 4 | umass0:3:0:-1: Attached to scbus3 | pass1 at umass-sim0 bus 0 target 0 lun 0 | pass1: Fixed Direct Access SCSI-0 device | pass1: 1.000MB/s transfers | Creating DISK da1 | da1 at umass-sim0 bus 0 target 0 lun 0 | da1: Fixed Direct Access SCSI-0 device | da1: 1.000MB/s transfers | da1: 238475MB (488397169 512 byte sectors: 255H 63S/T 30401C) | | exhibit 1 then connected via firewire: | pass1 at sbp0 bus 0 target 1 lun 0 | pass1: Fixed Simplified Direct Access SCSI-4 device | pass1: Serial Number \^_ | pass1: 50.000MB/s transfers | Creating DISK da1 | sbp0:1:0 sbp_cam_scan_lun | da1 at sbp0 bus 0 target 1 lun 0 | da1: Fixed Simplified Direct Access SCSI-4 device | da1: Serial Number \^_ | da1: 50.000MB/s transfers | da1: 238475MB (488397168 512 byte sectors: 255H 63S/T 30401C) | da1s1: type 0xa5, start 63, end = 488397168, size 488397106 : OK | da1s1: slice extends beyond end of disk: truncating from 488397106 to 488397105 | sectors | da1: raw partition size != slice size | da1: start 63, end 488397167, size 488397105 | da1c: start 63, end 488397168, size 488397106 | | | exhibit 2 connected via usb: | umass1: Generic USB 2.0 Storage Device, rev 2.00/0.01, addr 5 | umass1:4:1:-1: Attached to scbus4 | pass1 at umass-sim1 bus 1 target 0 lun 0 | pass1: Fixed Direct Access SCSI-0 device | pass1: 1.000MB/s transfers | Creating DISK da1 | da1 at umass-sim1 bus 1 target 0 lun 0 | da1: Fixed Direct Access SCSI-0 device | da1: 1.000MB/s transfers | da1: 190782MB (390721969 512 byte sectors: 255H 63S/T 24321C) | | and then via firewire: | da1 at sbp0 bus 0 target 1 lun 0 | da1: < 1394 to ATA 2804> Fixed Simplified Direct Access SCSI-4 device | da1: Serial Number ^_ | da1: 50.000MB/s transfers | da1: 190782MB (390721968 512 byte sectors: 255H 63S/T 24321C) | | | for reference, the Maxtor drive appears comparable with both: | usb: | umass1: Maxtor 5000XT v01.00.00, rev 2.00/1.00, addr 5 | umass1: Get Max Lun not supported (STALLED) | umass1:4:1:-1: Attached to scbus4 | pass1 at umass-sim1 bus 1 target 0 lun 0 | pass1: Fixed Direct Access SCSI-0 device | pass1: Serial Number A80A06AE | pass1: 1.000MB/s transfers | Creating DISK da1 | da1 at umass-sim1 bus 1 target 0 lun 0 | da1: Fixed Direct Access SCSI-0 device | da1: Serial Number A80A06AE | da1: 1.000MB/s transfers | da1: 239371MB (490232832 512 byte sectors: 255H 63S/T 30515C) | | firewire: | pass1 at sbp0 bus 0 target 0 lun 0 | pass1: Fixed Simplified Direct Access SCSI-4 devi | ce | pass1: Serial Number A80A06AE | pass1: 50.000MB/s transfers | Creating DISK da1 | sbp0:0:0 sbp_cam_scan_lun | da1 at sbp0 bus 0 target 0 lun 0 | da1: Fixed Simplified Direct Access SCSI-4 device | da1: Serial Number A80A06AE | da1: 50.000MB/s transfers | da1: 239371MB (490232832 512 byte sectors: 255H 63S/T 30515C) From owner-freebsd-usb@FreeBSD.ORG Sun Dec 26 20:45:16 2004 Return-Path: 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 70EFB16A4CF for ; Sun, 26 Dec 2004 20:45:16 +0000 (GMT) Received: from april.chuckr.org (april.chuckr.org [66.92.151.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5952943D3F for ; Sun, 26 Dec 2004 20:45:15 +0000 (GMT) (envelope-from chuckr@chuckr.org) Received: from april.chuckr.org (localhost [127.0.0.1]) by april.chuckr.org (8.13.1/8.12.11) with ESMTP id iBQL9AE8058329; Sun, 26 Dec 2004 16:09:10 -0500 (EST) (envelope-from chuckr@chuckr.org) Received: from localhost (chuckr@localhost)iBQL9A45058326; Sun, 26 Dec 2004 16:09:10 -0500 (EST) (envelope-from chuckr@chuckr.org) X-Authentication-Warning: april.chuckr.org: chuckr owned process doing -bs Date: Sun, 26 Dec 2004 16:09:09 -0500 (EST) From: Chuck Robey To: Barry Bouwsma In-Reply-To: <200412242250.iBOMot433057@Mail.NOSPAM.DynDNS.dK> Message-ID: <20041226160637.H54135@april.chuckr.org> References: <20041224010759.N1763@april.chuckr.org> <200412241756.56900.doconnor@gsoft.com.au> <200412242250.iBOMot433057@Mail.NOSPAM.DynDNS.dK> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-usb@freebsd.org Subject: Re: fingerprints X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Dec 2004 20:45:16 -0000 On Fri, 24 Dec 2004, Barry Bouwsma wrote: > > I suggest you consult the friendly folx hanging out on the USB list > (usb@ or freebsd-usb@), where I'm sending followups to this as well > as a copy of this. > > Bernd Walter (ticso) has a ports skeleton for the NetBSD USB utilities > that can tell you details about the endpoints and protocols of your > device. I didn't see any extra email postings on this, I hope it doesn't just disappear. Can I ask one favor? I would VERY much appreciate it if you would pick a single one of the usb devices, and I will read everything I see in the kernel on it. I'm trying to read the usb specification, but it's quite large, and I'm not sure thats the best way to go about learning. > > I thought I had another program that gave even more info, but I'll > have to look around to try and find it. I'm not aware of any user > utilities that can do useful things like extract strings from the > device, but it's so trivial to do that such a thing certainly > exists, which can tell you a bit more about the device. Perhaps > something in libusb is what I'm thinking of. > > That may be enough to get you started without reinventing the > wheel. > > > barry bouwsma > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@chuckr.org | electronics, communications, and SF/Fantasy. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary (on the wall at my old fraternity, Signa Phi Nothing). ---------------------------------------------------------------------------- From owner-freebsd-usb@FreeBSD.ORG Sun Dec 26 20:56:13 2004 Return-Path: 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 F415B16A4CE for ; Sun, 26 Dec 2004 20:56:12 +0000 (GMT) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 101DC43D55 for ; Sun, 26 Dec 2004 20:56:12 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de (cicely5.cicely.de [IPv6:3ffe:400:8d0:301:200:92ff:fe9b:20e7]) (authenticated bits=0) iBQKu5P8062912 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Sun, 26 Dec 2004 21:56:08 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [IPv6:3ffe:400:8d0:301::12]) by cicely5.cicely.de (8.12.10/8.12.10) with ESMTP id iBQKtjrU098697 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 26 Dec 2004 21:55:46 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.12.11/8.12.11) with ESMTP id iBQKtjvh076598; Sun, 26 Dec 2004 21:55:45 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.12.11/8.12.11/Submit) id iBQKti5u076597; Sun, 26 Dec 2004 21:55:44 +0100 (CET) (envelope-from ticso) Date: Sun, 26 Dec 2004 21:55:44 +0100 From: Bernd Walter To: Chuck Robey Message-ID: <20041226205543.GA76551@cicely12.cicely.de> References: <20041224010759.N1763@april.chuckr.org> <200412241756.56900.doconnor@gsoft.com.au> <200412242250.iBOMot433057@Mail.NOSPAM.DynDNS.dK> <20041226160637.H54135@april.chuckr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041226160637.H54135@april.chuckr.org> X-Operating-System: FreeBSD cicely12.cicely.de 5.2-CURRENT alpha User-Agent: Mutt/1.5.6i X-Spam-Status: No, hits=-4.9 required=3.0 tests=BAYES_00 autolearn=ham version=2.64 X-Spam-Report: * -4.9 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on cicely12.cicely.de cc: Barry Bouwsma cc: freebsd-usb@freebsd.org Subject: Re: fingerprints X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ticso@cicely.de List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Dec 2004 20:56:13 -0000 On Sun, Dec 26, 2004 at 04:09:09PM -0500, Chuck Robey wrote: > On Fri, 24 Dec 2004, Barry Bouwsma wrote: > > > > > I suggest you consult the friendly folx hanging out on the USB list > > (usb@ or freebsd-usb@), where I'm sending followups to this as well > > as a copy of this. > > > > Bernd Walter (ticso) has a ports skeleton for the NetBSD USB utilities > > that can tell you details about the endpoints and protocols of your > > device. > > I didn't see any extra email postings on this, I hope it doesn't just > disappear. Can I ask one favor? I would VERY much appreciate it if you > would pick a single one of the usb devices, and I will read everything I > see in the kernel on it. I'm trying to read the usb specification, but > it's quite large, and I'm not sure thats the best way to go about > learning. http://www.cosmo-project.de/~bernd/usbutil.tgz usbctl is the tool to get an overview of the device layout. It's old and has a number of bugs in respect to port system compliance so it never officially went into ports. Maybe someone with more port knowledge than me should take care of it. -- B.Walter BWCT http://www.bwct.de bernd@bwct.de info@bwct.de From owner-freebsd-usb@FreeBSD.ORG Mon Dec 27 00:00:31 2004 Return-Path: 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 A741616A4CE for ; Mon, 27 Dec 2004 00:00:31 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3CC1B43D1F for ; Mon, 27 Dec 2004 00:00:31 +0000 (GMT) (envelope-from mwisnicki@gmail.com) Received: by wproxy.gmail.com with SMTP id 71so307954wri for ; Sun, 26 Dec 2004 16:00:30 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=MHuOIAX9VUyRmzHicU6NJZyBz6VQV9emthSzEbdPxpnTIiyqumJOKVpCufh3KJTph8zZZ1hmDS02EeGKAM8FfvDHdv+KIRE9d2nC3ojTPOEe5sMrrfUuRghHWk0t6bRd5MHuh9/F6RZjyvjHXHIoG6piGc2ObwG9i1qfqriQMdY= Received: by 10.54.31.34 with SMTP id e34mr63480wre; Sun, 26 Dec 2004 16:00:30 -0800 (PST) Received: by 10.54.36.69 with HTTP; Sun, 26 Dec 2004 16:00:30 -0800 (PST) Message-ID: Date: Mon, 27 Dec 2004 01:00:30 +0100 From: Marcin Wisnicki To: freebsd-usb@freebsd.org In-Reply-To: <200412190252.iBJ2q1eW002380@wattres.watt.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <200412190252.iBJ2q1eW002380@wattres.watt.com> Subject: Re: panic w/ USB<->serial adapter and modem X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Marcin Wisnicki List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Dec 2004 00:00:31 -0000 On Sat, 18 Dec 2004 18:52:01 -0800, Steve Watt wrote: > I've got a 5.3-STABLE (updated 19 Nov around 2000PST) machine that > has serious difficulty when I attempt to use the modems that are > attached via the Prolofic Technology PL2303 serial adapters. I'm having similar problems on that device with an isdn modem (it works like normal serial modem) and ppp, using latest 5-stable. Sometimes under heavy load (for example during buildworld), system will panic with "uhci_abort_xfer: not in process context". Since I've finally managed to get a crashdump, I'm able to post a backtrace: make gdbinit kgdb -n0 kernel.debug (kgdb) getsyms (kgdb) bt #0 doadump () at pcpu.h:159 #1 0xc0491773 in boot (howto=0x104) at /usr/src/sys/kern/kern_shutdown.c:410 #2 0xc0491acb in panic (fmt=0xc0752f24 "uhci_abort_xfer: not in process context") at /usr/src/sys/kern/kern_shutdown.c:566 #3 0xc073feea in uhci_abort_xfer (xfer=0xc1763e00, status=USBD_NORMAL_COMPLETION) at /usr/src/sys/modules/usb/../../dev/usb/uhci.c:1956 #4 0xc073f6b9 in uhci_timeout_task (addr=0x0) at /usr/src/sys/modules/usb/../../dev/usb/uhci.c:1534 #5 0xc0738f2e in usb_task_thread (arg=0x0) at /usr/src/sys/modules/usb/../../dev/usb/usb.c:464 #6 0xc04779af in fork_exit (callout=0xc0738e90 , arg=0x0, frame=0x0) at /usr/src/sys/kern/kern_fork.c:807 #7 0xc05d41ac in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:209 This looks like the one in kern/67301, though I don't know why some arguments in my backtrace are wrong (I suppose they shouldn't be 0). I compiled almost everything in modules, but I hope that I've loaded symbols correctly usbdevs -v Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), VIA(0x0000), rev 1.00 port 1 addr 2: full speed, self powered, config 1, DeskJet 920C(0x1504), Hewlett-Packard(0x03f0), rev 1.00 port 2 addr 3: full speed, power 100 mA, config 1, PL2303 Serial adapter (ATEN/IOGEAR UC232A)(0x2303), Prolific Technology(0x067b), rev 2.02 Controller /dev/usb1: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), VIA(0x0000), rev 1.00 port 1 powered port 2 powered Controller /dev/usb2: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), VIA(0x0000), rev 1.00 port 1 powered port 2 powered Controller /dev/usb3: addr 1: high speed, self powered, config 1, EHCI root hub(0x0000), VIA(0x0000), rev 1.00 port 1 powered port 2 powered port 3 powered port 4 powered port 5 powered port 6 powered From owner-freebsd-usb@FreeBSD.ORG Mon Dec 27 01:20:19 2004 Return-Path: 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 6881516A4CE for ; Mon, 27 Dec 2004 01:20:19 +0000 (GMT) Received: from dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NOSPAM.dyndns.dk (84-72-30-72.dclient.hispeed.ch [84.72.30.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9835243D3F for ; Mon, 27 Dec 2004 01:20:17 +0000 (GMT) (envelope-from bounce@NOSPAM.dyndns.dk) Received: from Mail.NOSPAM.DynDNS.dK (ipv6.NOSPAM.dyndns.dk [2002:5448:1e48:0:210:60ff:fe25:f1e5]) (8.11.6/8.11.6-SPAMMERS-DeLiGHt) with ESMTP id iBR1KAI07905 verified NO) for ; Mon, 27 Dec 2004 02:20:15 +0100 (CET) (envelope-from bounce@NOSPAM.dyndns.dk) Received: (from beer@localhost) by Mail.NOSPAM.DynDNS.dK (8.11.6/FNORD) id iBR1K9o07904; Mon, 27 Dec 2004 02:20:10 +0100 (CET) (envelope-from bounce@NOSPAM.dyndns.dk) Date: Mon, 27 Dec 2004 02:20:10 +0100 (CET) Message-Id: <200412270120.iBR1K9o07904@Mail.NOSPAM.DynDNS.dK> X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: beer set sender to bounce@NOSPAM.dyndns.dk using -f X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: Processed from queue /tmp X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: Processed by beer with -C /etc/mail/sendmail.cf-LOCAL From: Barry Bouwsma References: <20041224010759.N1763@april.chuckr.org> <200412241756.56900.doconnor@gsoft.com.au> <200412242250.iBOMot433057@Mail.NOSPAM.DynDNS.dK> <20041226160637.H54135@april.chuckr.org> <20041226205543.GA76551@cicely12.cicely.de> To: freebsd-usb@freebsd.org Mail-Followup-To: freebsd-usb@freebsd.org Subject: Re: fingerprints X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Barry Bouwsma List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Dec 2004 01:20:19 -0000 > > Bernd Walter (ticso) has a ports skeleton for the NetBSD USB utilities > > I didn't see any extra email postings on this, I hope it doesn't just > disappear. Can I ask one favor? I would VERY much appreciate it if you > would pick a single one of the usb devices, and I will read everything I Erm, if I understand you right, how about a D-Link DU-128+ TA? Here are some hints: bLength=18 bDescriptorType=1 bcdUSB=1.10 bDeviceClass=255 bDeviceSubClass=0 ^^^^^^^^^^^^^^^^ bNumEndpoints=0 bInterfaceClass=255 bInterfaceSubClass=0 ^^^^^^^^^^^^^^^^^^^ bNumEndpoints=5 bInterfaceClass=255 bInterfaceSubClass=0 ^^^^^^^^^^^^^^^^^^^ Also, src/sys/dev/usb/usb.h . If I'm not understanding you right, then sorry... > usbctl is the tool to get an overview of the device layout. > It's old and has a number of bugs in respect to port system compliance Also `usbgen' is useful too. Although I'm not sure that as it exists, it's doing everything it should, as I seem to have some errors pulling some strings out of some devices. getstring 1 failed (error=5) getstring 2 failed (error=5) I wonder if the recent NetBSD language delta has anything to do with this; as recent NetBSD can retrieve the vendor of my sound card while the old FreeBSD code I'm still running can't... (usbctl is the tool I was thinking of -- I happened to have an old binary compiled for an old kernel with a different ioctl() to query the device.) Also of interest is `testlibusb' in the devel/libusb port. They pretty much present the same info in different ways. barry bouwsma From owner-freebsd-usb@FreeBSD.ORG Mon Dec 27 04:10:06 2004 Return-Path: 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 2D55B16A4CF for ; Mon, 27 Dec 2004 04:10:06 +0000 (GMT) Received: from web13522.mail.yahoo.com (web13522.mail.yahoo.com [216.136.174.125]) by mx1.FreeBSD.org (Postfix) with SMTP id E820B43D46 for ; Mon, 27 Dec 2004 04:10:05 +0000 (GMT) (envelope-from dyeske@yahoo.com) Received: (qmail 4699 invoked by uid 60001); 27 Dec 2004 04:10:05 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=S6gpdAq1ApXpedHu+2Z+6ApL9seSRqqk8KitNU/B0ZOwaPBqZLyxq/Aa94kUa8plqyIHSm7lX7tTFrT1UzDYGhv02gTMh+bda9AT9/W4+E8sqQRMoQfBGeO1uhVEnUE9GJlPVHD0VdcyK6gFvFY/qucxzQYr6DEWqwsk+VaDPr4= ; Message-ID: <20041227041005.4697.qmail@web13522.mail.yahoo.com> Received: from [24.197.165.156] by web13522.mail.yahoo.com via HTTP; Sun, 26 Dec 2004 20:10:05 PST Date: Sun, 26 Dec 2004 20:10:05 -0800 (PST) From: David Yeske To: usb@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: multimedia@freebsd.org Subject: external sound blaster X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Dec 2004 04:10:06 -0000 I would really like to get my external sound blaster working in FreeBSD HEAD. It is a Model SB0270 Here is a what it looks like when I attach with all the usb debug knobs turned on. ohci_rhsc: sc=0xc1ef8000 xfer=0xc1e6db00 hstatus=0x00000000 ohci_rhsc: change=0x08 uhub_explore: status change hub=1 port=3 ohci_rhsc: sc=0xc1ef8000 xfer=0xc1e6db00 hstatus=0x00000000 ohci_rhsc: change=0x08 usbd_new_device bus=0xc1ef8000 port=3 depth=1 speed=2 usbd_new_device: adding unit addr=2, rev=110, class=0, subclass=0, protocol=0, maxpacket=64, len=18, speed=2 usbd_new_device: new dev (addr 2), dev=0xc65fa280, parent=0xc1eef080 usbd_probe_and_attach: trying device specific drivers usbd_probe_and_attach: no device specific driver found usbd_probe_and_attach: looping over 1 configurations usbd_set_config_index: (addr 1) cno=2 attr=0x80, selfpowered=0, power=500 usbd_set_config_index: set config 1 uaudio0: Creative USB Audio, rev 1.10/1.00, addr 2 uaudio_add_selector: NOT IMPLEMENTED uaudio0: audio rev 1.00 uaudio0: 12 mixer controls pcm0: on uaudio0 pcm0: chn_init(pcm0:play:0) failed: err = 19 pcm0: pcm_chn_create(ua_chan, 1, 0xc65f6500) failed Here is the usbdevs ouput port 3 addr 2: full speed, power 500 mA, config 1, USB Audio(0x3010), Creative(0x041e), rev 1.00 uaudio0 Here is the usb_dump output. DEVICE descriptor: bLength=18 bDescriptorType=1 bcdUSB=1.10 bDeviceClass=0 bDeviceSubClass=0 bDeviceProtocol=0 bMaxPacketSize=64 idVendor=0x041e idProduct=0x3010 bcdDevice=100 iManufacturer=0 iProduct=1 iSerialNumber=0 bNumConfigurations=1 Current configuration is number 1 CONFIGURATION descriptor index 0: bLength=9 bDescriptorType=2 wTotalLength=294 bNumInterface=3 bConfigurationValue=1 iConfiguration=0 bmAttributes=80 bMaxPower=500 mA INTERFACE descriptor index 0, alt index 0: bLength=9 bDescriptorType=4 bInterfaceNumber=0 bAlternateSetting=0 bNumEndpoints=0 bInterfaceClass=1 bInterfaceSubClass=1 bInterfaceProtocol=0 iInterface=0 INTERFACE descriptor index 1, alt index 0: bLength=9 bDescriptorType=4 bInterfaceNumber=1 bAlternateSetting=0 bNumEndpoints=0 bInterfaceClass=1 bInterfaceSubClass=2 bInterfaceProtocol=0 iInterface=0 INTERFACE descriptor index 1, alt index 1: bLength=9 bDescriptorType=4 bInterfaceNumber=1 bAlternateSetting=1 bNumEndpoints=1 bInterfaceClass=1 bInterfaceSubClass=2 bInterfaceProtocol=0 iInterface=0 ENDPOINT descriptor index 0: bLength=9 bDescriptorType=5 bEndpointAddress=1-out bmAttributes=9 wMaxPacketSize=200 bInterval=1 INTERFACE descriptor index 2, alt index 0: bLength=9 bDescriptorType=4 bInterfaceNumber=2 bAlternateSetting=0 bNumEndpoints=0 bInterfaceClass=1 bInterfaceSubClass=2 bInterfaceProtocol=0 iInterface=0 INTERFACE descriptor index 2, alt index 1: bLength=9 bDescriptorType=4 bInterfaceNumber=2 bAlternateSetting=1 bNumEndpoints=1 bInterfaceClass=1 bInterfaceSubClass=2 bInterfaceProtocol=0 iInterface=0 ENDPOINT descriptor index 0: bLength=9 bDescriptorType=5 bEndpointAddress=2-in bmAttributes=5 wMaxPacketSize=200 bInterval=1 This works just fine in NetBSD HEAD uaudio0 at uhub1 port 2 configuration 1 interface 0: Creative Labs USB Audio, rev 1.10/1.00, addr 2 uaudio0: audio rev 1.00 audio1 at uaudio0: full duplex, independent Anyone have any ideas? Regards, David Yeske __________________________________ Do you Yahoo!? The all-new My Yahoo! - Get yours free! http://my.yahoo.com From owner-freebsd-usb@FreeBSD.ORG Mon Dec 27 04:16:12 2004 Return-Path: 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 B322316A4CE for ; Mon, 27 Dec 2004 04:16:12 +0000 (GMT) Received: from web13526.mail.yahoo.com (web13526.mail.yahoo.com [216.136.174.216]) by mx1.FreeBSD.org (Postfix) with SMTP id 9630743D45 for ; Mon, 27 Dec 2004 04:16:12 +0000 (GMT) (envelope-from dyeske@yahoo.com) Received: (qmail 46873 invoked by uid 60001); 27 Dec 2004 04:16:12 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=aklyTO1d7Zcz5Ov03GI08rfkZtIBZ2haX3iNgTi0450UtJMIrq7fVG4teT19p0qB2fDLy3FEeXinFyogx1TjvCLQ8Gzx7K/qixLiSJpohKZLE5fqJ/wmSjGrzQ9SvSoagrxfRN78a07oyl2+UAWJd1ooIPcdAawnI2rmwDgbjBg= ; Message-ID: <20041227041612.46871.qmail@web13526.mail.yahoo.com> Received: from [24.197.165.156] by web13526.mail.yahoo.com via HTTP; Sun, 26 Dec 2004 20:16:12 PST Date: Sun, 26 Dec 2004 20:16:12 -0800 (PST) From: David Yeske To: usb@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: help with uplcom X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Dec 2004 04:16:12 -0000 I have a usb->serial dongle that I would like to have work in FreeBSD. It used to work around 5.2, but it does not work in HEAD. Here is a usb_dump. DEVICE descriptor: bLength=18 bDescriptorType=1 bcdUSB=1.10 bDeviceClass=0 bDeviceSubClass=0 bDeviceProtocol=0 bMaxPacketSize=8 idVendor=0x067b idProduct=0x2303 bcdDevice=202 iManufacturer=0 iProduct=0 iSerialNumber=0 bNumConfigurations=1 Current configuration is number 1 CONFIGURATION descriptor index 0: bLength=9 bDescriptorType=2 wTotalLength=39 bNumInterface=1 bConfigurationValue=1 iConfiguration=0 bmAttributes=a0 bMaxPower=100 mA INTERFACE descriptor index 0, alt index 0: bLength=9 bDescriptorType=4 bInterfaceNumber=0 bAlternateSetting=0 bNumEndpoints=3 bInterfaceClass=255 bInterfaceSubClass=0 bInterfaceProtocol=0 iInterface=0 ENDPOINT descriptor index 0: bLength=7 bDescriptorType=5 bEndpointAddress=1-in bmAttributes=3 wMaxPacketSize=10 bInterval=1 ENDPOINT descriptor index 1: bLength=7 bDescriptorType=5 bEndpointAddress=2-out bmAttributes=2 wMaxPacketSize=64 bInterval=0 ENDPOINT descriptor index 2: bLength=7 bDescriptorType=5 bEndpointAddress=3-in bmAttributes=2 wMaxPacketSize=64 bInterval=0 Here is a usbdevs. port 3 addr 3: full speed, power 100 mA, config 1, PL2303 Serial adapter (ATEN/IOGEAR UC232A)(0x2303), Prolific Technology(0x067b), rev 2.02 ugen1 Here is the attach. usbd_new_device bus=0xc1ef5000 port=3 depth=1 speed=2 usbd_new_device: adding unit addr=3, rev=110, class=0, subclass=0, protocol=0, maxpacket=8, len=18, speed=2 usbd_new_device: new dev (addr 3), dev=0xc63c0180, parent=0xc1eba100 usbd_probe_and_attach: trying device specific drivers ucom0: Prolific Technology PL2303 Serial adapter (ATEN/IOGEAR UC232A), rev 1.10/2.02, addr 3 usbd_set_config_index: (addr 1) cno=3 attr=0xa0, selfpowered=0, power=100 usbd_set_config_index: set config 1 I do not get a /dev/ucom0 device though. I'm wondering if this is a issue with devfs. I'm running this version of FreeBSD on i386 $ cat /usr/src/CVS/Tag D2004.12.23.00.00.00 Anyone have any suggestions? Regards, David Yeske __________________________________ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com From owner-freebsd-usb@FreeBSD.ORG Mon Dec 27 06:43:49 2004 Return-Path: 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 D2FD516A4CE for ; Mon, 27 Dec 2004 06:43:49 +0000 (GMT) Received: from pimout1-ext.prodigy.net (pimout1-ext.prodigy.net [207.115.63.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3D0343D45 for ; Mon, 27 Dec 2004 06:43:48 +0000 (GMT) (envelope-from julian@elischer.org) Received: from [192.168.1.102] (adsl-216-100-134-143.dsl.snfc21.pacbell.net [216.100.134.143])iBR6hce2279948; Mon, 27 Dec 2004 01:43:42 -0500 Message-ID: <41CFAF19.8090502@elischer.org> Date: Sun, 26 Dec 2004 22:43:37 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8a3) Gecko/20041017 X-Accept-Language: en, hu MIME-Version: 1.0 To: ticso@cicely.de References: <41CD83E6.1010304@gmail.com> <20041225181725.GE58581@cicely12.cicely.de> <41CDEDE2.5030900@gmail.com> <20041226002721.GG58581@cicely12.cicely.de> <41CE5B7F.3090805@elischer.org> <20041226131607.GJ58581@cicely12.cicely.de> In-Reply-To: <20041226131607.GJ58581@cicely12.cicely.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-usb@freebsd.org Subject: Re: How to mount usb2 devices X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Dec 2004 06:43:49 -0000 Bernd Walter wrote: > On Sat, Dec 25, 2004 at 10:34:39PM -0800, Julian Elischer wrote: > >>Bernd Walter wrote: >> >>>On Sat, Dec 25, 2004 at 11:46:58PM +0100, Darksidex wrote: >>> >>> >>>>Bernd Walter wrote: >>>> >>>> >>>> >>>>>It is running high speed, because it is attached to your ehci >>>>>controller. >>>>>Having high throughput is another story - msdosfs is not very efficient >>>>>with some devices - you might want to check a dd with big block sizes >>>>>to verify if higher speed can be reached. >>>>> >>>>> >>>> >>>>How can I do it? >>> >>> >>>dd if=/dev/da-whatever-number-it-is of=/dev/null bs=64k >>>You may want to test higher values for bs= too. >> >>I think that there is a lot of work that can be done to speed up >>USB2 devices.. > > > Likely - there is still a lot that can be done even for full speed > devices. > > >>for example Ugen devices can be sped up by an order of magnitude >>with a simple set of changes. (that I will commit when I clean >>them up) I have to guess that the Umass driver may have similar >>performance problems. > > > So you can speed up ugen devices - sounds interesting. > What is the basic idea behind? ehci allows only 4000 interrupts per second. ugen packages data in 1024 byte chunks and does one per interrupt. Previously it allowed only 1000 interrupts per second, limiting you to 1MB/sec.. Now you can get 4MB/sec. however allowing internal transfers of 64KB per transfer allows 64KB*4000 = a lot more. :-) In my original example, throughput went from 1MB/sec to 16MB/sec which was the limit the device would send. With a faster device you should be able to get more throughput. From owner-freebsd-usb@FreeBSD.ORG Mon Dec 27 07:16:11 2004 Return-Path: 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 13A6416A4CE for ; Mon, 27 Dec 2004 07:16:11 +0000 (GMT) Received: from pimout2-ext.prodigy.net (pimout2-ext.prodigy.net [207.115.63.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9457B43D1D for ; Mon, 27 Dec 2004 07:16:10 +0000 (GMT) (envelope-from julian@elischer.org) Received: from [192.168.1.102] (adsl-216-100-134-143.dsl.snfc21.pacbell.net [216.100.134.143])iBR7G2Gr197618; Mon, 27 Dec 2004 02:16:07 -0500 Message-ID: <41CFB6AE.1080705@elischer.org> Date: Sun, 26 Dec 2004 23:15:58 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8a3) Gecko/20041017 X-Accept-Language: en, hu MIME-Version: 1.0 To: hselasky@c2i.net References: <41CB38A7.5020700@vicor.com> <41CB4BCB.1080708@elischer.org> <20041224124346.GG45586@cicely12.cicely.de> <200412261747.36555.hselasky@c2i.net> In-Reply-To: <200412261747.36555.hselasky@c2i.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-usb@freebsd.org Subject: Re: USB vendore designations.. X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Dec 2004 07:16:11 -0000 Hans Petter Selasky wrote: > On Friday 24 December 2004 13:43, Bernd Walter wrote: > >>On Thu, Dec 23, 2004 at 02:50:51PM -0800, Julian Elischer wrote: >> >>>EHCI is almost ok.. except for where it REALLY SUCKS! >> > > The EHCI manual says that QH's can be removed without stopping the HC. QH > removal is done like this: set the previous QH to point to the next QH, and > then set the DOORBELL bit in the EHCI command register and wait for it to > clear. This is the same whether the QH is finished or cancelled, though if it > is finished one might get around with a short DELAY(), hence the HC should > already be skipping the QH? Currently, no driver is checking cancelled QH's, > to see if they were finished after all. If the drivers did, then no > information as to whether the transfers on it were completed or not, would be > lost. > > As long as there are not so many transfers the EHCI is not that inefficient. yes I read the spec. here's the problem: If you have a QH with many qTDs hanging off it, you can tell whether a TD has been comleted by whether it is still active. if it is no longer active, you need to look at the error bits to see if the transfer was successful or not. Now, when you do the "doobell trick" as descibed in the spec, there is one little part of it.. that is the catch. The spec says: "Software should first deactivate all active qTDs, wait for the queue head to go inactive, then remove the queue head from the asynchronous list." Note the word "all" Ok, so since we want to remove only SOME of the qTDs from the queue (those corresponding to the aborting command), and we need to read the status word to see which has been completed by whether the active bit is set, and since we are in a race with the hardware to clear the active bit, which of the qTDs, not in the list of qTDs we want to remove, was completed? Remember that the "current qTD" pointer could have been changed by the hardware the very next bus cycle after we read it, so we can not trust that at all on an active queue. We can only tell where it has gotten past before we started fiddling, but we don't really know where it got to WHILE we were fiddling. (at least by my reading). It is possible that we might be able to turn a qTD and check the "current qTD" in some combined manner that would allow you to deduce the exact state, but my head hurts when I try work it out. Add to that that you need to be sure that you have a memory barrier in teh right place and be absolutly sure that the cache has been updated for the locations accessed by the PCI bus when you read them, etc.etc. The OHCI driver actually hands you the completed TDs by linking them onto a separate queue. There is NO ambiguity there. They could have even solved it by making the "completed" status bit be a different bit in a different memory word from the "This is not active" bit used by the software. One gets a little hope from reading the state diagrams at the back of the spec. but it's a lot to get one's head around. > > Yours > --HPS > _______________________________________________ > freebsd-usb@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-usb > To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org" From owner-freebsd-usb@FreeBSD.ORG Mon Dec 27 08:17:42 2004 Return-Path: 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 B4E2616A4CF; Mon, 27 Dec 2004 08:17:42 +0000 (GMT) Received: from dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NOSPAM.dyndns.dk (84-72-30-72.dclient.hispeed.ch [84.72.30.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD40543D41; Mon, 27 Dec 2004 08:17:38 +0000 (GMT) (envelope-from bounce@NOSPAM.dyndns.dk) Received: from Mail.NOSPAM.DynDNS.dK (ipv6.NOSPAM.dyndns.dk [2002:5448:1e48:0:210:60ff:fe25:f1e5]) (8.11.6/8.11.6-SPAMMERS-DeLiGHt) with ESMTP id iBR8HWh01910 verified NO); Mon, 27 Dec 2004 09:17:37 +0100 (CET) (envelope-from bounce@NOSPAM.dyndns.dk) Received: (from beer@localhost) by Mail.NOSPAM.DynDNS.dK (8.11.6/FNORD) id iBR8HW201908; Mon, 27 Dec 2004 09:17:32 +0100 (CET) (envelope-from bounce@NOSPAM.dyndns.dk) Date: Mon, 27 Dec 2004 09:17:32 +0100 (CET) Message-Id: <200412270817.iBR8HW201908@Mail.NOSPAM.DynDNS.dK> X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: beer set sender to bounce@NOSPAM.dyndns.dk using -f X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: Processed from queue /tmp X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: Processed by beer with -C /etc/mail/sendmail.cf-LOCAL From: Barry Bouwsma References: <20041227041005.4697.qmail@web13522.mail.yahoo.com> To: usb@freebsd.org Mail-Followup-To: usb@freebsd.org, multimedia@freebsd.org cc: multimedia@freebsd.org Subject: Re: external sound blaster X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Barry Bouwsma List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Dec 2004 08:17:42 -0000 On Sun, 26 Dec 2004 20:10:05 -0800 (PST), David Yeske wrote: > I would really like to get my external sound blaster working in FreeBSD HEAD. > Here is a what it looks like when I attach with all the usb debug knobs turned Can you also turn up uaudio debug a few levels? That should give more info... I'm not positive, but it looks like there are a few useful things wrapped with a USB_DEBUG alone (just reading source), are you using a module or is uaudio in the kernel? > uaudio_add_selector: NOT IMPLEMENTED Hmmm, this line is missing from the latest NetBSD, must work there... > Here is the usb_dump output. Thanks; it's slightly different from mine... Those alt settings have me interested. > This works just fine in NetBSD HEAD Good to know. Have you tried it in less-than-HEAD with FreeBSD, such as -stable or 4.x, to see if the latest commits a few days ago have broken it? thanks barry bouwsma From owner-freebsd-usb@FreeBSD.ORG Mon Dec 27 10:02:20 2004 Return-Path: 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 3987816A4CE for ; Mon, 27 Dec 2004 10:02:20 +0000 (GMT) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id A680143D1F for ; Mon, 27 Dec 2004 10:02:19 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de (cicely5.cicely.de [IPv6:3ffe:400:8d0:301:200:92ff:fe9b:20e7]) (authenticated bits=0) iBRA2EP8085616 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK) for ; Mon, 27 Dec 2004 11:02:17 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [IPv6:3ffe:400:8d0:301::12]) by cicely5.cicely.de (8.12.10/8.12.10) with ESMTP id iBRA16rU003515 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 27 Dec 2004 11:01:07 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.12.11/8.12.11) with ESMTP id iBRA16mH081355 for ; Mon, 27 Dec 2004 11:01:06 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.12.11/8.12.11/Submit) id iBRA16Gh081354 for freebsd-usb@freebsd.org; Mon, 27 Dec 2004 11:01:06 +0100 (CET) (envelope-from ticso) Date: Mon, 27 Dec 2004 11:01:05 +0100 From: Bernd Walter To: freebsd-usb@freebsd.org Message-ID: <20041227100104.GC76551@cicely12.cicely.de> References: <20041224010759.N1763@april.chuckr.org> <200412241756.56900.doconnor@gsoft.com.au> <200412242250.iBOMot433057@Mail.NOSPAM.DynDNS.dK> <20041226160637.H54135@april.chuckr.org> <20041226205543.GA76551@cicely12.cicely.de> <200412270120.iBR1K9o07904@Mail.NOSPAM.DynDNS.dK> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200412270120.iBR1K9o07904@Mail.NOSPAM.DynDNS.dK> X-Operating-System: FreeBSD cicely12.cicely.de 5.2-CURRENT alpha User-Agent: Mutt/1.5.6i X-Spam-Status: No, hits=-4.9 required=3.0 tests=BAYES_00 autolearn=ham version=2.64 X-Spam-Report: * -4.9 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on cicely12.cicely.de Subject: Re: fingerprints X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ticso@cicely.de List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Dec 2004 10:02:20 -0000 On Mon, Dec 27, 2004 at 02:20:10AM +0100, Barry Bouwsma wrote: > > > Bernd Walter (ticso) has a ports skeleton for the NetBSD USB utilities > > > > I didn't see any extra email postings on this, I hope it doesn't just > > disappear. Can I ask one favor? I would VERY much appreciate it if you > > would pick a single one of the usb devices, and I will read everything I > > Erm, if I understand you right, how about a D-Link DU-128+ TA? > Here are some hints: > bLength=18 bDescriptorType=1 bcdUSB=1.10 bDeviceClass=255 bDeviceSubClass=0 > ^^^^^^^^^^^^^^^^ > bNumEndpoints=0 bInterfaceClass=255 bInterfaceSubClass=0 > ^^^^^^^^^^^^^^^^^^^ > bNumEndpoints=5 bInterfaceClass=255 bInterfaceSubClass=0 > ^^^^^^^^^^^^^^^^^^^ > Also, src/sys/dev/usb/usb.h . > > If I'm not understanding you right, then sorry... bDeviceClass=255 means that the whole device is vendor specific. You can see what kind of interfaces with which pipes it uses, but beeing vendor specific you don't know their purpose. > > usbctl is the tool to get an overview of the device layout. > > It's old and has a number of bugs in respect to port system compliance > > Also `usbgen' is useful too. Although I'm not sure that as it exists, > it's doing everything it should, as I seem to have some errors pulling > some strings out of some devices. > getstring 1 failed (error=5) > getstring 2 failed (error=5) > I wonder if the recent NetBSD language delta has anything to do with > this; as recent NetBSD can retrieve the vendor of my sound card while > the old FreeBSD code I'm still running can't... I don't know, but I think it did run last year. > (usbctl is the tool I was thinking of -- I happened to have an old > binary compiled for an old kernel with a different ioctl() to query > the device.) Also of interest is `testlibusb' in the devel/libusb port. > They pretty much present the same info in different ways. libusb requires ugen presense of a device, while usbctl runs by accessing a device by opening the bus. -- B.Walter BWCT http://www.bwct.de bernd@bwct.de info@bwct.de From owner-freebsd-usb@FreeBSD.ORG Mon Dec 27 10:11:26 2004 Return-Path: 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 429C216A4CE for ; Mon, 27 Dec 2004 10:11:26 +0000 (GMT) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DAB843D1F for ; Mon, 27 Dec 2004 10:11:25 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de (cicely5.cicely.de [IPv6:3ffe:400:8d0:301:200:92ff:fe9b:20e7]) (authenticated bits=0) iBRABEP8085858 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Mon, 27 Dec 2004 11:11:17 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [IPv6:3ffe:400:8d0:301::12]) by cicely5.cicely.de (8.12.10/8.12.10) with ESMTP id iBRAAfrU003549 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Dec 2004 11:10:41 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.12.11/8.12.11) with ESMTP id iBRAAe3K081396; Mon, 27 Dec 2004 11:10:40 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.12.11/8.12.11/Submit) id iBRAAZ6r081395; Mon, 27 Dec 2004 11:10:36 +0100 (CET) (envelope-from ticso) Date: Mon, 27 Dec 2004 11:10:35 +0100 From: Bernd Walter To: Julian Elischer Message-ID: <20041227101034.GD76551@cicely12.cicely.de> References: <41CD83E6.1010304@gmail.com> <20041225181725.GE58581@cicely12.cicely.de> <41CDEDE2.5030900@gmail.com> <20041226002721.GG58581@cicely12.cicely.de> <41CE5B7F.3090805@elischer.org> <20041226131607.GJ58581@cicely12.cicely.de> <41CFAF19.8090502@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41CFAF19.8090502@elischer.org> X-Operating-System: FreeBSD cicely12.cicely.de 5.2-CURRENT alpha User-Agent: Mutt/1.5.6i X-Spam-Status: No, hits=-4.9 required=3.0 tests=BAYES_00 autolearn=ham version=2.64 X-Spam-Report: * -4.9 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on cicely12.cicely.de cc: ticso@cicely.de cc: freebsd-usb@freebsd.org Subject: Re: How to mount usb2 devices X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ticso@cicely.de List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Dec 2004 10:11:26 -0000 On Sun, Dec 26, 2004 at 10:43:37PM -0800, Julian Elischer wrote: > Bernd Walter wrote: > >On Sat, Dec 25, 2004 at 10:34:39PM -0800, Julian Elischer wrote: > >>for example Ugen devices can be sped up by an order of magnitude > >>with a simple set of changes. (that I will commit when I clean > >>them up) I have to guess that the Umass driver may have similar > >>performance problems. > > > > > >So you can speed up ugen devices - sounds interesting. > >What is the basic idea behind? > ehci allows only 4000 interrupts per second. > ugen packages data in 1024 byte chunks and does one per interrupt. > Previously it allowed only 1000 interrupts per second, limiting you to > 1MB/sec.. Now you can get 4MB/sec. Ah this old story. I didn't know that ugen reduces userland requests too low. Well yes - it should be raised - maybe only for high speed devices. What about umass, doesn't umass run the whole CAM request in one go? CAM reuqests should be big enough unless the underlying filesystem requests single sectors. The dd test should have issued slightly bigger (cam/umass overhead) requests as 64k and 128k. -- B.Walter BWCT http://www.bwct.de bernd@bwct.de info@bwct.de From owner-freebsd-usb@FreeBSD.ORG Mon Dec 27 10:13:18 2004 Return-Path: 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 CDFD916A4CE for ; Mon, 27 Dec 2004 10:13:18 +0000 (GMT) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32C8C43D46 for ; Mon, 27 Dec 2004 10:13:18 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de (cicely5.cicely.de [IPv6:3ffe:400:8d0:301:200:92ff:fe9b:20e7]) (authenticated bits=0) iBRADEP8085897 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Mon, 27 Dec 2004 11:13:16 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [IPv6:3ffe:400:8d0:301::12]) by cicely5.cicely.de (8.12.10/8.12.10) with ESMTP id iBRAC6rU003565 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Dec 2004 11:12:07 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.12.11/8.12.11) with ESMTP id iBRAC6op081417; Mon, 27 Dec 2004 11:12:06 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.12.11/8.12.11/Submit) id iBRAC60b081416; Mon, 27 Dec 2004 11:12:06 +0100 (CET) (envelope-from ticso) Date: Mon, 27 Dec 2004 11:12:05 +0100 From: Bernd Walter To: David Yeske Message-ID: <20041227101205.GE76551@cicely12.cicely.de> References: <20041227041612.46871.qmail@web13526.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041227041612.46871.qmail@web13526.mail.yahoo.com> X-Operating-System: FreeBSD cicely12.cicely.de 5.2-CURRENT alpha User-Agent: Mutt/1.5.6i X-Spam-Status: No, hits=-4.9 required=3.0 tests=BAYES_00 autolearn=ham version=2.64 X-Spam-Report: * -4.9 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on cicely12.cicely.de cc: usb@freebsd.org Subject: Re: help with uplcom X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ticso@cicely.de List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Dec 2004 10:13:18 -0000 On Sun, Dec 26, 2004 at 08:16:12PM -0800, David Yeske wrote: > ucom0: Prolific Technology PL2303 Serial adapter (ATEN/IOGEAR UC232A), rev > 1.10/2.02, addr 3 > > I do not get a /dev/ucom0 device though. I'm wondering if this is a issue with > devfs. I'm running this version of FreeBSD on i386 read UPDATING: 20041018: A major sweep over the tty drivers to elimnate approx 3100 lines of copy&pasted code have been performed. As a part of this change some tty devices have changed names: sio devices are now named: {tty,cua}d%d[.init,.lock] ucom devices are now named: {tty,cua}U%d[.init,.lock] For other drivers see the commit logs. -- B.Walter BWCT http://www.bwct.de bernd@bwct.de info@bwct.de From owner-freebsd-usb@FreeBSD.ORG Mon Dec 27 11:02:21 2004 Return-Path: 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 C7DBD16A50E for ; Mon, 27 Dec 2004 11:02:21 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9870443D48 for ; Mon, 27 Dec 2004 11:02:21 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iBRB2Lgt030329 for ; Mon, 27 Dec 2004 11:02:21 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iBRB2KaG030323 for freebsd-usb@freebsd.org; Mon, 27 Dec 2004 11:02:20 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 27 Dec 2004 11:02:20 GMT Message-Id: <200412271102.iBRB2KaG030323@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-usb@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Dec 2004 11:02:22 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/05/04] kern/66248 usb [panic] bootloader is confused by booting 1 problem total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- f [2001/09/11] kern/30502 usb panics if logitech joystick usb attached a [2001/10/31] kern/31659 usb USB controller driver will die after some f [2001/12/12] kern/32713 usb [usb] mouse detaches from hub and doesnt f [2002/01/13] kern/33839 usb usb0: host controller halted (involving A f [2002/02/17] kern/35061 usb After printing to HP Deskjet 656c USB pri f [2002/04/07] i386/36850 usb Page Fault using ppp with USB Modem [4.9] f [2002/05/30] kern/38736 usb kernel panic during memory stick removal f [2002/06/15] kern/39341 usb ppp + USB modem problem f [2002/06/24] kern/39805 usb 4.6R install panics with umass0 device co o [2002/07/19] kern/40792 usb signals lead to data loss on device ugen o [2002/09/13] kern/42748 usb USB does not work (Fujitsu Lifebook) f [2002/09/25] i386/43366 usb Cannot format media in USB floppy devices o [2002/09/29] kern/43462 usb copying files from olympus C-4040 digital o [2002/10/13] bin/43993 usb /usr/sbin/usbd does not handle an usb eve f [2002/11/22] kern/45579 usb Panic from USB stack after device detach o [2002/12/10] kern/46176 usb umass causes kernel panic if device remov o [2002/12/19] i386/46371 usb USB controller cannot be initialized on I f [2002/12/24] i386/46506 usb [usb] [hang] Crash Before Initialization o [2002/12/29] kern/46618 usb USB (UHCI/ICH3) PALM connect/disconnect/c f [2003/01/12] kern/47005 usb OHCI USB not noticing device detachments o [2003/02/17] kern/48359 usb SiS 5597/8 USB + uscanner breakage a [2003/03/02] kern/48849 usb Maxtor XT5000 causes panic in boot o [2003/03/05] kern/48952 usb uscanner0 hangs a [2003/03/20] kern/50149 usb Using Alcatel SpeedTouch results in "usb0 a [2003/08/14] kern/55587 usb null dereference in usbdi.c: usb_transfer o [2003/09/26] bin/57255 usb usbd and multi-function devices f [2003/12/11] kern/60131 usb [usb] Page fault on disconnect of USB dev f [2003/12/13] kern/60217 usb EHCI controller halts when USB 2.0 device o [2003/12/15] kern/60276 usb [usb] Kernel panic when plugging in USB ( o [2004/01/11] kern/61191 usb [usb] panic: USB vs. Serial problems o [2004/01/15] kern/61377 usb [kbd] usb keyboard not functional after b o [2004/01/20] kern/61627 usb [usb] [patch] New USB printer not support f [2004/01/23] kern/61804 usb [panic] panic with hitachi travelstar USB o [2004/01/24] kern/61841 usb [boot] 5.2 Boot freeze if memorybird (USB f [2004/01/30] kern/62088 usb [usb] Logitech Cordless/Optical Mouse not o [2004/01/30] kern/62123 usb [usb] LaCie 160GB USB drive umass: BBB re o [2004/02/23] i386/63251 usb [usb] USB stops working after 2nd APM sus o [2004/02/26] kern/63375 usb [patch] panic: unplugging USB devices pan o [2004/02/29] i386/63521 usb 5.2.1 doesn't detect drives on SATA contr o [2004/03/01] kern/63621 usb [usb] USB MemoryStick Reader stalls/crash o [2004/04/07] kern/65292 usb [panic] random page faults (usb-related?) o [2004/04/19] i386/65783 usb [panic] Panic when attaching card reader o [2004/05/06] kern/66324 usb [usb] usb driver memory leak grows wired o [2004/07/13] kern/69006 usb [patch] Apple Cinema Display hangs USB po o [2004/08/30] kern/71155 usb [usb] misbehaving usb-printer hangs proce o [2004/09/18] kern/71887 usb [kbd] Losing keyboard after plugging a bl o [2004/09/27] kern/72119 usb Detaching USB Memory Stick w/o umount cau f [2004/10/11] i386/72497 usb WD USB Disk Panics -stable and 5.2.1 o [2004/10/29] kern/73295 usb Lock order reversal in USB code. o [2004/10/30] kern/73307 usb Kernel panics on USB disconnect o [2004/11/18] kern/74088 usb ohci ehci uhub: port disabled on connecti 51 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2001/09/30] conf/30929 usb [patch] use usbd to initialize USB ADSL m o [2001/12/09] kern/32652 usb [patch] A new ioctl to uscanner s [2001/12/09] ports/32653 usb Added patches to improve USB scanner supp f [2002/04/23] kern/37374 usb [PATCH] closing ums0 blocks with wmesg uh f [2002/05/04] conf/37732 usb usbd start in wrong place in /etc/rc in 4 o [2002/05/23] kern/38452 usb [usb] Logitech USB iFeel: device_probe_an o [2002/07/16] kern/40657 usb [usb] Logitech iFeel usb mouse will not a o [2002/07/24] kern/40948 usb [usb] USB HP CDW8200 does not work o [2002/08/07] kern/41415 usb [usb] [patch] Some USB scanners cannot ta f [2002/10/25] kern/44450 usb USB support FAILURE for device that was s o [2003/01/18] kern/47200 usb USB port is disabled when Kodak DX4900 is o [2003/02/06] kern/48014 usb [usb] moused fails to correctly identify o [2003/02/16] bin/48342 usb [PATCH] usbd dynamic device list. o [2003/03/19] kern/50110 usb [usb] Astra 2100U scanner being detected o [2003/05/08] kern/51958 usb [usb] [patch] update for urio driver o [2003/05/10] kern/52026 usb [usb] feature request: umass driver suppo o [2003/06/08] kern/53025 usb [PATCH] ugen does not allow O_NONBLOCK fo f [2003/09/19] kern/56999 usb FreeCom USB CD/RW problem on FreeBSD 5.1 o [2003/11/10] i386/59147 usb [usb] USB active extension cable not reco o [2003/11/11] kern/59169 usb [patch] ulpt is missing read operation o [2003/12/15] kern/60248 usb [patch] Problem with USB printer HP Laser o [2004/01/12] bin/61234 usb [usb] [patch] usbhidaction doesn't suppor o [2004/01/14] kern/61365 usb FreeBSD resets when I turn off monitor w/ o [2004/02/13] kern/62788 usb need quirks for Super Talent Flash USB 2. o [2004/03/04] kern/63779 usb [usb] USB-mass storage (USB to IDE Conver o [2004/03/06] kern/63837 usb [patch] USB: hid_is_collection() only loo o [2004/04/11] kern/65436 usb QUIRK: [patch] to add support for PNY Att o [2004/04/19] kern/65769 usb [usb] Call to tcflush(x, TCIFLUSH) stops o [2004/05/11] kern/66547 usb [usb] Palm Tungsten T USB does not initia o [2004/06/27] kern/68412 usb [usb] [patch] QUIRK: Philips KEY013 USB M o [2004/07/06] i386/68719 usb [usb] USB 2.0 mobil rack+ fat32 performan o [2004/08/16] kern/70523 usb [usb] [patch] umct sending/receiving wron o [2004/08/25] kern/70942 usb [usb] Genius Wireless USB mouse: moused d o [2004/09/06] kern/71416 usb [usb] Cryptoflex e-gate USB token (ugen0) o [2004/09/06] kern/71417 usb [usb] Cryptoflex e-gate USB token (ugen0) o [2004/09/07] kern/71455 usb [usb] Slow USB umass performance of 5.3 o [2004/09/11] kern/71605 usb [usb] [patch] umass doesn't recognize mul o [2004/10/05] kern/72344 usb [usb] [patch] QUIRK: Dane-Elec zMate 512 f [2004/10/06] i386/72380 usb [usb] USB does not work [dual Celeron Abi o [2004/10/23] i386/73056 usb [usb] Sun Microsystems Type 6 USB mouse n o [2004/11/02] i386/73421 usb [usb] USB not recgnized/working on Toshib o [2004/11/16] kern/73999 usb [usb] USB Freezes when a device is plugge 42 problems total. From owner-freebsd-usb@FreeBSD.ORG Mon Dec 27 11:42:21 2004 Return-Path: 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 C998E16A4CE for ; Mon, 27 Dec 2004 11:42:21 +0000 (GMT) Received: from mailfe01.swip.net (mailfe01.swip.net [212.247.154.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 04EC443D41 for ; Mon, 27 Dec 2004 11:42:21 +0000 (GMT) (envelope-from hselasky@c2i.net) X-T2-Posting-ID: gvlK0tOCzrqh9CPROFOFPw== Received: from mp-216-52-16.daxnet.no ([193.216.52.16] verified) by mailfe01.swip.net (CommuniGate Pro SMTP 4.2.7) with ESMTP id 252482022 for freebsd-usb@freebsd.org; Mon, 27 Dec 2004 12:42:19 +0100 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Mon, 27 Dec 2004 12:42:42 +0100 User-Agent: KMail/1.7 References: <41CB38A7.5020700@vicor.com> <200412261747.36555.hselasky@c2i.net> <41CFB6AE.1080705@elischer.org> In-Reply-To: <41CFB6AE.1080705@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412271242.43441.hselasky@c2i.net> Subject: Re: USB vendore designations.. X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: hselasky@c2i.net List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Dec 2004 11:42:22 -0000 On Monday 27 December 2004 08:15, Julian Elischer wrote: > Now, when you do the "doobell trick" as descibed in the spec, > there is one little part of it.. that is the catch. > > The spec says: > "Software should first deactivate all active qTDs, wait for the > queue head to go inactive, then remove the queue head from > the asynchronous list." > > Note the word "all" > > Ok, so since we want to remove only SOME of the qTDs from the queue > (those corresponding to the aborting command), and we need to read > the status word to see which has been completed by whether the > active bit is set, and since we are in a race with the hardware > to clear the active bit, which of the qTDs, not in the list of > qTDs we want to remove, was completed? > Maybe the EHCI driver should not reuse the QH's for transfers on the same pipe, but instead like I did, have one QH for each transfer, insterted into the asynchronous schedule after that the last QH has been removed? Yours --HPS From owner-freebsd-usb@FreeBSD.ORG Mon Dec 27 14:44:16 2004 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3C7F816A4CE; Mon, 27 Dec 2004 14:44:16 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17E5543D46; Mon, 27 Dec 2004 14:44:16 +0000 (GMT) (envelope-from joe@FreeBSD.org) Received: from freefall.freebsd.org (joe@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iBREiFhD062223; Mon, 27 Dec 2004 14:44:15 GMT (envelope-from joe@freefall.freebsd.org) Received: (from joe@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iBREiFE5062219; Mon, 27 Dec 2004 14:44:15 GMT (envelope-from joe) Date: Mon, 27 Dec 2004 14:44:15 GMT From: Josef Karthauser Message-Id: <200412271444.iBREiFE5062219@freefall.freebsd.org> To: joe@FreeBSD.org, joe@FreeBSD.org, freebsd-usb@FreeBSD.org Subject: Re: bin/42213: moused(8) seems to delay some mouse events from a USB mouse X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Dec 2004 14:44:16 -0000 Synopsis: moused(8) seems to delay some mouse events from a USB mouse Responsible-Changed-From-To: joe->freebsd-usb Responsible-Changed-By: joe Responsible-Changed-When: Mon Dec 27 14:43:42 GMT 2004 Responsible-Changed-Why: This one belongs to the usb list. http://www.freebsd.org/cgi/query-pr.cgi?pr=42213 From owner-freebsd-usb@FreeBSD.ORG Mon Dec 27 14:44:44 2004 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D9EB516A4CE; Mon, 27 Dec 2004 14:44:44 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id B364B43D1D; Mon, 27 Dec 2004 14:44:44 +0000 (GMT) (envelope-from joe@FreeBSD.org) Received: from freefall.freebsd.org (joe@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iBREiiHO062271; Mon, 27 Dec 2004 14:44:44 GMT (envelope-from joe@freefall.freebsd.org) Received: (from joe@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iBREiiii062267; Mon, 27 Dec 2004 14:44:44 GMT (envelope-from joe) Date: Mon, 27 Dec 2004 14:44:44 GMT From: Josef Karthauser Message-Id: <200412271444.iBREiiii062267@freefall.freebsd.org> To: joe@FreeBSD.org, joe@FreeBSD.org, freebsd-usb@FreeBSD.org Subject: Re: bin/52432: [sysinstall] drivers.flp won't load with USB floppy drive X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Dec 2004 14:44:45 -0000 Synopsis: [sysinstall] drivers.flp won't load with USB floppy drive Responsible-Changed-From-To: joe->freebsd-usb Responsible-Changed-By: joe Responsible-Changed-When: Mon Dec 27 14:44:30 GMT 2004 Responsible-Changed-Why: This one belongs to the usb list. http://www.freebsd.org/cgi/query-pr.cgi?pr=52432 From owner-freebsd-usb@FreeBSD.ORG Mon Dec 27 22:38:40 2004 Return-Path: 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 0E40516A4CE for ; Mon, 27 Dec 2004 22:38:40 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id E325543D55 for ; Mon, 27 Dec 2004 22:38:39 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id BCC257A403; Mon, 27 Dec 2004 14:38:39 -0800 (PST) Message-ID: <41D08EEF.50807@elischer.org> Date: Mon, 27 Dec 2004 14:38:39 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: hselasky@c2i.net References: <41CB38A7.5020700@vicor.com> <200412261747.36555.hselasky@c2i.net> <41CFB6AE.1080705@elischer.org> <200412271242.43441.hselasky@c2i.net> In-Reply-To: <200412271242.43441.hselasky@c2i.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-usb@freebsd.org Subject: Re: USB vendore designations.. X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Dec 2004 22:38:40 -0000 Hans Petter Selasky wrote: >On Monday 27 December 2004 08:15, Julian Elischer wrote: > > >>Now, when you do the "doobell trick" as descibed in the spec, >>there is one little part of it.. that is the catch. >> >>The spec says: >>"Software should first deactivate all active qTDs, wait for the >>queue head to go inactive, then remove the queue head from >>the asynchronous list." >> >>Note the word "all" >> >>Ok, so since we want to remove only SOME of the qTDs from the queue >>(those corresponding to the aborting command), and we need to read >>the status word to see which has been completed by whether the >>active bit is set, and since we are in a race with the hardware >>to clear the active bit, which of the qTDs, not in the list of >>qTDs we want to remove, was completed? >> >> >> >Maybe the EHCI driver should not reuse the QH's for transfers on the same >pipe, but instead like I did, have one QH for each transfer, insterted into >the asynchronous schedule after that the last QH has been removed? > It's an interesting idea.. where did you do this? In a new driver? sorry to be stupid but qa pointer would be good? s this the driver in _usb I think I saw from you earlier? It has the good point of being "clean" It has the bad point of only allowing one transaction per interrupt cycle. > >Yours >--HPS >_______________________________________________ >freebsd-usb@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-usb >To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org" > > From owner-freebsd-usb@FreeBSD.ORG Tue Dec 28 02:58:39 2004 Return-Path: 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 13BBF16A4CE; Tue, 28 Dec 2004 02:58:39 +0000 (GMT) Received: from freebsd3.cimlogic.com.au (adsl-20-121.swiftdsl.com.au [218.214.20.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id BEDDF43D49; Tue, 28 Dec 2004 02:58:37 +0000 (GMT) (envelope-from jb@cimlogic.com.au) Received: by freebsd3.cimlogic.com.au (Postfix, from userid 102) id 7018E6AA01; Tue, 28 Dec 2004 13:58:36 +1100 (EST) Date: Tue, 28 Dec 2004 13:58:36 +1100 From: John Birrell To: Julian Elischer Message-ID: <20041228025836.GA53223@freebsd3.cimlogic.com.au> References: <20041228010938.GA39686@freebsd3.cimlogic.com.au> <41D0C63F.3000702@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41D0C63F.3000702@elischer.org> User-Agent: Mutt/1.4.2.1i cc: usb@freebsd.org Subject: Re: USB problems X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2004 02:58:39 -0000 On Mon, Dec 27, 2004 at 06:34:39PM -0800, Julian Elischer wrote: > can you be a bi tmore explicit abuot what you mena by "stalls the > control endpoint at > every opportunity". > > The linux libusb has code in its' timeout code that "unstalls" > endpoints if they timeout. I p[resume becasue they have seen this as > a common reason for timeouts. FreeBSD issues teh same command on > endpoint open.. try closing and reopenning the endpoint. The stall I'm referring to is a bit in the ISP1581 controller. According to the USB spec, a device sets the stall bit if it can't do something it is asked to do. In the case of this Philips device, it sends a descriptor (for instance) and then sets the stall bit on the control endpoint for seemingly no good reason. If you ask for device status, the firware sends it, then stalls the control endpoint. I have to set the NO_STRINGS quirk to stop FreeBSD from ignoring th device simply because it stalls the control endpoint after sending a string descriptor. > hmm I'll have to look at the spec to see if a stall status can > come back with data? My reading of the spec is that, yes it can. In 8.5.3 they refer to 'setup', 'data' and 'status' stages of a control transfer. > There are two 'stalls'.. the endpoint stalls, and the local status > word reflects that. (at least in EHCI), so you'd need to clear both.. > one with a write and teh other with a memory write.. Are you referring to the 'control' endpoint? The FreeBSD code seems to infer that the control endpoint shouldn't stall. > > if (nstatus & UHCI_TD_ACTIVE) > > break; > > > >> in uhci_idone() to the bottom of the loop, it returns the actlen > > properly (I think). At least I can get the data from the device despite > > the stall. > > can it then proceed? Yes, it can. I talk to the device with that change. I'm just not sure whether it makes sense. > I'm trying to address that issue right now.. > If we can't bring netBSD withus in some architectural changes than at > some stage we'll have to go it ourselves. Which I'd rather not do.. > but they are hard to contact.. (probably also short of time) No doubt. > >I'd love to get rid of the attach_args structure and just pass a > >usbd_device_handle into the drivers, with struct usbd_device containing > >a couple of extra variables for use during matching. > > sure.. there are a number of architectural changes "in the wings" > that I'd like ot thrash out with the NetBSD guys but I have found > it hard to find a forum to communicate with tehm on.. > the suggestion "send a NetBSD PR" is the best I've got back so far.. > Though they have seemed friendly enough. Who from NetBSD? If it's one of the 'elephants' (with long memories and who hold a grudge), they might react badly to my name. 8-) [ BTW, I just noticed there is a freebsd-usb list. I must have missed the announcement. ] -- John Birrell From owner-freebsd-usb@FreeBSD.ORG Tue Dec 28 03:13:53 2004 Return-Path: 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 5CF6616A4CE for ; Tue, 28 Dec 2004 03:13:53 +0000 (GMT) Received: from dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NOSPAM.dyndns.dk (84-72-30-72.dclient.hispeed.ch [84.72.30.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 990AD43D41 for ; Tue, 28 Dec 2004 03:13:51 +0000 (GMT) (envelope-from bounce@NOSPAM.dyndns.dk) Received: from Mail.NOSPAM.DynDNS.dK (ipv6.NOSPAM.dyndns.dk [2002:5448:1e48:0:210:60ff:fe25:f1e5]) (8.11.6/8.11.6-SPAMMERS-DeLiGHt) with ESMTP id iBS3Dke01403 verified NO) for ; Tue, 28 Dec 2004 04:13:49 +0100 (CET) (envelope-from bounce@NOSPAM.dyndns.dk) Received: (from beer@localhost) by Mail.NOSPAM.DynDNS.dK (8.11.6/FNORD) id iBS3Djc01402; Tue, 28 Dec 2004 04:13:45 +0100 (CET) (envelope-from bounce@NOSPAM.dyndns.dk) Date: Tue, 28 Dec 2004 04:13:45 +0100 (CET) Message-Id: <200412280313.iBS3Djc01402@Mail.NOSPAM.DynDNS.dK> X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: beer set sender to bounce@NOSPAM.dyndns.dk using -f X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: Processed from queue /tmp X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: Processed by beer with -C /etc/mail/sendmail.cf-LOCAL From: Barry Bouwsma To: freebsd-usb@freebsd.org Mail-Followup-To: freebsd-usb@freebsd.org Subject: umass.c for stable-4.x X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Barry Bouwsma List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2004 03:13:53 -0000 Salut, I just wanted to mention that I've tried the latest 4.x umass.c and it has problems for me, so I've taken the latest -current umass.c and hacked it to work with my 4.x, and added a few fixes and stuff. If anyone wants to try it out, since I don't know how much it relies on hacks I have elsewhere in my 4.x source, feel free to try it from https://NOSPAM.dyndns.dk/hacks/usb/ It probably won't work as-is for you; at least a couple things are products added to https://NOSPAM.dyndns.dk/hacks/usbdevs/usbdevs-in-progress-for-freebsd-4.x (that is probably broken for a whole kernel build so far) Other problems may exist as well, and I'd like to hear of them on clean 4.x systems. This is also a candidate for a few things which can be added to -current to help out a couple devices I have. I'll see about diffs for this as I look into merging NetBSD enhancements. The problems I had with unadulterated 4.x included: only saw one slot of a multi-all-in-one-cardreader device, and detaching a device was highly likely to cause instant panic. Also, a couple fixes are in here for improved operation of some devices I have. I've been running -current-based umass.c on my 4.x for months now with no real problems. enjoy barry bouwsma From owner-freebsd-usb@FreeBSD.ORG Tue Dec 28 15:23:29 2004 Return-Path: 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 244FD16A4CE for ; Tue, 28 Dec 2004 15:23:29 +0000 (GMT) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B59C43D48 for ; Tue, 28 Dec 2004 15:23:28 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de (cicely5.cicely.de [IPv6:3ffe:400:8d0:301:200:92ff:fe9b:20e7]) (authenticated bits=0) iBSFN8P8057268 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Tue, 28 Dec 2004 16:23:12 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [IPv6:3ffe:400:8d0:301::12]) by cicely5.cicely.de (8.12.10/8.12.10) with ESMTP id iBSFMGUU031940 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 28 Dec 2004 16:22:17 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.12.11/8.12.11) with ESMTP id iBSFMGMb091380; Tue, 28 Dec 2004 16:22:16 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.12.11/8.12.11/Submit) id iBSFMEo1091379; Tue, 28 Dec 2004 16:22:14 +0100 (CET) (envelope-from ticso) Date: Tue, 28 Dec 2004 16:22:13 +0100 From: Bernd Walter To: John Birrell Message-ID: <20041228152212.GM81585@cicely12.cicely.de> References: <20041228010938.GA39686@freebsd3.cimlogic.com.au> <41D0C63F.3000702@elischer.org> <20041228025836.GA53223@freebsd3.cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041228025836.GA53223@freebsd3.cimlogic.com.au> X-Operating-System: FreeBSD cicely12.cicely.de 5.2-CURRENT alpha User-Agent: Mutt/1.5.6i X-Spam-Status: No, hits=-4.9 required=3.0 tests=BAYES_00 autolearn=ham version=2.64 X-Spam-Report: * -4.9 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on cicely12.cicely.de cc: usb@freebsd.org cc: Julian Elischer Subject: Re: USB problems X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ticso@cicely.de List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2004 15:23:29 -0000 On Tue, Dec 28, 2004 at 01:58:36PM +1100, John Birrell wrote: > On Mon, Dec 27, 2004 at 06:34:39PM -0800, Julian Elischer wrote: > > can you be a bi tmore explicit abuot what you mena by "stalls the > > control endpoint at > > every opportunity". > > > > The linux libusb has code in its' timeout code that "unstalls" > > endpoints if they timeout. I p[resume becasue they have seen this as > > a common reason for timeouts. FreeBSD issues teh same command on > > endpoint open.. try closing and reopenning the endpoint. > > The stall I'm referring to is a bit in the ISP1581 controller. According to > the USB spec, a device sets the stall bit if it can't do something it is > asked to do. > > In the case of this Philips device, it sends a descriptor (for instance) > and then sets the stall bit on the control endpoint for seemingly no good > reason. > > If you ask for device status, the firware sends it, then stalls the control > endpoint. > > I have to set the NO_STRINGS quirk to stop FreeBSD from ignoring th > device simply because it stalls the control endpoint after sending a > string descriptor. Why is the quirk required? OK - you get a stall on control endpoint, but this shouldn't harm anything, as stalls on control enpoints are automatically cleared on the next setup phase and the Philips controllers do that on their own. If you get in trouble then the firmware on the device does more wrong than just stalling the endpoint. > > hmm I'll have to look at the spec to see if a stall status can > > come back with data? > > My reading of the spec is that, yes it can. In 8.5.3 they refer to 'setup', > 'data' and 'status' stages of a control transfer. You can get a stall later if the case isn't known at request time. IIRC some USB2.0 firmware stall the control enpoint after transfering legal data if they have been asked in an USB1.1 format. I think we had this a while back for high speed hubs. > > There are two 'stalls'.. the endpoint stalls, and the local status > > word reflects that. (at least in EHCI), so you'd need to clear both.. > > one with a write and teh other with a memory write.. > > Are you referring to the 'control' endpoint? The FreeBSD code seems to > infer that the control endpoint shouldn't stall. Maybe there are broken comments left, but a stalled control endpoint doesn't require any special handling other than taken this a an error. -- B.Walter BWCT http://www.bwct.de bernd@bwct.de info@bwct.de From owner-freebsd-usb@FreeBSD.ORG Tue Dec 28 19:03:55 2004 Return-Path: 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 5A17F16A4CE for ; Tue, 28 Dec 2004 19:03:55 +0000 (GMT) Received: from mailfe09.swip.net (mailfe09.swip.net [212.247.155.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8EF0943D5A for ; Tue, 28 Dec 2004 19:03:54 +0000 (GMT) (envelope-from hselasky@c2i.net) X-T2-Posting-ID: gvlK0tOCzrqh9CPROFOFPw== Received: from mp-216-36-122.daxnet.no ([193.216.36.122] verified) by mailfe09.swip.net (CommuniGate Pro SMTP 4.2.7) with ESMTP id 51979310; Tue, 28 Dec 2004 20:03:16 +0100 From: Hans Petter Selasky To: Julian Elischer Date: Tue, 28 Dec 2004 20:04:16 +0100 User-Agent: KMail/1.7 References: <41CB38A7.5020700@vicor.com> <200412271242.43441.hselasky@c2i.net> <41D08EEF.50807@elischer.org> In-Reply-To: <41D08EEF.50807@elischer.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200412282004.16958.hselasky@c2i.net> cc: freebsd-usb@freebsd.org Subject: Re: USB vendore designations.. X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: hselasky@c2i.net List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2004 19:03:55 -0000 On Monday 27 December 2004 23:38, Julian Elischer wrote: > Hans Petter Selasky wrote: > >On Monday 27 December 2004 08:15, Julian Elischer wrote: > >>Now, when you do the "doobell trick" as descibed in the spec, > >>there is one little part of it.. that is the catch. > >> > >>The spec says: > >>"Software should first deactivate all active qTDs, wait for the > >>queue head to go inactive, then remove the queue head from > >>the asynchronous list." > >> > >>Note the word "all" > >> > >>Ok, so since we want to remove only SOME of the qTDs from the queue > >>(those corresponding to the aborting command), and we need to read > >>the status word to see which has been completed by whether the > >>active bit is set, and since we are in a race with the hardware > >>to clear the active bit, which of the qTDs, not in the list of > >>qTDs we want to remove, was completed? > > > >Maybe the EHCI driver should not reuse the QH's for transfers on the same > >pipe, but instead like I did, have one QH for each transfer, insterted > > into the asynchronous schedule after that the last QH has been removed? > > It's an interesting idea.. > > where did you do this? In a new driver? > Yes, the one I posted earlier this year: Create a new directory and download the following files and type "make install" (to uninstall type "make deinstall") http://home.c2i.net/hselasky/isdn4bsd/privat/usb/Makefile http://home.c2i.net/hselasky/isdn4bsd/privat/usb/new_usb_1_5_4.diff.bz2 http://home.c2i.net/hselasky/isdn4bsd/privat/usb/new_usb_1_5_4.tar.bz2 > > > It has the good point of being "clean" > It has the bad point of only allowing one transaction per interrupt cycle. Thats the way UHCI driver is currently doing it. Transfer more data at a time, and the loss will be less. How about removing the QH from the asynchronous schedule, before removing the TD's and then insert the QH back into the asynchronous schedule? Very few drivers start more than one transfer at an asynchronous pipe at a time, so most of the time there will be a short delay between transfers anyway. Yours --HPS From owner-freebsd-usb@FreeBSD.ORG Tue Dec 28 19:19:13 2004 Return-Path: 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 0FECD16A4CE for ; Tue, 28 Dec 2004 19:19:13 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE38B43D41 for ; Tue, 28 Dec 2004 19:19:12 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id C05007A403; Tue, 28 Dec 2004 11:19:12 -0800 (PST) Message-ID: <41D1B1B0.8070003@elischer.org> Date: Tue, 28 Dec 2004 11:19:12 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: hselasky@c2i.net References: <41CB38A7.5020700@vicor.com> <200412271242.43441.hselasky@c2i.net> <41D08EEF.50807@elischer.org> <200412282004.16958.hselasky@c2i.net> In-Reply-To: <200412282004.16958.hselasky@c2i.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-usb@freebsd.org Subject: Re: USB vendore designations.. X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2004 19:19:13 -0000 Hans Petter Selasky wrote: >On Monday 27 December 2004 23:38, Julian Elischer wrote: > > >>Hans Petter Selasky wrote: >> >> >>>On Monday 27 December 2004 08:15, Julian Elischer wrote: >>> >>> >>>>Now, when you do the "doobell trick" as descibed in the spec, >>>>there is one little part of it.. that is the catch. >>>> >>>>The spec says: >>>>"Software should first deactivate all active qTDs, wait for the >>>>queue head to go inactive, then remove the queue head from >>>>the asynchronous list." >>>> >>>>Note the word "all" >>>> >>>>Ok, so since we want to remove only SOME of the qTDs from the queue >>>>(those corresponding to the aborting command), and we need to read >>>>the status word to see which has been completed by whether the >>>>active bit is set, and since we are in a race with the hardware >>>>to clear the active bit, which of the qTDs, not in the list of >>>>qTDs we want to remove, was completed? >>>> >>>> >>>Maybe the EHCI driver should not reuse the QH's for transfers on the same >>>pipe, but instead like I did, have one QH for each transfer, insterted >>>into the asynchronous schedule after that the last QH has been removed? >>> >>> >>It's an interesting idea.. >> >>where did you do this? In a new driver? >> >> >> >Yes, the one I posted earlier this year: > >Create a new directory and download the following files and type "make >install" (to uninstall type "make deinstall") > >http://home.c2i.net/hselasky/isdn4bsd/privat/usb/Makefile >http://home.c2i.net/hselasky/isdn4bsd/privat/usb/new_usb_1_5_4.diff.bz2 >http://home.c2i.net/hselasky/isdn4bsd/privat/usb/new_usb_1_5_4.tar.bz2 > > >>It has the good point of being "clean" >>It has the bad point of only allowing one transaction per interrupt cycle. >> >> >Thats the way UHCI driver is currently doing it. >Transfer more data at a time, and the loss will be less. > >How about removing the QH from the asynchronous schedule, before removing the >TD's and then insert the QH back into the asynchronous schedule? > that's what I'm doing now in my test code.. iI'll check it in today maybe. > >Very few drivers start more than one transfer at an asynchronous pipe at a >time, so most of the time there will be a short delay between transfers >anyway. > > yes, but why break it as a possibility? :-) > >Yours >--HPS >_______________________________________________ >freebsd-usb@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-usb >To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org" > > From owner-freebsd-usb@FreeBSD.ORG Tue Dec 28 19:54:39 2004 Return-Path: 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 8A7A316A4CE for ; Tue, 28 Dec 2004 19:54:39 +0000 (GMT) Received: from freebsd3.cimlogic.com.au (adsl-20-121.swiftdsl.com.au [218.214.20.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 864DC43D45 for ; Tue, 28 Dec 2004 19:54:38 +0000 (GMT) (envelope-from jb@cimlogic.com.au) Received: by freebsd3.cimlogic.com.au (Postfix, from userid 102) id DC47C6AA04; Wed, 29 Dec 2004 06:54:36 +1100 (EST) Date: Wed, 29 Dec 2004 06:54:36 +1100 From: John Birrell To: ticso@cicely.de Message-ID: <20041228195436.GA61668@freebsd3.cimlogic.com.au> References: <20041228010938.GA39686@freebsd3.cimlogic.com.au> <41D0C63F.3000702@elischer.org> <20041228025836.GA53223@freebsd3.cimlogic.com.au> <20041228152212.GM81585@cicely12.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041228152212.GM81585@cicely12.cicely.de> User-Agent: Mutt/1.4.2.1i cc: usb@freebsd.org cc: Julian Elischer Subject: Re: USB problems X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2004 19:54:39 -0000 On Tue, Dec 28, 2004 at 04:22:13PM +0100, Bernd Walter wrote: > Why is the quirk required? > OK - you get a stall on control endpoint, but this shouldn't harm > anything, as stalls on control enpoints are automatically cleared on > the next setup phase and the Philips controllers do that on their own. > If you get in trouble then the firmware on the device does more wrong > than just stalling the endpoint. The quirk gets around the problem that FreeBSD turns the stall status of the control endpoint into an error which aborts any further processing. The string descriptors are returned normally by the device, except for the fact that it sets the stall bit on the control endpoint. (If the handling of the stall status is changed, the quirk wouldn't be necessary) > IIRC some USB2.0 firmware stall the control enpoint after transfering > legal data if they have been asked in an USB1.1 format. > I think we had this a while back for high speed hubs. The firmware in this device doesn't test the format. It unconditionally stalls the control endpoint in many cases (like getting a device or configuration descriptor and requesting less bytes than the full descriptor; getting a string descriptor; getting configuration; getting status). > Maybe there are broken comments left, but a stalled control endpoint > doesn't require any special handling other than taken this a an error. In usbd_do_request_flags_pipe() there is code that detects a stalled control endpoint and then tries to clear the stall. In the case of the devices I have, this code just fails because it gets a stall error too. The FreeBSD code *never* takes into account that the control endpoint stall will be cleared with the next setup packet. I think that a control endpoint transfer should not return USBD_STALLED to the caller unless the length received is less than that requested and ~SHORT_TRANSER_OK. A stall on the control endpoint should only be an error if the controller has a problem with the protocol (i.e. it is a protocol stall, not a device stall); -- John Birrell From owner-freebsd-usb@FreeBSD.ORG Tue Dec 28 20:29:34 2004 Return-Path: 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 C373F16A4CE for ; Tue, 28 Dec 2004 20:29:34 +0000 (GMT) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01C3743D49 for ; Tue, 28 Dec 2004 20:29:33 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de (cicely5.cicely.de [IPv6:3ffe:400:8d0:301:200:92ff:fe9b:20e7]) (authenticated bits=0) iBSKTCP8069973 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Tue, 28 Dec 2004 21:29:16 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [IPv6:3ffe:400:8d0:301::12]) by cicely5.cicely.de (8.12.10/8.12.10) with ESMTP id iBSKSYUU045601 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 28 Dec 2004 21:28:35 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.12.11/8.12.11) with ESMTP id iBSKSYKT093261; Tue, 28 Dec 2004 21:28:34 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.12.11/8.12.11/Submit) id iBSKSYIb093260; Tue, 28 Dec 2004 21:28:34 +0100 (CET) (envelope-from ticso) Date: Tue, 28 Dec 2004 21:28:33 +0100 From: Bernd Walter To: John Birrell Message-ID: <20041228202832.GN81585@cicely12.cicely.de> References: <20041228010938.GA39686@freebsd3.cimlogic.com.au> <41D0C63F.3000702@elischer.org> <20041228025836.GA53223@freebsd3.cimlogic.com.au> <20041228152212.GM81585@cicely12.cicely.de> <20041228195436.GA61668@freebsd3.cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041228195436.GA61668@freebsd3.cimlogic.com.au> X-Operating-System: FreeBSD cicely12.cicely.de 5.2-CURRENT alpha User-Agent: Mutt/1.5.6i X-Spam-Status: No, hits=-4.9 required=3.0 tests=BAYES_00 autolearn=ham version=2.64 X-Spam-Report: * -4.9 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on cicely12.cicely.de cc: usb@freebsd.org cc: ticso@cicely.de cc: Julian Elischer Subject: Re: USB problems X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ticso@cicely.de List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2004 20:29:34 -0000 On Wed, Dec 29, 2004 at 06:54:36AM +1100, John Birrell wrote: > On Tue, Dec 28, 2004 at 04:22:13PM +0100, Bernd Walter wrote: > > Why is the quirk required? > > OK - you get a stall on control endpoint, but this shouldn't harm > > anything, as stalls on control enpoints are automatically cleared on > > the next setup phase and the Philips controllers do that on their own. > > If you get in trouble then the firmware on the device does more wrong > > than just stalling the endpoint. > > The quirk gets around the problem that FreeBSD turns the stall status > of the control endpoint into an error which aborts any further processing. Well, getting a stall on control endpoint is an error, but getting an error on string descriptors shouldn't stop further processing. > The string descriptors are returned normally by the device, except for the > fact that it sets the stall bit on the control endpoint. Here is the device broken, unless FreeBSD's request is not correct. > (If the handling of the stall status is changed, the quirk wouldn't be > necessary) Acording to your description things are not handled very well in both the device and FreeBSD. > > IIRC some USB2.0 firmware stall the control enpoint after transfering > > legal data if they have been asked in an USB1.1 format. > > I think we had this a while back for high speed hubs. > > The firmware in this device doesn't test the format. It unconditionally > stalls the control endpoint in many cases (like getting a device or > configuration descriptor and requesting less bytes than the full > descriptor; getting a string descriptor; getting configuration; getting > status). The device shouldn't stall on requesting partial descriptors. IIRC FreeBSD changed the way how descriptors are fetched normaly in that it doesn't trust the size fields anymore and asks for more data than required. > > Maybe there are broken comments left, but a stalled control endpoint > > doesn't require any special handling other than taken this a an error. > > In usbd_do_request_flags_pipe() there is code that detects a stalled > control endpoint and then tries to clear the stall. In the case of the > devices I have, this code just fails because it gets a stall error too. usbd_do_request_flags_pipe() shouldn't clear a stall condition on control endpoints anywhere than possibly in the host controller. It's perfectly legal for a device to refuse an unstall request for the control endpoint. But speaking of usbd_do_request_flags_pipe(), I don't see anything wrong here - it tries to unstall in case of a received stall for unstalling broken devices. The unstall itself gets a stall too for most devices, but that is ignored and shouldn't harm. > The FreeBSD code *never* takes into account that the control endpoint > stall will be cleared with the next setup packet. Maybe the host controller needs any kind of unstall mimic, but not the device. The question is more what happens with further requests after that error. > I think that a control endpoint transfer should not return USBD_STALLED > to the caller unless the length received is less than that requested > and ~SHORT_TRANSER_OK. A stall on the control endpoint should only be an > error if the controller has a problem with the protocol (i.e. it is > a protocol stall, not a device stall); I had something like this localy running (cut & paste'd): Index: usbdi.c =================================================================== RCS file: /home/ncvs/src/sys/dev/usb/usbdi.c,v retrieving revision 1.76 diff -u -r1.76 usbdi.c --- usbdi.c 26 May 2002 22:00:06 -0000 1.76 +++ usbdi.c 15 Jun 2003 21:32:34 -0000 @@ -931,8 +931,17 @@ usbd_do_request_flags(usbd_device_handle dev, usb_device_request_t *req, void *data, u_int16_t flags, int *actlen, u_int32_t timo) { - return (usbd_do_request_flags_pipe(dev, dev->default_pipe, req, - data, flags, actlen, timo)); + int actlen2; + usbd_status ret; + + ret = usbd_do_request_flags_pipe(dev, dev->default_pipe, req, + data, flags, &actlen2, timo); + if (actlen != NULL) + *actlen = actlen2; + if (ret == USBD_STALLED && actlen2 == UGETW(req->wLength)) { + ret = USBD_NORMAL_COMPLETION; + } + return (ret); } usbd_status But it's wrong. You just don't know if the received data is correct when receiving a stall - especially for requests without data. This is something to hand up to the driver which might have a clue about a specific device brokenness. -- B.Walter BWCT http://www.bwct.de bernd@bwct.de info@bwct.de From owner-freebsd-usb@FreeBSD.ORG Tue Dec 28 21:12:22 2004 Return-Path: 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 0936416A4CE for ; Tue, 28 Dec 2004 21:12:22 +0000 (GMT) Received: from freebsd3.cimlogic.com.au (adsl-20-121.swiftdsl.com.au [218.214.20.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BBC343D2D for ; Tue, 28 Dec 2004 21:12:20 +0000 (GMT) (envelope-from jb@cimlogic.com.au) Received: by freebsd3.cimlogic.com.au (Postfix, from userid 102) id 8C0186AA01; Wed, 29 Dec 2004 08:12:19 +1100 (EST) Date: Wed, 29 Dec 2004 08:12:19 +1100 From: John Birrell To: ticso@cicely.de Message-ID: <20041228211219.GE61668@freebsd3.cimlogic.com.au> References: <20041228010938.GA39686@freebsd3.cimlogic.com.au> <41D0C63F.3000702@elischer.org> <20041228025836.GA53223@freebsd3.cimlogic.com.au> <20041228152212.GM81585@cicely12.cicely.de> <20041228195436.GA61668@freebsd3.cimlogic.com.au> <20041228202832.GN81585@cicely12.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041228202832.GN81585@cicely12.cicely.de> User-Agent: Mutt/1.4.2.1i cc: usb@freebsd.org cc: Julian Elischer Subject: Re: USB problems X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2004 21:12:22 -0000 On Tue, Dec 28, 2004 at 09:28:33PM +0100, Bernd Walter wrote: > Well, getting a stall on control endpoint is an error, but getting an > error on string descriptors shouldn't stop further processing. Windows obviously begs to differ. This reference design comes from the Singapore lab of Philips which I believe also contains the engineers who contributed to the USB specification. The firmware code looks like it was written by an inexperienced hardware engineer. It is only provided as an example by Philips. They intend you to write your own when you build your own board. I will do that when I get the ability to burn 8051 code. In the meantime, I want FreeBSD's USB implementation to function as well as Windows. That means coming up with an implementation that tolerates the control endpoint being stalled. > > The string descriptors are returned normally by the device, except for the > > fact that it sets the stall bit on the control endpoint. > > Here is the device broken, unless FreeBSD's request is not correct. Windows can talk to it though, so at least it's possible to get around aspects of the device which, I agree, are probably broken. The thing that nags me, though, is that this is a 'reference design' and that means that any company choosing to build an MPEG2 encoder based on Philips' SAA7114, SAA6752 and ISP1581 is going to start with this firmware code and build a product that probably has the same behaviour. Philips only offer support to companies who are planning to by large numbers of chips. That means I'm on my own here. I can't communicate with their engineers in Singapore. I've tried - they won't respond. > The device shouldn't stall on requesting partial descriptors. > IIRC FreeBSD changed the way how descriptors are fetched normaly in > that it doesn't trust the size fields anymore and asks for more data > than required. It also shouldn't stall getting the configuration. Or getting status. But it is coded to do that. > > The FreeBSD code *never* takes into account that the control endpoint > > stall will be cleared with the next setup packet. > > Maybe the host controller needs any kind of unstall mimic, but not the > device. > The question is more what happens with further requests after that > error. Further requests start with a setup packet, so the stall is cleared when that is received. The problem is that FreeBSD gives up on talking to the device because it treats the stall condition as an error. It isn't even possible for FreeBSD to get past the device initialisation because the first 8 bytes of the device descriptor are returned with the stall bit set. At that point, FreeBSD barfs. > > I think that a control endpoint transfer should not return USBD_STALLED > > to the caller unless the length received is less than that requested > > and ~SHORT_TRANSER_OK. A stall on the control endpoint should only be an > > error if the controller has a problem with the protocol (i.e. it is > > a protocol stall, not a device stall); > > I had something like this localy running (cut & paste'd): > Index: usbdi.c > =================================================================== > RCS file: /home/ncvs/src/sys/dev/usb/usbdi.c,v > retrieving revision 1.76 > diff -u -r1.76 usbdi.c > --- usbdi.c 26 May 2002 22:00:06 -0000 1.76 > +++ usbdi.c 15 Jun 2003 21:32:34 -0000 > @@ -931,8 +931,17 @@ > usbd_do_request_flags(usbd_device_handle dev, usb_device_request_t *req, > void *data, u_int16_t flags, int *actlen, u_int32_t timo) > { > - return (usbd_do_request_flags_pipe(dev, dev->default_pipe, req, > - data, flags, actlen, timo)); > + int actlen2; > + usbd_status ret; > + > + ret = usbd_do_request_flags_pipe(dev, dev->default_pipe, req, > + data, flags, &actlen2, timo); > + if (actlen != NULL) > + *actlen = actlen2; > + if (ret == USBD_STALLED && actlen2 == UGETW(req->wLength)) { > + ret = USBD_NORMAL_COMPLETION; > + } > + return (ret); > } > > usbd_status > > But it's wrong. > You just don't know if the received data is correct when receiving > a stall - especially for requests without data. > This is something to hand up to the driver which might have a clue > about a specific device brokenness. A problem with FreeBSD's code is that some of the places where the driver *could* interpret the stall condition differently and actually handled in common routines that are hard-coded to treat the stall as an error. Take the configuration descriptor as an example. The FreeBSD code tries to get the first 9 bytes to discover the wTotalLength, then it goes and gets the full descriptor (including interfaces and endpoints). In the case of this rogue device, the get of the first 9 bytes results in a stall. FreeBSD's code then fails the entire configuration descriptor get and it isn't possible for a driver to configure the device. -- John Birrell From owner-freebsd-usb@FreeBSD.ORG Tue Dec 28 21:52:33 2004 Return-Path: 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 B066216A4D3 for ; Tue, 28 Dec 2004 21:52:33 +0000 (GMT) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id C82C843D31 for ; Tue, 28 Dec 2004 21:52:32 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de (cicely5.cicely.de [IPv6:3ffe:400:8d0:301:200:92ff:fe9b:20e7]) (authenticated bits=0) iBSLqDP8073118 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Tue, 28 Dec 2004 22:52:17 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [IPv6:3ffe:400:8d0:301::12]) by cicely5.cicely.de (8.12.10/8.12.10) with ESMTP id iBSLpJUU061578 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 28 Dec 2004 22:51:20 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.12.11/8.12.11) with ESMTP id iBSLpJax093707; Tue, 28 Dec 2004 22:51:19 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.12.11/8.12.11/Submit) id iBSLpJ34093706; Tue, 28 Dec 2004 22:51:19 +0100 (CET) (envelope-from ticso) Date: Tue, 28 Dec 2004 22:51:19 +0100 From: Bernd Walter To: John Birrell Message-ID: <20041228215118.GO81585@cicely12.cicely.de> References: <20041228010938.GA39686@freebsd3.cimlogic.com.au> <41D0C63F.3000702@elischer.org> <20041228025836.GA53223@freebsd3.cimlogic.com.au> <20041228152212.GM81585@cicely12.cicely.de> <20041228195436.GA61668@freebsd3.cimlogic.com.au> <20041228202832.GN81585@cicely12.cicely.de> <20041228211219.GE61668@freebsd3.cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041228211219.GE61668@freebsd3.cimlogic.com.au> X-Operating-System: FreeBSD cicely12.cicely.de 5.2-CURRENT alpha User-Agent: Mutt/1.5.6i X-Spam-Status: No, hits=-4.9 required=3.0 tests=BAYES_00 autolearn=ham version=2.64 X-Spam-Report: * -4.9 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on cicely12.cicely.de cc: usb@freebsd.org cc: ticso@cicely.de cc: Julian Elischer Subject: Re: USB problems X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ticso@cicely.de List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2004 21:52:33 -0000 On Wed, Dec 29, 2004 at 08:12:19AM +1100, John Birrell wrote: > On Tue, Dec 28, 2004 at 09:28:33PM +0100, Bernd Walter wrote: > > Well, getting a stall on control endpoint is an error, but getting an > > error on string descriptors shouldn't stop further processing. > > Windows obviously begs to differ. This reference design comes from the > Singapore lab of Philips which I believe also contains the engineers > who contributed to the USB specification. I develop hardware with Philips components myself, so I know what you are talking about. The hardware is good, but docs and samples are a mess and full of bugs. > The firmware code looks like it was written by an inexperienced hardware > engineer. It is only provided as an example by Philips. They intend you > to write your own when you build your own board. I will do that when I > get the ability to burn 8051 code. In the meantime, I want FreeBSD's > USB implementation to function as well as Windows. That means coming > up with an implementation that tolerates the control endpoint being > stalled. I prefered not to use Philips code as a starting point for my own hardware. > > > The string descriptors are returned normally by the device, except for the > > > fact that it sets the stall bit on the control endpoint. > > > > Here is the device broken, unless FreeBSD's request is not correct. > > Windows can talk to it though, so at least it's possible to get around > aspects of the device which, I agree, are probably broken. The point is that we use common generic code, while windows does not. > The thing that nags me, though, is that this is a 'reference design' and > that means that any company choosing to build an MPEG2 encoder based > on Philips' SAA7114, SAA6752 and ISP1581 is going to start with this > firmware code and build a product that probably has the same behaviour. > Philips only offer support to companies who are planning to by large > numbers of chips. That means I'm on my own here. I can't communicate > with their engineers in Singapore. I've tried - they won't respond. I understand this problem - I've seen lots of broken firmware in code and it's always a surprise that it runs anywhere. > > The device shouldn't stall on requesting partial descriptors. > > IIRC FreeBSD changed the way how descriptors are fetched normaly in > > that it doesn't trust the size fields anymore and asks for more data > > than required. > > It also shouldn't stall getting the configuration. Or getting status. > But it is coded to do that. Ack. > > > The FreeBSD code *never* takes into account that the control endpoint > > > stall will be cleared with the next setup packet. > > > > Maybe the host controller needs any kind of unstall mimic, but not the > > device. > > The question is more what happens with further requests after that > > error. > > Further requests start with a setup packet, so the stall is cleared when > that is received. The problem is that FreeBSD gives up on talking to the > device because it treats the stall condition as an error. It isn't > even possible for FreeBSD to get past the device initialisation because > the first 8 bytes of the device descriptor are returned with the stall > bit set. At that point, FreeBSD barfs. In the windows world this generic handling is part of the driver code so firmware developers don't even have to think about building compliant devices as long as their driver does the right thing. On the other hand windows is much blown with spread generic code and since each driver does a full port reset it also takes very long for a device to come up. What we really need is some kind of sanity check for stalled answers. One might think that a stall on requesting the device descriptor can't be true, but in this case it's a high speed device why simply just isn't prepared to be asked for 8 bytes. The brokeness in the device is very likely that it expects beeing asked for exactly the length the firmware developer had in mind to get asked for. Many firmware developers forget that fact that an USB device is just a slave and has to do whatever the host wants. They don't think a device as beeing an event handler. > > You just don't know if the received data is correct when receiving > > a stall - especially for requests without data. > > This is something to hand up to the driver which might have a clue > > about a specific device brokenness. > > A problem with FreeBSD's code is that some of the places where the driver > *could* interpret the stall condition differently and actually handled > in common routines that are hard-coded to treat the stall as an error. Agreed, but it's hard to do this in a generic way - a stall is still an error. > Take the configuration descriptor as an example. The FreeBSD code tries > to get the first 9 bytes to discover the wTotalLength, then it goes and > gets the full descriptor (including interfaces and endpoints). In the > case of this rogue device, the get of the first 9 bytes results in a > stall. FreeBSD's code then fails the entire configuration descriptor > get and it isn't possible for a driver to configure the device. I don't know the situation at other places, but in this case we can savely request the full descriptor length for high speed devices. High speed devices are required to have large control pipe sizes. It's very likely that the device behaves differently when running full speed - also asking for partial descriptors is perfectly legal under every condition. -- B.Walter BWCT http://www.bwct.de bernd@bwct.de info@bwct.de From owner-freebsd-usb@FreeBSD.ORG Wed Dec 29 10:45:13 2004 Return-Path: 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 4100816A4DC for ; Wed, 29 Dec 2004 10:45:13 +0000 (GMT) Received: from csmisc91.cs.chalmers.se (csmisc91.cs.chalmers.se [129.16.225.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5FF2043D1F for ; Wed, 29 Dec 2004 10:45:12 +0000 (GMT) (envelope-from lennart@augustsson.net) Received: from [IPv6:::1] (localhost [IPv6:::1])iBQA1Se7001773; Sun, 26 Dec 2004 11:01:30 +0100 (CET) Message-ID: <41CE8BF8.6090003@augustsson.net> Date: Sun, 26 Dec 2004 11:01:28 +0100 From: Lennart Augustsson User-Agent: Mozilla/5.0 (X11; U; NetBSD i386; en-US; rv:1.7.3) Gecko/20041004 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "M. Warner Losh" References: <200412242236.iBOMaig32845@Mail.NOSPAM.DynDNS.dK> <20041224.155218.123609434.imp@bsdimp.com> <200412250207.iBP27mQ40936@Mail.NOSPAM.DynDNS.dK> <20041225.202952.80502292.imp@bsdimp.com> In-Reply-To: <20041225.202952.80502292.imp@bsdimp.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-misuser@remove-NOSPAM-to-reply.NOSPAM.dyndns.dk cc: usb@freebsd.org cc: freebsd-misuser@NOSPAM.dyndns.dk Subject: Re: getting vendor IDs X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 10:45:13 -0000 M. Warner Losh wrote: > Yes. It is better to know and understand where NetBSD uses things > before going off on assumptions. NetBSD uses the strings if the device does not have a working string descriptor (which is determined by a quirk or by the device not supplying a string). The string only has a cosmetic purpose. The string table is only emitted if USBVERBOSE is in effect. It's really a waste to have all the strings present in the table since many devices do have working string descriptors. I've considered having some extra mark in usbdevs on devices that have working string descriptors, thereby avoiding putting them in the table. -- Lennart From owner-freebsd-usb@FreeBSD.ORG Wed Dec 29 10:45:30 2004 Return-Path: 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 3E0F716A4CE for ; Wed, 29 Dec 2004 10:45:30 +0000 (GMT) Received: from csmisc91.cs.chalmers.se (csmisc91.cs.chalmers.se [129.16.225.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9290443D54 for ; Wed, 29 Dec 2004 10:45:29 +0000 (GMT) (envelope-from lennart@augustsson.net) Received: from [IPv6:::1] (localhost [IPv6:::1])iBOAeNbu000366; Fri, 24 Dec 2004 11:40:24 +0100 (CET) Message-ID: <41CBF217.3000708@augustsson.net> Date: Fri, 24 Dec 2004 11:40:23 +0100 From: Lennart Augustsson User-Agent: Mozilla/5.0 (X11; U; NetBSD i386; en-US; rv:1.7.3) Gecko/20041004 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Julian Elischer References: <41CB38A7.5020700@vicor.com> <41CB4BCB.1080708@elischer.org> In-Reply-To: <41CB4BCB.1080708@elischer.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: usb@freebsd.org cc: Matthew Dillon cc: Julian Elischer Subject: Re: USB vendore designations.. X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 10:45:30 -0000 I think the EHCI design has some bad flaws. It was too long since I looked at it, so I can't remember if the ones you mention are problematic. Merry Chrisrmas! -- Lennart Julian Elischer wrote: > > EHCI is almost ok.. except for where it REALLY SUCKS! > > Is there anyone who really understands it? > It seems to me that there is almost no way to remove a pipe's queue from > the > async active schedule without losing information as to whether the > transfers > on it were completed or not. (other than halting the entire async schedule, > removing the queue, and then restarting the async schedule. Similarly, > there doesn't seen to be a really safe way to remove transfer items from > said queue (i,e. cancel/abort them), without losing statet information for > other items on the same queue. > > Anyone with any thoughts on this, speak up! :-) > > > > > From owner-freebsd-usb@FreeBSD.ORG Wed Dec 29 10:45:35 2004 Return-Path: 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 68B8D16A4CF for ; Wed, 29 Dec 2004 10:45:35 +0000 (GMT) Received: from csmisc91.cs.chalmers.se (csmisc91.cs.chalmers.se [129.16.225.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF66D43D45 for ; Wed, 29 Dec 2004 10:45:34 +0000 (GMT) (envelope-from lennart@augustsson.net) Received: from [IPv6:::1] (localhost [IPv6:::1])iBOAXWEd001079; Fri, 24 Dec 2004 11:33:33 +0100 (CET) Message-ID: <41CBF07C.3040108@augustsson.net> Date: Fri, 24 Dec 2004 11:33:32 +0100 From: Lennart Augustsson User-Agent: Mozilla/5.0 (X11; U; NetBSD i386; en-US; rv:1.7.3) Gecko/20041004 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matthew Dillon References: <41CB38A7.5020700@vicor.com> <200412240430.iBO4UVMl050469@apollo.backplane.com> In-Reply-To: <200412240430.iBO4UVMl050469@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: usb@freebsd.org cc: Julian Elischer Subject: Re: USB vendore designations.. X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 10:45:35 -0000 I would nnot consider the expanded definitions as progress. I would not apply the patch. I'm of the old school that thinks that even a few kB are worth saving. :) -- Lennart Matthew Dillon wrote: > :Lennart, Matt, Barry, USB hackers, > : > :On FreeBSD we have added vendor descriptiosn fo teh form > :XYZ electrical corp. > : > :where on NetBSD the same ID may be described as "XYZ" > : > :Is there a reason to go one way or the other? > :I'd rather not be different for no reason, but I'm loath to > :just discard information. > : > :thoughts? > > Well, the expanded definitions could be defined as 'progress', so I'd > probably stick with them and maybe submit a patch back to NetBSD to > bring NetBSD in synch with the better names. > > -Matt > Matthew Dillon > > From owner-freebsd-usb@FreeBSD.ORG Wed Dec 29 10:58:03 2004 Return-Path: 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 4A1F816A4CE for ; Wed, 29 Dec 2004 10:58:03 +0000 (GMT) Received: from 21322530218.direct.eti.at (21322530218.direct.eti.at [213.225.30.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E51D43D31 for ; Wed, 29 Dec 2004 10:58:02 +0000 (GMT) (envelope-from tilman@arved.at) Received: from jim.arved.de (localhost [127.0.0.1])iBTAw00m070835 for ; Wed, 29 Dec 2004 11:58:00 +0100 (CET) (envelope-from tilman@arved.at) Received: (from arved@localhost) by jim.arved.de (8.13.1/8.13.1/Submit) id iBTAw0md070834 for freebsd-usb@FreeBSD.org; Wed, 29 Dec 2004 11:58:00 +0100 (CET) (envelope-from tilman@arved.at) X-Authentication-Warning: jim.arved.de: arved set sender to tilman@arved.at using -f Date: Wed, 29 Dec 2004 11:58:00 +0100 From: Tilman Linneweh To: freebsd-usb@FreeBSD.org Message-ID: <20041229105800.GS687@arved.at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: Latest uaudio commits break Logitech USB Headset X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 10:58:03 -0000 Hi, I just updated to yesterdays CURRENT to try the latest changes to uaudio with my Logitech USB headset. RELENG_4,5 panic if the device is plugged in on boot, but sound works if it is plugged in later. CURRENT now doesn't panic anmyore, but the device doesn't work anymore: Here is an excerpt of the USB/pcm components on my system: uhci0: port 0xb400-0xb41f irq 21 at device 16.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ums0: Logitech USB-PS/2 Mouse M-BA47, rev 1.00/1.10, addr 2, iclass 3/1 ums0: 4 buttons and Z dir. uhci1: port 0xb800-0xb81f irq 21 at device 16.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xc000-0xc01f irq 21 at device 16.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uaudio0: Logitech Logitech USB Headset, rev 1.10/1.13, addr 2 uaudio0: audio rev 1.00 pcm0: on uaudio0 pcm0: chn_init(pcm0:play:0) failed: err = 19 pcm0: pcm_chn_create(ua_chan, 1, 0xffffff003d8ef600) failed pcm0: chn_init(pcm0:record:0) failed: err = 19 pcm0: pcm_chn_create(ua_chan, -1, 0xffffff003d8ef600) failed uhid0: Logitech Logitech USB Headset, rev 1.10/1.13, addr 2, iclass 1/1 uhci3: port 0xc400-0xc41f irq 21 at device 16.3 on pci0 uhci3: [GIANT-LOCKED] usb3: on uhci3 usb3: USB revision 1.0 uhub3: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered ucom0: Prolific Technology PL2303 Serial adapter (ATEN/IOGEAR UC232A), rev 1.10/2.02, addr 2 ehci0: mem 0xcff00000-0xcff000ff irq 21 at device 16.4 on pci0 ehci0: [GIANT-LOCKED] ehci_pci_attach: companion usb0 ehci_pci_attach: companion usb1 ehci_pci_attach: companion usb2 ehci_pci_attach: companion usb3 usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: VIA EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub4: single transaction translator uhub4: 8 ports with 8 removable, self powered pcm1: port 0xc800-0xc8ff irq 22 at device 17.5 on pci0 pcm1: [GIANT-LOCKED] pcm1: ums0: at uhub0 port 1 (addr 2) disconnected ums0: detached uaudio0: at uhub2 port 2 (addr 2) disconnected pcm0: detached uaudio0: detached uhid0: at uhub2 port 2 (addr 2) disconnected uhid0: detached ucom0: at uhub3 port 1 (addr 2) disconnected All threads purged from cuaU0 All threads purged from ttyU0 ucom0: detached ums0: Logitech USB-PS/2 Mouse M-BA47, rev 1.00/1.10, addr 2, iclass 3/1 ums0: 4 buttons and Z dir. ucom0: Prolific Technology PL2303 Serial adapter (ATEN/IOGEAR UC232A), rev 1.10/2.02, addr 2 uaudio0: Logitech Logitech USB Headset, rev 1.10/1.13, addr 2 uaudio0: audio rev 1.00 pcm0: on uaudio0 pcm0: chn_init(pcm0:play:0) failed: err = 19 pcm0: pcm_chn_create(ua_chan, 1, 0xffffff0000e3b500) failed pcm0: chn_init(pcm0:record:0) failed: err = 19 pcm0: pcm_chn_create(ua_chan, -1, 0xffffff0000e3b500) failed uhid0: Logitech Logitech USB Headset, rev 1.10/1.13, addr 2, iclass 1/1 If I disconnect the device and reconnect it, i get the following: uaudio0: at uhub2 port 2 (addr 2) disconnected pcm0: unregister: mixer busy pcm0: unregister: mixer busy uhid0: at uhub2 port 2 (addr 2) disconnected uhid0: detached uaudio1: Logitech Logitech USB Headset, rev 1.10/1.13, addr 2 uaudio1: audio rev 1.00 pcm2: on uaudio1 pcm2: chn_init(pcm2:play:0) failed: err = 19 pcm2: pcm_chn_create(ua_chan, 1, 0xffffff002347a900) failed pcm2: chn_init(pcm2:record:0) failed: err = 19 pcm2: pcm_chn_create(ua_chan, -1, 0xffffff002347a900) failed uhid0: Logitech Logitech USB Headset, rev 1.10/1.13, addr 2, iclass 1/1 regards tilman From owner-freebsd-usb@FreeBSD.ORG Wed Dec 29 17:21:47 2004 Return-Path: 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 A78A716A4CE for ; Wed, 29 Dec 2004 17:21:47 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id C43A643D39 for ; Wed, 29 Dec 2004 17:21:46 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iBTHKWns001072; Wed, 29 Dec 2004 10:20:33 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 29 Dec 2004 10:20:34 -0700 (MST) Message-Id: <20041229.102034.58436835.imp@bsdimp.com> To: lennart@augustsson.net From: "M. Warner Losh" In-Reply-To: <41CBF07C.3040108@augustsson.net> References: <41CB38A7.5020700@vicor.com> <200412240430.iBO4UVMl050469@apollo.backplane.com> <41CBF07C.3040108@augustsson.net> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: usb@freebsd.org cc: dillon@apollo.backplane.com cc: julian@vicor.com Subject: Re: USB vendore designations.. X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 17:21:47 -0000 In message: <41CBF07C.3040108@augustsson.net> Lennart Augustsson writes: [[ NetBSD uses the form Foo and FreeBSD uses Foo Inc or Foo Electric ]] : I would nnot consider the expanded definitions as : progress. I would not apply the patch. I'm of the : old school that thinks that even a few kB are worth : saving. :) I agree. In fact, I'm in the process of merging together the FreeBSD and NetBSD usbdevs and one of the things I'm doing is removing the extranious Inc, Electric, Technologies, etc where FreeBSD and NetBSD conflict. In fact, I've thought about doing the same thing to the NetBSD file where it is inconsistant, but so far haven't asked if that's OK. I'd also thought about merging the FreeBSD vendor/devices into NetBSD, but that's a lot of extra bytes into the table... Warner From owner-freebsd-usb@FreeBSD.ORG Wed Dec 29 18:53:11 2004 Return-Path: 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 A815916A4CE for ; Wed, 29 Dec 2004 18:53:11 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F3B343D5D for ; Wed, 29 Dec 2004 18:53:11 +0000 (GMT) (envelope-from julian@vicor.com) Received: from vicor.com (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id C93A87A403; Wed, 29 Dec 2004 10:53:10 -0800 (PST) Message-ID: <41D2FD16.1060108@vicor.com> Date: Wed, 29 Dec 2004 10:53:10 -0800 From: Julian Elischer Organization: VICOR User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: "M. Warner Losh" References: <41CB38A7.5020700@vicor.com> <200412240430.iBO4UVMl050469@apollo.backplane.com> <41CBF07C.3040108@augustsson.net> <20041229.102034.58436835.imp@bsdimp.com> In-Reply-To: <20041229.102034.58436835.imp@bsdimp.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: usb@freebsd.org cc: dillon@apollo.backplane.com cc: lennart@augustsson.net Subject: Re: USB vendore designations.. X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 18:53:11 -0000 M. Warner Losh wrote: > In message: <41CBF07C.3040108@augustsson.net> > Lennart Augustsson writes: > [[ NetBSD uses the form Foo and FreeBSD uses Foo Inc or Foo Electric ]] > : I would nnot consider the expanded definitions as > : progress. I would not apply the patch. I'm of the > : old school that thinks that even a few kB are worth > : saving. :) > > I agree. In fact, I'm in the process of merging together the FreeBSD > and NetBSD usbdevs and one of the things I'm doing is removing the > extranious Inc, Electric, Technologies, etc where FreeBSD and NetBSD > conflict. > > In fact, I've thought about doing the same thing to the NetBSD file > where it is inconsistant, but so far haven't asked if that's OK. I'd > also thought about merging the FreeBSD vendor/devices into NetBSD, > but that's a lot of extra bytes into the table... there is also the LINUX table. a competent perl hacker could write something to merge that with us too. > > Warner > From owner-freebsd-usb@FreeBSD.ORG Wed Dec 29 18:56:31 2004 Return-Path: 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 7D3D516A4CE for ; Wed, 29 Dec 2004 18:56:31 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F24243D45 for ; Wed, 29 Dec 2004 18:56:31 +0000 (GMT) (envelope-from julian@vicor.com) Received: from vicor.com (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id 1BC977A403; Wed, 29 Dec 2004 10:56:31 -0800 (PST) Message-ID: <41D2FDDE.2010001@vicor.com> Date: Wed, 29 Dec 2004 10:56:30 -0800 From: Julian Elischer Organization: VICOR User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: "M. Warner Losh" References: <41CB38A7.5020700@vicor.com> <200412240430.iBO4UVMl050469@apollo.backplane.com> <41CBF07C.3040108@augustsson.net> <20041229.102034.58436835.imp@bsdimp.com> In-Reply-To: <20041229.102034.58436835.imp@bsdimp.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: usb@freebsd.org cc: dillon@apollo.backplane.com cc: lennart@augustsson.net Subject: Re: USB vendore designations.. X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 18:56:31 -0000 Lennart, I never saw the original to this.. My spam filter must have eaten it.. sorry if I didn't respond. M. Warner Losh wrote: > In message: <41CBF07C.3040108@augustsson.net> > Lennart Augustsson writes: > [[ NetBSD uses the form Foo and FreeBSD uses Foo Inc or Foo Electric ]] > : I would nnot consider the expanded definitions as > : progress. I would not apply the patch. I'm of the > : old school that thinks that even a few kB are worth > : saving. :) > > I agree. In fact, I'm in the process of merging together the FreeBSD > and NetBSD usbdevs and one of the things I'm doing is removing the > extranious Inc, Electric, Technologies, etc where FreeBSD and NetBSD > conflict. > > In fact, I've thought about doing the same thing to the NetBSD file > where it is inconsistant, but so far haven't asked if that's OK. I'd > also thought about merging the FreeBSD vendor/devices into NetBSD, > but that's a lot of extra bytes into the table... > > Warner > From owner-freebsd-usb@FreeBSD.ORG Wed Dec 29 18:57:50 2004 Return-Path: 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 39E7516A4CE for ; Wed, 29 Dec 2004 18:57:50 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id CCFA443D2D for ; Wed, 29 Dec 2004 18:57:49 +0000 (GMT) (envelope-from imp@harmony.village.org) Received: from localhost (localhost [IPv6:::1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iBTIu5aF002011; Wed, 29 Dec 2004 11:56:05 -0700 (MST) (envelope-from imp@harmony.village.org) Date: Wed, 29 Dec 2004 11:56:05 -0700 (MST) Message-Id: <20041229.115605.74748430.imp@harmony.village.org> To: julian@vicor.com From: Warner Losh In-Reply-To: <41D2FD16.1060108@vicor.com> References: <41CBF07C.3040108@augustsson.net> <20041229.102034.58436835.imp@bsdimp.com> <41D2FD16.1060108@vicor.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: usb@freebsd.org cc: dillon@apollo.backplane.com cc: lennart@augustsson.net Subject: Re: USB vendore designations.. X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 18:57:50 -0000 From: Julian Elischer Subject: Re: USB vendore designations.. Date: Wed, 29 Dec 2004 10:53:10 -0800 > > > M. Warner Losh wrote: > > In message: <41CBF07C.3040108@augustsson.net> > > Lennart Augustsson writes: > > [[ NetBSD uses the form Foo and FreeBSD uses Foo Inc or Foo Electric ]] > > : I would nnot consider the expanded definitions as > > : progress. I would not apply the patch. I'm of the > > : old school that thinks that even a few kB are worth > > : saving. :) > > > > I agree. In fact, I'm in the process of merging together the FreeBSD > > and NetBSD usbdevs and one of the things I'm doing is removing the > > extranious Inc, Electric, Technologies, etc where FreeBSD and NetBSD > > conflict. > > > > In fact, I've thought about doing the same thing to the NetBSD file > > where it is inconsistant, but so far haven't asked if that's OK. I'd > > also thought about merging the FreeBSD vendor/devices into NetBSD, > > but that's a lot of extra bytes into the table... > > there is also the LINUX table. > a competent perl hacker could write something to merge that with us too. That would be someone else. The *BSD world should really have one table, and 'contiential drift' has happened in the 5 years or so this table has been out there. Warner From owner-freebsd-usb@FreeBSD.ORG Wed Dec 29 20:04:56 2004 Return-Path: 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 1406C16A4CE for ; Wed, 29 Dec 2004 20:04:55 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id B94C243D58 for ; Wed, 29 Dec 2004 20:04:55 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id 547CC7A403; Wed, 29 Dec 2004 12:04:55 -0800 (PST) Message-ID: <41D30DE6.8030007@elischer.org> Date: Wed, 29 Dec 2004 12:04:54 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: Warner Losh References: <41CBF07C.3040108@augustsson.net> <20041229.102034.58436835.imp@bsdimp.com> <41D2FD16.1060108@vicor.com> <20041229.115605.74748430.imp@harmony.village.org> In-Reply-To: <20041229.115605.74748430.imp@harmony.village.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: usb@freebsd.org cc: dillon@apollo.backplane.com cc: lennart@augustsson.net cc: julian@vicor.com Subject: Re: USB vendore designations.. X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 20:04:56 -0000 Warner Losh wrote: >From: Julian Elischer >Subject: Re: USB vendore designations.. >Date: Wed, 29 Dec 2004 10:53:10 -0800 > > > >>M. Warner Losh wrote: >> >> >>>In message: <41CBF07C.3040108@augustsson.net> >>> Lennart Augustsson writes: >>>[[ NetBSD uses the form Foo and FreeBSD uses Foo Inc or Foo Electric ]] >>>: I would nnot consider the expanded definitions as >>>: progress. I would not apply the patch. I'm of the >>>: old school that thinks that even a few kB are worth >>>: saving. :) >>> >>>I agree. In fact, I'm in the process of merging together the FreeBSD >>>and NetBSD usbdevs and one of the things I'm doing is removing the >>>extranious Inc, Electric, Technologies, etc where FreeBSD and NetBSD >>>conflict. >>> >>>In fact, I've thought about doing the same thing to the NetBSD file >>>where it is inconsistant, but so far haven't asked if that's OK. I'd >>>also thought about merging the FreeBSD vendor/devices into NetBSD, >>>but that's a lot of extra bytes into the table... >>> >>> >>there is also the LINUX table. >>a competent perl hacker could write something to merge that with us too. >> >> > >That would be someone else. The *BSD world should really have one >table, and 'contiential drift' has happened in the 5 years or so this >table has been out there. > so how do we stop further continental drift? Lennart, As the original author of teh USB code, you have a unique perspective here. We have a probelm with our USB code procedures in that we have a desire to maintain compatibility with you, yet we have several people who are doing work on USB (including one who has rewritten parts of the drivers) who do not have a very strong motivation to send NetBSD PRs etc. What is your situation at the moment.. You commented that it has been some time since you were closely working with the EHCI driver. Should we send changes to you for approval, inclusion and re-integration back to FreeBSD? Do you have time for that sort of thing? should we make some person/group of people a USB cabal? I know that I'd like to make lots of simple changes such as adding coments in places where the code gets trickier, but I'm very loath to make the diffs any greater than they are. It is very hard to work on the USB code when there seems to not be a procedure for getting that work put back into the sources. > >Warner >_______________________________________________ >freebsd-usb@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-usb >To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org" > > From owner-freebsd-usb@FreeBSD.ORG Wed Dec 29 20:23:38 2004 Return-Path: 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 6B18216A4CE for ; Wed, 29 Dec 2004 20:23:38 +0000 (GMT) Received: from dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NOSPAM.dyndns.dk (84-72-30-72.dclient.hispeed.ch [84.72.30.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 394FD43D5A for ; Wed, 29 Dec 2004 20:23:36 +0000 (GMT) (envelope-from bounce@NOSPAM.dyndns.dk) Received: from Mail.NOSPAM.DynDNS.dK (ipv6.NOSPAM.dyndns.dk [2002:5448:1e48:0:210:60ff:fe25:f1e5]) (8.11.6/8.11.6-SPAMMERS-DeLiGHt) with ESMTP id iBTKNJe93737 verified NO); Wed, 29 Dec 2004 21:23:23 +0100 (CET) (envelope-from bounce@NOSPAM.dyndns.dk) Received: (from beer@localhost) by Mail.NOSPAM.DynDNS.dK (8.11.6/FNORD) id iBTKNIp93736; Wed, 29 Dec 2004 21:23:18 +0100 (CET) (envelope-from bounce@NOSPAM.dyndns.dk) Date: Wed, 29 Dec 2004 21:23:18 +0100 (CET) Message-Id: <200412292023.iBTKNIp93736@Mail.NOSPAM.DynDNS.dK> X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: beer set sender to bounce@NOSPAM.dyndns.dk using -f X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: Processed from queue /tmp X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: Processed by beer with -C /etc/mail/sendmail.cf-LOCAL From: Barry Bouwsma References: <41CB38A7.5020700@vicor.com> <200412240430.iBO4UVMl050469@apollo.backplane.com> <41CBF07C.3040108@augustsson.net> <20041229.102034.58436835.imp@bsdimp.com> To: freebsd-usb@freebsd.org Mail-Followup-To: freebsd-usb@freebsd.org, lennart@augustsson.net, dillon@apollo.backplane.com cc: dillon@apollo.backplane.com cc: lennart@augustsson.net Subject: Re: USB vendore designations.. X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Barry Bouwsma List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 20:23:38 -0000 [Lennart, your messages are appearing on the FreeBSD list with several days delay, if you didn't know -- but thanks for joining in.] > [[ NetBSD uses the form Foo and FreeBSD uses Foo Inc or Foo Electric ]] > : I would nnot consider the expanded definitions as > : progress. I would not apply the patch. I'm of the > : old school that thinks that even a few kB are worth > : saving. :) > I agree. In fact, I'm in the process of merging together the FreeBSD > and NetBSD usbdevs and one of the things I'm doing is removing the > extranious Inc, Electric, Technologies, etc where FreeBSD and NetBSD > conflict. Are there several of us working to the same goal :-) ? Thanks to the responses of all, I'm also going for the shorter- is-better school, and my work-so-far is available from https://NOSPAM.dyndns.dk/hacks/usbdevs/ (sort by date for latest updates) The files there have been first built with NetBSD-current-GENERIC, then with FreeBSD RELENG_4 LINT. For the latter (taken from my NetBSD work), a few source file changes have been needed (SONYERICSSON -> SUSTEEN and the like) which I should also make available, and I'm building world as I write this. For -current FreeBSD, I'll start a crossbuild in a few days when my 4.x build finishes (slow machine, hey), then update my files. DragonFly should be comparable to FreeBSD at the moment, but don't take my word for it. Your machines are faster than mine, promise. I'll probably make a tarball of all my FreeBSD RELENG_4 hacks available so it doesn't get lost. Real Soon Now. Pick and choose what's useful. I'm not ready to give up on FBSD 4.x yet. This does not include any additions from OpenBSD yet. As it is a work-in-progress, expect changes. > In fact, I've thought about doing the same thing to the NetBSD file > where it is inconsistant, but so far haven't asked if that's OK. I'd See message in netbsd tech-kern a few days ago (also available at http://mail-index.NetBSD.org/tech-kern/2004/12/23/0008.html ) for one developer's input into this. I believe you're safe, particularly after learning the reasons. Shorter is mostly better, in this case. > also thought about merging the FreeBSD vendor/devices into NetBSD, > but that's a lot of extra bytes into the table... Not too many, compared with what's missing from D/FBSD, and as it's used in NetBSD for devices without a driver, probably worth the bytes. Those merges should mostly be in my NetBSD usbdevs at the above URL. (That one builds, unlike the previous one I announced to the netbsd-current list. Oops.) On a completely different matter, unrelated to USB, but related to merging, since some of my code hacks to 4.x involve changes to miidevs, I tried merging in NetBSD's additions as well. Can I assume it's a laudable goal to try to keep text *devs databases consistent between the BSDen? (There seem to be code differences that correct for some MII quirks present in NetBSD but not FBSD, or vice versa, so the merged file isn't as nice, but it was a nice idea, I thought) thanks barry bouwmsa From owner-freebsd-usb@FreeBSD.ORG Wed Dec 29 21:03:51 2004 Return-Path: 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 00D8716A4CE for ; Wed, 29 Dec 2004 21:03:51 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C89043D31 for ; Wed, 29 Dec 2004 21:03:50 +0000 (GMT) (envelope-from imp@harmony.village.org) Received: from localhost (localhost [IPv6:::1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iBTL28Xl003209; Wed, 29 Dec 2004 14:02:08 -0700 (MST) (envelope-from imp@harmony.village.org) Date: Wed, 29 Dec 2004 14:02:08 -0700 (MST) Message-Id: <20041229.140208.104029434.imp@harmony.village.org> To: freebsd-usb@FreeBSD.ORG, dillon@apollo.backplane.com, lennart@augustsson.net From: Warner Losh In-Reply-To: <200412292023.iBTKNIp93736@Mail.NOSPAM.DynDNS.dK> References: <41CBF07C.3040108@augustsson.net> <20041229.102034.58436835.imp@bsdimp.com> <200412292023.iBTKNIp93736@Mail.NOSPAM.DynDNS.dK> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: USB vendore designations.. X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 21:03:51 -0000 From: Barry Bouwsma Subject: Re: USB vendore designations.. Date: Wed, 29 Dec 2004 21:23:18 +0100 (CET) > > [[ NetBSD uses the form Foo and FreeBSD uses Foo Inc or Foo Electric ]] > > : I would nnot consider the expanded definitions as > > : progress. I would not apply the patch. I'm of the > > : old school that thinks that even a few kB are worth > > : saving. :) > > > I agree. In fact, I'm in the process of merging together the FreeBSD > > and NetBSD usbdevs and one of the things I'm doing is removing the > > extranious Inc, Electric, Technologies, etc where FreeBSD and NetBSD > > conflict. > > Are there several of us working to the same goal :-) ? > > Thanks to the responses of all, I'm also going for the shorter- > is-better school, and my work-so-far is available from > https://NOSPAM.dyndns.dk/hacks/usbdevs/ > (sort by date for latest updates) I think that it is going to take sepveral steps to get from here to there. Since I have CVS access to both FreeBSD and NetBSD, I can directly make changes there. Since I prefer smaller, more easily tested patches to one big jumbo patch, I'd like to propose that we harmonize strings first, as much as possible, before going after the name changes. I'd also like to do these in smaller batches so that if there are problems, only small, specific changes can be backed out. I'd also like to merge more predictably. Eg, I'd like to merge the stuff that isn't in FreeBSD into NetBSD and vice versa and then go after the conflicts. Once that's done, do the same for OpenBSD's and DFBSD's usbdevs. This likely will take a couple of iterations, plus vigilance to keep it in shape over time... > This does not include any additions from OpenBSD yet. As it is > a work-in-progress, expect changes. I've had strong encouragement from the OpenBSD folks to adopt their short names. I tend to agree with them... > > In fact, I've thought about doing the same thing to the NetBSD file > > where it is inconsistant, but so far haven't asked if that's OK. I'd > > See message > in netbsd tech-kern a few days ago (also available at > http://mail-index.NetBSD.org/tech-kern/2004/12/23/0008.html ) > for one developer's input into this. I believe you're safe, > particularly after learning the reasons. Shorter is mostly > better, in this case. Yes. Agreed. > > also thought about merging the FreeBSD vendor/devices into NetBSD, > > but that's a lot of extra bytes into the table... > > Not too many, compared with what's missing from D/FBSD, and as it's > used in NetBSD for devices without a driver, probably worth the bytes. Well, only if USBVERBOSE is defined, just like on FreeBSD. > On a completely different matter, unrelated to USB, but related > to merging, since some of my code hacks to 4.x involve changes > to miidevs, I tried merging in NetBSD's additions as well. > Can I assume it's a laudable goal to try to keep text *devs > databases consistent between the BSDen? Generally, yes. specifically for miidevs, pccarddevs and usbdevs. All the other devs aren't common between all the BSDs. Warner From owner-freebsd-usb@FreeBSD.ORG Wed Dec 29 21:17:20 2004 Return-Path: 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 3095D16A4CE for ; Wed, 29 Dec 2004 21:17:20 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15EF143D49 for ; Wed, 29 Dec 2004 21:17:20 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id BC1477A425; Wed, 29 Dec 2004 13:17:19 -0800 (PST) Message-ID: <41D31EDF.50807@elischer.org> Date: Wed, 29 Dec 2004 13:17:19 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: Warner Losh References: <41CBF07C.3040108@augustsson.net> <20041229.102034.58436835.imp@bsdimp.com> <200412292023.iBTKNIp93736@Mail.NOSPAM.DynDNS.dK> <20041229.140208.104029434.imp@harmony.village.org> In-Reply-To: <20041229.140208.104029434.imp@harmony.village.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: dillon@apollo.backplane.com cc: lennart@augustsson.net cc: freebsd-usb@freebsd.org Subject: Re: USB vendore designations.. X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 21:17:20 -0000 Warner Losh wrote: >I've had strong encouragement from the OpenBSD folks to adopt their >short names. I tend to agree with them... > > ok, looks like we have agreement.. smaller is better :-) From owner-freebsd-usb@FreeBSD.ORG Wed Dec 29 21:21:57 2004 Return-Path: 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 DF50A16A4CE; Wed, 29 Dec 2004 21:21:57 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id A694843D5C; Wed, 29 Dec 2004 21:21:57 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id 83F9B7A403; Wed, 29 Dec 2004 13:21:57 -0800 (PST) Message-ID: <41D31FF5.8030803@elischer.org> Date: Wed, 29 Dec 2004 13:21:57 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: Kazuhito HONDA References: <20041229105800.GS687@arved.at> In-Reply-To: <20041229105800.GS687@arved.at> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-usb@freebsd.org Subject: Re: Latest uaudio commits break Logitech USB Headset X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 21:21:58 -0000 Hi, Kazuhito-san, could you look into this? Tilman Linneweh wrote: >Hi, > >I just updated to yesterdays CURRENT to try the latest changes to uaudio >with my Logitech USB headset. >RELENG_4,5 panic if the device is plugged in on boot, but sound works >if it is plugged in later. > >CURRENT now doesn't panic anmyore, but the device doesn't work anymore: > >Here is an excerpt of the USB/pcm components on my system: > >uhci0: port 0xb400-0xb41f irq 21 at device 16.0 on pci0 >uhci0: [GIANT-LOCKED] >usb0: on uhci0 >usb0: USB revision 1.0 >uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 >uhub0: 2 ports with 2 removable, self powered >ums0: Logitech USB-PS/2 Mouse M-BA47, rev 1.00/1.10, addr 2, iclass 3/1 >ums0: 4 buttons and Z dir. >uhci1: port 0xb800-0xb81f irq 21 at device 16.1 on pci0 >uhci1: [GIANT-LOCKED] >usb1: on uhci1 >usb1: USB revision 1.0 >uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 >uhub1: 2 ports with 2 removable, self powered >uhci2: port 0xc000-0xc01f irq 21 at device 16.2 on pci0 >uhci2: [GIANT-LOCKED] >usb2: on uhci2 >usb2: USB revision 1.0 >uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 >uhub2: 2 ports with 2 removable, self powered >uaudio0: Logitech Logitech USB Headset, rev 1.10/1.13, addr 2 >uaudio0: audio rev 1.00 >pcm0: on uaudio0 >pcm0: chn_init(pcm0:play:0) failed: err = 19 >pcm0: pcm_chn_create(ua_chan, 1, 0xffffff003d8ef600) failed >pcm0: chn_init(pcm0:record:0) failed: err = 19 >pcm0: pcm_chn_create(ua_chan, -1, 0xffffff003d8ef600) failed >uhid0: Logitech Logitech USB Headset, rev 1.10/1.13, addr 2, iclass 1/1 >uhci3: port 0xc400-0xc41f irq 21 at device 16.3 on pci0 >uhci3: [GIANT-LOCKED] >usb3: on uhci3 >usb3: USB revision 1.0 >uhub3: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 >uhub3: 2 ports with 2 removable, self powered >ucom0: Prolific Technology PL2303 Serial adapter (ATEN/IOGEAR UC232A), rev 1.10/2.02, addr 2 >ehci0: mem 0xcff00000-0xcff000ff irq 21 at device 16.4 on pci0 >ehci0: [GIANT-LOCKED] >ehci_pci_attach: companion usb0 >ehci_pci_attach: companion usb1 >ehci_pci_attach: companion usb2 >ehci_pci_attach: companion usb3 >usb4: EHCI version 1.0 >usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 >usb4: on ehci0 >usb4: USB revision 2.0 >uhub4: VIA EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 >uhub4: single transaction translator >uhub4: 8 ports with 8 removable, self powered >pcm1: port 0xc800-0xc8ff irq 22 at device 17.5 on pci0 >pcm1: [GIANT-LOCKED] >pcm1: >ums0: at uhub0 port 1 (addr 2) disconnected >ums0: detached >uaudio0: at uhub2 port 2 (addr 2) disconnected >pcm0: detached >uaudio0: detached >uhid0: at uhub2 port 2 (addr 2) disconnected >uhid0: detached >ucom0: at uhub3 port 1 (addr 2) disconnected >All threads purged from cuaU0 >All threads purged from ttyU0 >ucom0: detached >ums0: Logitech USB-PS/2 Mouse M-BA47, rev 1.00/1.10, addr 2, iclass 3/1 >ums0: 4 buttons and Z dir. >ucom0: Prolific Technology PL2303 Serial adapter (ATEN/IOGEAR UC232A), rev 1.10/2.02, addr 2 >uaudio0: Logitech Logitech USB Headset, rev 1.10/1.13, addr 2 >uaudio0: audio rev 1.00 >pcm0: on uaudio0 >pcm0: chn_init(pcm0:play:0) failed: err = 19 >pcm0: pcm_chn_create(ua_chan, 1, 0xffffff0000e3b500) failed >pcm0: chn_init(pcm0:record:0) failed: err = 19 >pcm0: pcm_chn_create(ua_chan, -1, 0xffffff0000e3b500) failed >uhid0: Logitech Logitech USB Headset, rev 1.10/1.13, addr 2, iclass 1/1 > >If I disconnect the device and reconnect it, i get the following: > >uaudio0: at uhub2 port 2 (addr 2) disconnected >pcm0: unregister: mixer busy >pcm0: unregister: mixer busy >uhid0: at uhub2 port 2 (addr 2) disconnected >uhid0: detached >uaudio1: Logitech Logitech USB Headset, rev 1.10/1.13, addr 2 >uaudio1: audio rev 1.00 >pcm2: on uaudio1 >pcm2: chn_init(pcm2:play:0) failed: err = 19 >pcm2: pcm_chn_create(ua_chan, 1, 0xffffff002347a900) failed >pcm2: chn_init(pcm2:record:0) failed: err = 19 >pcm2: pcm_chn_create(ua_chan, -1, 0xffffff002347a900) failed >uhid0: Logitech Logitech USB Headset, rev 1.10/1.13, addr 2, iclass 1/1 > >regards >tilman >_______________________________________________ >freebsd-usb@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-usb >To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org" > > From owner-freebsd-usb@FreeBSD.ORG Thu Dec 30 07:19:56 2004 Return-Path: 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 8787516A4CE for ; Thu, 30 Dec 2004 07:19:56 +0000 (GMT) Received: from dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NOSPAM.dyndns.dk (84-72-30-72.dclient.hispeed.ch [84.72.30.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE16743D48 for ; Thu, 30 Dec 2004 07:19:54 +0000 (GMT) (envelope-from bounce@NOSPAM.dyndns.dk) Received: from Mail.NOSPAM.DynDNS.dK (ipv6.NOSPAM.dyndns.dk [2002:5448:1e48:0:210:60ff:fe25:f1e5]) (8.11.6/8.11.6-SPAMMERS-DeLiGHt) with ESMTP id iBU7Jme06880 verified NO); Thu, 30 Dec 2004 08:19:51 +0100 (CET) (envelope-from bounce@NOSPAM.dyndns.dk) Received: (from beer@localhost) by Mail.NOSPAM.DynDNS.dK (8.11.6/FNORD) id iBU7JlL06874; Thu, 30 Dec 2004 08:19:48 +0100 (CET) (envelope-from bounce@NOSPAM.dyndns.dk) Date: Thu, 30 Dec 2004 08:19:48 +0100 (CET) Message-Id: <200412300719.iBU7JlL06874@Mail.NOSPAM.DynDNS.dK> X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: beer set sender to bounce@NOSPAM.dyndns.dk using -f X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: Processed from queue /tmp X-Authentication-Warning: localhost.newsbastards.org.72.27.172.IN-addr.A: Processed by beer with -C /etc/mail/sendmail.cf-LOCAL From: Barry Bouwsma To: freebsd-usb@freebsd.org References: <41CBF07C.3040108@augustsson.net> <20041229.102034.58436835.imp@bsdimp.com> <200412292023.iBTKNIp93736@Mail.NOSPAM.DynDNS.dK> <20041229.140208.104029434.imp@harmony.village.org> Mail-Followup-To: freebsd-usb@freebsd.org, lennart@augustsson.net, dillon@apollo.backplane.com cc: lennart@augustsson.net Subject: Re: USB vendore designations.. X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Barry Bouwsma List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Dec 2004 07:19:56 -0000 [I can't sent Matt a copy of this directly, so...] On Wed, 29 Dec 2004 14:02:08 -0700 (MST), Warner Losh wrote: > > https://NOSPAM.dyndns.dk/hacks/usbdevs/ > > (sort by date for latest updates) > I think that it is going to take sepveral steps to get from here to > there. Since I have CVS access to both FreeBSD and NetBSD, I can > directly make changes there. Since I prefer smaller, more easily > tested patches to one big jumbo patch, I'd like to propose that we > harmonize strings first, as much as possible, before going after the > name changes. I'd also like to do these in smaller batches so that Okay, here's the status of things, as far as I know: Matt and Julian have merged the D/FBSD differences into -current, so that there's nothing missing between them. Matt, brave soul that he is, merged my untested NetBSD diffs into DFly. Another commit fixed the problems that introduced. Again, my apologies for not having tested things thoroughly on my slow machine. My NetBSD merge-from-D/FBSD is split into a vendors-patch and a devices-patch. There are still problems, which I've corrected in the BUILT-on-netbsd file. I needed to make no source changes on NetBSD yet, as I stuck with that naming (even when in conflict with the USB site info), to make my life easier. I'll return to that later. i386 GENERIC and world is what I built -- not sure if there's a LINT-like target to catch anything else. Then I used that as a basis for the -in-progress-for-freebsd file, but that needs source code changes. 4.x LINT built; world in the depend stage at the moment (75MHz, hey) Source changes not yet cleaned up and made available. I'll attack -current next. Next year. I could regenerate the vendors/devices diffs for addition to NetBSD, if you want to commit that to NetBSD, after review, or you could just diff the BUILT-on-netbsd file and cut the diff in half. I believe this is safe to commit, after I fixed my typos and other bozoisms. I may have added a few comments in this. As NetBSD is somewhat more state-of-the-art here, the majority of catching-up needs to happen in D/FBSD. And OpenBSD. > I'd also like to merge more predictably. Eg, I'd like to merge the > stuff that isn't in FreeBSD into NetBSD and vice versa and then go The first is easy; the second takes more effort. Feel free to take my work-in-progress and start from that. As you see, it's taken two weeks for me to get where I am today, that normal people need maybe two hours. > after the conflicts. Once that's done, do the same for OpenBSD's and > DFBSD's usbdevs. This likely will take a couple of iterations, plus DFly and FreeBSD were roughly identical, so that part's already done with no major breakage. OpenBSD has a bit to offer, although I haven't posted to the OpenBSD list (they bite, don't they?), and the major changes from that are further shortening strings. Another thing to note about my FreeBSD work-in-progress -- as I was bringing my 4.x miidevs file up-to-date against -current and then NetBSD, I noted that NetBSD had adopted an `xx' prefix for miidevs alternate IDs, so I decided to do similar for usbdevs, in the case of the byte-swapped HP id, HP2 => zyHP (`zy' chosen to indicate inadvertent byte-swapping). `xx' for alternate IDs, which probably belong to some other manufacturer that get used in those products. > > to miidevs, I tried merging in NetBSD's additions as well. > > Can I assume it's a laudable goal to try to keep text *devs > > databases consistent between the BSDen? > Generally, yes. specifically for miidevs, pccarddevs and usbdevs. > All the other devs aren't common between all the BSDs. Great. The NetBSD origin of the file is what encouraged me to do this. The differences are rather unpleasant though, and will require me to try and wrap my head around what's going on, so I'll stick with USB code for now. My head hurts enough just looking at the miidevs file without understanding it. If someone with MII-fu wants to look at the differences, I've put the FreeBSD-specific result of my merge up at https://NOSPAM.dyndns.dk/hacks/miidevs/miidevs The usual disclaimer, that I have no clue. I'll try to obtain clue later. 'Twon't be easy. thanks barry bouwsma From owner-freebsd-usb@FreeBSD.ORG Thu Dec 30 17:50:08 2004 Return-Path: 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 CBFBA16A4CE for ; Thu, 30 Dec 2004 17:50:08 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id F414343D1F for ; Thu, 30 Dec 2004 17:50:07 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iBUHlNlx010482; Thu, 30 Dec 2004 10:47:29 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Thu, 30 Dec 2004 10:46:52 -0700 (MST) Message-Id: <20041230.104652.72711160.imp@bsdimp.com> To: freebsd-misuser@dyndns.dk From: "M. Warner Losh" In-Reply-To: <200412300719.iBU7JlL06874@Mail.NOSPAM.DynDNS.dK> References: <200412292023.iBTKNIp93736@Mail.NOSPAM.DynDNS.dK> <20041229.140208.104029434.imp@harmony.village.org> <200412300719.iBU7JlL06874@Mail.NOSPAM.DynDNS.dK> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: lennart@augustsson.net cc: freebsd-usb@freebsd.org Subject: Re: USB vendore designations.. X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Dec 2004 17:50:08 -0000 In message: <200412300719.iBU7JlL06874@Mail.NOSPAM.DynDNS.dK> Barry Bouwsma writes: : [I can't sent Matt a copy of this directly, so...] : : On Wed, 29 Dec 2004 14:02:08 -0700 (MST), Warner Losh wrote: : : > > https://NOSPAM.dyndns.dk/hacks/usbdevs/ : > > (sort by date for latest updates) : : > I think that it is going to take sepveral steps to get from here to : > there. Since I have CVS access to both FreeBSD and NetBSD, I can : > directly make changes there. Since I prefer smaller, more easily : > tested patches to one big jumbo patch, I'd like to propose that we : > harmonize strings first, as much as possible, before going after the : > name changes. I'd also like to do these in smaller batches so that : : Okay, here's the status of things, as far as I know: : : Matt and Julian have merged the D/FBSD differences into -current, so : that there's nothing missing between them. This isn't true. Julian committed a huge diff, it failed, he backed it out. I've committed parts of the non conflicting stuff, and will continue to do so cautiously. : As NetBSD is somewhat more state-of-the-art here, the majority of : catching-up needs to happen in D/FBSD. And OpenBSD. Actually, that's not entirely true either. FreeBSD had a boatload of vendors not in NetBSD, and there's general agreement that the OpenBSD shortness of names is a good thing. : > I'd also like to merge more predictably. Eg, I'd like to merge the : > stuff that isn't in FreeBSD into NetBSD and vice versa and then go : : The first is easy; the second takes more effort. Feel free to : take my work-in-progress and start from that. As you see, it's : taken two weeks for me to get where I am today, that normal : people need maybe two hours. I did the first round of merging in about an hour, along with the merge backs to NetBSD. My big worry is breaking things on NetBSD when I merge back things there, so I really want to be cautious and do things very carefully. Warner From owner-freebsd-usb@FreeBSD.ORG Thu Dec 30 18:55:50 2004 Return-Path: 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 2204516A4CE for ; Thu, 30 Dec 2004 18:55:50 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id D3D3843D31 for ; Thu, 30 Dec 2004 18:55:49 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id F01077A403; Thu, 30 Dec 2004 10:55:48 -0800 (PST) Message-ID: <41D44F34.8070005@elischer.org> Date: Thu, 30 Dec 2004 10:55:48 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: "M. Warner Losh" References: <200412292023.iBTKNIp93736@Mail.NOSPAM.DynDNS.dK> <20041229.140208.104029434.imp@harmony.village.org> <200412300719.iBU7JlL06874@Mail.NOSPAM.DynDNS.dK> <20041230.104652.72711160.imp@bsdimp.com> In-Reply-To: <20041230.104652.72711160.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-misuser@dyndns.dk cc: lennart@augustsson.net cc: freebsd-usb@freebsd.org Subject: Re: USB vendore designations.. X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Dec 2004 18:55:50 -0000 M. Warner Losh wrote: > >This isn't true. Julian committed a huge diff, it failed, he backed >it out. I've committed parts of the non conflicting stuff, and will >continue to do so cautiously. > Actually that's not quite true.. I made two commits.. one , very small that added items from Dragonfly that were not in freeBSD already. That one was ok. the large one that I reverted was stuff from NetBSD. Dragonfly actually committed it and fixed it. > >: As NetBSD is somewhat more state-of-the-art here, the majority of >: catching-up needs to happen in D/FBSD. And OpenBSD. > >Actually, that's not entirely true either. FreeBSD had a boatload of >vendors not in NetBSD, and there's general agreement that the OpenBSD >shortness of names is a good thing. > yes, in looking at the merge, there are more new IDs going from FreeBSD -> netBSD than visa versa. From owner-freebsd-usb@FreeBSD.ORG Thu Dec 30 19:17:49 2004 Return-Path: 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 9C49F16A4CE; Thu, 30 Dec 2004 19:17:49 +0000 (GMT) Received: from moek.pir.net (moek.pir.net [130.64.1.215]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2637C43D41; Thu, 30 Dec 2004 19:17:49 +0000 (GMT) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 1Ck5nw-0002zM-Dc ; Thu, 30 Dec 2004 14:17:48 -0500 Date: Thu, 30 Dec 2004 14:17:48 -0500 From: Peter Radcliffe To: freebsd-stable@freebsd.org Message-ID: <20041230191748.GA11051@pir.net> Mail-Followup-To: freebsd-stable@freebsd.org, freebsd-usb@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2i X-fish: < cc: freebsd-usb@freebsd.org Subject: USB flash not working anymore X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-stable@freebsd.org, freebsd-usb@freebsd.org, pir@pir.net List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Dec 2004 19:17:49 -0000 I'm running FreeBSD 4-STABLE from Dec 28 on an IBM X30 laptop. I'm having increasingly worse USB problems as time goes on. Nothing that I try new works and various older devices that I bought specificly because they were supported and worked fine for years now do not work. My SanDisk CF reader (SDDR-31) used to work perfectly, now gives me; umass0: SanDisk Corporation ImageMate CompactFlash USB, rev 1.10/0.09, addr 2 umass0: Get Max Lun not supported (STALLED) usb_block_allocmem: in interrupt context, size=4096 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-2 device da0: 650KB/s transfers da0: 489MB (1001953 512 byte sectors: 64H 32S/T 489C) here I try to mount hte filesystem or use mtools; usb_block_allocmem: in interrupt context, size=4096 usb_block_allocmem: in interrupt context, size=4096 usb_block_allocmem: in interrupt context, size=4096 usb_block_allocmem: in interrupt context, size=65536 usb_block_allocmem: in interrupt context, failed umass0: BBB reset failed, STALLED usb_block_allocmem: in interrupt context, size=65536 usb_block_allocmem: in interrupt context, failed umass0: BBB reset failed, STALLED usb_block_allocmem: in interrupt context, size=65536 usb_block_allocmem: in interrupt context, failed umass0: BBB reset failed, STALLED and it hangs. Sometimes the process hangs, sometimes the machine hangs. My crucial gizmo flashdrive gives me; umass0: Crucial Gizmo, rev 2.00/0.01, addr 2 usb_block_allocmem: in interrupt context, size=4096 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-CCS device da0: 650KB/s transfers da0: 123MB (251904 512 byte sectors: 64H 32S/T 123C) [mount the drive] usb_block_allocmem: in interrupt context, size=4096 usb_block_allocmem: in interrupt context, size=4096 [repeated about 30 times] usb_block_allocmem: in interrupt context, size=4096 usb_block_allocmem: in interrupt context, size=4096 umass0: at uhub1 port 1 (addr 2) disconnected (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry umass0: detached This at least works when mounted but mtools will hang hard. The Iomega mini flashdrive hard hung my machine so I have no logs. Anyone seen these problems before or working on usb in 4.x ? I'll do what I can to help debugging... Thanks, P. -- pir From owner-freebsd-usb@FreeBSD.ORG Thu Dec 30 22:17:31 2004 Return-Path: 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 82DE916A4CE; Thu, 30 Dec 2004 22:17:31 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65F1443D1D; Thu, 30 Dec 2004 22:17:31 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id 56E0C7A425; Thu, 30 Dec 2004 14:17:31 -0800 (PST) Message-ID: <41D47E7B.4070407@elischer.org> Date: Thu, 30 Dec 2004 14:17:31 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: freebsd-stable@freebsd.org, freebsd-usb@freebsd.org, pir@pir.net References: <20041230191748.GA11051@pir.net> In-Reply-To: <20041230191748.GA11051@pir.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: USB flash not working anymore X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Dec 2004 22:17:31 -0000 Peter Radcliffe wrote: >I'm running FreeBSD 4-STABLE from Dec 28 on an IBM X30 laptop. > >I'm having increasingly worse USB problems as time goes on. Nothing >that I try new works and various older devices that I bought >specificly because they were supported and worked fine for years now >do not work. > >[...] > > usb_block_allocmem: in interrupt context, size=4096 > > >Anyone seen these problems before or working on usb in 4.x ? I'll do >what I can to help debugging... > this means exactly what it sounds like... something in the usb system tried to allocate memory while in an interrupt context. I don't see what USB controller you have. OHCI or UHCI (or EHCI). > >Thanks, >P. > > > From owner-freebsd-usb@FreeBSD.ORG Thu Dec 30 22:20:42 2004 Return-Path: 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 9423F16A4CE; Thu, 30 Dec 2004 22:20:42 +0000 (GMT) Received: from moek.pir.net (moek.pir.net [130.64.1.215]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B80243D41; Thu, 30 Dec 2004 22:20:42 +0000 (GMT) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 1Ck8ev-0004X2-Ld ; Thu, 30 Dec 2004 17:20:41 -0500 Date: Thu, 30 Dec 2004 17:20:41 -0500 From: Peter Radcliffe To: Julian Elischer Message-ID: <20041230222041.GG11051@pir.net> Mail-Followup-To: Julian Elischer , freebsd-stable@freebsd.org, freebsd-usb@freebsd.org References: <20041230191748.GA11051@pir.net> <41D47E7B.4070407@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41D47E7B.4070407@elischer.org> User-Agent: Mutt/1.4.2i X-fish: < X-Copy-On-Listmail: Please do NOT Cc: me on list mail. cc: freebsd-stable@freebsd.org cc: freebsd-usb@freebsd.org Subject: Re: USB flash not working anymore X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-stable@freebsd.org List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Dec 2004 22:20:42 -0000 Julian Elischer probably said: > this means exactly what it sounds like... something in the usb system > tried to allocate memory while in an interrupt context. I don't know anything about the USB subsystem, nor what can or cannot be done while handling an interrupt. > I don't see what USB controller you have. OHCI or UHCI (or EHCI). uhci0: port 0x1800-0x181f irq 11 at device 29.0 on pci0 usb0: on uhci0 uhci1: port 0x1820-0x183f irq 3 at device 29.1 on pci0 usb1: on uhci1 uhci2: port 0x1840-0x185f irq 5 at device 29.2 on pci0 usb2: on uhci2 P. -- pir From owner-freebsd-usb@FreeBSD.ORG Thu Dec 30 22:22:09 2004 Return-Path: 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 03E1716A4CE; Thu, 30 Dec 2004 22:22:09 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79EAE43D31; Thu, 30 Dec 2004 22:22:08 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id 6BE7B7A403; Thu, 30 Dec 2004 14:22:08 -0800 (PST) Message-ID: <41D47F90.1080500@elischer.org> Date: Thu, 30 Dec 2004 14:22:08 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: Tilman Linneweh References: <20041229105800.GS687@arved.at> In-Reply-To: <20041229105800.GS687@arved.at> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-usb@freebsd.org Subject: Re: Latest uaudio commits break Logitech USB Headset X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Dec 2004 22:22:09 -0000 Tilman Linneweh wrote: >Hi, > >I just updated to yesterdays CURRENT to try the latest changes to uaudio >with my Logitech USB headset. >RELENG_4,5 panic if the device is plugged in on boot, but sound works >if it is plugged in later. > >CURRENT now doesn't panic anmyore, but the device doesn't work anymore: > >Here is an excerpt of the USB/pcm components on my system: > >uhci0: port 0xb400-0xb41f irq 21 at device 16.0 on pci0 >uhci0: [GIANT-LOCKED] >usb0: on uhci0 >usb0: USB revision 1.0 >uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 >uhub0: 2 ports with 2 removable, self powered >ums0: Logitech USB-PS/2 Mouse M-BA47, rev 1.00/1.10, addr 2, iclass 3/1 >ums0: 4 buttons and Z dir. >uhci1: port 0xb800-0xb81f irq 21 at device 16.1 on pci0 >uhci1: [GIANT-LOCKED] >usb1: on uhci1 >usb1: USB revision 1.0 >uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 >uhub1: 2 ports with 2 removable, self powered >uhci2: port 0xc000-0xc01f irq 21 at device 16.2 on pci0 >uhci2: [GIANT-LOCKED] >usb2: on uhci2 >usb2: USB revision 1.0 >uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 >uhub2: 2 ports with 2 removable, self powered >uaudio0: Logitech Logitech USB Headset, rev 1.10/1.13, addr 2 >uaudio0: audio rev 1.00 >pcm0: on uaudio0 >pcm0: chn_init(pcm0:play:0) failed: err = 19 >pcm0: pcm_chn_create(ua_chan, 1, 0xffffff003d8ef600) failed >pcm0: chn_init(pcm0:record:0) failed: err = 19 >pcm0: pcm_chn_create(ua_chan, -1, 0xffffff003d8ef600) failed >uhid0: Logitech Logitech USB Headset, rev 1.10/1.13, addr 2, iclass 1/1 >uhci3: port 0xc400-0xc41f irq 21 at device 16.3 on pci0 >uhci3: [GIANT-LOCKED] >usb3: on uhci3 >usb3: USB revision 1.0 >uhub3: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 >uhub3: 2 ports with 2 removable, self powered >ucom0: Prolific Technology PL2303 Serial adapter (ATEN/IOGEAR UC232A), rev 1.10/2.02, addr 2 >ehci0: mem 0xcff00000-0xcff000ff irq 21 at device 16.4 on pci0 >ehci0: [GIANT-LOCKED] >ehci_pci_attach: companion usb0 >ehci_pci_attach: companion usb1 >ehci_pci_attach: companion usb2 >ehci_pci_attach: companion usb3 >usb4: EHCI version 1.0 >usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 >usb4: on ehci0 >usb4: USB revision 2.0 >uhub4: VIA EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 >uhub4: single transaction translator >uhub4: 8 ports with 8 removable, self powered >pcm1: port 0xc800-0xc8ff irq 22 at device 17.5 on pci0 >pcm1: [GIANT-LOCKED] >pcm1: >ums0: at uhub0 port 1 (addr 2) disconnected >ums0: detached >uaudio0: at uhub2 port 2 (addr 2) disconnected >pcm0: detached >uaudio0: detached >uhid0: at uhub2 port 2 (addr 2) disconnected >uhid0: detached >ucom0: at uhub3 port 1 (addr 2) disconnected >All threads purged from cuaU0 >All threads purged from ttyU0 >ucom0: detached >ums0: Logitech USB-PS/2 Mouse M-BA47, rev 1.00/1.10, addr 2, iclass 3/1 >ums0: 4 buttons and Z dir. >ucom0: Prolific Technology PL2303 Serial adapter (ATEN/IOGEAR UC232A), rev 1.10/2.02, addr 2 >uaudio0: Logitech Logitech USB Headset, rev 1.10/1.13, addr 2 >uaudio0: audio rev 1.00 >pcm0: on uaudio0 >pcm0: chn_init(pcm0:play:0) failed: err = 19 >pcm0: pcm_chn_create(ua_chan, 1, 0xffffff0000e3b500) failed >pcm0: chn_init(pcm0:record:0) failed: err = 19 >pcm0: pcm_chn_create(ua_chan, -1, 0xffffff0000e3b500) failed >uhid0: Logitech Logitech USB Headset, rev 1.10/1.13, addr 2, iclass 1/1 > >If I disconnect the device and reconnect it, i get the following: > >uaudio0: at uhub2 port 2 (addr 2) disconnected >pcm0: unregister: mixer busy >pcm0: unregister: mixer busy >uhid0: at uhub2 port 2 (addr 2) disconnected >uhid0: detached >uaudio1: Logitech Logitech USB Headset, rev 1.10/1.13, addr 2 >uaudio1: audio rev 1.00 >pcm2: on uaudio1 >pcm2: chn_init(pcm2:play:0) failed: err = 19 >pcm2: pcm_chn_create(ua_chan, 1, 0xffffff002347a900) failed >pcm2: chn_init(pcm2:record:0) failed: err = 19 >pcm2: pcm_chn_create(ua_chan, -1, 0xffffff002347a900) failed >uhid0: Logitech Logitech USB Headset, rev 1.10/1.13, addr 2, iclass 1/1 > can you try the following patch? (apply by hand) --- patch begins here --- --- src/sys/dev/sound/usb/uaudio_pcm.c.orig Sun Oct 31 02:56:01 2004 +++ src/sys/dev/sound/usb/uaudio_pcm.c Thu Dec 9 04:21:10 2004 @@ -58,7 +58,7 @@ static struct pcmchan_caps ua_reccaps = {8000, 48000, ua_recfmt, 0}; -#define UAUDIO_PCM_BUFF_SIZE 16*1024 +#define UAUDIO_PCM_BUFF_SIZE (16*1024-1) /************************************************************/ static void * --- patch ends here --- > >regards >tilman >_______________________________________________ >freebsd-usb@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-usb >To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org" > > From owner-freebsd-usb@FreeBSD.ORG Thu Dec 30 23:18:12 2004 Return-Path: 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 5C4D516A4CE; Thu, 30 Dec 2004 23:18:12 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3FB9743D31; Thu, 30 Dec 2004 23:18:12 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id 29D127A403; Thu, 30 Dec 2004 15:18:12 -0800 (PST) Message-ID: <41D48CB3.6070001@elischer.org> Date: Thu, 30 Dec 2004 15:18:11 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <20041230191748.GA11051@pir.net> <41D47E7B.4070407@elischer.org> <20041230222041.GG11051@pir.net> In-Reply-To: <20041230222041.GG11051@pir.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-usb@freebsd.org Subject: Re: USB flash not working anymore X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Dec 2004 23:18:12 -0000 Peter Radcliffe wrote: >Julian Elischer probably said: > > >>this means exactly what it sounds like... something in the usb system >>tried to allocate memory while in an interrupt context. >> >> do you have access to anything with an EHCI or OHCI controller for comparison with that device? >I don't know anything about the USB subsystem, nor what can or cannot >be done while handling an interrupt. > > > >>I don't see what USB controller you have. OHCI or UHCI (or EHCI). >> >> > >uhci0: port 0x1800-0x181f > irq 11 at device 29.0 on pci0 >usb0: on uhci0 >uhci1: port 0x1820-0x183f > irq 3 at device 29.1 on pci0 >usb1: on uhci1 >uhci2: port 0x1840-0x185f > irq 5 at device 29.2 on pci0 >usb2: on uhci2 > >P. > > > From owner-freebsd-usb@FreeBSD.ORG Fri Dec 31 02:31:14 2004 Return-Path: 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 9F52216A4CE; Fri, 31 Dec 2004 02:31:14 +0000 (GMT) Received: from moek.pir.net (moek.pir.net [130.64.1.215]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3686443D39; Fri, 31 Dec 2004 02:31:14 +0000 (GMT) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 1CkCZN-0006HV-EK ; Thu, 30 Dec 2004 21:31:13 -0500 Date: Thu, 30 Dec 2004 21:31:13 -0500 From: Peter Radcliffe To: Julian Elischer Message-ID: <20041231023113.GJ11051@pir.net> Mail-Followup-To: Julian Elischer , freebsd-stable@freebsd.org, freebsd-usb@freebsd.org References: <20041230191748.GA11051@pir.net> <41D47E7B.4070407@elischer.org> <20041230222041.GG11051@pir.net> <41D48CB3.6070001@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41D48CB3.6070001@elischer.org> User-Agent: Mutt/1.4.2i X-fish: < X-Copy-On-Listmail: Please do NOT Cc: me on list mail. cc: freebsd-stable@freebsd.org cc: freebsd-usb@freebsd.org Subject: Re: USB flash not working anymore X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-stable@freebsd.org List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Dec 2004 02:31:14 -0000 Julian Elischer probably said: > do you have access to anything with an EHCI or OHCI controller for > comparison with that device? My (now usually windows only) amd64 desktop box has ohci, but it doesn't have any ethernet devices that 4 has support for (5 does, apparently) so I can't easily give direct logs. Booting i386 FreeBSD from an old partition taken to 4-STABLE from earlier this month shows that the SanDisk CF redaer works fine with mtools to read from (when I try to write to it I get lots of umass0: BBB reset failed, STALLED) and the Iomega micro mini thumbdrive also works fine with mtools for read/write. The crucial gizmo does not work at all, I get a umass0 message, a disconnection and then detatch message and then another "umass0: Crucial Gizmo, rev 2.00/0.01, addr" message and nothing else, no da0; can't re-use a leaf (minimum_cmd_size)! umass0: at uhub1 port 4 (addr 2) disconnected (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry umass0: detached umass0: Crucial Gizmo, rev 2.00/0.01, addr 2 umass0: at uhub1 port 4 (addr 2) disconnected umass0: detached umass0: Crucial Gizmo, rev 2.00/0.01, addr 2 Shortly after removing the Gizmo the machine page faulted in kernel mode and crashed. After enabling crashdumps I tried this again and the gizmo as the first device worked; umass0: Crucial Gizmo, rev 2.00/0.01, addr 2 umass0: at uhub1 port 4 (addr 2) disconnected da0 at umass-sim0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-CCS device da0: 650KB/s transfers da0: 123MB (251904 512 byte sectors: 64H 32S/T 123C) (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry umass0: detached umass0: Crucial Gizmo, rev 2.00/0.01, addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-CCS device da0: 650KB/s transfers da0: 123MB (251904 512 byte sectors: 64H 32S/T 123C) can't re-use a leaf (minimum_cmd_size)! then I got a panic: ohci_abort_xfer: not in process context and a very big crashdump; IdlePTD at physical address 0x003ef000 initial pcb at physical address 0x00346b20 panicstr: ohci_abort_xfer: not in process context panic messages: --- panic: ohci_abort_xfer: not in process context syncing disks... done Uptime: 4m35s (kgdb) bt #0 0xc018b9aa in dumpsys () #1 0xc018b77b in boot () #2 0xc018bba0 in poweroff_wait () #3 0xc0246760 in ohci_abort_xfer () #4 0xc024641f in ohci_timeout_task () #5 0xc024a101 in usb_task_thread () Further down the rabbit hole, I build a kernel.debug and try to copy things over to a flash drive to get them to another machine; umass0: SanDisk Corporation ImageMate CompactFlash USB, rev 1.10/0.09, addr 2 umass0: Get Max Lun not supported (STALLED) da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-2 device da0: 650KB/s transfers da0: 489MB (1001953 512 byte sectors: 64H 32S/T 489C) umass0: BBB reset failed, STALLED umass0: Invalid CSW: tag 96 should be 97 umass0: BBB reset failed, STALLED umass0: Invalid CSW: tag 97 should be 98 [lots of these pairs] umass0: Invalid CSW: tag 150 should be 151 umass0: BBB reset failed, STALLED (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0 umass0: Invalid CSW: tag 151 should be 152 umass0: BBB reset failed, STALLED umass0: BBB reset failed, STALLED umass0: BBB reset failed, STALLED umass0: Invalid CSW: tag 234 should be 235 umass0: BBB reset failed, STALLED [lots more of these pairs] umass0: Invalid CSW: tag 235 should be 236 umass0: BBB reset failed, STALLED umass0: BBB reset failed, STALLED (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0 umass0: Invalid CSW: tag 248 should be 250 umass0: BBB reset failed, STALLED umass0: BBB reset failed, STALLED umass0: BBB reset failed, STALLED This didn't crash the machine, at least. Trying to reprovoke the crash it seems to only fail with a panic from one pair of usb ports, the rest work better. I get another page fault in kernel mode and it dumps; IdlePTD at physical address 0x003ec000 initial pcb at physical address 0x00346b20 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x4c fault code = supervisor read, page not present instruction pointer = 0x8:0xc024b23e stack pointer = 0x10:0xe1d91f30 frame pointer = 0x10:0xe1d91f44 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 4 (usbtask) interrupt mask = bio trap number = 12 panic: page fault syncing disks... 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 giving up on 1 buffers Uptime: 7m9s (kgdb) bt #0 0xc018b9aa in dumpsys () #1 0xc018b77b in boot () #2 0xc018bba0 in poweroff_wait () #3 0xc02a5f7a in trap_fatal () #4 0xc02a5c4d in trap_pfault () #5 0xc02a5837 in trap () #6 0xc024b23e in usb_transfer_complete () #7 0xc0246817 in ohci_abort_xfer () #8 0xc024641f in ohci_timeout_task () #9 0xc024a101 in usb_task_thread () That help any ? P. -- pir From owner-freebsd-usb@FreeBSD.ORG Fri Dec 31 09:24:15 2004 Return-Path: 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 8058C16A4CE for ; Fri, 31 Dec 2004 09:24:15 +0000 (GMT) Received: from zed.bpsw.biz (zed.bpsw.biz [67.18.135.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42FD743D1F for ; Fri, 31 Dec 2004 09:24:15 +0000 (GMT) (envelope-from lists@bridgeportsoftware.com) Received: from fez.bpsw.biz (unknown [10.0.1.3]) by zed.bpsw.biz (Postfix) with ESMTP id D6A9958AA for ; Fri, 31 Dec 2004 01:20:07 -0800 (PST) Received: from [10.0.1.53] (gigante.bpsw.biz [10.0.1.53]) by fez.bpsw.biz (Postfix) with ESMTP id 5DBA33E8845 for ; Fri, 31 Dec 2004 01:24:13 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v619) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; format=flowed To: freebsd-usb@freebsd.org From: Max Campos Date: Fri, 31 Dec 2004 01:24:12 -0800 X-Mailer: Apple Mail (2.619) Subject: ukbd & Console Scrollback X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Dec 2004 09:24:15 -0000 Hi, I have an Apple Pro USB Keyboard, but for the life of me I cannot get the system console scrollback to work (ie. scroll lock, then pgup/pg down). I'm running CURRENT, though I also had this problem under 5.3-p2. The Apple Pro Keyboard has no Scroll-lock key (instead it has F13/F14/F15 where SysRq/Scrl Lock/Pause would be), but I looked online and I _believe_ the F14 key has the same scancode as scroll lock. A few questions: 1) Does this work for anyone? (ie. is this a problem with all USB keyboards?) 2) Is there a way to find out what scan code is being emitted when I hit a certain key? 3) If (1) isn't the case, any idea how to get this working? I suppose I could create a layout that redefines scroll lock to a different key, or correct the keymap if the F14 scancode != scrl lock. What fun. Thanks for your help. - Max From owner-freebsd-usb@FreeBSD.ORG Fri Dec 31 12:28:38 2004 Return-Path: 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 1B52916A4CE for ; Fri, 31 Dec 2004 12:28:38 +0000 (GMT) Received: from 21322530218.direct.eti.at (21322530218.direct.eti.at [213.225.30.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1621F43D31 for ; Fri, 31 Dec 2004 12:28:36 +0000 (GMT) (envelope-from tilman@arved.at) Received: from jim.arved.de (localhost [127.0.0.1])iBVCSNco090644; Fri, 31 Dec 2004 13:28:23 +0100 (CET) (envelope-from tilman@arved.at) Received: (from arved@localhost) by jim.arved.de (8.13.1/8.13.1/Submit) id iBVCSILk090643; Fri, 31 Dec 2004 13:28:18 +0100 (CET) (envelope-from tilman@arved.at) X-Authentication-Warning: jim.arved.de: arved set sender to tilman@arved.at using -f Date: Fri, 31 Dec 2004 13:28:17 +0100 From: Tilman Linneweh To: Julian Elischer Message-ID: <20041231122817.GT687@arved.at> References: <20041229105800.GS687@arved.at> <41D47F90.1080500@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41D47F90.1080500@elischer.org> User-Agent: Mutt/1.4.2.1i cc: freebsd-usb@freebsd.org Subject: Re: Latest uaudio commits break Logitech USB Headset X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Dec 2004 12:28:38 -0000 * Julian Elischer [2004-12-30 23:22]: > > >pcm0: on uaudio0 > >pcm0: chn_init(pcm0:play:0) failed: err = 19 > >pcm0: pcm_chn_create(ua_chan, 1, 0xffffff003d8ef600) failed > >pcm0: chn_init(pcm0:record:0) failed: err = 19 > >pcm0: pcm_chn_create(ua_chan, -1, 0xffffff003d8ef600) failed > >uhid0: Logitech Logitech USB Headset, rev 1.10/1.13, addr 2, iclass 1/1 > can you try the following patch? > (apply by hand) > > --- patch begins here --- > --- src/sys/dev/sound/usb/uaudio_pcm.c.orig Sun Oct 31 02:56:01 2004 > +++ src/sys/dev/sound/usb/uaudio_pcm.c Thu Dec 9 04:21:10 2004 > > @@ -58,7 +58,7 @@ > > static struct pcmchan_caps ua_reccaps = {8000, 48000, ua_recfmt, 0}; > > -#define UAUDIO_PCM_BUFF_SIZE 16*1024 > +#define UAUDIO_PCM_BUFF_SIZE (16*1024-1) > > /************************************************************/ > static void * > --- patch ends here --- Thanks a lot! Playback now works again. Please commit! uaudio0: Logitech Logitech USB Headset, rev 1.10/1.13, addr 2 uaudio0: audio rev 1.00 pcm0: on uaudio0 Recording, as far as I remember never worked with the device. With CURRENT+your patch, recording results in a kernel panic: pcm0:record:0: record interrupt timeout, channel dead pcm0:record:0: record interrupt timeout, channel dead kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode fault virtual address = 0x48 fault code = supervisor read, page not present instruction pointer = 0x8:0xffffffff802c7f57 stack pointer = 0x10:0xffffffffa5200b10 frame pointer = 0x10:0xffffffffa5200b50 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = resume, IOPL = 0 current process = 33 (irq22: pcm1) ^^^^^^^ huh? Unfortunately kgdb does not like the dump. regards tilman