From: "don@homedns" <don@prince.homedns.org>
To: Robert Schedel <r.schedel@yahoo.de>
Cc: Jiri Kosina <jkosina@suse.cz>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.34-rc7] HID: hid-samsung: add support for Creative Desktop Wireless 6000
Date: Sun, 16 May 2010 13:12:22 +0100 [thread overview]
Message-ID: <4BEFE126.4080606@prince.homedns.org> (raw)
In-Reply-To: <4BEFCA05.8000402@yahoo.de>
On 16/05/10 11:33, Robert Schedel wrote:
> Hello,
>
> On 16.05.2010 02:32, Don Prince wrote:
>
>> Add support for the Creative Desktop Wireless 6000 keyboard/mouse
>> bundle's multimedia buttons which are not currently handled by
>> the default/samsung HID driver.
>>
>> Signed-off-by: Don Prince <dhprince-devel@yahoo.co.uk>
>>
>> ---
>> [...]
>>
> As originator of the "old" 0419:0001 IrDA driver parts had a short look at it:
> - Merging with old code looks OK. Tested with old 0419:0001 (184) device, still functional.
> - 0419:0600 not yet known in usb.ids, might be worth a contribution
> - As you merged in a new device, and for explaining why this handling was added, my suggestion is to adapt the existing comments, e.g.:
>
> /*
> * This driver supports several HID devices:
> *
> * [0419:0001] Samsung IrDA remote controller (reports as Cypress USB Mouse).
> *
> * There are several variants:
> *
> * 1. 184 byte report descriptor
> [...]
> * [0419:0600] Creative Desktop Wireless 6000 keyboard/mouse combo
> *
> * Several key mappings used from the consumer usage page
> * deviate from the USB HUT 1.12 standard.
> */
>
> Of course some HID maintainer should also review it, for general policy.
>
> Regards,
> Robert Schedel
>
>
Ok I'll add some comments and re-submit patch as v2.
Regards
Don Prince
next prev parent reply other threads:[~2010-05-16 12:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-16 0:32 Don Prince
2010-05-16 10:33 ` Robert Schedel
2010-05-16 12:12 ` don@homedns [this message]
2010-05-16 12:25 ` [PATCH 2.6.34-rc7 v2] " Don Prince
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=4BEFE126.4080606@prince.homedns.org \
--to=don@prince.homedns.org \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=r.schedel@yahoo.de \
/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
all inboxes | Powered by JetHome®