From owner-freebsd-usb@FreeBSD.ORG Tue Jun 17 23:45:26 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 B8FB0106566C for ; Tue, 17 Jun 2008 23:45:26 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe10.swipnet.se [212.247.155.33]) by mx1.freebsd.org (Postfix) with ESMTP id 4B5A58FC12 for ; Tue, 17 Jun 2008 23:45:26 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=6I5d2MoRAAAA:8 a=y1j_YmdPi5X9K6UrknIA:9 a=-Oz_EF7rwxxqIyXj_gwA:7 a=lpIMOWfPDPKg0OBHWBy6XOnaFWcA:4 a=SV7veod9ZcQA:10 a=50e4U0PicR4A:10 Received: from [71.120.223.131] (account mc467741@c2i.net HELO [172.20.100.16]) by mailfe10.swip.net (CommuniGate Pro SMTP 5.2.4b) with ESMTPA id 808015437; Wed, 18 Jun 2008 01:45:24 +0200 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Wed, 18 Jun 2008 01:46:57 +0200 User-Agent: KMail/1.9.7 References: <4857E4D3.2090904@telenix.org> In-Reply-To: <4857E4D3.2090904@telenix.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200806180146.57555.hselasky@c2i.net> Cc: Subject: Re: USB device probing 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: Tue, 17 Jun 2008 23:45:26 -0000 Hi, Can you do a udesc_dump of your troublesome device ? --HPS On Tuesday 17 June 2008, Chuck Robey wrote: > OK, this won't slow me up, but at some point before I finish, I need an > answer to this question. I've written a USB test program, to prove to > myself that I have a firm handle on all of the required USB functions for > my graphic tablet Xorg Xinput driver. It ahs a single problem: my graphic > tablet, and (it seems) all of the many tablets that are OEM copies of mine > (the UC-Logic family of tablets), their report descriptors all have > multiple report ID's defined in their report descriptor. They are, > however, only sending a single report, and it's neither the first, nor the > most logical report ID for them to have decided upon. > > The way I tell right now which one they're sending is because the first 8 > bits of each input report is always set to the report ID. My problem is, I > don't get any input, if the user has just booted the machine, and hasn't > moved the stylus around on the tablet yet. There's nothing in the input > buffer yet. I don't think I can hang the input driver, waiting upon the > first user input, because that stuff is all done in the preInit phase, and > needs to be reported and set up for later parsing. > > Anybody know of any way to sort of goose the tablet, to FORCE an input > report? I don't care a whit about the rest of the fields at this point, > it's prior even to my reading of the report descriptor, so I'm not parsing > the input yet, just trying to probe out the report ID. > > I'd feel really amateurish if I needed just to set a WAG for the report ID. > Hell, I don't even know the universe the report IDs can be set from yet. I > need that first input report. > _______________________________________________ > 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"