From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Manoel PN <pinusdtv@hotmail.com>
Cc: linux-media@vger.kernel.org, lgspn@hotmail.com
Subject: Re: [PATCH 4/4] Modifications to the driver mb86a20s
Date: Fri, 13 May 2011 09:27:13 +0200 [thread overview]
Message-ID: <4DCCDD51.1030709@infradead.org> (raw)
In-Reply-To: <BLU157-w51A0D0CDE5F2B0061ACA23D8880@phx.gbl>
Em 13-05-2011 04:13, Manoel PN escreveu:
>
>
> This patch implement changes to the function mb86a20s_read_signal_strength.
>
> The original function, binary search, does not work with device dtb08.
Hmm... that's interesting. Maybe due to a different mb86a20s chip stepping?
>
> I would like to know if this function works.
I'll test it when I return back to Brazil.
Please send this patch in separate, as a RFC, and keep both methods enabled,
printing debug messages. This way, I can test it with the two devices I have,
comparing the SNR relations provided by both ways.
Thanks,
Mauro.
prev parent reply other threads:[~2011-05-13 7:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 2:13 [PATCH 4/4] Modifications to the driver mb86a20s Manoel PN
2011-05-13 7:27 ` Mauro Carvalho Chehab [this message]
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=4DCCDD51.1030709@infradead.org \
--to=mchehab@infradead.org \
--cc=lgspn@hotmail.com \
--cc=linux-media@vger.kernel.org \
--cc=pinusdtv@hotmail.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