From: "P. van Gaans" <w3ird_n3rd@gmx.net>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] [PATCH] Fix the unc for the frontends tda10021 and stv0297
Date: Mon, 12 May 2008 19:03:52 +0200 [thread overview]
Message-ID: <48287878.9090401@gmx.net> (raw)
In-Reply-To: <200805121802.34413@orion.escape-edv.de>
On 05/12/2008 06:02 PM, Oliver Endriss wrote:
> P. van Gaans wrote:
>> On 05/12/2008 03:16 PM, Oliver Endriss wrote:
>>> @all:
>>> 1. If nobody objects I will commit the patches.
>>> 2. Please check and fix the other frontend drivers to follow the spec.
>> Will the behaviour of femon change, and if so, in what way?
>
> For a correct driver unc would not return to 0 (unless the counter
> wrapped).
>
>> I use it now
>> to see at what points in time I've had hickups by writing femon's output
>> to a file and grep -nv "unc 0". This way I can see for example I've had
>> errors at 16:35 and 17:48. If this will still work after the patch, I'm
>> fine with it. If it won't work, will there be an alternative?
>
> - Monitor the log for changes of the unc value.
> - femon could be modified to display the delta value, or we might add an
> option (-U) to choose between absolute and delta unc display.
>
> I am open to suggestions.
>
> CU
> Oliver
>
I don't know much about programming but I guess femon could be changed.
I doubt I'll be able to do it but otherwise maybe someone else will.
Looking for changes in the unc value will be more work when
investigating a 12-hour femon log, so adding an option sounds like a
good idea.
P.
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-05-12 17:04 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-10 8:46 [linux-dvb] [PATCH] Fix the unc for the frontends tda10021 and stv0297 e9hack
2008-05-10 15:17 ` Oliver Endriss
2008-05-10 15:27 ` Oliver Endriss
2008-05-10 15:48 ` Michael Krufky
2008-05-12 13:29 ` Oliver Endriss
2008-05-10 16:02 ` e9hack
2008-05-10 16:39 ` Oliver Endriss
2008-05-10 21:53 ` Andy Walls
2008-05-10 22:16 ` Manu Abraham
2008-05-10 23:44 ` Andy Walls
2008-05-11 6:14 ` Manu Abraham
2008-05-11 18:35 ` Andy Walls
2008-05-11 19:33 ` Manu Abraham
2008-05-11 21:32 ` Andy Walls
2008-05-12 13:16 ` Oliver Endriss
2008-05-12 13:47 ` P. van Gaans
2008-05-12 16:02 ` Oliver Endriss
2008-05-12 17:03 ` P. van Gaans [this message]
2008-05-12 22:42 ` Andy Walls
2008-05-11 23:45 ` P. van Gaans
2008-05-12 6:47 ` e9hack
2008-05-12 14:26 ` Luca Olivetti
2008-05-10 16:12 ` e9hack
2008-05-30 23:46 ` Oliver Endriss
2008-05-31 0:01 ` Manu Abraham
2008-05-31 7:19 ` e9hack
2008-05-31 12:45 ` Oliver Endriss
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=48287878.9090401@gmx.net \
--to=w3ird_n3rd@gmx.net \
--cc=linux-dvb@linuxtv.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