From: Sean Young <sean@mess.org>
To: linux-media@vger.kernel.org
Subject: [PATCH 0/7] a800 dvb rc changes
Date: Sat, 2 Sep 2017 12:42:41 +0100 [thread overview]
Message-ID: <cover.1504352252.git.sean@mess.org> (raw)
Various changes to make the a800 dvb adapter work again and to
improve its ir receiver.
Sean Young (7):
media: dvb: i2c transfers over usb cannot be done from stack
media: dvb: a800: port to rc-core
media: rc: avermedia keymap for a800
media: rc: ensure that protocols are enabled for scancode drivers
media: rc: dvb: use dvb device name for rc device
media: rc: if protocols can't be changed, don't be writable
media: rc: include device name in rc udev event
drivers/media/cec/cec-core.c | 1 -
drivers/media/dvb-frontends/dib3000mc.c | 50 ++++++++++++++++-----
drivers/media/dvb-frontends/dvb-pll.c | 21 ++++++---
drivers/media/i2c/ir-kbd-i2c.c | 1 -
drivers/media/rc/keymaps/rc-avermedia-m135a.c | 3 +-
drivers/media/rc/rc-main.c | 33 +++++++++++---
drivers/media/tuners/mt2060.c | 59 +++++++++++++++++++-----
drivers/media/usb/dvb-usb/a800.c | 65 ++++++---------------------
drivers/media/usb/dvb-usb/dvb-usb-remote.c | 2 +-
9 files changed, 145 insertions(+), 90 deletions(-)
--
2.13.5
next reply other threads:[~2017-09-02 11:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-02 11:42 Sean Young [this message]
2017-09-02 11:42 ` [PATCH 1/7] media: dvb: i2c transfers over usb cannot be done from stack Sean Young
2017-09-02 11:42 ` [PATCH 2/7] media: dvb: a800: port to rc-core Sean Young
2017-09-02 11:42 ` [PATCH 3/7] media: rc: avermedia keymap for a800 Sean Young
2017-09-02 11:42 ` [PATCH 4/7] media: rc: ensure that protocols are enabled for scancode drivers Sean Young
2017-09-02 11:42 ` [PATCH 5/7] media: rc: dvb: use dvb device name for rc device Sean Young
2017-09-02 11:42 ` [PATCH 6/7] media: rc: if protocols can't be changed, don't be writable Sean Young
2017-09-02 11:42 ` [PATCH 7/7] media: rc: include device name in rc udev event Sean Young
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=cover.1504352252.git.sean@mess.org \
--to=sean@mess.org \
--cc=linux-media@vger.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 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.