From owner-freebsd-usb@FreeBSD.ORG Mon Mar 14 11:21:30 2005 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA9F516A4CE for ; Mon, 14 Mar 2005 11:21:30 +0000 (GMT) Received: from hosea.tallye.com (joel.tallye.com [216.99.199.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A04243D49 for ; Mon, 14 Mar 2005 11:21:30 +0000 (GMT) (envelope-from lorenl@alzatex.com) Received: from hosea.tallye.com (hosea.tallye.com [127.0.0.1]) by hosea.tallye.com (8.12.8/8.12.10) with ESMTP id j2EBLTUQ015256 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 14 Mar 2005 03:21:30 -0800 Received: (from sttng359@localhost) by hosea.tallye.com (8.12.8/8.12.10/Submit) id j2EBLSUB015254 for freebsd-usb@freebsd.org; Mon, 14 Mar 2005 03:21:28 -0800 X-Authentication-Warning: hosea.tallye.com: sttng359 set sender to lorenl@alzatex.com using -f Date: Mon, 14 Mar 2005 03:21:28 -0800 From: "Loren M. Lang" To: freebsd-usb@freebsd.org Message-ID: <20050314112128.GB15137@alzatex.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="QKdGvSO+nmPlgiQ/" Content-Disposition: inline User-Agent: Mutt/1.4.1i X-GPG-Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc X-GPG-Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C Subject: uhid device file format X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Mar 2005 11:21:31 -0000 --QKdGvSO+nmPlgiQ/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I'm curious where the format of data coming in on uhid is. Are there any good documents on this other than the source code. Looking at freebsd.org, I don't see many technical documents describing the usb subsystem. It looks like the first byte is the report id from the hid descriptor, and following that are the bytes from the report. My usb keyboard/mouse combo provides three different reports on uhid0 according to the hid descriptor it provides. One report is a byte long, the other two are 4 bytes long, but each line I read is 10 bytes long. What are the other 5 bytes for? I'm been able to successfully decode the first five bytes and now I can read all the multimedia keys and mouse events so I'm wondering what is left. --=20 I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: CEE1 AAE2 F66C 59B5 34CA C415 6D35 E847 0118 A3D2 =20 --QKdGvSO+nmPlgiQ/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFCNXO4bTXoRwEYo9IRAnJvAJ9yGhisSjorP69lcm8NuegbaLQnFgCdHNG5 fRPdOklin5lWo81m9Og/Qzw= =suTb -----END PGP SIGNATURE----- --QKdGvSO+nmPlgiQ/--