From: Samuel Ortiz <samuel@sortiz.org>
To: Dave <kilroyd@googlemail.com>
Cc: Matthew Ryan <rudicus@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: Porting AR6K to use cfg80211
Date: Sun, 27 Sep 2009 17:24:21 +0200 [thread overview]
Message-ID: <1254065061.2747.6.camel@sortiz-mobl> (raw)
In-Reply-To: <4ABD2ECE.50501@gmail.com>
Hi Dave,
On Fri, 2009-09-25 at 21:57 +0100, Dave wrote:
> Matthew Ryan wrote:
> > Michael Buesch <mb@...> writes:
> >> On Friday 25 September 2009 19:40:52 Matthew Ryan wrote:
> >>> I was curious if I could get a few expert opinions on if its possible to port
> >>> this driver to use mac80211, and how difficult/ what pitfalls there may be.
> >> The device is fullmac, so it does not require mac80211.
> >> I guess however, ar6k can be ported to use cfg80211.
> >>
> >
> > Do you know of any examples in the source tree which are fullmac, but utilize
> > cfg80211 that I could use as a base to get started?
>
> There are a few fullmac drivers in wireless-testing that use cfg80211. I
> don't think these are in the recently released 2.6.31, but are queued
> for 2.6.32.
At least iwmc3200wifi is in 2.6.31.
Cheers,
Samuel.
> iwmc3200wifi and rndis_wlan are furthest along. orinoco is in the
> process of conversion (it uses cfg80211, but relies on the wext
> compatibility code for a large portion of functionality).
>
>
> Dave.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-09-27 15:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 17:40 Porting AR6K to use cfg80211 Matthew Ryan
2009-09-25 18:05 ` Michael Buesch
2009-09-25 20:25 ` Matthew Ryan
2009-09-25 20:57 ` Dave
2009-09-25 21:06 ` Luis R. Rodriguez
2009-09-25 21:16 ` Luis R. Rodriguez
2009-09-25 21:17 ` Luis R. Rodriguez
2009-09-25 21:25 ` Matthew Ryan
2009-09-27 15:24 ` Samuel Ortiz [this message]
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=1254065061.2747.6.camel@sortiz-mobl \
--to=samuel@sortiz.org \
--cc=kilroyd@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rudicus@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).