From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Michael Wu <flamingice@sourmilk.net>,
Mohamed Abbas <mabbas@linux.intel.com>,
netdev@vger.kernel.org
Subject: Re: 3945 driver using d80211
Date: Wed, 9 Aug 2006 10:50:47 -0400 [thread overview]
Message-ID: <20060809145042.GA2570@tuxdriver.com> (raw)
In-Reply-To: <44D99558.1000507@sipsolutions.net>
On Wed, Aug 09, 2006 at 09:57:12AM +0200, Johannes Berg wrote:
> Michael Wu wrote:
> >I think it would be best if you made the firmware not be aware of a
> >connection, and let the d80211 code take care of all the
> >scanning/authenticating/associating. Of course, I know nothing about 3945,
> >so I don't know if that's possible.
> >
> Please not, for now. We need someone pushing for fullmac features in
> d80211, we need those anyway for embedded systems that can't afford
> running all of it on the main CPU. While obviously Intel would benefit
> from doing this since a lot more d80211 features would come available,
> the greater good would be having a main-stream card that someone cares
> about and helps making d80211 full-mac capable.
I second this opinion. It would be good to make d80211 more capable
of dealing with these cards.
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2006-08-09 14:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 21:27 3945 driver using d80211 Mohamed Abbas
2006-08-08 21:40 ` Michael Wu
2006-08-09 7:57 ` Johannes Berg
2006-08-09 14:50 ` John W. Linville [this message]
2006-08-09 16:47 ` Michael Wu
2006-08-09 17:26 ` Christoph Hellwig
2006-08-09 19:22 ` Dan Williams
2006-08-09 21:07 ` Mohamed Abbas
2006-08-09 21:32 ` Simon Barber
2006-08-09 21:41 ` Simon Barber
2006-08-09 22:42 ` Michael Wu
2006-08-09 0:06 ` Jouni Malinen
2006-08-09 15:49 ` Jouni Malinen
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=20060809145042.GA2570@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=flamingice@sourmilk.net \
--cc=johannes@sipsolutions.net \
--cc=mabbas@linux.intel.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).