From: Martin Herrman <martin.herrman@gmail.com>
To: linux-media@vger.kernel.org
Subject: Re: Cine CT V6.1 code change request
Date: Wed, 15 Feb 2017 20:20:58 +0100 [thread overview]
Message-ID: <CADR1r6gvOXYpz2Qa5HnuSYmyz9pv6e9-tbRQ6PgtK8pqWWHo6A@mail.gmail.com> (raw)
In-Reply-To: <572edbb2-a542-01a7-9ba0-20cee18a3217@xs4all.nl>
2017-02-15 8:55 GMT+01:00 Hans Verkuil <hverkuil@xs4all.nl>:
Hi Hans,
Thanks for the quick response!
> I'm not sure what this media_build directory is. It certainly is
> outdated. The latest media_build is here: https://git.linuxtv.org/media_build.git/
And thanks for sharing!
> Can you show that line and the surrounding lines? I.e. the whole menu
> entry?
Of course, here it is:
if STAGING
menu "Media devices in staging"
config STAGING_BROKEN
bool "Enable drivers that are known to not compile"
default n
--- help ---
Say N here, except if you will be fixing the drivers
compilation.
menuconfig STAGING_MEDIA
> Most likely because the media build you use is outdated.
I cloned the latest repository and build it, all went fine, however.. (read on)
> Which driver?
This is my device:
02:00.0 Multimedia controller: Digital Devices GmbH Octopus DVB Adapter
Subsystem: Digital Devices GmbH Cine CT V6.1 DVB adapter
Flags: bus master, fast devsel, latency 0, IRQ 32
Memory at fbcf0000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [50] Power Management version 3
Capabilities: [70] MSI: Enable+ Count=1/2 Maskable- 64bit+
Capabilities: [90] Express Endpoint, MSI 00
Capabilities: [100] Vendor Specific Information: ID=0000 Rev=0 Len=00c <?>
Kernel driver in use: ddbridge
Kernel modules: ddbridge
I am using the following modules:
[htpc@htpc ~]$ lsmod | grep dd
tda18212dd 20480 2
stv0367dd 24576 2
ddbridge 90112 29
cxd2099 20480 1 ddbridge
dvb_core 102400 1 ddbridge
The ddbridge and cxd2099 are in the latest media_build, but the
stv0367dd and tda18212dd are missing (however, the stv0367 and
tda18212 are available). How hard is it to add these two?
Regards,
Martin
> Regards,
>
> Hans
>
next prev parent reply other threads:[~2017-02-15 19:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 20:59 Cine CT V6.1 code change request Martin Herrman
2017-02-15 7:55 ` Hans Verkuil
2017-02-15 19:20 ` Martin Herrman [this message]
2017-02-19 13:27 ` Daniel Scheller
2017-02-21 19:13 ` Martin Herrman
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=CADR1r6gvOXYpz2Qa5HnuSYmyz9pv6e9-tbRQ6PgtK8pqWWHo6A@mail.gmail.com \
--to=martin.herrman@gmail.com \
--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.