From: "John W. Linville" <linville@tuxdriver.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: Dan Williams <dcbw@redhat.com>,
linux-wireless@vger.kernel.org,
Holger Schurig <holgerschurig@googlemail.com>
Subject: Re: [PATCH] libertas: cfg80211 support
Date: Tue, 2 Feb 2010 15:36:43 -0500 [thread overview]
Message-ID: <20100202203643.GD2967@tuxdriver.com> (raw)
In-Reply-To: <20100202000934.GA19847@sortiz.org>
On Tue, Feb 02, 2010 at 01:09:46AM +0100, Samuel Ortiz wrote:
>
> From: Holger Schurig <holgerschurig@googlemail.com>
>
> We can get rid of the libertas wext, assoc and scan code.
> The cfg80211 support is almost complete, the main missing feature being mesh
> support. There are also a few cfg80211_ops handlers missing (tx_power,
> bss_change for example).
> Monitor and STA mode are supported and the latter have been tested on open,
> WEP, WPA and WPA2 links. At connection time, the cfg80211 bss list has to be
> populated with the BSS we're trying to join.
> Also, passive and active (broadcast and directed) scanning have been tested
> (on a specific channel and on the whole band).
>
> Signed-off-by: Holger Schurig <holgerschurig@gmail.com>
> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
> ---
> v1: scanning
> v2: + WEP, WPA, WPA2
> v3: + disconnect & MIC events, 11D region hint to cfg80211, auth_type TLV
> v4: + IBSS
> + monitor mode
> v5: + Search the cfg80211 bss list for the right BSSID when connecting.
> + Removed carrier off toggling when scanning.
> + Slightly changed the scanning state machine: The scan worker is
> scheduled from the scan response handler, and we're checking for scan_channel
> to know if a scan is currently running.
> + Implemented RTS and fragmentation threshold.
> + Use the recently exported cfg80211_find_ie() routine.
>
> In my opinion, the only missing feature (besides some small wext settings) is
> mesh, but I think this patch is ready for wireless-testing.
I'm happy to have libertas support cfg80211. But doesn't this remove
the mesh support that the OLPC guys still use?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2010-02-02 20:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 0:09 [PATCH] libertas: cfg80211 support Samuel Ortiz
2010-02-02 20:36 ` John W. Linville [this message]
2010-02-03 9:31 ` Holger Schurig
2010-02-03 12:04 ` Samuel Ortiz
2010-02-03 15:32 ` Holger Schurig
2010-02-03 20:30 ` Dan Williams
2010-02-04 7:28 ` Holger Schurig
2010-02-04 21:49 ` Dan Williams
2010-02-04 9:52 ` Holger Schurig
2010-02-11 12:01 ` Samuel Ortiz
2010-02-11 12:24 ` Holger Schurig
2010-02-04 10:11 ` Holger Schurig
2010-02-11 12:03 ` Samuel Ortiz
2010-02-04 13:44 ` [PATCH] libertas+cfg80211: better disconnect support Holger Schurig
2010-02-15 10:46 ` [PATCH] libertas: cfg80211 support Holger Schurig
[not found] ` <cdd918981002240005o1fa50956yfb2a692716c06a55@mail.gmail.com>
2010-02-24 23:35 ` Dan Williams
2010-02-25 8:42 ` David MOUSSAUD
2010-02-25 8:48 ` Johannes Berg
2010-02-25 18:05 ` Andrey Yurovsky
2010-03-07 17:32 ` Kalle Valo
2010-03-07 17:52 ` Gábor Stefanik
2010-02-24 8:22 ` David MOUSSAUD
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=20100202203643.GD2967@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=dcbw@redhat.com \
--cc=holgerschurig@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sameo@linux.intel.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).