From owner-freebsd-usb@FreeBSD.ORG Sun Jun 8 21:09:38 2008 Return-Path: Delivered-To: FreeBSD-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 101C9106566C; Sun, 8 Jun 2008 21:09:38 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe02.swip.net [212.247.154.33]) by mx1.freebsd.org (Postfix) with ESMTP id B03818FC20; Sun, 8 Jun 2008 21:09:36 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=UlUzKLwsL7l1WSYqPADo3w==:17 a=OjL5efmLpeUuAzQxxMQA:9 a=LqE2GmgLi8lQSo1KvhwA:7 a=Qw_YYm2e8Jokuysy-0mJSCIgbrsA:4 a=LY0hPdMaydYA:10 Received: from [62.113.132.30] (account mc467741@c2i.net [62.113.132.30] verified) by mailfe02.swip.net (CommuniGate Pro SMTP 5.1.13) with ESMTPA id 969261740; Sun, 08 Jun 2008 23:09:26 +0200 From: Hans Petter Selasky To: Chuck Robey Date: Sun, 8 Jun 2008 23:10:55 +0200 User-Agent: KMail/1.9.7 References: <484BEE1C.8040903@telenix.org> <200806082132.51357.hselasky@c2i.net> <484C46D6.6050908@telenix.org> In-Reply-To: <484C46D6.6050908@telenix.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200806082310.56920.hselasky@c2i.net> Cc: markus@freebsd.org, FreeBSD USB List Subject: Re: final usb question X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jun 2008 21:09:38 -0000 On Sunday 08 June 2008, Chuck Robey wrote: > Hans Petter Selasky wrote: > > Hi Chuck, > > > > On Sunday 08 June 2008, Chuck Robey wrote: > >> Hans, this is the big question, requires more thought, so if you don't > >> have enough time on hand, give this a skip for a while. I'm CC'ing this > >> to the FreeBSD-USB list, it's conceivable that I might get lucky there, > >> too. > >> > >> This replaces my last usb question, because (even though I think the > >> answer to that one confirms the utter insanity of the people who wrote > >> the USB-HID spec), I have absolute confirmation of the fact that I > >> cannot, in situations where the report descriptor has multiple sections > >> ID'd by multiple report IDs, force the USB peripheral to send me the > >> report ID that makes the best sense, and I must be satisfied with > >> whatever the device sends me. That's ridiculous, but I wrote down the > >> reference, just so I could look back at it and confirm to myself that I > >> wasn't dreaming any of this. > >> > >> As a better illustration of that, my tablet has report IDs 7, 8, and 9. > >> ID# 7 is the only one that matches well, but the device manufacturer has > >> set it up to respond ONLY with report ID# 9. If I _could_ change that, > >> I surely would, and I spent a LOT of time investigating until I > >> absolutely found hard confirmation of the fact that I can't. If you get > >> lucky and have a mfr sending all of the report ID's, you then can toss > >> out the ones you don't like, but if they only send one (as in my case), > >> well, you're screwed. What a stupid spec! > > > > You mean if you can set another USB configuration ? > > That's what I'm saying SHOULD be possible, but it isn't. There will soon be a utility that can do this, so that you can run: usbconfig -u ugen0 -c 1 for example to select configuration index 1 for your device. Please note that there will be one ugen device for every USB device present in the future! And I'm in the future :-) --HPS