From: "Aleksandr V. Piskunov" <aleksandr.v.piskunov@gmail.com>
To: linux-media@vger.kernel.org
Subject: Re: correct implementation of FE_READ_UNCORRECTED_BLOCKS
Date: Sun, 2 Aug 2009 20:56:22 +0300 [thread overview]
Message-ID: <20090802175622.GB19034@moon> (raw)
In-Reply-To: <20090802174836.GA19034@moon>
Oops, sent it way too fast. Anyway.
DVB API documentation says:
"This ioctl call returns the number of uncorrected blocks detected by
the device driver during its lifetime.... Note that the counter will
wrap to zero after its maximum count has been reached."
Does it mean that correct implementation of frontend driver should
keep its own counter of UNC blocks and increment it every time hardware
reports such block?
>From what I see, a lot of current frontend drivers simply dump a value
from some hardware register. For example zl10353 I got here reports
some N unc blocks and then gets back to reporting zero.
next prev parent reply other threads:[~2009-08-02 17:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-02 17:48 correct implementation of FE_READ_UNCORRECTED_BLOCKS Aleksandr V. Piskunov
2009-08-02 17:56 ` Aleksandr V. Piskunov [this message]
2009-08-02 18:11 ` Andy Walls
2009-08-02 19:01 ` Aleksandr V. Piskunov
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=20090802175622.GB19034@moon \
--to=aleksandr.v.piskunov@gmail.com \
--cc=linux-media@vger.kernel.org \
/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