All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pat Erley <pat-lkml@erley.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Ath9k - Newbie question
Date: Sun, 11 Apr 2010 12:07:07 -0400	[thread overview]
Message-ID: <4BC1F3AB.300@erley.org> (raw)
In-Reply-To: <SNT140-w21A934AC308D12131913B1BD140@phx.gbl>

On 04/10/10 02:54, Arun Govindan wrote:
> Hello,
> 
> I'm trying to bring up ath9k in AP mode with DWA-556 PCI-x card. I see
> three options to compile and test ath9k:
> 
> 1. Download the kernel source code and build. But this means that I need
> to rebuild kernel every time make changes.
> 
> 2. compat-wireless
> 
> 3. wireless-testing
> 
> My questions is that whether compat-wireless and wireless-testing are
> two different versions or the same? Which one is better?
> 
> Also please point me to documents on how to setup Ath9k in AP mode.
> 
> Thanks,
> Arun
> 

Arun,

compat-wireless is just a way to use the wireless drivers from wireless-next (I believe) with older kernels, and is generally the 'best' way to get the drivers, especially if you choose a snapshot from a stable kernel release.  The drivers that ship with each kernel should 'just work' always, and then you can choose to stick with those drivers, if they work for you, or update to more recent ones to gain bug fixes, and new features.  Many (most?) distros provide these drivers as backports, so you might look into that option, depending on your particular needs and what distro you run.

As far as running ath9k in master mode:

http://wireless.kernel.org/en/users/Documentation/hostapd

That should be all you need.  I've run ath9k as an AP for a long time now (since before that page was authored), and when I was first setting it up, that page would have been insanely valuable to me.  

Pat Erley

  reply	other threads:[~2010-04-11 16:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-10  6:54 [ath9k-devel] Ath9k - Newbie question Arun Govindan
2010-04-11 16:07 ` Pat Erley [this message]
2010-04-12  5:59   ` Arun Govindan
2010-04-12  9:38     ` Joerg Pommnitz
2010-04-11 16:39 ` Ben Gamari
2010-04-11 19:05   ` Rakesh Kumar

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=4BC1F3AB.300@erley.org \
    --to=pat-lkml@erley.org \
    --cc=ath9k-devel@lists.ath9k.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 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.