linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans Maes <Hans@bitnet.be>
To: linux-wireless@vger.kernel.org
Subject: Re: how to set antenna iw + ath5k
Date: Tue, 21 Apr 2009 13:56:36 +0200	[thread overview]
Message-ID: <49EDB474.2020809@bitnet.be> (raw)
In-Reply-To: <40f31dec0904160611l58500309wa1ba92fe3aeff843@mail.gmail.com>


Nick Kossifidis wrote:
> 2009/4/16 Hans Maes <Hans@bitnet.be>:
>   
>> Hello,
>>
>> I'm not sure this is the correct place to ask my question, but I've been
>> searching on google for ages now and can't seem to find an answer so I'm
>> asking it here.
>> If not, please yell at me and tell me where to go whine instead ;-)
>>
>> I'm using CM11 a/b/g cards with the Atheros AR5414A Chip, which have 2
>> antenna connectors.
>> I only have 1 antenna connected to the MAIN connector.
>> Running a self compiled 2.6.29 kernel on a few debian lenny boxes with ath5k
>> module for the wireless cards, set up in mesh mode.
>> Seems to work fine on the test bench, but behaves rather poorly in
>> production environment.
>> Everything related to the mesh network setup seems to work, but I have about
>> 40% - 60% packet loss on the entire netwerk (about 15 nodes)
>>
>> I'm guessing this has something to do with the antenna diversity setting.
>>
>> Can anybody tell me how to tell the ath5k module to disable antenna
>> diversity and only use the MAIN antenna ?
>>
>> If this is a RTFM thingie, then I apologize, I just can't seem to find it
>> anywhere.
>>
>> Please reply to my personal e-mail address as well, I'm not subscribed to
>> the list.
>>
>> Thanks for your help.
>>
>> Regards,
>>
>> Hans
>>     
>
> After this patch...
> https://lists.ath5k.org/pipermail/ath5k-devel/2009-April/002264.html
>
> It's possible to tell the driver to use one fixed antenna (in your
> case its fixed antenna A). Just change...
> ath5k_hw_set_antenna_mode(ah, AR5K_ANTMODE_DEFAULT);
>
> with
> ath5k_hw_set_antenna_mode(ah, AR5K_ANTMODE_FIXED_A);
>   
Seems like a quite recent patch ;-)

I've been reading up on how to patch the source myself, but I'm not sure 
I'll succeed without breaking things.
I can manage pulling the git repository and compiling the ath5k module, 
but I'm no expert at patching stuff.

Any pointers where to look for a simple howto on 'the proper way' to 
apply these patches ?
Any idea when this patch would make it into the git repository ?
> we will have a better way to change this in the future ;-)
>   
That would be nice, I know most users don't need to change this and can 
live with default settings, but there are so many possible scenarios 
where one would want more specific control over antenna settings.


Thanks for the help!

Hans

  parent reply	other threads:[~2009-04-21 11:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-16 11:41 how to set antenna iw + ath5k Hans Maes
2009-04-16 13:11 ` Nick Kossifidis
2009-04-16 13:37   ` Gábor Stefanik
2009-04-16 15:22     ` Arnd Hannemann
2009-04-16 15:45       ` Nick Kossifidis
2009-04-21 11:56   ` Hans Maes [this message]
2009-04-21 14:27     ` 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=49EDB474.2020809@bitnet.be \
    --to=hans@bitnet.be \
    --cc=linux-wireless@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 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).