linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jouni Malinen <j@w1.fi>
To: Holger Schurig <holgerschurig@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	"Gábor Stefanik" <netrolller.3d@gmail.com>,
	"Luis R. Rodriguez" <mcgrof@gmail.com>,
	devel@driverdev.osuosl.org,
	linux-wireless <linux-wireless@vger.kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: cfg80211 conversion of all drivers
Date: Fri, 12 Mar 2010 10:02:16 +0200	[thread overview]
Message-ID: <20100312080216.GA18550@jm.kir.nu> (raw)
In-Reply-To: <201003120810.38194.holgerschurig@gmail.com>

On Fri, Mar 12, 2010 at 08:10:37AM +0100, Holger Schurig wrote:
> > I think that is code for "replace it with something based on mac80211"...
> 
> That's not going to happen, hostap + orinoco both work against fullmac chips, 
> which can't send arbitrary packets and therefore no 802.11 management frames.

The Host AP mode in Prism 2/2.5/3 provides for a somewhat special
situation.. It does actually allow sending of (almost) arbitrary packets
and management frames in AP mode. In other words, it should be possible
to create a mac80211-based AP mode driver for Prism 2/2.5/3 to replace
the AP side of the Host AP driver. Whether anyone has enough interest
and time to do that is another question, though.

As far as station functionality is concerned, I would agree that
mac80211 is not a good target for the Host AP driver. If AP side were to
be made available as a mac80211-based driver, it could make more sense
to merge station side from the Host AP driver into orinoco or some kind
of combination of the driver. However, having two different drivers for
same hardware issue would not go anywhere with this.

One of the problems here is that the hardware is question is quite old
and for many practical purposes obsolete, so finding people to work on
this can get difficult. I can certainly come up with much better uses
for my time.. ;-)
 
-- 
Jouni Malinen                                            PGP id EFC895FA

  reply	other threads:[~2010-03-12  8:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-12  1:22 cfg80211 conversion of all drivers Luis R. Rodriguez
2010-03-12  1:56 ` Gábor Stefanik
2010-03-12  2:53   ` John W. Linville
2010-03-12  6:01     ` Gábor Stefanik
2010-03-12  7:10     ` Holger Schurig
2010-03-12  8:02       ` Jouni Malinen [this message]
2010-03-12  8:12         ` Holger Schurig

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=20100312080216.GA18550@jm.kir.nu \
    --to=j@w1.fi \
    --cc=devel@driverdev.osuosl.org \
    --cc=holgerschurig@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mcgrof@gmail.com \
    --cc=netrolller.3d@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).