From: "Michal Malý" <madcatxster@devoid-pointer.net>
To: Jiri Kosina <jkosina@suse.cz>
Cc: "simon@mungewell.org" <simon@mungewell.org>,
linux-input <linux-input@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
edwin@velds.nl, "elias.vds@gmail.com" <elias.vds@gmail.com>,
Roland Bosa <rbosa@logitech.com>
Subject: Re: PATCH hid: Implement mode switching on Logitech gaming wheels accordingly to the documentation
Date: Tue, 12 Aug 2014 16:02:53 +0200 [thread overview]
Message-ID: <4338127.9nsJWYLUyM@sigyn> (raw)
In-Reply-To: <alpine.LNX.2.00.1408121509550.15220@pobox.suse.cz>
On Tuesday 12 of August 2014 15:10:12 Jiri Kosina wrote:
> On Thu, 31 Jul 2014, simon@mungewell.org wrote:
> > > +#define LG4FF_MSW_MIN 0
> > > +#define LG4FF_MSW_NATIVE 0 /* Switch device to its native mode (if
> > > applicable) */
> > > +#define LG4FF_MSW_DONTSWITCH 1 /* Leave device in its current mode */
> > > +#define LG4FF_MSW_DFP 2 /* Switch device so that it emulates
Driving
> > > Force Pro (only G25, G27, DFGT) */
> > > +#define LG4FF_MSW_G25 3 /* Switch device so that it emulates G25
(only
> > > G27) */
> > > +#define LG4FF_MSW_MAX 3
> >
> > Just to let everyone know I am looking at this patch, and have emailed
> > Michal some questions on whether it covers all options for control.
>
> Hi guys,
>
> did you reach any kind of conclusion here?
Hi,
Simon mailed me his revised patchset which has the changes broken out into
four separate patches and allows to switch "extended compatibility" modes on
the fly through sysfs. I looked them over and I they seem fine to me. I
suppose he'll submit them for review very soon.
Michal
next prev parent reply other threads:[~2014-08-12 14:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 10:10 PATCH hid: Implement mode switching on Logitech gaming wheels accordingly to the documentation Michal Malý
2014-07-31 9:20 ` Elias Vanderstuyft
2014-07-31 17:29 ` simon
2014-08-12 13:10 ` Jiri Kosina
2014-08-12 14:02 ` Michal Malý [this message]
2014-08-14 16:30 ` simon
2014-08-21 4:55 ` simon
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=4338127.9nsJWYLUyM@sigyn \
--to=madcatxster@devoid-pointer.net \
--cc=edwin@velds.nl \
--cc=elias.vds@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rbosa@logitech.com \
--cc=simon@mungewell.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 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).