From: Steve Brown <sbrown@cortland.com>
To: Bob Copeland <bcopeland@gmail.com>
Cc: Keir <keirlawson@gmail.com>,
Nick Kossifidis <mickflemm@gmail.com>,
Andrey Yurovsky <andrey@cozybit.com>,
linux-wireless@vger.kernel.org, javier@cozybit.com
Subject: Re: Mesh now completely broken on ath5k, latest git
Date: Thu, 18 Dec 2008 16:02:37 -0500 [thread overview]
Message-ID: <494ABA6D.8070002@cortland.com> (raw)
In-Reply-To: <b6c5339f0812181138s1ba134a6qeff21eb063a87e08@mail.gmail.com>
Bob Copeland wrote:
> On Thu, Dec 18, 2008 at 9:00 AM, Steve Brown <sbrown@cortland.com> wrote:
>
>> I did a binary chop on the pcu patch. Reverting this part of the patch
>> restores ap and mesh beaconing. I've no idea why.
>>
>> 77: + else
>> 78: + AR5K_REG_ENABLE_BITS(ah, AR5K_CFG,
>> AR5K_CFG_ADHOC);
>>
>
> Hmm, that looks exactly backwards, shouldn't it be DISABLE_BITS
> (and ENABLE_BITS in the adhoc case?)
>
> I think it's supposed to be 0 for AP/STA and 1 for IBSS.
>
>
Your interpretation matches the recently released hal source. I switched
them around in the pcu patch and ap/mesh beacons return.
Lots of these however:
Dec 18 15:53:20 fl-ws kernel: ath5k phy23: beacon queue 7 didn't stop?
If I make the same change to the current git, still no beacons. But, the
"queue 7" msgs persist.
Anyway, it's not antenna related.
Steve
next prev parent reply other threads:[~2008-12-18 21:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 12:05 Mesh now completely broken on ath5k, latest git Keir
2008-12-16 13:22 ` Steve Brown
2008-12-16 16:07 ` Keir
2008-12-16 18:30 ` Andrey Yurovsky
2008-12-17 10:56 ` Keir
2008-12-17 11:20 ` Michael Renzmann
2008-12-17 18:03 ` Keir
2008-12-17 17:06 ` Nick Kossifidis
2008-12-17 18:04 ` Keir
2008-12-18 14:00 ` Steve Brown
2008-12-18 19:38 ` Bob Copeland
2008-12-18 21:02 ` Steve Brown [this message]
2008-12-18 21:48 ` Bob Copeland
2008-12-18 23:14 ` Steve Brown
2008-12-19 20:18 ` Steve Brown
2008-12-19 20:41 ` Bob Copeland
2008-12-22 22:29 ` Steve Brown
2008-12-22 22:40 ` 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=494ABA6D.8070002@cortland.com \
--to=sbrown@cortland.com \
--cc=andrey@cozybit.com \
--cc=bcopeland@gmail.com \
--cc=javier@cozybit.com \
--cc=keirlawson@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mickflemm@gmail.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 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.