From: Daniel Scheller <d.scheller.oss@gmail.com>
To: Philipp Hahn <pmhahn+video@pmhahn.de>, linux-media@vger.kernel.org
Cc: rjkm@metzlerbros.de
Subject: Re: [PATCH RESEND 00/14] ddbridge: bump to ddbridge-0.9.29
Date: Tue, 25 Jul 2017 17:42:27 +0200 [thread overview]
Message-ID: <20170725174227.325ecfb7@audiostation.wuest.de> (raw)
In-Reply-To: <57b893dc-d54f-0293-1874-b3606bb811c1@pmhahn.de>
Am Tue, 25 Jul 2017 07:36:12 +0200
schrieb Philipp Hahn <pmhahn+video@pmhahn.de>:
> > Stripped functionality compared to dddvb:
> >
> > - DVB-C modulator card support removed (requires DVB core API)
>
> Since I'm in DVB-C land, what is required to get that working as well?
> I only know myself around in general Linux Kernel land and I'm not a
> DVB expert, but if there is anything I can help with, please send me
> a note. (I only have one ddbridge system, which is running my
> "production" MythTV system, so testing is limited to the times were
> my house does not need it).
When speaking of MythTV and "regular" tuner cards, there's nothing you
need to do in this regard, DVB-C/C2/T/T2 tunercard support for all
currently available DD hardware is done already and merged into
linux-media. With modulator cards, these ([1]) are meant, used to set
up private cable networks, fed by ie. streams received via DVB-S.
[1] https://digitaldevices.de/produkte/modulatoren/
Best regards,
Daniel Scheller
--
https://github.com/herrnst
prev parent reply other threads:[~2017-07-25 15:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-23 18:16 [PATCH RESEND 00/14] ddbridge: bump to ddbridge-0.9.29 Daniel Scheller
2017-07-23 18:16 ` [PATCH RESEND 01/14] [media] ddbridge: move/reorder functions Daniel Scheller
2017-07-23 18:16 ` [PATCH RESEND 02/14] [media] ddbridge: split code into multiple files Daniel Scheller
2017-07-27 22:11 ` kbuild test robot
2017-07-23 18:16 ` [PATCH RESEND 03/14] [media] ddbridge: bump ddbridge code to version 0.9.29 Daniel Scheller
2017-07-27 23:02 ` kbuild test robot
2017-07-23 18:16 ` [PATCH RESEND 04/14] [media] ddbridge: split I/O related functions off from ddbridge.h Daniel Scheller
2017-07-23 18:16 ` [PATCH RESEND 05/14] [media] ddbridge: split off IRQ handling Daniel Scheller
2017-07-23 18:16 ` [PATCH RESEND 06/14] [media] ddbridge: split off hardware definitions and mappings Daniel Scheller
2017-07-23 18:16 ` [PATCH RESEND 07/14] [media] ddbridge: check pointers before dereferencing Daniel Scheller
2017-07-23 18:16 ` [PATCH RESEND 08/14] [media] ddbridge: only register frontends in fe2 if fe is not NULL Daniel Scheller
2017-07-23 18:16 ` [PATCH RESEND 09/14] [media] ddbridge: fix possible buffer overflow in ddb_ports_init() Daniel Scheller
2017-07-23 18:16 ` [PATCH RESEND 10/14] [media] ddbridge: remove unreachable code Daniel Scheller
2017-07-23 18:16 ` [PATCH RESEND 11/14] [media] ddbridge: fix impossible condition warning Daniel Scheller
2017-07-23 18:16 ` [PATCH RESEND 12/14] [media] ddbridge: fix dereference before check Daniel Scheller
2017-07-23 18:16 ` [PATCH RESEND 13/14] [media] ddbridge: Kconfig option to control the MSI modparam default Daniel Scheller
2017-07-23 18:16 ` [PATCH RESEND 14/14] [media] MAINTAINERS: add entry for ddbridge Daniel Scheller
2017-07-25 5:36 ` [PATCH RESEND 00/14] ddbridge: bump to ddbridge-0.9.29 Philipp Hahn
2017-07-25 15:42 ` Daniel Scheller [this message]
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=20170725174227.325ecfb7@audiostation.wuest.de \
--to=d.scheller.oss@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=pmhahn+video@pmhahn.de \
--cc=rjkm@metzlerbros.de \
/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