From: Bastien Nocera <hadess@hadess.net>
To: Jiri Kosina <jkosina@suse.cz>
Cc: "Gunn, Brian" <bgunn@solekai.com>,
Marcel Holtmann <marcel@holtmann.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input <linux-input@vger.kernel.org>,
BlueZ development <linux-bluetooth@vger.kernel.org>,
Ping <pinglinux@gmail.com>
Subject: RE: [PATCHes] Implement Bluetooth Wacom tablet's mode change in the kernel
Date: Fri, 29 Jan 2010 13:45:13 +0000 [thread overview]
Message-ID: <1264772713.29532.4943.camel@localhost.localdomain> (raw)
In-Reply-To: <alpine.LRH.2.00.1001291039350.15694@twin.jikos.cz>
On Fri, 2010-01-29 at 10:39 +0100, Jiri Kosina wrote:
> 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?
Most likely, yes. Feature is enough for the 2 devices I provided patches
for. Could you please comment on what you'd like the implementation of
this to look like? This simple bug fix is turning into a lot more
to-and-fro than I would have anticipated.
Cheers
next prev parent reply other threads:[~2010-01-29 13:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 16:49 [PATCHes] Implement Bluetooth Wacom tablet's mode change in the kernel Bastien Nocera
[not found] ` <167e8a331001181144u54cefd15m65a5a63ca8c4c4b6@mail.gmail.com>
2010-01-18 21:35 ` Bastien Nocera
[not found] ` <1263850557.20565.3204.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-01-19 0:19 ` Bastien Nocera
[not found] ` <1263833399.20565.2905.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-01-18 22:01 ` Przemysław Firszt
2010-01-19 7:29 ` Marcel Holtmann
2010-01-19 10:30 ` Bastien Nocera
2010-01-19 14:20 ` Jiri Kosina
2010-01-19 16:36 ` Gunn, Brian
[not found] ` <FE57175CCE23E5419899C1B0CFA26FAD101B5F8B9D-qt6i7J1wJoTyaV9iOGU/das+acoFTUjB@public.gmane.org>
2010-01-19 17:03 ` Bastien Nocera
[not found] ` <1263920596.1816.56.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-01-19 17:05 ` Gunn, Brian
2010-01-19 20:47 ` Gunn, Brian
2010-01-21 1:08 ` Gunn, Brian
2010-01-21 1:35 ` Bastien Nocera
[not found] ` <1264037759.1735.5008.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-01-28 22:33 ` Gunn, Brian
[not found] ` <FE57175CCE23E5419899C1B0CFA26FAD12CDF72C0F-qt6i7J1wJoTyaV9iOGU/das+acoFTUjB@public.gmane.org>
2010-01-28 22:53 ` Bastien Nocera
2010-01-28 22:57 ` Gunn, Brian
2010-01-29 9:39 ` Jiri Kosina
2010-01-29 13:45 ` Bastien Nocera [this message]
2010-01-29 13:53 ` Jiri Kosina
-- strict thread matches above, loose matches on Subject: below --
2010-01-20 11:47 Bastien Nocera
[not found] ` <1263988051.1735.2474.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-01-20 11:52 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1264772713.29532.4943.camel@localhost.localdomain \
--to=hadess@hadess.net \
--cc=bgunn@solekai.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=pinglinux@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).