From owner-freebsd-bugs@FreeBSD.ORG  Fri Feb 22 18:48:50 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 850FF7CF;
 Fri, 22 Feb 2013 18:48:50 +0000 (UTC)
 (envelope-from adrian.chadd@gmail.com)
Received: from mail-we0-x234.google.com (mail-we0-x234.google.com
 [IPv6:2a00:1450:400c:c03::234])
 by mx1.freebsd.org (Postfix) with ESMTP id EA619250;
 Fri, 22 Feb 2013 18:48:49 +0000 (UTC)
Received: by mail-we0-f180.google.com with SMTP id k14so780215wer.39
 for <multiple recipients>; Fri, 22 Feb 2013 10:48:49 -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=y2w/vqcXX45VBne0M+30JkWey5mXDKr+CuNXDv1CQ+k=;
 b=sSCnA9g0DcW33ZLV3420xmiCH2swTZgGkPsozPDZNkfMzXyPi1+IAtPqyJRaytWMB7
 qqVvrrMu8tVFCKtolcYsRBTXYMwrODOcZgsz6CCkuiSK5SOrGPNotRq8yvVAuu7pkl0+
 /MQzRpKeeNPmBPP+CIdn7g3CRzUEDJIbpVmNoIeNSunf+6N/p3215WgSGzXF2galtzG2
 oOeM88RxX5GR/qB13GolGo690tsoGG1/1ldd49J+42uIqFEfPwsZFzmuhisNQWG/2vxn
 U7kOl6WFPFO9gzk8bdFDoPBzuzj8jgjQcwgcxIm5i7oBWj+7iVROt5vw1C8/NNiyOgNf
 YevA==
MIME-Version: 1.0
X-Received: by 10.180.81.2 with SMTP id v2mr36350wix.17.1361558928735; Fri, 22
 Feb 2013 10:48:48 -0800 (PST)
Sender: adrian.chadd@gmail.com
Received: by 10.216.74.194 with HTTP; Fri, 22 Feb 2013 10:48:48 -0800 (PST)
In-Reply-To: <201302221947.24307.bschmidt@techwires.net>
References: <201302180246.r1I2kocv064092@freefall.freebsd.org>
 <201302221933.25718.bschmidt@techwires.net>
 <CAJ-Vmom9sE0dMXCp2Tn=DUFTGhgpH+W2uDHpv5VeDL3+3RgJsw@mail.gmail.com>
 <201302221947.24307.bschmidt@techwires.net>
Date: Fri, 22 Feb 2013 10:48:48 -0800
X-Google-Sender-Auth: KXzFgbhzigmNQFEOYD_TZ1EI8co
Message-ID: <CAJ-VmonXhBfxKMAD4EqhksqOKwVffQeE=JJ+R0qdifwAowcBkA@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:48:50 -0000

Ah, damn. Sorry. I was thinking about the node versus vap
configuration and got confused.

IBSS is the same as the APmode of operation - you advertise what
you're capable of and sending stations just calculate the
MIN(ampdusize) and MAX(ampdudensity) when sending to you. Exactly the
same needs to be done for AP mode.

STA mode should do the same too - it just happens there's only one
node (the AP.)

We have the same issue with 2040, shortgi, stbc, ldpc - ni_htparams
includes what the peer node has, not necessarily what you've
negotiated. So in the ath(4) driver I needed to look at both what _my_
capabilities are _and_ the remote capabilities before I decide whether
to use 40mhz, shortgi, etc.

It'd be shinier if there were some net80211 functions that did this for me.


Adrian