From owner-freebsd-usb@FreeBSD.ORG Thu Mar 8 07:18:30 2012 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8A760106566B for ; Thu, 8 Mar 2012 07:18:30 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe09.c2i.net [212.247.155.2]) by mx1.freebsd.org (Postfix) with ESMTP id 1C6ED8FC15 for ; Thu, 8 Mar 2012 07:18:29 +0000 (UTC) X-T2-Spam-Status: No, hits=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 Received: from [176.74.212.201] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe09.swip.net (CommuniGate Pro SMTP 5.4.2) with ESMTPA id 73955930; Thu, 08 Mar 2012 08:18:28 +0100 From: Hans Petter Selasky To: freebsd-usb@freebsd.org, hartzell@alerce.com Date: Thu, 8 Mar 2012 08:16:55 +0100 User-Agent: KMail/1.13.5 (FreeBSD/8.3-PRERELEASE; KDE/4.4.5; amd64; ; ) References: <20310.51557.331624.617177@gargle.gargle.HOWL> In-Reply-To: <20310.51557.331624.617177@gargle.gargle.HOWL> X-Face: 'mmZ:T{)),Oru^0c+/}w'`gU1$ubmG?lp!=R4Wy\ELYo2)@'UZ24N@ =?iso-8859-1?q?d2+AyewRX=7DmAm=3BYp=0A=09=7CU=5B?=@, _z/([?1bCfM{_"B<.J>mICJCHAzzGHI{y7{%JVz%R~yJHIji`y> =?iso-8859-1?q?Y=7Dk1C4TfysrsUI=0A=09-=25GU9V5=5DiUZF=26nRn9mJ=27=3F=26?=>O MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201203080816.55920.hselasky@c2i.net> Cc: Subject: Re: radioSHARK, libusbhid and 'Device not configured' 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: Thu, 08 Mar 2012 07:18:30 -0000 On Wednesday 07 March 2012 03:35:17 George Hartzell wrote: > here: > > http://shrimp.alerce.com/radioSHARK/usbconfig-output.txt Hi, I see that there are two interrupt endpoints on the HID device. By default the /dev/uhidX will use the control endpoint to transmit the report data. Maybe that isn't supported. Have you tried sending the protocol data on the interrupt OUT endpoint? --HPS