From: Jiri Kosina <jkosina@suse.cz>
To: Antonio Ospite <ospite@studenti.unina.it>
Cc: "pascal@pabr.org" <pascal@pabr.org>,
linux-input@vger.kernel.org, linux-bluetooth@vger.kernel.org,
Bastien Nocera <hadess@hadess.net>,
Marcel Holtmann <marcel@holtmann.org>,
Alan Ott <alan@signal11.us>
Subject: Re: hidp_output_raw_report, HID_OUTPUT_REPORT and Sixaxis
Date: Fri, 18 Feb 2011 09:45:49 +0100 (CET) [thread overview]
Message-ID: <alpine.LNX.2.00.1102180944590.2160@pobox.suse.cz> (raw)
In-Reply-To: <20110217151931.d7ee7e29.ospite@studenti.unina.it>
On Thu, 17 Feb 2011, Antonio Ospite wrote:
> However, even if my patch gets is, Output reports on the Sixaxis will
> stop working again as soon as someone implements the behavior you are
> suggesting, that is:
> Feature Report -> SET_REPORT on the Control channel
> Output Report -> DATA on the Interrupt channel
>
> So I am going to submit the hidp_output_raw_report() override in
> hid-sony.c as well, does this sound OK?
That makes sense to me.
Could you please repost all the patches that are currently being discussed
are flying around in the air?
I feel I haven't been CCed on all of them, so I don't have the complete
picture.
Thanks,
--
Jiri Kosina
SUSE Labs, Novell Inc.
WARNING: multiple messages have this Message-ID (diff)
From: Jiri Kosina <jkosina-AlSwsSmVLrQ@public.gmane.org>
To: Antonio Ospite
<ospite-aNJ+ML1ZbiP93QAQaVx+gl6hYfS7NtTn@public.gmane.org>
Cc: "pascal-dXI0m6hRz7k@public.gmane.org"
<pascal-dXI0m6hRz7k@public.gmane.org>,
linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-bluetooth-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Bastien Nocera <hadess-0MeiytkfxGOsTnJN9+BGXg@public.gmane.org>,
Marcel Holtmann <marcel-kz+m5ild9QBg9hUCZPvPmw@public.gmane.org>,
Alan Ott <alan-yzvJWuRpmD1zbRFIqnYvSA@public.gmane.org>
Subject: Re: hidp_output_raw_report, HID_OUTPUT_REPORT and Sixaxis
Date: Fri, 18 Feb 2011 09:45:49 +0100 (CET) [thread overview]
Message-ID: <alpine.LNX.2.00.1102180944590.2160@pobox.suse.cz> (raw)
In-Reply-To: <20110217151931.d7ee7e29.ospite-aNJ+ML1ZbiP93QAQaVx+gl6hYfS7NtTn@public.gmane.org>
On Thu, 17 Feb 2011, Antonio Ospite wrote:
> However, even if my patch gets is, Output reports on the Sixaxis will
> stop working again as soon as someone implements the behavior you are
> suggesting, that is:
> Feature Report -> SET_REPORT on the Control channel
> Output Report -> DATA on the Interrupt channel
>
> So I am going to submit the hidp_output_raw_report() override in
> hid-sony.c as well, does this sound OK?
That makes sense to me.
Could you please repost all the patches that are currently being discussed
are flying around in the air?
I feel I haven't been CCed on all of them, so I don't have the complete
picture.
Thanks,
--
Jiri Kosina
SUSE Labs, Novell Inc.
next prev parent reply other threads:[~2011-02-18 8:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 13:54 hidp_output_raw_report, HID_OUTPUT_REPORT and Sixaxis Antonio Ospite
2010-11-30 13:54 ` Antonio Ospite
2010-11-30 14:06 ` Antonio Ospite
2010-11-30 17:40 ` pascal
2010-12-01 21:06 ` Antonio Ospite
2010-12-01 22:40 ` pascal
2011-02-17 14:19 ` Antonio Ospite
2011-02-17 14:19 ` Antonio Ospite
2011-02-18 8:45 ` Jiri Kosina [this message]
2011-02-18 8:45 ` Jiri Kosina
2011-02-20 17:26 ` [PATCH 0/2] Fix sending Output reports to the Sony Sixaxis Antonio Ospite
2011-02-20 17:26 ` [PATCH 1/2] hid-sony.c: Fix sending Output reports to the Sixaxis Antonio Ospite
2011-02-21 12:49 ` Jiri Kosina
2011-02-20 17:26 ` [PATCH 2/2] bt hidp: send Output reports using SET_REPORT on the Control channel Antonio Ospite
2011-02-21 3:45 ` Alan Ott
2011-02-21 3:45 ` Alan Ott
2011-02-21 12:50 ` Jiri Kosina
2011-02-21 21:09 ` Gustavo F. Padovan
2011-02-22 10:09 ` Jiri Kosina
2011-02-22 10:09 ` Jiri Kosina
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=alpine.LNX.2.00.1102180944590.2160@pobox.suse.cz \
--to=jkosina@suse.cz \
--cc=alan@signal11.us \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=ospite@studenti.unina.it \
--cc=pascal@pabr.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.