From owner-freebsd-usb@FreeBSD.ORG Fri Apr 8 19:58:29 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 EA06016A4CE for ; Fri, 8 Apr 2005 19:58:29 +0000 (GMT) Received: from smtp.housing.ufl.edu (smtp.housing.ufl.edu [128.227.47.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 103C043D49 for ; Fri, 8 Apr 2005 19:58:29 +0000 (GMT) (envelope-from WillS@housing.ufl.edu) Received: (qmail 61946 invoked by uid 98); 8 Apr 2005 15:58:28 -0400 Received: from WillS@housing.ufl.edu by smtp.housing.ufl.edu by uid 1003 with qmail-scanner-1.20 (spamassassin: 3.0.2. Clear:RC:1(128.227.47.18):. Processed in 0.01462 secs); 08 Apr 2005 19:58:28 -0000 X-Qmail-Scanner-Mail-From: WillS@housing.ufl.edu via smtp.housing.ufl.edu X-Qmail-Scanner: 1.20 (Clear:RC:1(128.227.47.18):. Processed in 0.01462 secs) Received: from bragi.housing.ufl.edu (128.227.47.18) by smtp.housing.ufl.edu with (RC4-MD5 encrypted) SMTP; 8 Apr 2005 15:58:28 -0400 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0 Date: Fri, 8 Apr 2005 15:58:28 -0400 Message-ID: <0E972CEE334BFE4291CD07E056C76ED805A2C657@bragi.housing.ufl.edu> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Please commit fix outlined in PR/63837 Thread-Index: AcU8cx6tM9OG6NemQ8ancN0HgNrxFAAAJEyQ From: "Will Saxon" To: "Warner Losh" cc: usb@FreeBSD.org Subject: RE: Please commit fix outlined in PR/63837 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: Fri, 08 Apr 2005 19:58:30 -0000 > -----Original Message----- > From: Warner Losh [mailto:imp@bsdimp.com] > Sent: Friday, April 08, 2005 3:40 PM > To: Will Saxon > Cc: usb@FreeBSD.org > Subject: Re: Please commit fix outlined in PR/63837 >=20 >=20 > From: "Will Saxon" > Subject: Please commit fix outlined in PR/63837 > Date: Fri, 8 Apr 2005 15:34:14 -0400 >=20 > > Is it possible to get the 1 line fix posted in PR/63837 added=20 > > before 5.4? This has been a problem since before 5.3, the fix is=20 > > trivial and it works fine. > >=20 > > It is kind of annoying to have to edit hid.c every time I cvsup. > >=20 > > This has been asked about before by myself and others... Is there > > a stylistic problem or a planned cleanup that has held this back? > >=20 > > --- /usr/src/sys/dev/usb/hid.c.orig Fri Apr 8 15:26:46 2005 > > +++ /usr/src/sys/dev/usb/hid.c Fri Apr 8 14:55:01 2005 > > @@ -375,7 +375,7 @@ > >=20 > > id =3D 0; > > for (d =3D hid_start_parse(buf, len, 1< > - if (h.report_ID !=3D 0) > > + if (h.report_ID !=3D 0 && !id) > > id =3D h.report_ID; > > hid_end_parse(d); > > size =3D h.loc.pos; >=20 > So this patch just makes report_ID the FIRST id in the item list, > right? Looks like it, although really I haven't the foggiest. I do know that=20 without the patch, the mouse included with my MX Duo doesn't work.=20 With it, the mouse works.=20 Reading through the PR notes, it appears that a) the answer to=20 your question is yes and b) the below patch is more of a hack=20 that makes things work and that 'this seems to be a horrible=20 interface.' That's fine, but the last message on the PR that was NOT a 'hey this=20 works for me too' was mid November. The assertion was that we should=20 try to adopt the solution(s) NetBSD has to fix this and other things,=20 however I don't think that has happened yet. It would just be nice to get an update, it would make editing hid.c less aggravating if I knew for sure it wasn't always going to be this way. I guess I just forget that I have to do it and then I get mad when I've built a new kernel and my mouse stops working :). -Will