From: Manu Abraham <abraham.manu@gmail.com>
To: Devin Heitmueller <devin.heitmueller@gmail.com>
Cc: Mika Laitio <lamikr@pilppa.org>, Andy Walls <awalls@radix.net>,
linux-media@vger.kernel.org, Trent Piepho <xyzzy@speakeasy.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Ang Way Chuang <wcang@nav6.org>, VDR User <user.vdr@gmail.com>
Subject: Re: The right way to interpret the content of SNR, signal strength and BER from HVR 4000 Lite
Date: Fri, 27 Mar 2009 23:00:02 +0400 [thread overview]
Message-ID: <49CD2232.4060701@gmail.com> (raw)
In-Reply-To: <412bdbff0903251527i5fa6a534j17ce9dad4204da05@mail.gmail.com>
Devin Heitmueller wrote:
> On Wed, Mar 25, 2009 at 6:02 PM, Manu Abraham <abraham.manu@gmail.com> wrote:
>> Sure, of course. Here is an updated list based on the information
>> that you accumulated. I have corrected some of them, which were not
>> accurate.
>
> Before I comment any further on your email, could you please clarify
> what you mean by "Relative, confirms to API". The current DVB API
> specification does not specify any units of measure for the content of
> the field, so I am not sure what you mean by this.
Sorry about not responding earlier, wasn't feeling well at all and
hence.
By Relative, i meant dimensionless, but still it makes some sense
based on some documented references.
What i mean "relative" is that the API expects something like this.
http://linuxtv.org/hg/dvb-apps/file/5fbdd3f898b1/util/szap/README
Regards,
Manu
next prev parent reply other threads:[~2009-03-27 19:00 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 1:53 The right way to interpret the content of SNR, signal strength and BER from HVR 4000 Lite Ang Way Chuang
2009-03-13 2:23 ` VDR User
2009-03-13 4:19 ` Ang Way Chuang
2009-03-13 14:27 ` Devin Heitmueller
2009-03-13 21:11 ` Trent Piepho
2009-03-13 21:32 ` Devin Heitmueller
2009-03-13 21:52 ` Michael Krufky
2009-03-13 22:27 ` VDR User
2009-03-13 22:31 ` Devin Heitmueller
2009-03-15 13:20 ` wk
2009-03-15 14:40 ` Devin Heitmueller
2009-03-13 23:55 ` Trent Piepho
2009-03-19 13:16 ` Mauro Carvalho Chehab
2009-03-19 20:11 ` Trent Piepho
2009-03-19 22:17 ` Trent Piepho
2009-03-19 22:36 ` Devin Heitmueller
2009-03-19 23:06 ` Trent Piepho
2009-03-20 14:21 ` Devin Heitmueller
2009-03-20 19:38 ` Trent Piepho
2009-03-19 23:27 ` Manu Abraham
2009-03-20 6:55 ` Manu Abraham
2009-03-20 13:07 ` Devin Heitmueller
2009-03-20 15:07 ` VDR User
2009-03-27 9:14 ` Roberto Ragusa
2009-03-22 2:45 ` Andy Walls
2009-03-22 10:27 ` Manu Abraham
2009-03-23 1:00 ` Devin Heitmueller
2009-03-24 21:39 ` Devin Heitmueller
2009-03-24 22:08 ` Steven Toth
2009-03-25 1:12 ` Andy Walls
2009-03-24 23:18 ` Manu Abraham
2009-03-24 23:28 ` Mika Laitio
2009-03-24 23:46 ` Manu Abraham
2009-03-25 0:29 ` VDR User
2009-03-25 14:38 ` Devin Heitmueller
2009-03-25 22:02 ` Manu Abraham
2009-03-25 22:27 ` Devin Heitmueller
2009-03-27 18:09 ` Devin Heitmueller
2009-03-27 19:00 ` Manu Abraham [this message]
2009-03-24 23:54 ` Manu Abraham
2009-03-14 0:43 ` Andy Walls
2009-03-14 1:34 ` Trent Piepho
2009-03-14 2:44 ` Andy Walls
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=49CD2232.4060701@gmail.com \
--to=abraham.manu@gmail.com \
--cc=awalls@radix.net \
--cc=devin.heitmueller@gmail.com \
--cc=lamikr@pilppa.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=user.vdr@gmail.com \
--cc=wcang@nav6.org \
--cc=xyzzy@speakeasy.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