From: Tony Houghton <h@realh.co.uk>
To: linux-media@vger.kernel.org
Subject: Re: TBS 6920 remote
Date: Sun, 5 Feb 2012 18:52:33 +0000 [thread overview]
Message-ID: <20120205185233.3ca5024a@tiber> (raw)
In-Reply-To: <CAH4Ag-BZ+Csasy=yk5sNt7_Q5maFuxga2PqeXtJrRYvVLa8zzA@mail.gmail.com>
On Fri, 3 Feb 2012 17:28:59 +0000
Simon Jones <sijones2010@gmail.com> wrote:
> On 3 February 2012 17:12, Tony Houghton <h@realh.co.uk> wrote:
> > I've got a TBS 6920 PCI-E DVB-S2 card, which explicitly claims Linux
> > compatibility on the box. It works as a satellite receiver, but I get no
> > response from the remote control (trying to read /dev/input/event5). I
> > think this is its entry in /proc/bus/input/devices:
>
> TBS have there own media tree for their cards, they do not submit the
> drivers upstream for inclusion in the kernel, if you go to the
> manufacturer site you'll get support from their forums. But it has
> been very well known they have issues with remote support.
Thanks. It seems that there was a bug in their driver which prevented
some keys from working, but AFIACT it's fixed now. The code is GPL so is
it just lack of interest/demand that's stopped it from going into the
main kernel?
I think I'll pass on having to maintain a 3rd party driver whenever the
Debian kernel upgrades. The remote is missing some quite important keys
like Play, so they seem to have only considered it for live viewing, not
for PVRs. I'll probably end up buying a separate USB remote or
continuing to use a portable keyboard.
next prev parent reply other threads:[~2012-02-05 18:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 17:12 TBS 6920 remote Tony Houghton
2012-02-03 17:28 ` Simon Jones
2012-02-05 18:52 ` Tony Houghton [this message]
2012-02-06 11:48 ` Simon Jones
2012-02-06 13:35 ` Tony Houghton
2012-02-06 14:25 ` Simon Jones
2012-02-06 16:38 ` Tony Houghton
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=20120205185233.3ca5024a@tiber \
--to=h@realh.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox