From: Daniel Scheller <d.scheller.oss@gmail.com>
To: mchehab@kernel.org, mchehab@s-opensource.com
Cc: linux-media@vger.kernel.org, rjkm@metzlerbros.de
Subject: Re: [PATCH 0/2] Add FEC rates, S2X modulations and 64K transmission
Date: Sat, 6 Jan 2018 13:08:12 +0100 [thread overview]
Message-ID: <20180106130812.33e59792@lt530> (raw)
In-Reply-To: <20171221202321.30539-1-d.scheller.oss@gmail.com>
Am Thu, 21 Dec 2017 21:23:19 +0100
schrieb Daniel Scheller <d.scheller.oss@gmail.com>:
> From: Daniel Scheller <d.scheller@gmx.net>
>
> As the DVB API is bumped to 5.11 for the next cycle.
>
> dddvb brings a few additional FEC rates (1/4 and 1/3), 64/128/256APSK
> modulations (DVB-S2X) and the 64K transmission mode. These two rather
> trivial patches bring them to mainline, and puts these missing bits
> into the stv0910's get_frontend() callback (FEC 1/4 and 1/3 are
> handled throughout the rest of the demod driver already).
>
> Let's have these enums as a part of DVB core 5.11.
>
> Daniel Scheller (2):
> media: dvb_frontend: add FEC modes, S2X modulations and 64K
> transmission
> media: dvb-frontends/stv0910: report FEC 1/4 and 1/3 in
> get_frontend()
>
> Documentation/media/frontend.h.rst.exceptions | 6 ++++++
> drivers/media/dvb-frontends/stv0910.c | 2 +-
> include/uapi/linux/dvb/frontend.h | 13 +++++++++++++
> 3 files changed, 20 insertions(+), 1 deletion(-)
(Rather early) Ping - any chance these few constants/enums can make it
as part of DVB core 5.11?
Best regards,
Daniel Scheller
--
https://github.com/herrnst
prev parent reply other threads:[~2018-01-06 12:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 20:23 [PATCH 0/2] Add FEC rates, S2X modulations and 64K transmission Daniel Scheller
2017-12-21 20:23 ` [PATCH 1/2] media: dvb_frontend: add FEC modes, " Daniel Scheller
2017-12-21 20:23 ` [PATCH 2/2] media: dvb-frontends/stv0910: report FEC 1/4 and 1/3 in get_frontend() Daniel Scheller
2018-01-06 12:08 ` 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=20180106130812.33e59792@lt530 \
--to=d.scheller.oss@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mchehab@s-opensource.com \
--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 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.