From owner-freebsd-wireless@FreeBSD.ORG Thu Feb 21 04:40:39 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id EFE9EF26 for ; Thu, 21 Feb 2013 04:40:39 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x234.google.com (we-in-x0234.1e100.net [IPv6:2a00:1450:400c:c03::234]) by mx1.freebsd.org (Postfix) with ESMTP id 8D96618F for ; Thu, 21 Feb 2013 04:40:39 +0000 (UTC) Received: by mail-we0-f180.google.com with SMTP id k14so7153156wer.11 for ; Wed, 20 Feb 2013 20:40:38 -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=g24gqajdPzp4IKICn+zZulk1ZWFCWDGxQzEUOtO+Q3Q=; b=NrzEBdIbZL0Wxd0EMaCgc3NDmWD0nXV+cRBs/GF51XqfDPt0HmzYoqxpIIgSjWAlxD jVuGONcD6Chap+pow+u43P3542y3Z66Tx/9BHq+bDi7QKZRyN/jmk3FxaWFFDj2nR3fh jlxpy7U8+enLcW7gMVBHMYrsIGzac32y76KPsiylITxiPvKmo6MyV4T83vFpKCUmRhZX ++nr+RtPvd4FEF0qE/MbBOIqp3Dov2AHsJ7OxBiq4HJ0FXvJeSAhuUstQR5TQ2Oa4dIc ZD3/kJWHxW0x1au8U4KBYC3IlatoDwe4uAdtCTVs3quNwOBgssCGNWIxBHssbEoavEK2 pkdg== MIME-Version: 1.0 X-Received: by 10.180.79.227 with SMTP id m3mr35055377wix.12.1361421638819; Wed, 20 Feb 2013 20:40:38 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.236.88 with HTTP; Wed, 20 Feb 2013 20:40:38 -0800 (PST) In-Reply-To: References: Date: Wed, 20 Feb 2013 20:40:38 -0800 X-Google-Sender-Auth: ttlXz6g3jw2eTw7UvyNQT91tE7A Message-ID: Subject: Re: negotiating HT params at assoc in sta mode From: Adrian Chadd To: PseudoCylon Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Feb 2013 04:40:40 -0000 On 20 February 2013 20:38, PseudoCylon wrote: >> Who can we rope in to review whether this is being done "right" ? > > Since it is ht param issue, anyone with 11n capable hardware with > working driver, or anyone with an AP which can tell Tx'd ampdu packets > are smaller than what the station has asked for. > > run(4) still generates lots of Rx errors. I cannot tell if the patch > does any good. I can only tell the AP does receive the driver defined > ht param, now. When doing aggregation? Try upping the ampdu density to something like 8 or 16 microseconds, maybe it needs more spacing between frames. What are you using as a transmitter in your run(4) tests? Thanks, Adrian