From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: unlisted-recipients:; (no To-header on input)
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
"Daniel W. S. Almeida" <dwlsalmeida@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: [PATCH RFC 00/11] Solve some issues and do some improvements at vidtv
Date: Mon, 14 Sep 2020 11:03:15 +0200 [thread overview]
Message-ID: <cover.1600073975.git.mchehab+huawei@kernel.org> (raw)
This patch series is not ready yet. However, as there are some problems reported
when this driver got merged at linux-next, let me send it, in order to avoid
someone to address the same problems I already fixed.
There are still some things to be fixed there. For example, the bitfield
endiannes logic for MPEG-TS tables are wrong. My plan is to address those
along this week.
Also, Kaffeine is not properly detecting the audio streams. It will likely need
some additional patches for it to properly detect and work with SMPTE 302m
audio streams.
Mauro Carvalho Chehab (11):
media: vidtv: add modaliases for the bridge driver
media: vidtv: prefer using dev_foo() instead of pr_foo()
media: vidtv: fix 32-bit warnings
media: vidtv: fix frequency tuning logic
media: vidtv: add an initial channel frequency
media: vidtv: get rid of some endiannes nonsense
media: vidtv: remove a wrong endiannes check from s302m generator
media: vidtv: properly initialize the internal state struct
media: vidtv: add basic support for DVBv5 stats
media: vidtv: get rid of the work queue
media: vidtv: increment byte and block counters
.../media/test-drivers/vidtv/vidtv_bridge.c | 35 ++-
.../media/test-drivers/vidtv/vidtv_bridge.h | 3 +
.../media/test-drivers/vidtv/vidtv_channel.c | 23 +-
.../media/test-drivers/vidtv/vidtv_common.c | 4 +-
.../media/test-drivers/vidtv/vidtv_demod.c | 242 +++++++++---------
.../media/test-drivers/vidtv/vidtv_demod.h | 4 -
drivers/media/test-drivers/vidtv/vidtv_mux.c | 32 ++-
drivers/media/test-drivers/vidtv/vidtv_mux.h | 9 +-
drivers/media/test-drivers/vidtv/vidtv_pes.c | 12 +-
drivers/media/test-drivers/vidtv/vidtv_psi.c | 32 ---
.../media/test-drivers/vidtv/vidtv_s302m.c | 10 +-
.../media/test-drivers/vidtv/vidtv_tuner.c | 41 ++-
12 files changed, 221 insertions(+), 226 deletions(-)
--
2.26.2
next reply other threads:[~2020-09-14 9:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 9:03 Mauro Carvalho Chehab [this message]
2020-09-14 9:03 ` [PATCH RFC 01/11] media: vidtv: add modaliases for the bridge driver Mauro Carvalho Chehab
2020-09-14 9:03 ` [PATCH RFC 02/11] media: vidtv: prefer using dev_foo() instead of pr_foo() Mauro Carvalho Chehab
2020-09-14 9:03 ` [PATCH RFC 03/11] media: vidtv: fix 32-bit warnings Mauro Carvalho Chehab
2020-09-14 9:03 ` [PATCH RFC 04/11] media: vidtv: fix frequency tuning logic Mauro Carvalho Chehab
2020-09-14 9:03 ` [PATCH RFC 05/11] media: vidtv: add an initial channel frequency Mauro Carvalho Chehab
2020-09-14 9:03 ` [PATCH RFC 06/11] media: vidtv: get rid of some endiannes nonsense Mauro Carvalho Chehab
2020-09-14 15:14 ` Daniel W. S. Almeida
2020-09-15 11:49 ` Mauro Carvalho Chehab
2020-09-14 9:03 ` [PATCH RFC 07/11] media: vidtv: remove a wrong endiannes check from s302m generator Mauro Carvalho Chehab
2020-09-14 9:03 ` [PATCH RFC 08/11] media: vidtv: properly initialize the internal state struct Mauro Carvalho Chehab
2020-09-14 9:03 ` [PATCH RFC 09/11] media: vidtv: add basic support for DVBv5 stats Mauro Carvalho Chehab
2020-09-14 9:03 ` [PATCH RFC 10/11] media: vidtv: get rid of the work queue Mauro Carvalho Chehab
2020-09-14 9:03 ` [PATCH RFC 11/11] media: vidtv: increment byte and block counters Mauro Carvalho Chehab
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=cover.1600073975.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=dwlsalmeida@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sfr@canb.auug.org.au \
/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