From: Steve Brown <sbrown@cortland.com>
To: Keir <keirlawson@gmail.com>
Cc: 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 09:00:42 -0500 [thread overview]
Message-ID: <494A578A.7070803@cortland.com> (raw)
In-Reply-To: <e27b78a40812171004r3a8d424dk7c390aaf7c757665@mail.gmail.com>
Keir wrote:
> Tried this, and I'm getting slightly odd results. The two nodes
> running with these lines commented out can see the node whose code is
> previous to the PCU patch, but they cant see each other. Also the
> other node can see both of them... very strange.
>
> Cheers
>
> Keir
>
> 2008/12/17 Nick Kossifidis <mickflemm@gmail.com>:
>
>> 2008/12/16 Andrey Yurovsky <andrey@cozybit.com>:
>>
>>> Hi Keir. What type of Atheros-based card are you using? How many
>>> antennas do you have connected? If I understand things correctly, the
>>> PCU code regression (with respect to mesh and maybe AP and IBSS) has
>>> to do with having one antenna hooked up when your hardware also has an
>>> AUX antenna connector. If you have only one antenna, can you please
>>> plug in a second one and try again (before and after the commit in
>>> question)? I will try to do the same test here. More details from
>>> Nick were posted here:
>>> http://marc.info/?l=linux-wireless&m=122771338021489&w=2
>>>
>>>
>> To summarize, the following code on base.c is the problem...
>>
>> 1955 /*
>> 1956 * Switch antenna every 4 beacons if txantenna is not set
>> 1957 * XXX assumes two antennas
>> 1958 */
>> 1959 if (antenna == 0)
>> 1960 antenna = sc->bsent & 4 ? 2 : 1;
>>
>> ...we should always set 0 on tx descriptor for the default scenario to
>> work. Can you please comment this out and see if it works ?
>>
>> --
>> GPG ID: 0xD21DB2DB
>> As you read this post global entropy rises. Have Fun ;-)
>> Nick
>>
>>
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);
Steve
next prev parent reply other threads:[~2008-12-18 14:00 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 [this message]
2008-12-18 19:38 ` Bob Copeland
2008-12-18 21:02 ` Steve Brown
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=494A578A.7070803@cortland.com \
--to=sbrown@cortland.com \
--cc=andrey@cozybit.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 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).