linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Leffler <sam@errno.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Li YanBo <dreamfly281@gmail.com>,
	Patrick Ziegler <patrick.ziegler@fh-kl.de>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: 802.11n drivers
Date: Sat, 29 Sep 2007 09:11:24 -0700	[thread overview]
Message-ID: <46FE792C.6000803@errno.com> (raw)
In-Reply-To: <1191055790.22960.39.camel@johannes.berg>

Johannes Berg wrote:
> On Sat, 2007-09-29 at 10:09 +0800, Li YanBo wrote:
>
>   
>> The Airgo chipset is a pre-n product, and the feature to support
>> standard 802.11n hasn't been implement yet. we will try to see whether
>> it can be used to support 80211n later. but if anything I can help you
>> now, I'd glad to do.
>>     
>
> Oh, ok, do you know what's different between the pre-N implemented by
> this chip and standard-N (say draft 2.0 or so)?
>   

I am aware of 3 flavors: pre-N (pre 802.11 working group, like Airgo), 
D1.x 11n, D2.x 11n.  Getting D1.x and D2.x cards to interop isn't a big 
deal (at least at some reduced level of operation).  Several things make 
this confusing:

1. retail labeling is unclear
2. chips are being rev'd quickly so retail products are typically out of 
date
    before they hit the shelves
3. 11n isn't ratified so in the meantime various groups have defined 
test plans
    for interop and compliance w/ one plan doesn't necessarily mean you
    interop w/ the other(s)

Now is definitely the time to be doing 11n.  There is significant effort 
getting up to speed on all that is involved.

    Sam


  parent reply	other threads:[~2007-09-29 16:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-28 12:47 802.11n drivers Patrick Ziegler
2007-09-28 15:03 ` Johannes Berg
2007-09-29  2:09   ` Li YanBo
2007-09-29  8:49     ` Johannes Berg
2007-09-29  9:29       ` Li YanBo
2007-09-29 16:11       ` Sam Leffler [this message]
2007-10-01  9:14   ` Patrick Ziegler

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=46FE792C.6000803@errno.com \
    --to=sam@errno.com \
    --cc=dreamfly281@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=patrick.ziegler@fh-kl.de \
    /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).