All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo@kvack.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Dan Williams <dcbw@redhat.com>, Jiri Benc <jbenc@suse.cz>,
	Marcelo Tosatti <marcelo@kvack.org>,
	netdev <netdev@vger.kernel.org>, Jeff Garzik <jgarzik@pobox.com>,
	"John W. Linville" <linville@redhat.com>,
	"Luis R. Rodriguez" <mcgrof@gmail.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: [PATCH] Marvell Libertas 8388 802.11b/g USB driver (v2)
Date: Mon, 22 Jan 2007 09:26:13 -0200	[thread overview]
Message-ID: <20070122112613.GA3038@dmt> (raw)
In-Reply-To: <1169056884.9175.66.camel@johannes.berg>

On Wed, Jan 17, 2007 at 06:01:24PM +0000, Johannes Berg wrote:
> On Wed, 2007-01-17 at 12:43 -0500, Dan Williams wrote:
> 
> > I said "mostly" fullmac.  Sort of like ipw2100 (IIRC) is softmac but it
> > does all the association stuff in firmware.  It doesn't fit fullmac, but
> > it's a lot more fullmac than atheros.  There isn't any management frame
> > processing, it doesn't do any data frame processing.
> 
> Right. I hadn't looked at data frames but suspected this is the case.
> 
> > The 8388 architecture is typical of a thick firmware architecture, where
> > the firmware handles all 802.11 MAC management tasks.  The host driver
> > downloads standard 802.3 frames to the firmware to be transmitted over
> > the link as 802.11 frames.
> > 
> > I thought these 2 things were essentially _the_ definition of fullmac,
> > please correct me if I'm wrong.
> 
> Well we'll need more terms here. I had a short chat with Jouni and we
> agree that what the Marvell card is doing is exposing the MLME
> interface, and what d80211 is doing is implementing most of the MLME.
> 
> I guess the thing I'm saying is that exposing the MLME interface which
> changes fairly frequently is a bad thing and I'd love to have firmware
> that exposes lower level stuff like .
> 
> > Perhaps I just don't understand how flexible d80211 has become; when we
> > last were talking about it 8 months ago, it appears that it could not
> > handle parts that did significant pieces of work in firmware, like the
> > 8388 does.  Do we have the functionality in d80211 yet to handle pieces
> > that are a full mix of hybrid full/soft mac?
> 
> No, we don't have that yet, and we might never have. But I think I'm
> starting to understand the issues at hand a bit better and it seems that
> we'll need cfg80211 to be redefined.

So using the d80211 stack is completly out of question?

Another detail is the way we deal with mesh networking: a separate
device "mshX" is created, and that certainly does not fit d80211?


  reply	other threads:[~2007-01-22 11:31 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-16 18:55 [PATCH] Marvell Libertas 8388 802.11b/g USB driver (v2) Marcelo Tosatti
2007-01-16 19:32 ` Arkadiusz Miskiewicz
2007-01-16 22:41   ` Dan Williams
2007-01-17  7:52 ` Johannes Berg
2007-01-17 18:42   ` Marcelo Tosatti
2007-01-17 23:06     ` Christoph Hellwig
2007-01-18 15:41       ` Dan Williams
2007-01-18 22:40         ` Christoph Hellwig
2007-01-18 22:54           ` Jon Smirl
2007-01-19  3:29             ` Dan Williams
2007-01-19  3:27           ` Dan Williams
2007-01-17 13:11 ` Jiri Benc
2007-01-17 15:01   ` Dan Williams
2007-01-17 15:18     ` Johannes Berg
2007-01-17 17:43       ` Dan Williams
2007-01-17 18:00         ` Dan Williams
2007-01-17 23:09           ` Christoph Hellwig
2007-01-17 23:19             ` Jeff Garzik
2007-01-18  8:22               ` John W. Linville
2007-01-24 15:26                 ` Marcelo Tosatti
2007-01-24 18:52                   ` Dan Williams
2007-01-24 20:13                     ` John W. Linville
2007-01-18 15:40             ` Dan Williams
2007-01-17 18:01         ` Johannes Berg
2007-01-22 11:26           ` Marcelo Tosatti [this message]
2007-01-22 15:20             ` Jon Smirl
2007-01-23 15:41               ` Johannes Berg
2007-01-23 16:18                 ` Jon Smirl
2007-01-23 16:54                   ` Johannes Berg
2007-01-23 17:14                     ` Jon Smirl
2007-01-23 17:38                       ` Johannes Berg
2007-01-23 17:59                       ` Dan Williams
2007-01-23 18:23                         ` Jon Smirl
2007-01-23 18:30                         ` Johannes Berg
2007-01-23 19:01                           ` Jon Smirl
2007-01-23 19:13                           ` Johannes Berg
2007-01-22 11:28           ` Marcelo Tosatti
2007-01-17 18:07         ` Jiri Benc
2007-01-18 15:43           ` Marcelo Tosatti
2007-01-17 15:43     ` Jiri Benc
2007-01-18 15:02       ` Marcelo Tosatti
2007-01-27  1:53 ` Arnd Bergmann
2007-02-03 22:43   ` Marcelo Tosatti
2007-02-05 14:01     ` John W. Linville
2007-02-05 15:12       ` Arnd Bergmann
2007-02-05 15:42       ` Christoph Hellwig
2007-02-06 22:42     ` Marcelo Tosatti
2007-02-10 14:05   ` Marcelo Tosatti
  -- strict thread matches above, loose matches on Subject: below --
2007-01-20 20:15 Marcelo Tosatti
2007-01-20 20:15 Marcelo Tosatti
2007-02-01  0:58 ` Marcelo Tosatti

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=20070122112613.GA3038@dmt \
    --to=marcelo@kvack.org \
    --cc=acme@ghostprotocols.net \
    --cc=arnd@arndb.de \
    --cc=dcbw@redhat.com \
    --cc=jbenc@suse.cz \
    --cc=jgarzik@pobox.com \
    --cc=johannes@sipsolutions.net \
    --cc=linville@redhat.com \
    --cc=mcgrof@gmail.com \
    --cc=netdev@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.