Return-Path: Date: Fri, 29 Jan 2010 10:39:59 +0100 (CET) From: Jiri Kosina To: "Gunn, Brian" Cc: Bastien Nocera , Marcel Holtmann , Dmitry Torokhov , linux-input , BlueZ development , Ping Subject: RE: [PATCHes] Implement Bluetooth Wacom tablet's mode change in the kernel In-Reply-To: Message-ID: References: <1263833399.20565.2905.camel@localhost.localdomain> <1263886149.5591.166.camel@localhost.localdomain> <1263897015.20565.3988.camel@localhost.localdomain> <1264037759.1735.5008.camel@localhost.localdomain> <1264719198.29532.3149.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII List-ID: On Thu, 28 Jan 2010, Gunn, Brian wrote: > > > > I sent a new version of the patch, which uses "HIDP_TRANS_SET_REPORT | > > > > HIDP_DATA_RTYPE_FEATURE" for the first byte. Would that work? > > > > > > Actually for my application it doesn't. I use HIDP_TRANS_DATA | > > HIDP_DATA_RTYPE_OUTPUT. > > > > > > Perhaps allowing the user the choice of what do to here is more flexible. > > > > Except that it would mean different code for USB and Bluetooth > > versions... > > So do we need a method of setting which device reports we're sending before writing them? Having separate methods for feature and output reports should be sufficient and general enough, right? -- Jiri Kosina SUSE Labs, Novell Inc.