From owner-freebsd-wireless@FreeBSD.ORG Sat Apr 9 09:36:42 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 69D091065674 for ; Sat, 9 Apr 2011 09:36:42 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 00BC48FC16 for ; Sat, 9 Apr 2011 09:36:41 +0000 (UTC) Received: by wyf23 with SMTP id 23so4223596wyf.13 for ; Sat, 09 Apr 2011 02:36:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:date:x-google-sender-auth :message-id:subject:from:to:content-type; bh=rVa/WrYPRCcXVzOS0fd1pjIZNTyOt9ksZCYMaFDDY8o=; b=m2tR1MYQJqGsaOPI5cVgkXJtHqGdWotBOu/x7gJgek7QinUQ1FDq4vr5ZvEiN2G8iu YXCsaoYB7G3bXTfhkVhneqnCo0HFkNwjk1QJsAc3evctdxKfGGktn12JxKTZ9B84GPtX Byqk7EyeRdw1OSp3sOTAy+DlsjoJN/CMqnzco= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=sbLQ45BmBdpBZTSx0VLAZaOUPSv+9DKWxSus2sXy/bAvaqw4G0HLtNFODPghFh6IXK GMFpMN+HC1tgwFxrDhmNQmXLp+MBv5zA1ugX/j4/AjGMWLGq+KNp5AKlIrov97K9ESB8 fRkXSzrABPnG5JfX+mPJbEBvQbCMsq4sCksNc= MIME-Version: 1.0 Received: by 10.227.0.140 with SMTP id 12mr3140402wbb.122.1302341800892; Sat, 09 Apr 2011 02:36:40 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.227.132.199 with HTTP; Sat, 9 Apr 2011 02:36:40 -0700 (PDT) Date: Sat, 9 Apr 2011 17:36:40 +0800 X-Google-Sender-Auth: P3wL1hvyuPrziVqbZ_unm5Xjj9I Message-ID: From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: net80211 - my short-term feature list(s) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Sat, 09 Apr 2011 09:36:42 -0000 Hi everyone, I'd like to just jot down what I'm planning on squeezing into net80211 before 9.0-RELEASE occurs. I'd appreciate it if others would comment and add to this list. Regulatory stuff: * Survey what's going on with the atheros regulatory stuff and what's supported by net80211 * Bring unity to this stuff * Look at some better userland exposure to the regulatory database TX stuff: * Per-rate TX power support * Better integration with the driver to communicate what -exactly- is being programmed into the hardware, versus just the regulatory limit (since they may be different) * Extend net80211's rate control stuff to support multi-rate retry * Port ath_rate_sample to net80211 * Extend the net80211 rate control modules to (initially) support MCS rates 802.11n stuff: * Look at what's needed for coding up TX aggregation, even if it's just a placeholder per-TID struct pointer so ABI isn't changed after 9.0-RELEASE is tagged. Misc stuff: * Survey support - store per-channel busy statistics - percentage time spent TX, RX, channel busy, ext channel busy (when doing HT/40) * EVM support (even if it's just from the if_ath driver, I don't know of any other chipsets that export EVM statistics) Adrian