From: Bruno Randolf <br1@einfach.org>
To: Bob Copeland <me@bobcopeland.com>
Cc: ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org,
linville@tuxdriver.com, mcgrof@gmail.com, jirislaby@gmail.com,
nbd@openwrt.org, sedat.dilek@googlemail.com
Subject: Re: [ath5k-devel] [PATCH 1/6] ath5k: Always write tx powertable on hw
Date: Sat, 1 Jan 2011 23:51:07 +0900 [thread overview]
Message-ID: <201101012351.07339.br1@einfach.org> (raw)
In-Reply-To: <AANLkTinD+XrkXeUR2PNqj4eVVvTmrh8a9c4UEy0Nr7JE@mail.gmail.com>
On Thursday 30 December 2010 06:02:29 Bob Copeland wrote:
> On Thu, Dec 2, 2010 at 11:03 PM, Nick Kossifidis <mickflemm@gmail.com>
wrote:
> > * By skipping tx power table calibration we also skip setting
> > tx power table on hw. Make sure we always write tx power table
> > on hw since it gets cleared on reset.
> >
> > Signed-off-by: Nick Kossifidis <mickflemm@gmail.com>
>
> Just a very late heads-up, this patch seems to be causing problems
> for me.
>
> Seems a bit weird given the content, but the symptom is that
> when I bring up the device none of my probe requests are actually
> getting sent, according to wireshark captures from another device.
> Reverting just this patch helps, so my power table must be broken
> at start up.
>
> I saw that Bruno had a later series that touched this area, so I'll
> try them next.
Yep, they should fix that problem. Please try them and report if they don't.
Bruno
next prev parent reply other threads:[~2011-01-01 14:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-03 4:03 [PATCH 1/6] ath5k: Always write tx powertable on hw Nick Kossifidis
2010-12-03 6:34 ` Sedat Dilek
2010-12-03 14:55 ` John W. Linville
2010-12-03 22:23 ` Bob Copeland
2010-12-04 21:37 ` Nick Kossifidis
2010-12-29 21:02 ` [ath5k-devel] " Bob Copeland
2011-01-01 14:51 ` Bruno Randolf [this message]
2011-01-02 18:23 ` Bob Copeland
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=201101012351.07339.br1@einfach.org \
--to=br1@einfach.org \
--cc=ath5k-devel@lists.ath5k.org \
--cc=jirislaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
--cc=me@bobcopeland.com \
--cc=nbd@openwrt.org \
--cc=sedat.dilek@googlemail.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;
as well as URLs for NNTP newsgroup(s).