public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Marcelo Tosatti <marcelo@kvack.org>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	Jeff Garzik <jgarzik@pobox.com>,
	Christoph Hellwig <hch@infradead.org>,
	Johannes Berg <johannes@sipsolutions.net>,
	Jiri Benc <jbenc@suse.cz>, netdev <netdev@vger.kernel.org>,
	"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: Wed, 24 Jan 2007 13:52:35 -0500	[thread overview]
Message-ID: <1169664755.14073.2.camel@localhost.localdomain> (raw)
In-Reply-To: <20070124152638.GC3036@dmt.poa.virtua.com.br>

On Wed, 2007-01-24 at 13:26 -0200, Marcelo Tosatti wrote:
> On Thu, Jan 18, 2007 at 03:22:50AM -0500, John W. Linville wrote:
> > On Wed, Jan 17, 2007 at 06:19:07PM -0500, Jeff Garzik wrote:
> > > Christoph Hellwig wrote:
> > > >On Wed, Jan 17, 2007 at 01:00:47PM -0500, Dan Williams wrote:
> > 
> > > >>allows the 8388 to continue routing other laptops' packets over the mesh
> > > >>*while the host CPU is asleep*.
> > > >
> > > >We're not going to put a lot of junk into the kernel just because the OLPC
> > > >folks decide to do odd powermanagment schemes.
> > > 
> > > We're not going to ignore useful power management schemes just because 
> > > they don't fit neatly into a pre-existing category.
> > > 
> > > I think the request to determine how all this maps into MLME is fair, 
> > > though.
> > 
> > Definitely.  Also, I wonder if there was any attempt to evaluate how
> > the ieee80211 (or d80211) code might be extended in order to elimnate
> > the need for some of the libertas wlan_* files?
> 
> The regulatory domain structures, channel information (struct
> ieee80211_channel), HW mode (struct ieee80211_hw_mode) compromised of
> supported channels and rates, and probably a few others in the same
> category. I can't see the possibility of using d80211 as it stands
> (designed for softmac cards dealing with 802.11 packets to/from the OS).
> 
> However, it does not make any sense to use the structures defined by
> d80211 if not effectively using it (we send/receive 802.3 frames to the
> firmware, after all), IMO.
> 
> As discussed on this thread, there is a lot of code to be cleanup up,
> but no structural changes AFAICT. Is there a general agreement on that,
> now?

I pushed for a general "lib80211" sort of thing at the Summit, which I
think was agreed in principle with others like Intel.  We need something
to hold the bits that are common to d80211 and non-softmac drivers.
These include scan result handling, some bits of the regulatory stuff
(at least structures and definitions for allowed channels and txpower in
each domain), and 802.3 <-> 802.11 framing conversion code.  We should
be able to fold more stuff in there as we go along.  But there certainly
will be code that both softmac/d80211 and non-softmac drivers (airo,
ipw2x00, libertas, etc) can share.

Dan



  reply	other threads:[~2007-01-24 18:51 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 [this message]
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
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=1169664755.14073.2.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=acme@ghostprotocols.net \
    --cc=arnd@arndb.de \
    --cc=hch@infradead.org \
    --cc=jbenc@suse.cz \
    --cc=jgarzik@pobox.com \
    --cc=johannes@sipsolutions.net \
    --cc=linville@redhat.com \
    --cc=linville@tuxdriver.com \
    --cc=marcelo@kvack.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox