From: Simon Farnsworth <simon.farnsworth@onelan.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: "Devin Heitmueller" <dheitmueller@kernellabs.com>,
"Frank Schäfer" <fschaefer.oss@googlemail.com>,
"Linux Media Mailing List" <linux-media@vger.kernel.org>
Subject: Re: [PATCH RFCv9 1/4] dvb: Add DVBv5 stats properties for Quality of Service
Date: Thu, 10 Jan 2013 10:19:34 +0000 [thread overview]
Message-ID: <19692716.qk9lES9tlU@f17simon> (raw)
In-Reply-To: <20130109132425.659243af@redhat.com>
On Wednesday 9 January 2013 13:24:25 Mauro Carvalho Chehab wrote:
<snip>
> Yes, it makes sense to document that the signal strength should be reported
> on either dBm or dBµW, if the scale is FE_SCALE_DECIBEL. I prefer to specify
> it in terms of Watt (or a submultiple) than in terms of voltage/impedance, as
> different Countries use different impedances on DTV cabling (typically,
> 50Ω or 75Ω).
>
> So, either dBm or dBµW works for me. As you said, applications can convert
> between those mesures as they wish, by simply adding some constant when
> displaying the power measure.
>
> As the wifi subsytem use dBm, I vote for using dBm for the signal measure
> at the subsystem (actually, 0.1 dBm).
>
0.1 dBm suits me. I just want something that I can present to the end user in
a format that will match their aerial installer's kit.
--
Simon Farnsworth
Software Engineer
ONELAN Ltd
http://www.onelan.com
next prev parent reply other threads:[~2013-01-10 10:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 0:25 [PATCH RFCv9 0/4] DVB QoS statistics API Mauro Carvalho Chehab
2013-01-08 0:25 ` [PATCH RFCv9 1/4] dvb: Add DVBv5 stats properties for Quality of Service Mauro Carvalho Chehab
2013-01-08 11:45 ` Simon Farnsworth
2013-01-08 18:00 ` Frank Schäfer
2013-01-08 23:18 ` Simon Farnsworth
2013-01-08 23:28 ` Devin Heitmueller
2013-01-09 11:02 ` Simon Farnsworth
2013-01-09 15:24 ` Mauro Carvalho Chehab
2013-01-10 10:19 ` Simon Farnsworth [this message]
2013-01-13 13:30 ` [linux-media] " Klaus Schmidinger
2013-01-08 12:33 ` Mauro Carvalho Chehab
2013-01-08 0:25 ` [PATCH RFCv9 2/4] dvb: the core logic to handle the DVBv5 QoS properties Mauro Carvalho Chehab
2013-01-08 0:25 ` [PATCH RFCv9 3/4] mb86a20s: provide signal strength via DVBv5 stats API Mauro Carvalho Chehab
2013-01-08 0:25 ` [PATCH RFCv9 4/4] mb86a20s: add BER measure Mauro Carvalho Chehab
2013-01-08 0:37 ` [PATCH RFCv9] " 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=19692716.qk9lES9tlU@f17simon \
--to=simon.farnsworth@onelan.com \
--cc=dheitmueller@kernellabs.com \
--cc=fschaefer.oss@googlemail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.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