From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Simon Farnsworth <simon.farnsworth@onelan.com>,
Manu Abraham <abraham.manu@gmail.com>,
Antti Palosaari <crope@iki.fi>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH RFCv10 00/15] DVB QoS statistics API
Date: Sat, 19 Jan 2013 10:04:17 -0200 [thread overview]
Message-ID: <20130119100417.49da9f10@redhat.com> (raw)
In-Reply-To: <20130116200153.3ec3ee7d@redhat.com>
Em Wed, 16 Jan 2013 20:01:53 -0200
Mauro Carvalho Chehab <mchehab@redhat.com> escreveu:
> Em Wed, 16 Jan 2013 19:29:28 +0000
> Simon Farnsworth <simon.farnsworth@onelan.com> escreveu:
...
> > So, how do you provide such information?
...
I just finished to code it on my experimental tree:
http://git.linuxtv.org/mchehab/experimental-v4l-utils.git/shortlog/refs/heads/stats
The code there is tested, and it should be displaying all stats at dvbv5-zap
code. While I didn't test yet, backward compatibility with DVBv3 stats is
provided.
What's missing:
a) a routine to calculate and return PER
I didn't write it just because I need to first make UCB/PER measurements to
work with mb86a20s. The userspace code, however, is trivial.
b) display only one layer for the statistics.
It is relatively easy to detect if the displayed program is 1-seg.
All the code needs is to read the NIT table and check if the Partial TS
descriptor is present at NIT table and matches the service ID of the
displayed program. If so, only the statistics for the 1-seg layer applied.
This descriptor is mandatory. So, a code for doing it shouldn't be hard
to code, and should work fine if just 2 layers (1-seg and 12-seg) are
present on a given channel (that's the most usual usecase).
However, I couldn't find yet a way to do the same for the 3-seg layer when
present. In thesis, the TS Information Descriptor would be carrying this
data, inside the Transmission Type field, but both ARIB and ABNT specs
I read lacks a table with the possible values for it. The ABNT spec
mentions that a latter document would carry that info, but I couldn't
find it yet. Also, the TS Information Descriptor is optional, although
I never find any broadcaster that don't implement it in Brazil, as, on
ISDB, the Remote Control channel uses this descriptor as well.
This is less critical than the first case, as most broadcasters use
2 layers. However, I've seen already a few broadcasters using 3 layers
(generally, 1-seg, 3-seg and 9-seg) on some cities.
So, for now, if multiple layers are found, the dvbv5-zap program on my
experimental tree will just display data for all existing layers.
I'll address it there later.
-
The following changes since commit 28178e74681db0d0d924b1c2cc69e0d7a9295b16:
v4l2-compliance: add check whether the timestamp is monotonic. (2013-01-10 13:47:15 +0100)
are available in the git repository at:
git://linuxtv.org/mchehab/experimental-v4l-utils.git stats
for you to fetch changes up to b20f43e723fa8fd5f1ed74f1566d314490946fa6:
dvbv5-zap: better display BER (2013-01-19 09:30:18 -0200)
----------------------------------------------------------------
Mauro Carvalho Chehab (9):
dvbv5-zap: Allow to enable FE debug
Sync with kernel, with DVB stats
dvb-fe: add support for DVBv5 stats
dvbv5-zap: use the new DVBv5 stats API
dvb-fe: Add a flag to indicate if DVBv5 stats is in use
dvb-fe: Move the logic that calculates BER measures
dvb-fe: Improve BER measurements for DVBv5
dvb-fe: Allow returning BER in a float value
dvbv5-zap: better display BER
contrib/freebsd/include/linux/dvb/frontend.h | 77 +++++++++++++++++++++++++++++++++++++++++-
contrib/freebsd/include/linux/dvb/version.h | 2 +-
lib/include/dvb-fe.h | 39 ++++++++++++++++------
lib/include/dvb-frontend.h | 77 +++++++++++++++++++++++++++++++++++++++++-
lib/include/dvb-v5-std.h | 12 ++++++-
lib/libdvbv5/dvb-fe.c | 265 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-------------------------
lib/libdvbv5/dvb-file.c | 24 ++------------
lib/libdvbv5/dvb-v5-std.c | 19 ++++++++---
lib/libdvbv5/dvb-v5.c | 10 ++++--
lib/libdvbv5/dvb-v5.h | 2 +-
utils/dvb/Makefile.am | 2 +-
utils/dvb/dvbv5-zap.c | 177 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++---------------
12 files changed, 590 insertions(+), 116 deletions(-)
Cheers,
Mauro
next prev parent reply other threads:[~2013-01-19 12:05 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 2:30 [PATCH RFCv10 00/15] DVB QoS statistics API Mauro Carvalho Chehab
2013-01-15 2:30 ` [PATCH RFCv10 01/15] mb86a20s: improve error handling at get_frontend Mauro Carvalho Chehab
2013-01-15 2:30 ` [PATCH RFCv10 02/15] dvb: Add DVBv5 stats properties for Quality of Service Mauro Carvalho Chehab
2013-01-15 2:30 ` [PATCH RFCv10 03/15] dvb: the core logic to handle the DVBv5 QoS properties Mauro Carvalho Chehab
2013-01-15 2:30 ` [PATCH RFCv10 04/15] mb86a20s: Update QoS statistics at FE read_status Mauro Carvalho Chehab
2013-01-15 2:30 ` [PATCH RFCv10 05/15] mb86a20s: functions reorder Mauro Carvalho Chehab
2013-01-15 2:30 ` [PATCH RFCv10 06/15] mb86a20s: Fix i2c gate on error Mauro Carvalho Chehab
2013-01-15 2:30 ` [PATCH RFCv10 07/15] mb86a20s: improve debug for RF level Mauro Carvalho Chehab
2013-01-15 2:30 ` [PATCH RFCv10 08/15] mb86a20s: fix interleaving and FEC retrival Mauro Carvalho Chehab
2013-01-15 2:30 ` [PATCH RFCv10 09/15] mb86a20s: convert it to use dev_info/dev_err/dev_dbg Mauro Carvalho Chehab
2013-01-15 2:30 ` [PATCH RFCv10 10/15] mb86a20s: -EBUSY is expected when getting QoS measures Mauro Carvalho Chehab
2013-01-15 2:30 ` [PATCH RFCv10 11/15] mb86a20s: make AGC work better Mauro Carvalho Chehab
2013-01-15 2:30 ` [PATCH RFCv10 12/15] mb86a20s: Some improvements for BER measurement Mauro Carvalho Chehab
2013-01-15 2:30 ` [PATCH RFCv10 13/15] mb86a20s: improve bit error count for BER Mauro Carvalho Chehab
2013-01-15 2:31 ` [PATCH RFCv10 14/15] dvb: increase API version Mauro Carvalho Chehab
2013-01-15 8:20 ` [PATCH RFCv10 00/15] DVB QoS statistics API Johannes Stezenbach
2013-01-15 8:55 ` Antti Palosaari
2013-01-15 12:23 ` Mauro Carvalho Chehab
2013-01-15 9:34 ` Antti Palosaari
2013-01-15 13:10 ` Mauro Carvalho Chehab
2013-01-15 14:49 ` Antti Palosaari
2013-01-15 15:21 ` Mauro Carvalho Chehab
2013-01-15 15:47 ` Devin Heitmueller
2013-01-15 17:02 ` Mauro Carvalho Chehab
2013-01-15 15:26 ` Antti Palosaari
2013-01-15 17:12 ` Mauro Carvalho Chehab
2013-01-15 20:37 ` Antti Palosaari
2013-01-16 4:26 ` Manu Abraham
2013-01-16 11:41 ` Luca Olivetti
2013-01-16 13:56 ` Mauro Carvalho Chehab
2013-01-16 15:19 ` Manu Abraham
2013-01-16 17:21 ` Mauro Carvalho Chehab
2013-01-16 18:26 ` Manu Abraham
2013-01-16 19:22 ` Mauro Carvalho Chehab
2013-01-16 21:40 ` Manu Abraham
2013-01-16 19:29 ` Simon Farnsworth
2013-01-16 21:37 ` Manu Abraham
2013-01-16 22:11 ` Mauro Carvalho Chehab
2013-01-17 3:26 ` Manu Abraham
2013-01-16 22:01 ` Mauro Carvalho Chehab
2013-01-17 3:40 ` Manu Abraham
2013-01-17 9:33 ` Antti Palosaari
2013-01-17 16:50 ` Mauro Carvalho Chehab
2013-01-17 17:15 ` Antti Palosaari
2013-01-17 18:11 ` Mauro Carvalho Chehab
2013-01-17 18:27 ` Antti Palosaari
2013-01-17 18:37 ` Manu Abraham
2013-01-17 18:50 ` Mauro Carvalho Chehab
2013-01-17 19:11 ` Antti Palosaari
2013-01-17 19:35 ` Mauro Carvalho Chehab
2013-01-17 21:29 ` Manu Abraham
2013-01-17 22:22 ` Antti Palosaari
2013-01-17 22:46 ` Mauro Carvalho Chehab
2013-01-22 12:16 ` Mauro Carvalho Chehab
2013-01-23 15:08 ` Antti Palosaari
2013-01-23 15:12 ` Antti Palosaari
2013-01-23 18:18 ` Mauro Carvalho Chehab
2013-01-23 18:57 ` Mauro Carvalho Chehab
2013-01-23 19:55 ` Antti Palosaari
2013-01-23 21:00 ` Mauro Carvalho Chehab
2013-01-23 22:02 ` Mauro Carvalho Chehab
2013-01-17 17:16 ` Manu Abraham
2013-01-17 17:22 ` Antti Palosaari
2013-01-17 17:37 ` [linux-media] " Klaus Schmidinger
2013-01-17 17:39 ` [linux-media] " Klaus Schmidinger
2013-01-17 18:36 ` Mauro Carvalho Chehab
2013-01-19 12:04 ` Mauro Carvalho Chehab [this message]
2013-01-16 13:24 ` Mauro Carvalho Chehab
2013-01-15 10:38 ` Manu Abraham
2013-01-15 15:23 ` 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=20130119100417.49da9f10@redhat.com \
--to=mchehab@redhat.com \
--cc=abraham.manu@gmail.com \
--cc=crope@iki.fi \
--cc=linux-media@vger.kernel.org \
--cc=simon.farnsworth@onelan.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;
as well as URLs for NNTP newsgroup(s).