From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Zhu Yi <yi.zhu@intel.com>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
"Luis R. Rodriguez" <mcgrof@bombadil.infradead.org>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [Announce] Intel Wireless Multicomm 3200 WiFi driver
Date: Sun, 31 May 2009 15:10:47 +0300 [thread overview]
Message-ID: <1243771847.5248.10.camel@maxim-laptop> (raw)
In-Reply-To: <1243752126.3623.375.camel@debian>
On Sun, 2009-05-31 at 14:42 +0800, Zhu Yi wrote:
> On Sun, 2009-05-31 at 14:27 +0800, Luis R. Rodriguez wrote:
> >
> > What is the 11n configuration on these devices? Do they have 2
> > streams? Or are they just 1 stream?
>
> It has 1x1, 1x2 and 2x2 on for both 20MHz and 40MHz channels. The
> firmware HT support is not quite ready at this point. So we haven't done
> anything 11n related in the driver yet.
I have small question:
This is a fullmac driver, thus if I understand correctly, it behaves on
the outside more like an Ethernet adapter.
This will mean that many things possible with normal softmac card won't
be possible, like sending raw packets, etc...
(and besides I belive that hardware is more or less the same, but more
functionality is pushed down to firmware, and more firmware code equals
to bigger probability of bugs that aren't possible to triage and solve
easily.
Does this device indicate that intel moves away from softmac devices, or
this is a device that will mostly be used in some dedicated market
sector (embedded devices for example)?
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2009-05-31 12:10 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 2:18 [Announce] Intel Wireless Multicomm 3200 WiFi driver Zhu Yi
2009-05-21 2:18 ` [PATCH 1/2] wireless: move some utility functions from mac80211 to cfg80211 Zhu Yi
2009-05-21 2:19 ` [PATCH 2/2] iwmc3200wifi: Add new Intel Wireless Multicomm 802.11 driver Zhu Yi
2009-05-21 2:54 ` Luis R. Rodriguez
2009-05-21 3:13 ` Zhu Yi
2009-05-21 7:12 ` [PATCH 1/2] wireless: move some utility functions from mac80211 to cfg80211 drago01
2009-05-21 7:09 ` Zhu Yi
2009-05-21 9:21 ` Johannes Berg
2009-05-21 13:38 ` John W. Linville
2009-05-21 13:56 ` Johannes Berg
2009-05-21 14:10 ` Gábor Stefanik
2009-05-21 14:41 ` John W. Linville
2009-05-21 14:54 ` Johannes Berg
2009-05-21 9:32 ` Johannes Berg
2009-05-21 11:53 ` Zhu, Yi
2009-05-21 16:10 ` [Announce] Intel Wireless Multicomm 3200 WiFi driver Johannes Berg
2009-05-21 17:54 ` Gábor Stefanik
2009-05-21 17:57 ` Johannes Berg
2009-05-21 18:23 ` Gábor Stefanik
2009-05-26 22:24 ` Luis R. Rodriguez
2009-05-31 2:17 ` Zhu Yi
2009-05-31 6:27 ` Luis R. Rodriguez
2009-05-31 6:42 ` Zhu Yi
2009-05-31 12:10 ` Maxim Levitsky [this message]
2009-05-31 12:20 ` Gábor Stefanik
2009-06-01 1:29 ` Zhu Yi
2009-06-01 22:52 ` Luis R. Rodriguez
2009-06-02 7:36 ` Zhu Yi
2009-06-01 23:00 ` Luis R. Rodriguez
2009-06-02 7:42 ` Zhu Yi
2009-06-02 16:53 ` Luis R. Rodriguez
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=1243771847.5248.10.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@bombadil.infradead.org \
--cc=mcgrof@gmail.com \
--cc=yi.zhu@intel.com \
/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