From: Tony Houghton <h@realh.co.uk>
To: linux-media@vger.kernel.org
Subject: TBS 6920 remote
Date: Fri, 3 Feb 2012 17:12:50 +0000 [thread overview]
Message-ID: <20120203171250.52278c25@junior> (raw)
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:
I: Bus=0019 Vendor=0000 Product=0006 Version=0000
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0A03:00/device:12/LNXVIDEO:00/input/input5
U: Uniq=
H: Handlers=kbd event5
B: PROP=0
B: EV=3
B: KEY=3e000b00000000 0 0 0
And lspci -v:
03:00.0 Multimedia video controller: Conexant Systems, Inc. CX23885 PCI Video and Audio Decoder (rev 02)
Subsystem: Device 6920:8888
Flags: bus master, fast devsel, latency 0, IRQ 19
Memory at fea00000 (64-bit, non-prefetchable) [size=2M]
Capabilities: [40] Express Endpoint, MSI 00
Capabilities: [80] Power Management version 2
Capabilities: [90] Vital Product Data
Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [100] Advanced Error Reporting
Capabilities: [200] Virtual Channel
Kernel driver in use: cx23885
Is there an extra module I need to load to make it work, or is any work
being done on this if it isn't supported yet? Is there anything I can do
to help? I'm an experienced C programmer, but not a kernel hacker.
next reply other threads:[~2012-02-03 17:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 17:12 Tony Houghton [this message]
2012-02-03 17:28 ` TBS 6920 remote Simon Jones
2012-02-05 18:52 ` Tony Houghton
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=20120203171250.52278c25@junior \
--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 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.