From owner-freebsd-bugs@FreeBSD.ORG  Fri Feb 22 18:04:41 2013
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id 114C5636;
 Fri, 22 Feb 2013 18:04:41 +0000 (UTC)
 (envelope-from adrian.chadd@gmail.com)
Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com
 [209.85.212.174])
 by mx1.freebsd.org (Postfix) with ESMTP id 5E7A6F68;
 Fri, 22 Feb 2013 18:04:40 +0000 (UTC)
Received: by mail-wi0-f174.google.com with SMTP id hi8so1262182wib.13
 for <multiple recipients>; Fri, 22 Feb 2013 10:04:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:x-received:sender:in-reply-to:references:date
 :x-google-sender-auth:message-id:subject:from:to:cc:content-type;
 bh=Hc1hOOL4PSTiREYhSjMd37w/UJb6wEgmWn5QwyoyNC4=;
 b=pWr395scdwKsi4PjNRgTJzKiA+KPgJQTcMgnnlrCa8rEhXuLhzuI2w7Rrwy3wxlFlV
 FnhvrGWXDS2bm85fFEvfcwNrEedP2Z22WFP1bTot4hoH5AgQUR/wz9uVQNh0nSUMKc0d
 L8eLUHI4D2fetwCXuNO/JAM5aj56AqEQgP/BL9hDhdKDO48DQDNdJY9hZ4n7H7Uy1dB4
 9voLJ87NXCKNcLyLZwEN1E3yiKyQngrCbS29bbLDOIQUkTlSjNoX3h11UrcWZ7VeZFBQ
 vyccEbJFTKcrCHu/xi7Zn9kR0DhjnAjbZOV9HY9wXBRPYqrNSGRv9WgHtE+kF2pzIH4w
 lZhw==
MIME-Version: 1.0
X-Received: by 10.194.238.226 with SMTP id vn2mr5291034wjc.23.1361556279238;
 Fri, 22 Feb 2013 10:04:39 -0800 (PST)
Sender: adrian.chadd@gmail.com
Received: by 10.216.74.194 with HTTP; Fri, 22 Feb 2013 10:04:39 -0800 (PST)
In-Reply-To: <201302221859.31446.bschmidt@techwires.net>
References: <201302180246.r1I2kocv064092@freefall.freebsd.org>
 <201302221859.31446.bschmidt@techwires.net>
Date: Fri, 22 Feb 2013 10:04:39 -0800
X-Google-Sender-Auth: HrDJY4lcOpiPfihEVQ8yJdrDKS0
Message-ID: <CAJ-VmomCtXoDWfpc+-XK-xBFb7dCCzPtrLDMegCT+ZWL1Ye=xQ@mail.gmail.com>
Subject: Re: kern/176201: [net80211] [patch] 11n station includes unrelated ht
 params into ASSOC_REQ packet
From: Adrian Chadd <adrian@freebsd.org>
To: Bernhard Schmidt <bschmidt@techwires.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: freebsd-bugs@freebsd.org, PseudoCylon <moonlightakkiy@yahoo.ca>,
 freebsd-wireless@freebsd.org
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Feb 2013 18:04:41 -0000

Hm, we need to use MIN(rxmax) and MAX(density) regardless, right?

If an AP is transmitting to a STA that has a lower rxmax or higher
density, it should obey that.

The same rules apply for mesh, ibss, tdma operational modes.

So yes, what we should do is:

* initialise rxmax/density with the VAP capabilities
* track what the remote node rxmax/density is
* have a couple of functions that return the density and rxmax based
on the destination node and current VAP config
* teach the 11n drivers to use that.

Thanks,

Adrian