From owner-freebsd-usb@FreeBSD.ORG Wed May 14 21:31:17 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 E7332106567C for ; Wed, 14 May 2008 21:31:17 +0000 (UTC) (envelope-from freebsd-usb@dino.sk) Received: from loki.netlab.sk (loki.netlab.sk [84.245.65.11]) by mx1.freebsd.org (Postfix) with ESMTP id 87F048FC0C for ; Wed, 14 May 2008 21:31:17 +0000 (UTC) (envelope-from freebsd-usb@dino.sk) Received: from fox.dino.sk (home.dino.sk [84.245.95.252]) (AUTH: PLAIN milan, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by loki.netlab.sk with esmtp; Wed, 14 May 2008 23:16:30 +0200 id 0002E00A.482B56AE.0000A503 From: Milan Obuch To: freebsd-usb@freebsd.org Date: Wed, 14 May 2008 23:21:07 +0200 User-Agent: KMail/1.9.7 References: <482B4C79.3030100@telenix.org> In-Reply-To: <482B4C79.3030100@telenix.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200805142321.08246.freebsd-usb@dino.sk> Subject: Re: USB HID parser 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: Wed, 14 May 2008 21:31:18 -0000 On Wednesday 14 May 2008, Chuck Robey wrote: > I wrote a parser, and I don't know if anyone might be interested in it. I > didn't write it as something to be used in a driver ... I wrote it as a > learning aid, for someone who's trying to learn that horrible USB HID spec. > It's quite verbose, most especially if you use it in GUI mode (I wrote it > in Python, and it's got a integral Tkinter GUI. In Python mode, it's got > help info available on every output it has, and displays the data it's > parsing in a way taht makes it fairly easy to have the USB HID parser on > your knee, while you slowly step the parser thru the input data. > > The input data, I originally wrote it to use the output of Kai Wang's USB > HID parser/descriptor dumper, but it's more verbose, and (like I said) is > perfectly set up to let you follow the parsing, item by item, from the > orignal hex to the output. > > The Non-GUI is somewhat less verbose, but this is the first time I;ve let > it be seen, and if you think you'd like to see it changed, I'm not against > adding a special mode for a small group of users, even just one user if it > seems like a likely-enough suggestion. > > I called it parsetool. I know that's a fairly dumb name )(there are one or > two projects already oout with that name), come up with a better one, and > I'll gladly use it (if it's not overly silly). > > Write me if you want it, I'll mail it to you, the tarball is fairly small > (even with all those tables, it's only about 25K compressed) and > installation couldn't really get any easier, just make sure you have a > working python of 2.3 or later, with a working Tkinter. > Could you eventually make a port from it and submit it this way? I think it could be usefull for many... Regards, Milan -- Address this mail is sent from is used only for this mailing list. Do not send any messages to it directly as a response, reply only to mailing list. For mail to me personally, use milan in address instead.