From: Steffen Barszus <steffenbpunkt@googlemail.com>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: James <bjlockie@lockie.ca>,
linux-media Mailing List <linux-media@vger.kernel.org>
Subject: Re: femon signal strength
Date: Sun, 6 Nov 2011 14:15:15 +0100 [thread overview]
Message-ID: <20111106141515.5b56a377@grobi> (raw)
In-Reply-To: <CAGoCfiwC+7pkY6ZchySBYRkyY1XjFjKeJYQEPTc2ZiBN-pdoyw@mail.gmail.com>
On Sat, 5 Nov 2011 15:38:50 -0400
Devin Heitmueller <dheitmueller@kernellabs.com> wrote:
> On Saturday, November 5, 2011, Steffen Barszus
> <steffenbpunkt@googlemail.com> wrote:
> > On Wed, 26 Oct 2011 15:58:32 -0400
> > James <bjlockie@lockie.ca> wrote:
> >> How about adding switches to femon, it won't be automatic?
> >>
> >> I'm going to make femon work for my card, anyways. :-)
> >
> > This is no solution - drivers should be patched to deliver result in
> > common format. femon is not the only application reading this
> > values. And every application carrying its own set of correction
> > tables doesn't help in any way. Shouldn't be to hard to agree on
> > one scale and scale whatever value to that in reporting the signal
> > strength.
>
> You would think this would be relatively simple to get a consensus on.
> You would be wrong though. I would suggest doing a search of the ML
> for "SNR" so you can see all. the history of the debate amongst the
> driver developers.
I don't need to read the history of this and i am not even interested
in doing so. No matter what "The right solution" is, showing the
inability of acting as a team and putting the conflict to the user is
the worst solution you can achieve. Any uniform scale is better, then
whats there at the moment.
Being ignorant in this respect is and was intended.
next prev parent reply other threads:[~2011-11-06 13:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 4:36 femon signal strength James
2011-10-26 8:15 ` Devin Heitmueller
2011-10-26 19:45 ` James
2011-10-26 19:49 ` Devin Heitmueller
2011-10-26 19:58 ` James
2011-11-05 10:10 ` Steffen Barszus
[not found] ` <CAGoCfiwC+7pkY6ZchySBYRkyY1XjFjKeJYQEPTc2ZiBN-pdoyw@mail.gmail.com>
2011-11-06 13:15 ` Steffen Barszus [this message]
[not found] ` <CAGoCfixoOwZumohwJrLVKhfpUNGYwbD9uSq7nM0GhqriOx0FxA@mail.gmail.com>
2011-11-06 19:59 ` Steffen Barszus
2011-11-07 10:47 ` Andreas Oberritter
2011-11-07 15:13 ` Luca Olivetti
2011-11-07 19:16 ` Andreas Oberritter
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=20111106141515.5b56a377@grobi \
--to=steffenbpunkt@googlemail.com \
--cc=bjlockie@lockie.ca \
--cc=dheitmueller@kernellabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.