From: Marcelo Tosatti <marcelo@kvack.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Marcelo Tosatti <marcelo@kvack.org>,
netdev <netdev@vger.kernel.org>, Jeff Garzik <jgarzik@pobox.com>,
"John W. Linville" <linville@redhat.com>,
Dan Williams <dcbw@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, 17 Jan 2007 16:42:04 -0200 [thread overview]
Message-ID: <20070117184204.GA3899@dmt> (raw)
In-Reply-To: <1169020333.9175.15.camel@johannes.berg>
On Wed, Jan 17, 2007 at 07:52:13AM +0000, Johannes Berg wrote:
> On Tue, 2007-01-16 at 16:55 -0200, Marcelo Tosatti wrote:
>
> > _Please_ review, this driver is targeted for mainline inclusion.
> >
> > There have been almost no comments resulting from the first submission.
>
> We had looked over the previous version a few days ago and noticed that
> the biggest part of the code is a mostly generic wireless stack that
> you're including along with the driver, essentially all the wlan_*
> files. I don't think that's going to fly.
How come is it a generic wireless stack? As Dan mentioned, the driver is
large, but the wireless stack is _inside_ the firmware.
It does not implement a wireless stack. Its simply an interface to the
firmware.
And using the Marvell provided firmware is a requirement for OLPC
machines, where the CPU will be shut down but the chip+firmware will
continue to forward packets in the mesh network (there are extreme power
saving constraints on these machines).
Quoting Dan Williams, who quoted the device documentation:
"This basic architecture is typical of a thick firmware architecture,
where the WLAN firmware handles all 802.11 MAC Management tasks."
"The host driver downloads standard 802.3 frames to the firmware to
transmit over the wireless link as 802.11 frames."
So it really looks like a fullmac chip, although it might require higher
interaction from the driver part, in comparison with IPW.
Its also important to note, regarding the size in LOC, that the driver
implements most of the firmware/chip configuration knobs, and there are
a _lot_ of them, unlike smaller in-tree drivers. (ie. the driver is
highly configurable). See the README file for a list.
> Also a bunch of minor things but I'd rather look over this version again
> before commenting on that.
Please go ahead and comment on all minor issues you see so we can fix
them.
next prev parent reply other threads:[~2007-01-17 18:45 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 [this message]
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
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=20070117184204.GA3899@dmt \
--to=marcelo@kvack.org \
--cc=acme@ghostprotocols.net \
--cc=arnd@arndb.de \
--cc=dcbw@redhat.com \
--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 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).