From: Anssi Hannula <anssi.hannula@gmail.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: "Łukasz Lubojański" <lukasz@lubojanski.info>,
linux-input@vger.kernel.org
Subject: Re: New Force Feedback device support - GreenAsia 0x12
Date: Fri, 28 Nov 2008 20:27:51 +0200 [thread overview]
Message-ID: <49303827.4050907@gmail.com> (raw)
In-Reply-To: <alpine.LNX.1.10.0811281514210.19853@jikos.suse.cz>
Jiri Kosina wrote:
> On Fri, 28 Nov 2008, Łukasz Lubojański wrote:
>
>>> Could you please rebase your patch on top of current state of Linus'
>>> kernel tree for 2.6.28-rc? Then the code could be reviewed and I'll merge
>>> it through my tree.
>>> For inspiration, you can look into
>>>
>>> drivers/hid/hid-pl.c
>>>
>>> That driver even contains support for some Greenasia device ... (0x0003).
>> I have rewriten the code for 2.6.28-rc6 and after testing and checking
>> it with checkpatch I will send it again.
>
> Great, thanks.
>
>> Anyway I know that pantherlord code is also supporting greenasia devices
>> (first code was also mostly taken from that) - and I'm still don't know
>> if I'm dooing right naming my part "greenasia" - because some people
>> could get confused. It could also happen that someone else will
>> implement other greenasia device and this will make another confusion.
>
> The question is how much the protocol that is used by your device differs
> from the one that is already implemented in hid-pl.c? Would it make sense
> to have these two implementations in the same driver, or is the protocol
> just completely different?
It seems the protocol resembles more the hid-lg2ff one. The differences
are the additional 0xfa 0xfe 0x0 report sent to the device, and the
missing 0xf3 stop command.
Łukasz, I see your code implements both FF_RUMBLE and FF_CONSTANT in the
same way. If the device only supports rumble effects, then you should
only implement FF_RUMBLE.
--
Anssi Hannula
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-11-28 18:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 22:33 New Force Feedback device support - GreenAsia 0x12 Łukasz Lubojański
2008-11-26 23:01 ` Marek Vasut
2008-11-26 23:01 ` Jiri Slaby
2008-11-27 12:41 ` Jiri Kosina
2008-11-28 6:18 ` Łukasz Lubojański
2008-11-28 14:21 ` Jiri Kosina
2008-11-28 18:27 ` Anssi Hannula [this message]
2008-11-28 19:08 ` Łukasz Lubojański
2008-11-29 22:30 ` Jiri Kosina
2008-12-04 20:35 ` Łukasz Lubojański
2008-12-04 20:55 ` Łukasz Lubojański
2008-12-05 18:32 ` Anssi Hannula
2008-12-05 20:49 ` Łukasz Lubojański
2008-12-06 12:08 ` Jiri Slaby
2008-12-06 15:50 ` Anssi Hannula
[not found] ` <alpine.LNX.1.10.0812111610330.21089@jikos.suse.cz>
2008-12-11 19:46 ` Łukasz Lubojański
2008-12-11 21:13 ` 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=49303827.4050907@gmail.com \
--to=anssi.hannula@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=lukasz@lubojanski.info \
/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).