All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Chan <robert.chan.list@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Progress on Ath9k HT support on Adhoc mode
Date: Wed, 29 Dec 2010 15:21:13 +0800	[thread overview]
Message-ID: <B8B45CB92F5145C6A2B5466AC24D0869@PatrickAsus> (raw)
In-Reply-To: <1293605549.30342.8.camel@jm-desktop>

Hi Jouni and Mohammed,

Thanks very much for the quick reply.

As I am implementing a project that requires a 802.11N mesh network at low 
(or zero actually, for a poor area deployment) budget.  May I ask what is 
the progress in that end (mesh over 11N)?  Or if I want to jump in, which 
part of the code should I begin with (of course I really doubt I could do 
much all by myself, but I will try to probably help out)?

Thanks very much again in advance.

Regards,

Robert

--------------------------------------------------
From: "Jouni Malinen" <jouni.malinen@atheros.com>
Sent: Wednesday, December 29, 2010 2:52 PM
To: "Mohammed Shafi" <shafi.ath9k@gmail.com>
Cc: "Robert Chan" <robert.chan.list@gmail.com>; 
<ath9k-devel@lists.ath9k.org>
Subject: Re: [ath9k-devel] Progress on Ath9k HT support on Adhoc mode

> On Tue, 2010-12-28 at 22:32 -0800, Mohammed Shafi wrote:
>> On Wed, Dec 29, 2010 at 11:40 AM, Robert Chan
>> <robert.chan.list@gmail.com> wrote:
>> > So should I assume that the details here are "too updated" or are the 
>> > modes
>> > above are only independently supported (but not able to work together 
>> > such
>> > as IBSS + N + mesh)?
>
> The modes in that table should be considered independent and support for
> 802.11n in the table should really be read as at least one of the modes
> supporting it, not all modes supporting it. So no, that does not mean
> that either IBSS or mesh would support 802.11n (AP and station modes
> do).
>
>> I think 'mesh mode' also handled in mac80211 , if mesh mode is
>> supported with 11n then ibss(which is a sub-set ?) should have 11n
>> support.
>
> Mesh and IBSS are independent modes and both will need to be
> independently addressed for 802.11n support. In addition, both of them
> have protocol limitations on which 802.11n HT features can be supported.
> Finally, HT support for either mode is not yet complete in mac80211 and
> as such, cannot be complete with ath9k either.
>
> - Jouni
>
>
> 

  parent reply	other threads:[~2010-12-29  7:21 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-03  5:30 [ath9k-devel] Progress on Ath9k HT support on Adhoc mode Peizhao Hu
2010-12-03  6:51 ` Mohammed Shafi
2010-12-09 12:36 ` Alexander Simon
2010-12-09 18:55   ` Luis R. Rodriguez
2010-12-22  8:25   ` Robert Chan
2010-12-29  6:10     ` Robert Chan
2010-12-29 20:20       ` Brian Prodoehl
2010-12-29  6:10     ` Robert Chan
2010-12-29  6:32       ` Mohammed Shafi
2010-12-29  6:52         ` Jouni Malinen
2010-12-29  7:00           ` Mohammed Shafi
2010-12-29  7:21           ` Robert Chan [this message]
2010-12-29  8:30             ` Jouni Malinen
2011-01-19 13:42     ` Alexander Simon
2011-02-04  3:04       ` Peizhao Hu
2011-02-04  5:27         ` Mohammed Shafi
2011-02-08  3:38           ` Peizhao Hu
2011-02-10 14:07             ` Mohammed Shafi
2011-01-28  8:58 ` bcoll
2011-02-08 16:00 le thanh son
2011-02-10 12:04 Baldomero Coll
2011-02-10 14:11 ` Mohammed Shafi
2011-02-10 16:45   ` Baldomero Coll
2011-02-11 10:24     ` Mohammed Shafi
2011-02-15  9:05 Baldomero Coll
2011-02-15  9:10 ` Sagar Bijwe
2011-02-16  0:10   ` Peizhao Hu
2011-02-16 12:16 ` Mohammed Shafi
2011-02-16 14:47   ` Baldomero Coll
2011-02-16 16:46     ` Brian Prodoehl
2011-02-17  9:05       ` Baldomero Coll
2011-02-16 17:03     ` Adrian Chadd
2011-02-17  9:27       ` Baldomero Coll
2011-02-17 16:11         ` Adrian Chadd
2011-02-18 18:49 Baldomero Coll
2011-03-07 21:49 ` Xianghua Xiao
2011-03-08  5:25 ` Mohammed Shafi
2011-03-10  8:41 Baldomero Coll
2011-03-22 10:13 Baldomero Coll

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=B8B45CB92F5145C6A2B5466AC24D0869@PatrickAsus \
    --to=robert.chan.list@gmail.com \
    --cc=ath9k-devel@lists.ath9k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.