public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: VDR User <user.vdr@gmail.com>
Cc: Chris Mayo <aklhfex@gmail.com>,
	Markus Heiser <markus.heiser@darmarit.de>,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH 2/2] v4l-utils: fixed dvbv5 vdr format
Date: Tue, 6 Sep 2016 12:47:23 -0300	[thread overview]
Message-ID: <20160906124723.6783fd39@vento.lan> (raw)
In-Reply-To: <CAA7C2qj5ap3PoK2uenF+kqpCrqjO9znR4y5Y7h2UoaENDcT8XA@mail.gmail.com>

Em Tue, 6 Sep 2016 08:16:22 -0700
VDR User <user.vdr@gmail.com> escreveu:

> I can tell you that people do still use VDR-1.6.0-3. It would be
> unwise (and unnecessary) to break backwards compatible, which would be
> grounds for NACK if you ask me. Knowingly causing breakage has always
> been an unpopular thing in the VDR community, and this sounds like
> it's going beyond fixing a small issue to fixing it til it breaks.

Well, the libdvbv5 VDR output support was written aiming VDR version 2.1.6.
I've no idea if it works with VDR 1.6.0. Don't remember if I tested support
for such version when I wrote the code.

Also, as it seems that VDR 1.6.0 was released in 2008, it probably won't
support DVB-T2 (with was added in 2011) and may not support DVB-S2
(added in 2008, but support for DTV_STREAM_ID seems to be added only
in 2012).

So, at least for DVB-T2/DVB-S2, people likely need some version newer
than VDR 1.6.0 for full support. If so, the changes proposed by Markus
and Chris won't be disruptive for 1.6, as they seem to be touching only
on DVB-T2 and DVB-S2 support, right?

Please correct me if I'm wrong.

Thanks,
Mauro

  reply	other threads:[~2016-09-06 15:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-10  9:52 [PATCH 0/2] v4l-utils build instruction and dvbv5 format Markus Heiser
2016-08-10  9:52 ` [PATCH 1/2] v4l-utils: add comments to the build instructions Markus Heiser
2016-08-10  9:52 ` [PATCH 2/2] v4l-utils: fixed dvbv5 vdr format Markus Heiser
2016-08-16  7:10   ` Markus Heiser
2016-08-22  9:53     ` Markus Heiser
2016-08-24 14:49   ` Mauro Carvalho Chehab
2016-08-24 14:52     ` Mauro Carvalho Chehab
2016-09-05 13:13       ` Markus Heiser
2016-09-05 13:25         ` Mauro Carvalho Chehab
2016-09-05 19:01           ` Chris Mayo
2016-09-06  9:41             ` Mauro Carvalho Chehab
2016-09-06 15:16               ` VDR User
2016-09-06 15:47                 ` Mauro Carvalho Chehab [this message]
2016-09-07  9:51                   ` Markus Heiser
2016-09-07 17:59                     ` VDR User
2016-09-08  7:15                       ` Markus Heiser
2016-09-08 15:59                         ` VDR User
2016-09-08 18:33                       ` Mauro Carvalho Chehab
2016-10-17 12:24                     ` [PATCH 0/2] " Markus Heiser
2016-10-17 12:24                       ` [PATCH 1/2] " Markus Heiser
2016-10-17 12:24                       ` [PATCH 2/2] libdvbv5: Improve vdr format output for DVB-T(2) Markus Heiser

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=20160906124723.6783fd39@vento.lan \
    --to=mchehab@s-opensource.com \
    --cc=aklhfex@gmail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=markus.heiser@darmarit.de \
    --cc=user.vdr@gmail.com \
    /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