From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Dan Williams <dcbw@redhat.com>
Subject: Re: [RFC] libertas: monster-patch to make CFG/WEXT configurable
Date: Tue, 20 Oct 2009 08:35:35 +0200 [thread overview]
Message-ID: <200910200835.35747.hs4233@mail.mn-solutions.de> (raw)
In-Reply-To: <1255998802.4475.2.camel@johannes.local>
> I really don't understand the point. Can't you just use the
> cfg80211 hooks and keep both functional at the same time? Just
> like orinoco does it uses cfg80211 only partially.
I think I can't do this in a sane way.
Oh, and please don't compare libertas all the time with orinoco.
Orinoco is FULLMAC, libertas is HALFMAC.
Because libertas firmware doesn't roam, it has to be done in
software. Libertas does this in assoc.c, partly in scan.c, cmd.c
and wext.c and even main.c. For example, libertas keeps its own
list of BSS entries, has code to select the best matching BSS
when it comes to associating ... things like this.
cfg80211 has this code too.
Having two competing implementations running in one driver is a
way to havoc.
I could keep "old" stuff of the libertas in, e.g. monitor
mode --- but then it's not too difficult to use .change_intf()
to add monitor mode to cfg80211.
I can't and won't do the MESH stuff: I don't have a firmware that
does MESH, no knowledge and usage case for MESH. It would,
however, be possible to keep the current mesh code with WEXT and
use cfg80211 for monitor/station mode. However, I dislike this
more than cfg80211/wext configurability.
--
http://www.holgerschurig.de
next prev parent reply other threads:[~2009-10-20 6:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-19 12:49 [RFC] libertas: monster-patch to make CFG/WEXT configurable Holger Schurig
2009-10-20 0:33 ` Johannes Berg
2009-10-20 6:35 ` Holger Schurig [this message]
2009-10-22 8:31 ` Johannes Berg
2009-10-23 15:38 ` Holger Schurig
2009-10-23 16:27 ` Dan Williams
2009-10-21 18:36 ` Dan Williams
2009-10-21 18:39 ` Dan Williams
2009-10-22 9:28 ` Holger Schurig
2009-10-22 15:31 ` Dan Williams
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=200910200835.35747.hs4233@mail.mn-solutions.de \
--to=hs4233@mail.mn-solutions.de \
--cc=dcbw@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.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.