All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mike (mwester)" <mwester@dls.net>
To: Adrien Demarez <adrien.demarez@bolloretelecom.eu>
Cc: openembedded-devel@openembedded.org
Subject: Re: madwifi-ng & linux 2.6.29
Date: Wed, 01 Apr 2009 22:06:03 -0500	[thread overview]
Message-ID: <49D42B9B.3040304@dls.net> (raw)
In-Reply-To: <49D363A5.3010503@bolloretelecom.eu>

Adrien Demarez wrote:
> Hi all,
> 
> I am working with Jeremy Lainé on the boc01 architecture. Currently, we
> do use Madwifi + hostapd 0.5 for our 11g Atheros minicard modules
> (despite we want to switch to ath9k / ath5k when it is mature enough).
> As we are still using 2.6.27 kernel and found ath9k is not mature enough
> for AP in this version (at least, it does not work with our AR9160
> modules), I have written a working recipe for compat-wireless (not yet
> committed into OE though, please tell if anyone is interested. Beware :
> it does not compile if MAC80211 or CFG80211 is defined as 'y' in the
> kernel, use 'm' or 'n' instead !).
> This is working, though I'd prefer using vanilla in-kernel drivers
> instead of compat-wireless (so I plan to have a look to ath*k in 2.6.29
> kernel very soon).
> 
> In order to use ath*k (or any drivers using nl80211) with hostapd, I
> have also written a recipe for hostapd-0.6.9 (Jeremy has uploaded it
> into OE) and this is working perfectly with our AR9160 modules using
> ath9k from compat-wireless. I am currently testing ath5k, but I run into
> a few troubles with AP mode, so until this is fixed we still need to
> keep a working madwifi+hostapd-0.5.10 (I also experienced a few troubles
> with madwifi + hostapd-0.6.9 so for the moment we stand with hostapd-0.5
> when using madwifi, and hostapd-0.6 is not set as the default one. I
> will look at this soon but getting a working ath5k/AP is more important
> to me currently).
> I also have to do more testing with wpa_supplicant (currently, AP mode
> is my focus).
> 
> BTW, if anyone is interested, I also have written a working recipe for
> madwifi using hal-0.10.5.6. I found this hal is necessary for some
> recent chips like AR2417 with whom the vanilla madwifi-ng driver does
> not work.
> 
> Best regards,
> 
> --
> Adrien Demarez

Wow.

I had no idea this was so complicated.

For the moment, I'm going to drop madwifi, hostapd from the SlugOS
feeds, and put a SlugOS-specific hack into wpa-supplicant.  I guess
we'll need to invest a whole lot more time to sort out the new Atheros
driver world.

Mike (mwester)




  reply	other threads:[~2009-04-02  3:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-31 16:33 madwifi-ng & linux 2.6.29 Mike (mwester)
2009-04-01 12:52 ` Adrien Demarez
2009-04-02  3:06   ` Mike (mwester) [this message]
2010-04-13  8:43     ` madwifi-ng &amp; " Panayot Daskalov

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=49D42B9B.3040304@dls.net \
    --to=mwester@dls.net \
    --cc=adrien.demarez@bolloretelecom.eu \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.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.