From: vdr@helmutauer.de
To: "Mauro Carvalho Chehab" <mchehab@kernel.org>
Cc: "Linux Media Mailing List" <linux-media@vger.kernel.org>
Subject: [PATCH] [MEDIA] add device ID to ati remote
Date: Tue, 7 Feb 2017 09:42:47 +0100 [thread overview]
Message-ID: <cfb14339f809faa9b5e40d2fa53f330b.squirrel@helmutauer.de> (raw)
In-Reply-To: <33044ec5031546f79ae9d37565240ed3.squirrel@helmutauer.de>
Author: Helmut Auer <vdr@xxx.de>
Date: Fri Jan 27 19:09:35 2017 +0100
Adding 1 device ID to ati_remote driver.
Signed-off-by: Helmut Auer <vdr@xxx.de>
diff --git a/drivers/media/rc/ati_remote.c b/drivers/media/rc/ati_remote.c
index 0884b7d..83022b1 100644
--- a/drivers/media/rc/ati_remote.c
+++ b/drivers/media/rc/ati_remote.c
@@ -108,6 +108,7 @@
#define NVIDIA_REMOTE_PRODUCT_ID 0x0005
#define MEDION_REMOTE_PRODUCT_ID 0x0006
#define FIREFLY_REMOTE_PRODUCT_ID 0x0008
+#define REYCOM_REMOTE_PRODUCT_ID 0x000c
#define DRIVER_VERSION "2.2.1"
#define DRIVER_AUTHOR "Torrey Hoffman <thoffman@arnor.net>"
@@ -227,6 +228,10 @@ static struct usb_device_id ati_remote_table[] = {
USB_DEVICE(ATI_REMOTE_VENDOR_ID, FIREFLY_REMOTE_PRODUCT_ID),
.driver_info = (unsigned long)&type_firefly
},
+ {
+ USB_DEVICE(ATI_REMOTE_VENDOR_ID, REYCOM_REMOTE_PRODUCT_ID),
+ .driver_info = (unsigned long)&type_firefly
+ },
{} /* Terminating entry */
};
next prev parent reply other threads:[~2017-02-07 8:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 8:06 [patch] [media] mantis_dvb: fix some error codes in mantis_dvb_init() Dan Carpenter
2017-01-27 8:15 ` [patch] [media] add device IDs to ngene vdr
2017-01-27 13:20 ` [PATCH] [MEDIA] " vdr
2017-02-07 8:42 ` vdr [this message]
2017-02-13 13:42 ` [PATCH] [MEDIA] add device ID to ati remote Sean Young
2017-02-13 22:57 ` Helmut Auer
2017-02-14 7:11 ` Helmut Auer
2017-02-14 7:20 ` [PATCH] [MEDIA] add device IDs to ngene driver Helmut Auer
2017-01-27 8:29 ` [patch] [media] mantis_dvb: fix some error codes in mantis_dvb_init() walter harms
2017-01-27 9:46 ` Dan Carpenter
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=cfb14339f809faa9b5e40d2fa53f330b.squirrel@helmutauer.de \
--to=vdr@helmutauer.de \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.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).