From owner-freebsd-usb@FreeBSD.ORG Sat May 22 18:03:28 2010 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 3BE82106566B for ; Sat, 22 May 2010 18:03:28 +0000 (UTC) (envelope-from ee@athyriogames.com) Received: from caprica.sslcatacombnetworking.com (caprica.sslcatacombnetworking.com [70.86.206.218]) by mx1.freebsd.org (Postfix) with ESMTP id 16AF78FC08 for ; Sat, 22 May 2010 18:03:27 +0000 (UTC) Received: from c-71-239-114-115.hsd1.in.comcast.net ([71.239.114.115] helo=laptopv) by caprica.sslcatacombnetworking.com with esmtpa (Exim 4.69) (envelope-from ) id 1OFrxV-0000QT-Rb for freebsd-usb@FreeBSD.org; Sat, 22 May 2010 11:53:58 -0500 From: "Engineering" To: References: <201005181540.o4IFe3m9016461@freefall.freebsd.org> In-Reply-To: <201005181540.o4IFe3m9016461@freefall.freebsd.org> Date: Sat, 22 May 2010 11:53:38 -0500 Message-ID: <00fe01caf9cf$55127560$ff376020$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acr2oGfKB0UG2d4NTh2/wukL6JIyzwDKsySg Content-Language: en-us X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - caprica.sslcatacombnetworking.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - athyriogames.com X-Source: X-Source-Args: X-Source-Dir: Cc: Subject: uhid write EIO 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: Sat, 22 May 2010 18:03:28 -0000 Hello all I am having trouble communicating with a custom HID device using FreeBSD 7.2. Open and read work fine, but write() errors with EIO My code works well with another HID that uses read and feature reports. Oddly enough, my Windows version using ReadFile and WriteFile works perfectly. The device is a simple PIC based IO board. Windows WriteFile uses the interrupt OUT endpoint - does uhid not do the same? I have also tried changing the descriptor so the device shows up as a ugen. In previous (6.2 and 7.0) versions of BSD, I was able to open, read, and write to communicate with the device, but write is failing as a ugen too. I can provide more information, but I thought I'd check if this is appropriate for this list, and if anyone has an idea before I post. Thanks Sam