From owner-freebsd-wireless@FreeBSD.ORG Sun Oct 6 09:01:27 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9961B2A0 for ; Sun, 6 Oct 2013 09:01:27 +0000 (UTC) (envelope-from sven@hazejager.nl) Received: from mail-qa0-f41.google.com (mail-qa0-f41.google.com [209.85.216.41]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5E4FB2F73 for ; Sun, 6 Oct 2013 09:01:26 +0000 (UTC) Received: by mail-qa0-f41.google.com with SMTP id ii20so2218072qab.7 for ; Sun, 06 Oct 2013 02:01:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=ysYsX2/O4aEzBr+zKDA5qNL5KYnFHGocdUK8lXaPlmI=; b=BTCqQXGqOOoKf6+ck1ZONV+MrLz+oDHnSLTjLFq6sGxNEacSqBAwGKWbLbT65qnxor rd2u9PSsc6SHC9dpRDib6pljhlnIRCNT+6JbXuhw/LCmNfhDftQt0L0k+rL8XWYeKq4+ 8WCiYcnsDD192SO9211HtxVZE528yfk4zTSMyTV4zhWhLoLFu4emmle9CObDVVp0NGQo 20RL1k+tutK/R/9YEfqmI21slfhbnN1XllP9R7GKsuQoWRH4d3Lf+0ZSLm+K0mcpjLsl 5UwcrE2K6JOxbRopHcK16MXoPf9YpFZQjKziEf03VwP+GoldtxgM7R5nA9NAHwCMe1JB y4tA== X-Gm-Message-State: ALoCoQn9l7Z+LgSvw20k8/Cyb//uLsBDD9T2ZFjAPX+0U8x8tC1+iblryA8JOYZMJfLMNGA0WCVD MIME-Version: 1.0 X-Received: by 10.224.89.73 with SMTP id d9mr20284944qam.5.1381049597969; Sun, 06 Oct 2013 01:53:17 -0700 (PDT) Received: by 10.49.118.2 with HTTP; Sun, 6 Oct 2013 01:53:17 -0700 (PDT) X-Originating-IP: [212.123.177.47] Date: Sun, 6 Oct 2013 10:53:17 +0200 Message-ID: Subject: From AR9160 to AR9340/AR9582 From: Sven Hazejager To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Sun, 06 Oct 2013 09:01:27 -0000 Does anyone know enough about the various Atheros devices to tell me the differences between various radios, output power, sensitivity and expected range? For various reasons, I am thinking of replacing my present FreeBSD ALIX router by a COTS OpenWRT router such as the TP-Link WDR3600. Current hardware is a WNC DNMA-83 AR9160 chipset and I'm only using 2.4GHz. The TP-Link has a AR9340 for 2.4GHz and a AR9582 for 5GHz. I read somewhere that it seems to be capped at 63 mW / 18 dBm (for 5GHz at least)... I wonder if this is better or worse than my current setup. Thanks for any insights! Sven From owner-freebsd-wireless@FreeBSD.ORG Sun Oct 6 09:03:51 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6EBD62CE for ; Sun, 6 Oct 2013 09:03:51 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qe0-x22d.google.com (mail-qe0-x22d.google.com [IPv6:2607:f8b0:400d:c02::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2F7552F82 for ; Sun, 6 Oct 2013 09:03:51 +0000 (UTC) Received: by mail-qe0-f45.google.com with SMTP id 8so1422501qea.18 for ; Sun, 06 Oct 2013 02:03:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=Zla3fxqNIzwMXatDTuTgXkCzVpmcOpF4Lmoc0jBiDB0=; b=tTmkw6KrPx0ej9NN6QPs4Aha8JabAYuy/eH2VDmgxdhhbZHHveswYFQPnSL06Tabdu N+WRVaIupYBqh7pYPl/x1e/2nJBppNB9x7ETV4wMHrnJbmz1iGq2GQljadzdQ/CPh9+a K3ZI/pA//MCrEIotu2gqKevKdJIWL5cEynD7+9XVi6t9CZI+TweS6v1gBYX8SFfRLPkW BDMELlxp2r5lWdmxpATJyk+j7VcMSZid+eyah8EsKE+/npMJwZIQJwrjP8qk6yZMdRPv RWo0S33pH8Nqgl+v2bikdJ6y3CCVNPXaDt1iW9/j54/Pa/JMevQnIca64z6ul4BAbgPG vNMw== MIME-Version: 1.0 X-Received: by 10.224.8.136 with SMTP id h8mr200804qah.99.1381050230322; Sun, 06 Oct 2013 02:03:50 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Sun, 6 Oct 2013 02:03:50 -0700 (PDT) In-Reply-To: References: Date: Sun, 6 Oct 2013 02:03:50 -0700 X-Google-Sender-Auth: BpAi5hOmcqgq57l4gkfd5LpO5iA Message-ID: Subject: Re: From AR9160 to AR9340/AR9582 From: Adrian Chadd To: Sven Hazejager Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Sun, 06 Oct 2013 09:03:51 -0000 hi, a lot of it has to do with what the manufacturer attaches to the chip. The chip itself may only be able to put out 18dBm at the lowest transmit rate and significantly less (12-14dBm) at the highest transmit rate. The manufacturer may then opt to add extra output amplifiers :) (Also, I'm doing the FreeBSD port to the AR9340 now, in my spare time. Watch this space!) -adrian On 6 October 2013 01:53, Sven Hazejager wrote: > Does anyone know enough about the various Atheros devices to tell me the > differences between various radios, output power, sensitivity and expected > range? > > For various reasons, I am thinking of replacing my present FreeBSD ALIX > router by a COTS OpenWRT router such as the TP-Link WDR3600. > > Current hardware is a WNC DNMA-83 AR9160 chipset and I'm only using 2.4GHz. > > The TP-Link has a AR9340 for 2.4GHz and a AR9582 for 5GHz. I read somewhere > that it seems to be capped at 63 mW / 18 dBm (for 5GHz at least)... I > wonder if this is better or worse than my current setup. > > Thanks for any insights! > > Sven > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org > " > From owner-freebsd-wireless@FreeBSD.ORG Mon Oct 7 11:06:55 2013 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6C2AE919 for ; Mon, 7 Oct 2013 11:06:55 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4D3A42850 for ; Mon, 7 Oct 2013 11:06:55 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r97B6tIk077910 for ; Mon, 7 Oct 2013 11:06:55 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r97B6sqH077908 for freebsd-wireless@FreeBSD.org; Mon, 7 Oct 2013 11:06:54 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 7 Oct 2013 11:06:54 GMT Message-Id: <201310071106.r97B6sqH077908@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-wireless@FreeBSD.org Subject: Current problem reports assigned to 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: Mon, 07 Oct 2013 11:06:55 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/181898 wireless [iwn] [patch] Centrino Advanced-N 6235 with latest iwn o kern/181694 wireless [iwn] [patch] Initialize hardware in iwn(4) resume cod o kern/181161 wireless [wl] config a old compaq wl-110 wireless card make ker o kern/181132 wireless [iwn] stream calculation is wrong for the Intel 4965 o kern/181100 wireless [bwi] Turning up bwi0 crashes / deadlocks the kernel o kern/180816 wireless [iwl] Intel Centrino Wireless-N 2200 not supported o kern/179847 wireless [ath] [patch] Update regdomain in ath drivers includin o kern/179709 wireless [ath] Atheros 5212 does not work: stuck beacon; resett o kern/179547 wireless [ath] Add AR9485 custom board fixes (CUS198) o kern/179482 wireless [ath] [patch] Fix AR9462 external LNA configuration o kern/179269 wireless [ath] [AR9285] RX antenna diversity is not functioning o kern/179232 wireless [ath] panic in ath o kern/178986 wireless [ath] Change mac address of ath(4) is not reflected wh o kern/178492 wireless [ath] ath0 (AR9287) panic o kern/178491 wireless [ath] ath0 (AR9287) stuck beacon o kern/178477 wireless [ath] missed beacon / soft reset in STA mode results i o kern/178470 wireless [panic][ath] bss vap can and does change o kern/178411 wireless [ral] [panic] FreeBSD kernel crash in rt2860 o kern/178379 wireless [net80211] [ath] WPA rekey on the STA side fails when o kern/178378 wireless [net80211] crypto state isn't reset during a reassocia o kern/178263 wireless [ath] review the use of ic_freq / ic_ieee / ic_flags / o kern/177847 wireless [ath] With TPC enabled, TX power values aren't clamped o kern/177846 wireless [ath] [net80211] net80211 TX power limit isn't correct o conf/177688 wireless WiFi regodmains information is inconsistent between "e o kern/177530 wireless [ath] ath driver isn't 32 bit int clean o kern/177465 wireless [iwn] 20%-100% packet loss with iwn driver o kern/177451 wireless [ieee80211] page fault in ieee80211_tx_mgt_timeout o kern/176238 wireless [ath] [patch] Correct buffer size calculation and simp o kern/176201 wireless [net80211] [patch] 11n station includes unrelated ht p o kern/176104 wireless [iwn] iwn0: iwn_intr: fatal firmware error o kern/175722 wireless [ath]lot of bad seriesx hwrate in kernel messages o kern/175446 wireless [ath] high volumes of PHY errors lead to BB/MAC hangs o kern/175227 wireless [ath] beacon timers aren't necessarily reprogrammed af o kern/175183 wireless [iwn] iwn(4) becomes unresponsive during initial confi o kern/175053 wireless [iwn] iwn firmware error on 9-stable with Ultimate-N 6 o kern/174891 wireless [ieee80211] struct ieee80211_node is freed during acti o kern/174722 wireless [wlan] can't use channel 12 and 13 (14) with my wifi i o kern/174661 wireless [wlan] lost alias on wlan interface o kern/174283 wireless [net80211] panics in ieee80211_ff_age() and ieee80211_ o kern/174276 wireless [ath] if_ath memory modified after free o kern/174273 wireless [net80211] taking down a net80211 node with active fas o kern/173917 wireless [iwn] wpa-supplicant issues on iwn o kern/173898 wireless [iwn] [patch] iwn(4) DOES support 6235 chip. o kern/173883 wireless [ath] ath0: unable to attach - pci issue? o kern/173711 wireless [ath] powerd kills ath on the Asus EeePC 1005HA o kern/173342 wireless PS-Poll isn't working o kern/173336 wireless [ath] Atheros card improper device poweroff handling o o kern/172955 wireless [ath] 11n does not work in adhoc mode o kern/172706 wireless [wpi] wpi0 fails to load firmware when using country o kern/172672 wireless [ubt] Bluetooth device recognised but not working o kern/172661 wireless hostapd(8) securing wireless adapter in HostAP mode is o kern/172338 wireless [ath] [net80211] CCMP IV transmit counters are not cor o kern/171598 wireless [ath] TP-Link TL-WN951N W-LAN PCI Adapter 300 MBit stu o kern/171235 wireless [ath] ath loses connection, system freezes on netif re o kern/170889 wireless [ath] ath driver uses some uninitilized memory o kern/170620 wireless [ath] LOR and deadlock when multiple vaps are used o kern/170573 wireless [iwi] Intel 2200BG iwi NIC hangs with need multicast c o kern/170513 wireless [ath] ath logs: ath_tx_aggr_comp_aggr: AR5416 bug: o kern/170433 wireless [ath] TX hang after a stuck beacon message with active o kern/170411 wireless [ath] Uninitialized variables in if_ath.c o kern/170397 wireless [ath] [patch] Uninitialized variables in ah_eeprom_928 o kern/170302 wireless [ath] 802.11n frames are not being transmitted with mu o kern/170281 wireless [ath] 802.11n locks up on aggregation setup (ampdutx) o kern/170098 wireless [ath] [net80211] VAPs (Virtual access points) with Ath o kern/170066 wireless [ral] ral(4) rt61pci Linksys freezes the machine as so o kern/169432 wireless [ath] BAR TX hang when aggregation session is reset du p kern/169362 wireless [ath] AR5416: radar pulse PHY errors sometimes include o kern/169336 wireless [ath] ANI isn't triggering in a busy/noisy environment o kern/169199 wireless [ath] Cannot set up static ip addresses for wireless w o kern/169084 wireless [ath] suspend/resume doesn't cause a rescan; the assoc o kern/168530 wireless [ath] Broken WEP probably o kern/168393 wireless AR9285: suspend/resume sometimes fails o kern/168170 wireless [net80211] ieee80211_send_bar() doesn't complete corre o kern/167870 wireless [ath] adhoc wifi client does not join an existing IBSS o kern/167834 wireless [ath] kickpcu; 'handled 0 packets' o kern/167828 wireless [iwn] iwn(4) doesn't recover automatically after firmw o kern/167798 wireless ifconfig(8): problem with "ifconfig list scan" command o kern/167491 wireless [ath] TID != hardware queue TID in ath_tx_aggr_comp_ag o kern/167113 wireless [ath] AR5210: "stuck" TX seems to be occuring, without o kern/167080 wireless [ath] channel switch on another VAP break channel setu o kern/166684 wireless [ath] [net80211] mgmtrate/mcastrate isn't updated base p kern/166642 wireless [ieee80211] [patch] in 802.11n mode for FreeBSD AP, ha o kern/166641 wireless [ieee80211] [patch] mbuf/cluster leak in AP mode in 80 p kern/166357 wireless [ath] 802.11n TX stall when the first frame in the BAW o kern/166286 wireless [net80211] [ath] initial switch to HT40 isn't causing p kern/166190 wireless [ath] TX hangs and frames stuck in TX queue o kern/166086 wireless [Patch][ath] Reflect state of rfkill switch in a sysct o kern/165969 wireless [ath] Slower performance in adhoc mode vs Client/AP mo o kern/165966 wireless [ath] ath0: device timeout on SMP machines due to race o kern/165895 wireless [ath] overly busy cabq can tie up all tx buffers o kern/165870 wireless [bwn] bwn driver does not attach on HP Pavilion dv9420 o kern/165866 wireless [ath] TX hangs, requiring a "scan" to properly reset t o kern/165849 wireless [ath] [hang] network ath driver freeze o kern/165595 wireless [ipw] ipw(4): Can't load firmare for ipw2200bg o kern/165543 wireless [ath] ath0 endless scanning of channels without connec o kern/165517 wireless [net80211] bgscan isn't triggered when invalid beacons o kern/165475 wireless [ath] operational mode change doesn't poke the underly o kern/165382 wireless [kernel] taskqueue_unblock doesn't unblock currently q o kern/165306 wireless [ath] race conditions between scanning and beacon time o kern/165220 wireless [ath] "ath_rx_tasklet: sc_inreset_cnt > 0; skipping" m o kern/165214 wireless [ieee80211] Kernel panic in ieee80211_output.c:2505 o kern/165212 wireless [ath] No WiFi on Acer Aspire One 751h (Atheros AR5BHB6 o kern/165149 wireless [ath] [net80211] Ping with data length more than iv_fr o kern/165146 wireless [net80211] Net802.11 Fragment number is assigned 1 (sh o kern/165060 wireless [ath] vap->iv_bss race conditions causing crashes insi o kern/165021 wireless [ath] ath device timeout during scan/attach, if wlan_c o kern/164721 wireless [ath] ath device timeouts o kern/164382 wireless [ath] crash when down/deleting a vap - inside ieee8021 o kern/164365 wireless [iwi] iwi0: UP/DOWN in o bin/164102 wireless hostapd not configured for 802.11n o kern/163759 wireless [ath] ath(4) "stops working" in hostap mode o kern/163724 wireless [mwl] [patch] NULL check before dereference o kern/163719 wireless [ath] ath interface do not receive multicast o kern/163689 wireless [ath] TX timeouts when sending probe/mgmt frames durin o kern/163574 wireless [net80211] overly-frequent HT occupancy changes o kern/163573 wireless [ath] hostap mode TX buffer hang o kern/163559 wireless [ath] kernel panic AH_DEBUG o kern/163318 wireless [ath] ath(4) stops working p kern/163312 wireless [panic] [ath driver] kernel panic: page fault with ath o kern/163237 wireless [ath] AR5416 as HostAP. Delays among clients when a cl o kern/163082 wireless [ath] ar9285 diversity fixes o kern/162648 wireless [ath] AR9227 ADC DC calibration failure o kern/162647 wireless [ath] 11n TX aggregation session / TX hang o kern/161293 wireless [iwn] hang at startup when starting network o kern/161035 wireless [ieee80211] Incorrect number describing 11ng MCS rate o kern/160391 wireless [ieee80211] [patch] Panic in mesh mode o kern/160296 wireless [zyd] [panic] 802.11 usb device reboots system on 'ifc o misc/160176 wireless [mips] [panic] Kernel panic on AR7161 platform with AR o kern/157449 wireless [ath] MAC address conflict causes system to freeze o kern/157243 wireless [ath] investigate beacon TX (AP) / RX (STA) when under o kern/156904 wireless [ath] AR9285 antenna diversity algorithm is buggy and o kern/156884 wireless [ath] ath instablity o kern/156327 wireless [bwn] bwn driver causes 20%-50% packet loss o kern/156322 wireless [wpi] no ahdemo support for if_wpi o kern/156321 wireless [ath] ahdemo doesn't work with if_ath o kern/155498 wireless [ral] ral(4) needs to be resynced with OpenBSD's to ga o kern/155100 wireless [ath] ath driver on busy channel: "stuck beacon" p kern/154598 wireless [ath] Atheros 5424/2424 can't connect to WPA network o kern/154567 wireless [ath] ath(4) lot of bad series(0) o kern/154327 wireless [ath] AR5416 in station mode hangs when transmitting f o kern/154284 wireless [ath] Modern ath wifi cards (such as AR9285) have miss o kern/154153 wireless [ath] AR5213 + MIPS + WPA group key packet corruption o kern/153594 wireless [wlan] netif/devd race o kern/153448 wireless [ath] ath networking device loses association after a o kern/152750 wireless [ath] ath0 lot of bad series hwrate o kern/151198 wireless [ath] ath/5416 fails bgscan with "ath0: ath_chan_set: o kern/149786 wireless [bwn] bwn on Dell Inspiron 1150: connections stall o kern/149516 wireless [ath] ath(4) hostap with fake MAC/BSSID results in sta o kern/149373 wireless [realtek/atheros]: None of my network card working o kern/148322 wireless [ath] Triggering atheros wifi beacon misses in hostap o kern/148317 wireless [ath] FreeBSD 7.x hostap memory leak in net80211 or At o kern/148078 wireless [ath] wireless networking stops functioning o kern/146426 wireless [mwl] 802.11n rates not possible on mwl o kern/146425 wireless [mwl] mwl dropping all packets during and after high u o kern/145826 wireless [panic] [ath] Unable to configure adhoc mode on ath0/w o kern/144987 wireless [wpi] [panic] injecting packets with wlaninject using o kern/144755 wireless [wlan] netif/devd race o bin/144109 wireless hostapd(8) uses the MAC of the wireless interface, but o conf/143079 wireless hostapd(8) startup missing multi wlan functionality p kern/140567 wireless [ath] [patch] ath is not worked on my notebook PC o kern/140245 wireless [ath] [panic] Kernel panic during network activity on o kern/137592 wireless [ath] panic - 7-STABLE (Aug 7, 2009 UTC) crashes on ne o kern/136943 wireless [wpi] [lor] wpi0_com_lock / wpi0 o kern/136836 wireless [ath] atheros card stops functioning after about 12 ho o kern/132722 wireless [ath] Wifi ath0 associates fine with AP, but DHCP or I o bin/131549 wireless ifconfig(8) can't clear 'monitor' mode on the wireless o kern/126475 wireless [ath] [panic] ath pcmcia card inevitably panics under o kern/125721 wireless [ath] Terrible throughput/high ping latency with Ubiqu o kern/125617 wireless [ath] [panic] ath(4) related panic o kern/125501 wireless [ath] atheros cardbus driver hangs o kern/125332 wireless [ath] [panic] crash under any non-tiny networking unde o kern/124767 wireless [iwi] Wireless connection using iwi0 driver (Intel 220 o kern/124753 wireless [ieee80211] net80211 discards power-save queue packets o kern/121061 wireless [ath] [panic] panic while ejecting ath(4)-adapter duri o docs/120456 wireless ath(4) needs to specify requirement on wlan_scan_sta o kern/119513 wireless [ath] [irq] inserting dlink dwl-g630 wireless card res o kern/116747 wireless [ndis] FreeBSD 7.0-CURRENT crash with Dell TrueMobile f kern/105348 wireless [ath] ath device stopps TX 178 problems total. From owner-freebsd-wireless@FreeBSD.ORG Mon Oct 7 12:21:28 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C5AA5DEC for ; Mon, 7 Oct 2013 12:21:28 +0000 (UTC) (envelope-from sbremal@hotmail.com) Received: from dub0-omc1-s24.dub0.hotmail.com (dub0-omc1-s24.dub0.hotmail.com [157.55.0.223]) by mx1.freebsd.org (Postfix) with ESMTP id 6D6112F4B for ; Mon, 7 Oct 2013 12:21:27 +0000 (UTC) Received: from DUB126-W43 ([157.55.0.238]) by dub0-omc1-s24.dub0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 7 Oct 2013 05:21:26 -0700 X-TMN: [sKtyFp6/VwTMrzyy2aqtXtV3TSvG/KYo] X-Originating-Email: [sbremal@hotmail.com] Message-ID: From: To: "freebsd-wireless@freebsd.org" Subject: RE: WLAN PCIe HW recommendation for 8.1 Date: Mon, 7 Oct 2013 12:21:26 +0000 Importance: Normal In-Reply-To: References: , , , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginalArrivalTime: 07 Oct 2013 12:21:26.0807 (UTC) FILETIME=[BEA04A70:01CEC357] 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: Mon, 07 Oct 2013 12:21:28 -0000 Hi=0A= =A0=0A= Hardware notes are fairly succinct about particular hardware for the 'ath' = driver:=0A= =A0=0A= 3.5 Wireless Network Interfaces=0A= =A0=0A= [i386=2Cpc98=2Camd64=2Csparc64] The =0A= ath(4) driver=0A= supports all Atheros Cardbus and PCI cards=2C except those that are based o= n the AR5005VL=0A= chipset.=0A= =A0=0A= For other drivers ('ipw'=2C 'iwi' etc.) there is a list of HW that I can re= adily order. Do you plan to add such list also for 'ath'?=0A= =A0=0A= Is there any advantage of choosing Atheros based card and using 'ath' over = Intel and 'ipw'.=0A= =A0=0A= I found it cumbersome to map Atheros chipsets to PCIe cards=2C most of the = time this info is hidden from the adapters data sheet. I must be completely= on the wrong way. I would expect 10 min. to pick a PCIe WLAN card from the= Freebsd HW notes=2C order it=2C plug it in=2C configure and enjoy. Like wi= th LAN cards=2C hard disks etc. What do I do wrong?=0A= =A0=0A= =A0=0A= Cheers=0A= Balazs=0A= =0A= ________________________________=0A= > Date: Mon=2C 30 Sep 2013 06:40:09 -0700 =0A= > Subject: Re: WLAN PCIe HW recommendation for 8.1 =0A= > From: adrian@freebsd.org =0A= > To: sbremal@hotmail.com =0A= > CC: freebsd-wireless@freebsd.org =0A= > =0A= > Hi=2C =0A= > =0A= > Anything that has an Atheros chip on it=2C is pcie and does 11abg is =0A= > fine. 2315/2417/5414 should all be fine. =0A= > =0A= > =0A= > =0A= > -adrian =0A= > =0A= > =0A= > On 30 September 2013 06:29=2C =0A= > > wrote: =0A= > Thanks=2C any particular HW that you would recommend? Do not mind if it = =0A= > is not the fastest with the latest features though want 'zero' network = =0A= > outage. =0A= > =0A= > I believe there were cards you plugged in and you were happy with. =0A= > Which card has which chipset is not always obvious on the major =0A= > shopping sites. =0A= > =0A= > =0A= > Thanks =0A= > Balazs =0A= > =0A= > ________________________________ =0A= > > Date: Mon=2C 30 Sep 2013 06:13:54 -0700 =0A= > > Subject: Re: WLAN PCIe HW recommendation for 8.1 =0A= > > From: adrian@freebsd.org =0A= > > To: sbremal@hotmail.com =0A= > > CC: freebsd-wireless@freebsd.org = =0A= > > =0A= > > Hi! =0A= > > =0A= > > The most stable PCIe WLAN NICs by far will be the 802.11abg Atheros =0A= > > devices. The 11n stuff became stable in 10.0. =0A= > > =0A= > > =0A= > > -adrian =0A= > > =0A= > > =0A= > > On 30 September 2013 06:10=2C =0A= > > =0A= > >> =0A= > wrote: =0A= > > Hello =0A= > > =0A= > > Would anyone recommend a PCIe WLAN card for 8.1? It is for a production= =0A= > > machine so stability is of prime importance. =0A= > > =0A= > > Honestly=2C a bit confused what HW to pick after going through 'Hardwar= e =0A= > > Matrix' at =0A= > > 'https://wiki.freebsd.org/dev/ath_hal%284%29/HardwareSupport'. =0A= > > =0A= > > I do not want to upgrade to release 9 ... unless it is really necessary= . =0A= > > =0A= > > =0A= > > Thanks =0A= > > Balazs =0A= > > _______________________________________________ =0A= > > =0A= > freebsd-wireless@freebsd.org> =0A= > > mailing list =0A= > > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless =0A= > > To unsubscribe=2C send any mail to =0A= > > =0A= > "freebsd-wireless-unsubscribe@freebsd.org>" =0A= > > =0A= > _______________________________________________ =0A= > freebsd-wireless@freebsd.org =0A= > mailing list =0A= > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless =0A= > To unsubscribe=2C send any mail to =0A= > "freebsd-wireless-unsubscribe@freebsd.org" =0A= > = From owner-freebsd-wireless@FreeBSD.ORG Mon Oct 7 13:45:51 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 96DDBC1E for ; Mon, 7 Oct 2013 13:45:51 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qc0-x22c.google.com (mail-qc0-x22c.google.com [IPv6:2607:f8b0:400d:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5564124C3 for ; Mon, 7 Oct 2013 13:45:51 +0000 (UTC) Received: by mail-qc0-f172.google.com with SMTP id l13so4844104qcy.31 for ; Mon, 07 Oct 2013 06:45:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=XnIbuK7po7FG0HPHpdSC+2wSeY89Eg6bA23whAp063U=; b=wqkaMRj4zqi5d12xzuub6b72zhSlw8HYb6E42NIs1tZ0/f/xR4ZdQpBJqxRni1HhWR ibwmZg2NAB9eSVLRL/k7zjzEghYSbqVpixYEKUqE/XlPUiyBFAawcpGkgaWejIEulW2S inSrfB8c/p/lIr64memiyacicSFHkR223DdS5R/0v5CdLTUXsU6fG5owDSHwtjEnb+UG FIzJpIS6kOOXqTJA38Z6I84pA77dSrkLV7VLgW5rQ5RI4gO0To0hdLT+QgcB7f9OXjTp jYnyZDhoomxKITDghuwwEoZLFDAafT5LmKBNSXX9b9DSNCH6yHSZs0NrpDfuELA5Ir5N 3L7A== MIME-Version: 1.0 X-Received: by 10.49.103.161 with SMTP id fx1mr36381501qeb.68.1381153550387; Mon, 07 Oct 2013 06:45:50 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Mon, 7 Oct 2013 06:45:50 -0700 (PDT) In-Reply-To: References: Date: Mon, 7 Oct 2013 06:45:50 -0700 X-Google-Sender-Auth: BIVq0OBt7qmaQpTpJPuOAVFLees Message-ID: Subject: Re: WLAN PCIe HW recommendation for 8.1 From: Adrian Chadd To: Abcd Efgh Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Mon, 07 Oct 2013 13:45:51 -0000 The problem is that there's a lot of them. If someone wants to tackle this, I'm all ears. :-) -adrian On 7 October 2013 05:21, wrote: > Hi > > Hardware notes are fairly succinct about particular hardware for the 'ath' > driver: > > 3.5 Wireless Network Interfaces > > [i386,pc98,amd64,sparc64] The > ath(4) driver > supports all Atheros Cardbus and PCI cards, except those that are based on > the AR5005VL > chipset. > > For other drivers ('ipw', 'iwi' etc.) there is a list of HW that I can > readily order. Do you plan to add such list also for 'ath'? > > Is there any advantage of choosing Atheros based card and using 'ath' over > Intel and 'ipw'. > > I found it cumbersome to map Atheros chipsets to PCIe cards, most of the > time this info is hidden from the adapters data sheet. I must be completely > on the wrong way. I would expect 10 min. to pick a PCIe WLAN card from the > Freebsd HW notes, order it, plug it in, configure and enjoy. Like with LAN > cards, hard disks etc. What do I do wrong? > > > Cheers > Balazs > > ________________________________ > > Date: Mon, 30 Sep 2013 06:40:09 -0700 > > Subject: Re: WLAN PCIe HW recommendation for 8.1 > > From: adrian@freebsd.org > > To: sbremal@hotmail.com > > CC: freebsd-wireless@freebsd.org > > > > Hi, > > > > Anything that has an Atheros chip on it, is pcie and does 11abg is > > fine. 2315/2417/5414 should all be fine. > > > > > > > > -adrian > > > > > > On 30 September 2013 06:29, > > > wrote: > > Thanks, any particular HW that you would recommend? Do not mind if it > > is not the fastest with the latest features though want 'zero' network > > outage. > > > > I believe there were cards you plugged in and you were happy with. > > Which card has which chipset is not always obvious on the major > > shopping sites. > > > > > > Thanks > > Balazs > > > > ________________________________ > > > Date: Mon, 30 Sep 2013 06:13:54 -0700 > > > Subject: Re: WLAN PCIe HW recommendation for 8.1 > > > From: adrian@freebsd.org > > > To: sbremal@hotmail.com > > > CC: freebsd-wireless@freebsd.org > > > > > > Hi! > > > > > > The most stable PCIe WLAN NICs by far will be the 802.11abg Atheros > > > devices. The 11n stuff became stable in 10.0. > > > > > > > > > -adrian > > > > > > > > > On 30 September 2013 06:10, > > > > > sbremal@hotmail.com>> > > wrote: > > > Hello > > > > > > Would anyone recommend a PCIe WLAN card for 8.1? It is for a production > > > machine so stability is of prime importance. > > > > > > Honestly, a bit confused what HW to pick after going through 'Hardware > > > Matrix' at > > > 'https://wiki.freebsd.org/dev/ath_hal%284%29/HardwareSupport'. > > > > > > I do not want to upgrade to release 9 ... unless it is really > necessary. > > > > > > > > > Thanks > > > Balazs > > > _______________________________________________ > > > > > freebsd-wireless@freebsd.org > >> > > > mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > > > To unsubscribe, send any mail to > > > > > "freebsd-wireless-unsubscribe@freebsd.org freebsd-wireless-unsubscribe@freebsd.org> freebsd-wireless-unsubscribe@freebsd.org freebsd-wireless-unsubscribe@freebsd.org>>" > > > > > _______________________________________________ > > freebsd-wireless@freebsd.org > > mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > > To unsubscribe, send any mail to > > "freebsd-wireless-unsubscribe@freebsd.org freebsd-wireless-unsubscribe@freebsd.org>" > > > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org > " > From owner-freebsd-wireless@FreeBSD.ORG Mon Oct 7 20:10:38 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id EC3CE1C6 for ; Mon, 7 Oct 2013 20:10:38 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9CD672EE0 for ; Mon, 7 Oct 2013 20:10:38 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id r97KAbsu091163; Mon, 7 Oct 2013 14:10:37 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id r97KAbUx091160; Mon, 7 Oct 2013 14:10:37 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Mon, 7 Oct 2013 14:10:37 -0600 (MDT) From: Warren Block To: sbremal@hotmail.com Subject: RE: WLAN PCIe HW recommendation for 8.1 In-Reply-To: Message-ID: References: , , , User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Mon, 07 Oct 2013 14:10:37 -0600 (MDT) 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: Mon, 07 Oct 2013 20:10:39 -0000 On Mon, 7 Oct 2013, sbremal@hotmail.com wrote: > I found it cumbersome to map Atheros chipsets to PCIe cards, most of > the time this info is hidden from the adapters data sheet. I must be > completely on the wrong way. I would expect 10 min. to pick a PCIe > WLAN card from the Freebsd HW notes, order it, plug it in, configure > and enjoy. Like with LAN cards, hard disks etc. What do I do wrong? A search at wikidevi.com for "atheros pcie" finds a few PCIe cards, and a bunch of mini-PCIe cards. There might be a better search term to show just desktop-type PCIe. There are adapter cards to put a mini-PCIe card in a PCIe slot, which provides more versatility. From owner-freebsd-wireless@FreeBSD.ORG Mon Oct 7 21:19:12 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5CCBCBAE for ; Mon, 7 Oct 2013 21:19:12 +0000 (UTC) (envelope-from kurt.buff@gmail.com) Received: from mail-ee0-x234.google.com (mail-ee0-x234.google.com [IPv6:2a00:1450:4013:c00::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EE7EF24BF for ; Mon, 7 Oct 2013 21:19:11 +0000 (UTC) Received: by mail-ee0-f52.google.com with SMTP id c41so3584123eek.11 for ; Mon, 07 Oct 2013 14:19:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=1gOVHiyEaAVG3ICyptQLUn/99Ikucm3jQ1H/34E9syM=; b=x4mHVgkSe2MpmE5zu0aeX4s1MuRqshGicokx+0C4xRimcw3X2vndESdvEw90QwONOX HKzigkqRK5vUXk0gyyPUTBJx9263zpUYfeiAvb6ypizTnWyBzZiULZKsCd+3RhYE+wfQ pIft9JnOszG6kFSRhTeXYZ0z1PUs/DnQaFCNgVFZJNOm45qQUdU/makq0kbV8TZT7CyI Pf24sY7jh6dYPhoBU5I6Kan8ROcMHfLJLcrzBUUZFwNrEMLmk4r4lEO1rrVQERFu3vZx a+lGQr2mnBaiZPF2KwCXX+0pVgm4G2x/pYSiGXbvlRJBckF7kmuWKNe4rOmDFpodvzpN Tt7w== MIME-Version: 1.0 X-Received: by 10.14.29.67 with SMTP id h43mr52393831eea.7.1381180749397; Mon, 07 Oct 2013 14:19:09 -0700 (PDT) Received: by 10.14.142.209 with HTTP; Mon, 7 Oct 2013 14:19:09 -0700 (PDT) Date: Mon, 7 Oct 2013 14:19:09 -0700 Message-ID: Subject: iwn on a Lenovo 5100 - can't connect to wireless From: Kurt Buff To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=UTF-8 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: Mon, 07 Oct 2013 21:19:12 -0000 I'm sure I'm making a silly mistake in the config somewhere, but I'm working from these two pages: http://www.freebsd.org/cgi/man.cgi?query=wpa_supplicant.conf&sektion=5 and http://www.freebsd.org/doc/handbook/network-wireless.html Situation as follows: multiple WAPS running multiple SSIDs, on multiple channels (1,6,11) but I'm only interested in one SSID. It's WPA PSK. The laptop is running 9.2-RELEASE and configured with the folllowing: >From /boot/loader.conf if_iwn_load="YES" wlan_wep_load="YES wlan_ccmp_load="YES" wlan_tkip_load="YES" >From /etc/rc.conf (DHCP configuration doesn't work, either) defaultrouter="192.168.15.1" wlans_iwn0="wlan0" ifconfig_wlan0="inet 192.168.15.50 netmask 255.255.255.0 ssid wireless" >From /etc/wpa_supplicant.conf ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=wheel network={ ssid="wireless" scan_ssid=1 key_mgmt=WPA-PSK psk="longrandompassword" } When I boot the machine, and run 'ifconfig wlan0', I see "status: no carrier". If I do 'ifconfig wlan0 scan', I get results, seeing the WAPs near me, etc., but I can't ping anything. When I manually run 'wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf', I get connection, and can ping from a different console session, but once I ^c out of wpa_supplicant, I lose the network. Can anyone tell me what I'm missing on this? Kurt From owner-freebsd-wireless@FreeBSD.ORG Mon Oct 7 21:20:29 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2E2DEBDC for ; Mon, 7 Oct 2013 21:20:29 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qc0-x234.google.com (mail-qc0-x234.google.com [IPv6:2607:f8b0:400d:c01::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E30B824F1 for ; Mon, 7 Oct 2013 21:20:28 +0000 (UTC) Received: by mail-qc0-f180.google.com with SMTP id p19so5248343qcv.25 for ; Mon, 07 Oct 2013 14:20:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=9hZEX3SpVhIWUVsgLZEC7WgbAxdPzOXYq+ONh7X/FhY=; b=f8f7mm8+9NtfDtFkJ6bb8CItFpq04OUpUuM0BNEibcOoFLBvIbfzm7bHAX1sWTs3+q XdmQhg1InfBzAr9coAJwz519bSgggXyDEKPG8uuSF7143KD5QQEDVVDjrkO/FfZBdFgJ sGzh9wR7xlG8Niu08V5bi11z9wIsV2OgTEHxC0Fj5gi4VDAkzTau+f8snf4rWboh0JQE WcFvcnus3uUEHswG8uJhIufrD23ZozUJAMlm8jM25pbPDv3QA3XA7ouGXzbJRSci4jXX q2+7aLWpUSeB7iJf/OyokVCbC9FtRVL1ykJDcm8C5hFKoKw8txPxNLgHfNeEPZ5rhc6Y 2Dcg== MIME-Version: 1.0 X-Received: by 10.224.51.131 with SMTP id d3mr40627286qag.0.1381180828090; Mon, 07 Oct 2013 14:20:28 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Mon, 7 Oct 2013 14:20:28 -0700 (PDT) In-Reply-To: References: Date: Mon, 7 Oct 2013 14:20:28 -0700 X-Google-Sender-Auth: -WSHBB-cYTJUG6obqo9lQN3Ywn4 Message-ID: Subject: Re: iwn on a Lenovo 5100 - can't connect to wireless From: Adrian Chadd To: Kurt Buff Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Mon, 07 Oct 2013 21:20:29 -0000 Hi, Add "WPA" at the end if ifconfig_wlan0, not 'ssid wireless'. That way wpa_supplicant runs. For maximum correctness: ifconfig_wlan0="DHCP WPA" -adiran From owner-freebsd-wireless@FreeBSD.ORG Mon Oct 7 21:25:07 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 14264ECF; Mon, 7 Oct 2013 21:25:07 +0000 (UTC) (envelope-from kurt.buff@gmail.com) Received: from mail-vb0-x22c.google.com (mail-vb0-x22c.google.com [IPv6:2607:f8b0:400c:c02::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B68562533; Mon, 7 Oct 2013 21:25:06 +0000 (UTC) Received: by mail-vb0-f44.google.com with SMTP id e13so3749473vbg.17 for ; Mon, 07 Oct 2013 14:25:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=wo7wI+N8DLub3SbXPh3179MxExuZcISmDprwmg26R7s=; b=OrDkgnESjcvQxKmy33HIRFddnjfPQ5SwwBtNRpxt4VlOpsWX1G+X8nh9+6uMCETn1R LcUPWwOnN7rUID3N0eVJqvmZEsWLJG5Fgo82buXOVDajkpJH0HSOBW2vE0/uGbv4kD0Z ayF8wyyogQr6FxzzCwNqYX1kS0JTYRyA54pVU3mKce1vmrgLSlr2qPFjPAXnOuDy36vI Clw4fW7tLA1wXAYNy8yvaON4JQiIr/JL4lsCKwHt0rlDdND7UoVp/x4aFgcy0bBruTVY XLP26Ix26CW0MFQfNvR9tzk14VQw/xby4yAwVpoi7QV69VCn6sj5HIt5e1CrNvg+SdbX 2TEQ== MIME-Version: 1.0 X-Received: by 10.52.100.202 with SMTP id fa10mr23737363vdb.0.1381181105935; Mon, 07 Oct 2013 14:25:05 -0700 (PDT) Received: by 10.220.14.196 with HTTP; Mon, 7 Oct 2013 14:25:05 -0700 (PDT) In-Reply-To: References: Date: Mon, 7 Oct 2013 14:25:05 -0700 Message-ID: Subject: Re: iwn on a Lenovo 5100 - can't connect to wireless From: Kurt Buff To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 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: Mon, 07 Oct 2013 21:25:07 -0000 Knew it had to be something simple. That was it, and thanks again for your help. Kurt On Mon, Oct 7, 2013 at 2:20 PM, Adrian Chadd wrote: > Hi, > > Add "WPA" at the end if ifconfig_wlan0, not 'ssid wireless'. That way > wpa_supplicant runs. > > For maximum correctness: > > ifconfig_wlan0="DHCP WPA" > > > > -adiran > From owner-freebsd-wireless@FreeBSD.ORG Tue Oct 8 08:54:34 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id BD34E644 for ; Tue, 8 Oct 2013 08:54:34 +0000 (UTC) (envelope-from sbremal@hotmail.com) Received: from dub0-omc1-s9.dub0.hotmail.com (dub0-omc1-s9.dub0.hotmail.com [157.55.0.208]) by mx1.freebsd.org (Postfix) with ESMTP id 5E6392FB8 for ; Tue, 8 Oct 2013 08:54:33 +0000 (UTC) Received: from DUB126-W73 ([157.55.0.237]) by dub0-omc1-s9.dub0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 8 Oct 2013 01:53:27 -0700 X-TMN: [JbEm4Pz6TZ3OnyBFla8cksXDywEM5/AL] X-Originating-Email: [sbremal@hotmail.com] Message-ID: From: To: "freebsd-wireless@freebsd.org" Subject: RE: WLAN PCIe HW recommendation for 8.1 Date: Tue, 8 Oct 2013 08:53:27 +0000 Importance: Normal In-Reply-To: References: , , , , , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginalArrivalTime: 08 Oct 2013 08:53:27.0160 (UTC) FILETIME=[DA970780:01CEC403] 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: Tue, 08 Oct 2013 08:54:34 -0000 'wikidevi.com' is the answer to all questions. Many thanks!=0A= =0A= Wonder if there is a link to 'wikidevi.com' on the FreeBSD WLAN driver proj= ect site...=0A= =0A= =0A= Cheers=0A= Balazs=0A= =0A= ----------------------------------------=0A= > Date: Mon=2C 7 Oct 2013 14:10:37 -0600=0A= > From: wblock@wonkity.com=0A= > To: sbremal@hotmail.com=0A= > CC: freebsd-wireless@freebsd.org=0A= > Subject: RE: WLAN PCIe HW recommendation for 8.1=0A= >=0A= > On Mon=2C 7 Oct 2013=2C sbremal@hotmail.com wrote:=0A= >=0A= >> I found it cumbersome to map Atheros chipsets to PCIe cards=2C most of= =0A= >> the time this info is hidden from the adapters data sheet. I must be=0A= >> completely on the wrong way. I would expect 10 min. to pick a PCIe=0A= >> WLAN card from the Freebsd HW notes=2C order it=2C plug it in=2C configu= re=0A= >> and enjoy. Like with LAN cards=2C hard disks etc. What do I do wrong?=0A= >=0A= > A search at wikidevi.com for "atheros pcie" finds a few PCIe cards=2C and= =0A= > a bunch of mini-PCIe cards. There might be a better search term to show= =0A= > just desktop-type PCIe.=0A= >=0A= > There are adapter cards to put a mini-PCIe card in a PCIe slot=2C which= =0A= > provides more versatility. = From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 10 02:04:19 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4E27B80E for ; Thu, 10 Oct 2013 02:04:19 +0000 (UTC) (envelope-from tx2023@gmail.com) Received: from mail-pd0-x232.google.com (mail-pd0-x232.google.com [IPv6:2607:f8b0:400e:c02::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2C307256E for ; Thu, 10 Oct 2013 02:04:19 +0000 (UTC) Received: by mail-pd0-f178.google.com with SMTP id w10so1830207pde.23 for ; Wed, 09 Oct 2013 19:04:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=Hgi73k3chjng+JdLX41xvR09WGtm3CL8ZnkicY4KKN0=; b=bF3/ohjpZb6saY6kXClpRkxsfbT0ssvkOOrLw3khOe5dzvZ8hYpc5ZuWGXc/tPtMt5 VBgNeQVm+KG668ZWriZxekYBx+SiWCdsnwWNAjhPv4jGc0XWnTxeX0Eifk7s/KL2Ej7d PxFeB+uDY4hUc9OiJ4SoWI4Kc3mANGz9MyXAOLE7scRtdYrtVHFdKXDv7k+eliagq6Pt zf3xHIbeGtfpRODRCDLdyb6qCPCjwChONYZSq6/ppgtfKw/qqN8V+gqPHj5l+IylbzZf uHEMKN/rHWO1f9ATBgw3qoxR037rMEi4LVToWpcxcr/3hrf2mD5Pbzgj5w6wGu7/24W/ Ew+g== MIME-Version: 1.0 X-Received: by 10.66.19.137 with SMTP id f9mr12838620pae.138.1381370657939; Wed, 09 Oct 2013 19:04:17 -0700 (PDT) Received: by 10.68.13.226 with HTTP; Wed, 9 Oct 2013 19:04:17 -0700 (PDT) Date: Thu, 10 Oct 2013 10:04:17 +0800 Message-ID: Subject: Correlation values for Atheros adaptive noise immunity From: w To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable 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, 10 Oct 2013 02:04:19 -0000 Is there any way I can printk the correlation values for ar5416_ani.c? I couldn=92t find the variable that contains the correlation value. Line 267 of the ar5416_ani.c file says: OS_REG_RMW_FIELD(ah, AR_PHY_SFCORR, AR_PHY_SFCORR_M1_THRESH, m1Thresh[on]); I don=92t know what the variables mean or what the function means or what data type the variables are because I want to printk them. References: http://svnweb.freebsd.org/base/head/sys/dev/ath/ath_hal/ar5416/ar5416_ani.c= ?view=3Dmarkup https://wiki.freebsd.org/dev/ath_hal%284%29/AutomaticNoiseImmunity ~ w ~ From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 10 02:05:02 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 1C7E4907 for ; Thu, 10 Oct 2013 02:05:02 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qc0-x236.google.com (mail-qc0-x236.google.com [IPv6:2607:f8b0:400d:c01::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C7CF62578 for ; Thu, 10 Oct 2013 02:05:01 +0000 (UTC) Received: by mail-qc0-f182.google.com with SMTP id n4so1265610qcx.41 for ; Wed, 09 Oct 2013 19:05:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=wHipbzK9+MW2K8erp5PsiWwm/MLcHnBTwxfFaA0IEPo=; b=GenCiHoyBGj1UzZbP6Znn6oKPv98lmDLtn9pOlcL9H9FqPdlydaLGoPyoRm0cItcqz Crw/DTCv8GluDwSS5LllXQKDwy+vUcGR1VFWfQp6e8VLfDsDiYbQ36Uqu2N8FISprjGr pBsZYcAqKsw085+MbqlTVbHWdxNwFieweF8kVSMqkHPB1H/4b0sxx//JCaB70W4eJLc5 8OO5eundZw4ittFtP5umGoNZSoOzTeKyPvpO3+SAQaMKsASeCodcMhJFBfBrSkY0L+U+ yjJP4fOVhcKCYpfjY6MIy41AW82keG/kQapIAaml6UDTMGFTPoviE/XlDLAt9XTeHqJU uz8Q== MIME-Version: 1.0 X-Received: by 10.49.27.226 with SMTP id w2mr838496qeg.32.1381370700978; Wed, 09 Oct 2013 19:05:00 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Wed, 9 Oct 2013 19:05:00 -0700 (PDT) In-Reply-To: References: Date: Wed, 9 Oct 2013 19:05:00 -0700 X-Google-Sender-Auth: HHua3IYD9_g_wtkD2BqsovamEBk Message-ID: Subject: Re: Correlation values for Atheros adaptive noise immunity From: Adrian Chadd To: w Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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, 10 Oct 2013 02:05:02 -0000 I'm not sure. I think it's a signal level. Have you read the ANI patent(s) = ? -adrian On 9 October 2013 19:04, w wrote: > Is there any way I can printk the correlation values for ar5416_ani.c? > > I couldn=92t find the variable that contains the correlation value. > Line 267 of the ar5416_ani.c file says: > OS_REG_RMW_FIELD(ah, AR_PHY_SFCORR, > AR_PHY_SFCORR_M1_THRESH, m1Thresh[on]); > > I don=92t know what the variables mean or what the function means or > what data type the variables are because I want to printk them. > > References: > > > http://svnweb.freebsd.org/base/head/sys/dev/ath/ath_hal/ar5416/ar5416_ani= .c?view=3Dmarkup > > https://wiki.freebsd.org/dev/ath_hal%284%29/AutomaticNoiseImmunity > > ~ w ~ > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.or= g > " > From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 10 02:12:31 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 62031C38; Thu, 10 Oct 2013 02:12:31 +0000 (UTC) (envelope-from tx2023@gmail.com) Received: from mail-pa0-x22c.google.com (mail-pa0-x22c.google.com [IPv6:2607:f8b0:400e:c03::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 37FF02605; Thu, 10 Oct 2013 02:12:31 +0000 (UTC) Received: by mail-pa0-f44.google.com with SMTP id lf10so1974774pab.3 for ; Wed, 09 Oct 2013 19:12:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Ls7F7p02bm2xnx1BImTFQqwOXbb1pMK8a+fJgkzZ1Ic=; b=o2fMZpdwrrYLEhYTzpMXFTCRchtbUaCpzRJEtcS1w5hOwVZyWntaaq8pnC6EXE4Lct k3zRBeIl4CqNO9tmMjer73nQP2tTRjYrMurC5ghTqoyZOkJb4Txb47ragIp/pA3WZSVl OQDC83A+BlrFTeVtatP1cWFKefDmYGsXXMk/PuIRVJBEcBfh0uw3BqOMG9jwllcJC4Ld mlPAknbMgk1o8aEgmdHshtX9HVBcVFIg2xSd2QFdwNjyOkr8yCNg+Dc/TywoW/zHS8Rg SUpCbg93KhIg0KMQdV3PUPK+kUh6WoUIQtTqMj9oO0T2OOFt4ahwBAYInYfYfGW/ZBqf igug== MIME-Version: 1.0 X-Received: by 10.68.197.129 with SMTP id iu1mr11062840pbc.139.1381371150772; Wed, 09 Oct 2013 19:12:30 -0700 (PDT) Received: by 10.68.13.226 with HTTP; Wed, 9 Oct 2013 19:12:30 -0700 (PDT) In-Reply-To: References: Date: Thu, 10 Oct 2013 10:12:30 +0800 Message-ID: Subject: Re: Correlation values for Atheros adaptive noise immunity From: w To: Adrian Chadd Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable 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, 10 Oct 2013 02:12:31 -0000 Yup, I read the patent. I have also read the Atheros documentation for ANI (for a different hardware version but it says the operation is similar). Are we able to see physical layer parameters like signal level / correlation / channel state information, or are they hidden inside the hardware? ~ w ~ On Thu, Oct 10, 2013 at 10:05 AM, Adrian Chadd wrote: > I'm not sure. I think it's a signal level. Have you read the ANI patent(s= ) ? > > > > -adrian > > > > On 9 October 2013 19:04, w wrote: >> >> Is there any way I can printk the correlation values for ar5416_ani.c? >> >> I couldn=92t find the variable that contains the correlation value. >> Line 267 of the ar5416_ani.c file says: >> OS_REG_RMW_FIELD(ah, AR_PHY_SFCORR, >> AR_PHY_SFCORR_M1_THRESH, m1Thresh[on]); >> >> I don=92t know what the variables mean or what the function means or >> what data type the variables are because I want to printk them. >> >> References: >> >> >> http://svnweb.freebsd.org/base/head/sys/dev/ath/ath_hal/ar5416/ar5416_an= i.c?view=3Dmarkup >> >> https://wiki.freebsd.org/dev/ath_hal%284%29/AutomaticNoiseImmunity >> >> ~ w ~ >> _______________________________________________ >> freebsd-wireless@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to >> "freebsd-wireless-unsubscribe@freebsd.org" > > From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 10 02:44:33 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id CD6A652E for ; Thu, 10 Oct 2013 02:44:33 +0000 (UTC) (envelope-from tx2023@gmail.com) Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id AB4A32752 for ; Thu, 10 Oct 2013 02:44:33 +0000 (UTC) Received: by mail-pa0-f41.google.com with SMTP id bj1so2010300pad.14 for ; Wed, 09 Oct 2013 19:44:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=aoD+okuMeZ+/Kj1u68ONZJ/SxXaUbRJl0TN+gqGrfH0=; b=z/mA7G1y+xg3wl+Thopc7BxIY0AUGqanGg3HICC+kmBJkxoGLINeJUS/Yz2TexmZPL 1LOetYSOjBwl1usALfi0AFwS9RZiWQAKLPdN5btsVbf4LNY0y4oyexvzlNVCy4rUZHx5 baKtoZsyjZnxNsW6gh8YO9h4lXf8G5AcZRSF0AwRCsnWRVSuk8hWCq9tPLl7e1sAsjgT WlC/jgP8nzylGQHHiJDxJpz2TrEYeZIn4oRf18KvD5J2MH4y6+aRdWGE657vIFpQe5oW sbXjhKwWqZHttJQOFmrlil0SAWVLFXTQHbM3A1DaYAHffmDflJg1bWXKJAyRp2VFtdjL 6TEw== MIME-Version: 1.0 X-Received: by 10.68.196.227 with SMTP id ip3mr11075268pbc.163.1381373073254; Wed, 09 Oct 2013 19:44:33 -0700 (PDT) Received: by 10.68.13.226 with HTTP; Wed, 9 Oct 2013 19:44:33 -0700 (PDT) Date: Thu, 10 Oct 2013 10:44:33 +0800 Message-ID: Subject: Atheros ANI and other WLAN signals as interference From: w To: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 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, 10 Oct 2013 02:44:33 -0000 For the Atheros ANI, are the WLAN signals for other APs (with different SSID) considered as false detection? (I think it does not. Then how to test the ANI operation given that I only have a machine that generates arbitrary WLAN signals?) Atheros adaptive noise immunity: https://wiki.freebsd.org/dev/ath_hal%284%29/AutomaticNoiseImmunity ~ w ~ From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 10 03:03:17 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 508F07F9 for ; Thu, 10 Oct 2013 03:03:17 +0000 (UTC) (envelope-from tx2023@gmail.com) Received: from mail-pd0-x230.google.com (mail-pd0-x230.google.com [IPv6:2607:f8b0:400e:c02::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2A744288C for ; Thu, 10 Oct 2013 03:03:17 +0000 (UTC) Received: by mail-pd0-f176.google.com with SMTP id q10so1906312pdj.35 for ; Wed, 09 Oct 2013 20:03:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:cc :content-type:content-transfer-encoding; bh=d44DV1FHpwX4srKk0H1e76IlUmS+WBly6kIsDPU9MHM=; b=Dphrw1cGJa5El3aHczRXmdTl/jMOAvajwXz6jJzdStw1r4WcmS7iE1GZOMHzLG6csF 4PNzk2QYj93DCmzeXwIBOVRLCESagnGJPE7aQ4+ruZr8qp1IEbaWJLhTBXaT4kquWqQ6 K1WtGcY10x+dNUchsZ2dUHFGpHz1UXTP5vEODRyHqusrAER5Nka6N+Df9qdA0WfdXdSB DBnHVocM00s2I8cWlcAQvUdDJJs9Mqcg3clpDd7sfoJ0iZv/hgu9M0h5BUaDg3Zb+IEL 5N9fmeEwAgbHyuWOSDMIQocr0rlg5MLRDksaw3sOnP5m0F6RUIOsyXX1blEeqmDWGBWQ TMxQ== MIME-Version: 1.0 X-Received: by 10.66.157.165 with SMTP id wn5mt7175221pab.169.1381374196808; Wed, 09 Oct 2013 20:03:16 -0700 (PDT) Received: by 10.68.13.226 with HTTP; Wed, 9 Oct 2013 20:03:16 -0700 (PDT) In-Reply-To: References: Date: Thu, 10 Oct 2013 11:03:16 +0800 Message-ID: Subject: Re: Correlation values for Atheros adaptive noise immunity From: w Cc: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable 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, 10 Oct 2013 03:03:17 -0000 Update: looking at the patent again: http://www.freepatentsonline.com/7349503.html Note that bb_m1thres and bb_m2thres refer to normalized, self-correlated thresholds, bb_m2count_thr refers to the number of self-correlation values (wherein a typical count would not exceed 31), and bb_use_self_corr_low refers to an enabling bit value. (but the variables are still quite confusing.) ~ w ~ On Thu, Oct 10, 2013 at 10:12 AM, w wrote: > Yup, I read the patent. I have also read the Atheros documentation for > ANI (for a different hardware version but it says the operation is > similar). > > Are we able to see physical layer parameters like signal level / > correlation / channel state information, > or are they hidden inside the hardware? > > ~ w ~ > > > > On Thu, Oct 10, 2013 at 10:05 AM, Adrian Chadd wrote= : >> I'm not sure. I think it's a signal level. Have you read the ANI patent(= s) ? >> >> >> >> -adrian >> >> >> >> On 9 October 2013 19:04, w wrote: >>> >>> Is there any way I can printk the correlation values for ar5416_ani.c? >>> >>> I couldn=92t find the variable that contains the correlation value. >>> Line 267 of the ar5416_ani.c file says: >>> OS_REG_RMW_FIELD(ah, AR_PHY_SFCORR, >>> AR_PHY_SFCORR_M1_THRESH, m1Thresh[on]); >>> >>> I don=92t know what the variables mean or what the function means or >>> what data type the variables are because I want to printk them. >>> >>> References: >>> >>> >>> http://svnweb.freebsd.org/base/head/sys/dev/ath/ath_hal/ar5416/ar5416_a= ni.c?view=3Dmarkup >>> >>> https://wiki.freebsd.org/dev/ath_hal%284%29/AutomaticNoiseImmunity >>> >>> ~ w ~ >>> _______________________________________________ >>> freebsd-wireless@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >>> To unsubscribe, send any mail to >>> "freebsd-wireless-unsubscribe@freebsd.org" >> >> From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 10 12:05:41 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2F647229 for ; Thu, 10 Oct 2013 12:05:41 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qe0-x22e.google.com (mail-qe0-x22e.google.com [IPv6:2607:f8b0:400d:c02::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E51B225F5 for ; Thu, 10 Oct 2013 12:05:40 +0000 (UTC) Received: by mail-qe0-f46.google.com with SMTP id s14so541133qeb.33 for ; Thu, 10 Oct 2013 05:05:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=fhLI6T2gEu/OmR2wedfhc2OAr7Kf5WuBkuJ8+By9G+E=; b=f9DKyGmYkJgq06gA8hosk/huQSVnOecnB7ogy3MONgbCXU9CgQJEA5RzeLMLp89+PL c06Jc0S+eA4AZcDsPAjXhbl7pajTC5V+iEVsvxLGgnCD/FCbnQY8icR7dGLfSRytT51q 16DWOOUhtjae/DVvU2U/yfXnxcXflnre0KuMH5maku3cYO6MGQqtjeI7ZMz+Y79/J+so w27mHKS6uIDgwiidJfZj19JiVoQvNhSLTGWmayEyfAT8ae0gipL2jUs7/BdnA3fn6E4z ZKzUypAxJzewT0PnnJrdqY5jqhZYl0Z+Njxs4T/PPUaOQNniBXq1FrdcOUsa3BkUEkFO uk+A== MIME-Version: 1.0 X-Received: by 10.49.127.179 with SMTP id nh19mr13391901qeb.1.1381406740057; Thu, 10 Oct 2013 05:05:40 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Thu, 10 Oct 2013 05:05:39 -0700 (PDT) In-Reply-To: References: Date: Thu, 10 Oct 2013 05:05:39 -0700 X-Google-Sender-Auth: MlVcUIhTr7DfUJVyPOJEkCXNm5o Message-ID: Subject: Re: Atheros ANI and other WLAN signals as interference From: Adrian Chadd To: w Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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, 10 Oct 2013 12:05:41 -0000 Hi, If it can decode it as a wifi frame, it doesn't count as false detection. -a On 9 October 2013 19:44, w wrote: > For the Atheros ANI, are the WLAN signals for other APs (with > different SSID) considered as false detection? > > (I think it does not. Then how to test the ANI operation given that I > only have a machine that generates arbitrary WLAN signals?) > > Atheros adaptive noise immunity: > https://wiki.freebsd.org/dev/ath_hal%284%29/AutomaticNoiseImmunity > > ~ w ~ > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org > " > From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 10 12:24:55 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 76E60C7F; Thu, 10 Oct 2013 12:24:55 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qe0-x22f.google.com (mail-qe0-x22f.google.com [IPv6:2607:f8b0:400d:c02::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 259BD2765; Thu, 10 Oct 2013 12:24:55 +0000 (UTC) Received: by mail-qe0-f47.google.com with SMTP id b4so1777358qen.6 for ; Thu, 10 Oct 2013 05:24:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=D7sikeDMJD3WMh6NBKd2puEPUvWh6KMSqtcN+810Fcw=; b=A/5naT7kkplFuLwIXXsGI6HtPpXYYZ1hEPIR/ls1dkKxwdpEfLXyNTM84PuaEJuwHe 9A5UqYnLU/Jo9JMl67WyLSJtTcG4v6VB8yjNE1RAYFYcDhkB6a+4RWHIwaBLxjRF5mnf K9dwOzZ9P44uS3vG7mLrrhX/lKaEL+JXxuLWZrFDJdrTgxPnRD0UUxPD0GxyZpJN2ttn Q2J7PnenuiIRtFE7PkMR6RuVs+mwl5iEkl18NZKAofEYCHHq8mJxqeXHeMMOvDiKpsCW ArdcDnR+mZN7aOyJnX0hhtRYzJyeKQc/Nz3LmZ/qqZ2sJWfBStcTttjfNztkZ6nJ+kV+ wvcg== MIME-Version: 1.0 X-Received: by 10.229.38.202 with SMTP id c10mr9634473qce.23.1381407894288; Thu, 10 Oct 2013 05:24:54 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Thu, 10 Oct 2013 05:24:54 -0700 (PDT) In-Reply-To: References: Date: Thu, 10 Oct 2013 05:24:54 -0700 X-Google-Sender-Auth: jtxOSjn7IDnRMVrbPnmtvLSjMac Message-ID: Subject: Re: [ieee80211] [patch] BPF taps not working for ieee80211 interfaces in monitor mode From: Adrian Chadd To: Patrick Kelsey Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Net , "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, 10 Oct 2013 12:24:55 -0000 On 9 October 2013 17:27, Patrick Kelsey wrote: > Hi, > > A bug was introduced in r254082 that results in BPF taps never being > enabled for ieee80211 interfaces that are in monitor mode. > > Before r254082, bpf_track() in sys/net80211/ieee80211_freebsd.c was > identifying ieee80211 interfaces by checking to see if the value of > the ifp->if_start pointer was equal to ieee80211_start. r254082 was a > move away from using if_start to using if_transmit in the ieee80211 > stack, and bpf_track() was correspondingly updated to check the value > of ifp->if_transmit against ieee80211_vap_transmit. The problem is > that ifp->if_transmit is set to null_transmit by > ieee80211_vap_attach() in sys/net80211/ieee80211.c for interfaces that > are in monitor mode (code that has been in place since r195846). > > One fix that resolves the issue is to use what is likely to be a more > stable signature in the check in bpf_track(). > > A patch against r256155 is attached. > Hi! Good catch! Yeah, this is all very dirty code that needs to be ripped out. I'll get this committed ASAP. Thanks! -adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 10 17:33:40 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5576CF62 for ; Thu, 10 Oct 2013 17:33:40 +0000 (UTC) (envelope-from ksramanujan@gmail.com) Received: from mail-ie0-x229.google.com (mail-ie0-x229.google.com [IPv6:2607:f8b0:4001:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 28D112DF1 for ; Thu, 10 Oct 2013 17:33:40 +0000 (UTC) Received: by mail-ie0-f169.google.com with SMTP id tp5so5877015ieb.14 for ; Thu, 10 Oct 2013 10:33:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=cO6YvggHI4nOfHI4gXFyrjAlu7EIT0RsPalJuGfvtzI=; b=ps3I0VkMOlfYQfSt5SWA8p4V3vrSP9Z7pmA8l5gC6WyuWKyGy9/MMm21Bj9gaJROoK yxTth4Ov8Sn5JIuF6UoJQYpFcaX02PbRsmvEJVmu1INUUFgFH5+N9u2faX2VoKQkV1Lh pNeRzKzcRbH6bREvDnyvx4mjQmKbCZ2dYRzjHc23axNThS21sDUql6SoBnFgdllR3z9q /YUSR/gdXVPcbklduSYcY+buMNqCOdoBCgPa0ShNBkPmc/mu6l6HN1OebHtNvfrYLkdd bX2A9DZyFBZ4i7Jyfyv2zhMUfPnMJeoVkRqdnqCrfcmb/RKnjzFsbzsvwUkdJdTK0b13 sp+Q== MIME-Version: 1.0 X-Received: by 10.50.67.46 with SMTP id k14mr7549639igt.16.1381426419452; Thu, 10 Oct 2013 10:33:39 -0700 (PDT) Received: by 10.64.82.73 with HTTP; Thu, 10 Oct 2013 10:33:39 -0700 (PDT) Date: Thu, 10 Oct 2013 13:33:39 -0400 Message-ID: Subject: Ralink RT2860 frame aggregation From: Ramanujan Seshadri To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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, 10 Oct 2013 17:33:40 -0000 Hello all, i was testing some features of ralink rt2860 driver. i saw a bit weird results. below is the result of what i saw. The throughput achieved doesn't change much when the MPDU aggregation in an AMPDU goes from 3 to 8. And also, the driver doesn't seem to aggregate more than 8 MPDU's in an AMPDU even when the BA win size is set to max of 64. i was testing this by fixing the rate at MCS 15 Is there anything else i need to do to force the driver to aggregate more MPDU's in an AMPDU ? BA Win Size No. of MPDU's Throughput(Mbps) aggregated 1. 64 7-8 85.7 2. 32 6-7 84.2 3. 16 6-7 81.7 4. 8 6-7 79.9 5. 4 5 84.7 6. 2 3 71.8 7. 1 2 73.5 Thanks ram From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 10 20:41:11 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4966AFEC for ; Thu, 10 Oct 2013 20:41:11 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qc0-x22c.google.com (mail-qc0-x22c.google.com [IPv6:2607:f8b0:400d:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0A7762BC3 for ; Thu, 10 Oct 2013 20:41:10 +0000 (UTC) Received: by mail-qc0-f172.google.com with SMTP id k18so2253197qcv.31 for ; Thu, 10 Oct 2013 13:41:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=SDC9fZVBB79pVSbNzCiFnkjeDDcJjJXBJQR9CwnHotg=; b=IKHKavAaL4qXKotS/Rs4ueY8+2G1dh+uN06vsIA4AxLEHcRSTsrbXTeEF8wd9wUGwm StJcNP2MVgTaJJN1t4AdVW8wYLILmVyjxW6Q212K9twJQdst9EwL0UouYiMfbRjQ7Z+3 hrw07+2PMgUNSROzCQ6x2RyL1DIqv5sMz5BOFGRM2B2UpAkdy4GvMx6bUgeBKDf/g9rr msoU0Fyt3e9GCxAx4STr+GiBG3ZwwTIUlDI4hj0ky8z0Qh7LwEJaSJ3nzs8Uala/Betu WzgbwKNEDbywpKXRpyuy7e4ONVgs5Z0uecV4TvqYe3PdcO9D3fKCz0100MrSm5fDk3Nf zrIw== MIME-Version: 1.0 X-Received: by 10.229.116.197 with SMTP id n5mr14126902qcq.22.1381437670152; Thu, 10 Oct 2013 13:41:10 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Thu, 10 Oct 2013 13:41:10 -0700 (PDT) In-Reply-To: References: Date: Thu, 10 Oct 2013 13:41:10 -0700 X-Google-Sender-Auth: VqCNX3BczDWOGo0Q0dseHQJugTw Message-ID: Subject: Re: Ralink RT2860 frame aggregation From: Adrian Chadd To: Ramanujan Seshadri Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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, 10 Oct 2013 20:41:11 -0000 I forget .. is the driver or the NIC itself doing aggregation? -a On 10 October 2013 10:33, Ramanujan Seshadri wrote: > Hello all, > i was testing some features of ralink rt2860 driver. i saw a bit weird > results. below is the result of what i saw. The throughput achieved doesn't > change much when the MPDU aggregation in an AMPDU goes from 3 to 8. And > also, the driver doesn't seem to aggregate more than 8 MPDU's in an AMPDU > even when the BA win size is set to max of 64. i was testing this by fixing > the rate at MCS 15 > > Is there anything else i need to do to force the driver to aggregate more > MPDU's in an AMPDU ? > > > > BA Win Size No. of MPDU's Throughput(Mbps) > aggregated > > 1. 64 7-8 85.7 > > 2. 32 6-7 84.2 > > 3. 16 6-7 81.7 > > 4. 8 6-7 79.9 > > 5. 4 5 84.7 > > 6. 2 3 71.8 > > 7. 1 2 73.5 > > > Thanks > ram > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org > " > From owner-freebsd-wireless@FreeBSD.ORG Thu Oct 10 20:43:06 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 850EF10B for ; Thu, 10 Oct 2013 20:43:06 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qe0-x22f.google.com (mail-qe0-x22f.google.com [IPv6:2607:f8b0:400d:c02::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 430A02BDC for ; Thu, 10 Oct 2013 20:43:06 +0000 (UTC) Received: by mail-qe0-f47.google.com with SMTP id b4so2532770qen.6 for ; Thu, 10 Oct 2013 13:43:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=Zw05ddMxDacw3yFHgmt4praF2jLfEZI5o6OpXcIxsaA=; b=qIm0dS1qGwQ6cSHNQML6oxUl0wJl61zUK3LCn/ajUH90MYBq6gM4fQd1fHW6jDVxsn qWFBdIJTfgLOCqLQHWrZNHYokQMF0k+8E0PmFRfGum7daVkJd4y/v5eI6aIKXsQYz9IV MiXm7wFSzULucGdFSyPhCqK6c4HK5sIhUZVJl2uyiIBTM8wBQIibtZYByvjkRf0m02yl gM2C0cO3Eh7cnigTUIcX4WgDsIqHs16MyzP7M8KZMeAgfkjBntJc3FFpCZ+XcQLBJnTj Feh2UlzXtiqszEi6iks/hfD0h9uML7dhCLPJIISqr/qvYR1D9Q3PQmXlGMVNsAWHWokJ lR8A== MIME-Version: 1.0 X-Received: by 10.49.131.132 with SMTP id om4mr15151058qeb.2.1381437785368; Thu, 10 Oct 2013 13:43:05 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Thu, 10 Oct 2013 13:43:05 -0700 (PDT) In-Reply-To: References: Date: Thu, 10 Oct 2013 13:43:05 -0700 X-Google-Sender-Auth: jsTA7sNT71AQGbCoQT0eFClf0Q0 Message-ID: Subject: Re: Correlation values for Atheros adaptive noise immunity From: Adrian Chadd To: w Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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, 10 Oct 2013 20:43:06 -0000 Yeah, it's all a bit confusing. I'd have to re-read the PHY documentation i have here in order to really understand whta's going on. What are you trying to achieve herE? -adrian On 9 October 2013 20:03, w wrote: > Update: looking at the patent again: > http://www.freepatentsonline.com/7349503.html > > Note that bb_m1thres and bb_m2thres refer to normalized, > self-correlated thresholds, bb_m2count_thr refers to the number of > self-correlation values (wherein a typical count would not exceed 31), > and bb_use_self_corr_low refers to an enabling bit value. > > (but the variables are still quite confusing.) > > > ~ w ~ > > On Thu, Oct 10, 2013 at 10:12 AM, w wrote: > > Yup, I read the patent. I have also read the Atheros documentation for > > ANI (for a different hardware version but it says the operation is > > similar). > > > > Are we able to see physical layer parameters like signal level / > > correlation / channel state information, > > or are they hidden inside the hardware? > > > > ~ w ~ > > > > > > > > On Thu, Oct 10, 2013 at 10:05 AM, Adrian Chadd > wrote: > >> I'm not sure. I think it's a signal level. Have you read the ANI > patent(s) ? > >> > >> > >> > >> -adrian > >> > >> > >> > >> On 9 October 2013 19:04, w wrote: > >>> > >>> Is there any way I can printk the correlation values for ar5416_ani.c= ? > >>> > >>> I couldn=92t find the variable that contains the correlation value. > >>> Line 267 of the ar5416_ani.c file says: > >>> OS_REG_RMW_FIELD(ah, AR_PHY_SFCORR, > >>> AR_PHY_SFCORR_M1_THRESH, m1Thresh[on]); > >>> > >>> I don=92t know what the variables mean or what the function means or > >>> what data type the variables are because I want to printk them. > >>> > >>> References: > >>> > >>> > >>> > http://svnweb.freebsd.org/base/head/sys/dev/ath/ath_hal/ar5416/ar5416_ani= .c?view=3Dmarkup > >>> > >>> https://wiki.freebsd.org/dev/ath_hal%284%29/AutomaticNoiseImmunity > >>> > >>> ~ w ~ > >>> _______________________________________________ > >>> freebsd-wireless@freebsd.org mailing list > >>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > >>> To unsubscribe, send any mail to > >>> "freebsd-wireless-unsubscribe@freebsd.org" > >> > >> > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.or= g > " > From owner-freebsd-wireless@FreeBSD.ORG Fri Oct 11 01:30:08 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 20FD367A; Fri, 11 Oct 2013 01:30:08 +0000 (UTC) (envelope-from tx2023@gmail.com) Received: from mail-pa0-x22c.google.com (mail-pa0-x22c.google.com [IPv6:2607:f8b0:400e:c03::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E98CF2C1A; Fri, 11 Oct 2013 01:30:07 +0000 (UTC) Received: by mail-pa0-f44.google.com with SMTP id lf10so3611291pab.17 for ; Thu, 10 Oct 2013 18:30:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=W0uPUs8316JGl3E1/Up/9cprChDku9JsUDzTuxSfAHA=; b=TAltZRiK6XoAEjyzzfUX3a6yenTCx0TFkwYLpl9rKuOdvMMbXo0tdnLzRiSMVBrB6Z oLFyq48SE/z3xXaNaXt8FXLUJYRW9SVjnM9YaOJC3xagu/ccaOWvYUGVwi1cqL1Lq/fP pzMjtfEG3/n6gy0PtgO0s/Bnk9MscI6V+dunWvBBe15X3MXynjjWqDOrtsMY23GaX1qe c3DB0L7rm3dk80xHWn0UW7Om/SOmPiqiGGiJ+cblEksPQNtTp7ruciKr4bUsxqiZF+TS 7HjadDutJ5uga9cBavpeNUDrDngGUzNGzkPsGwjoK9egywe7wA3KIYpnCJ1ebTlXPZNj fIrA== MIME-Version: 1.0 X-Received: by 10.68.178.161 with SMTP id cz1mr17025428pbc.131.1381455007607; Thu, 10 Oct 2013 18:30:07 -0700 (PDT) Received: by 10.68.13.226 with HTTP; Thu, 10 Oct 2013 18:30:07 -0700 (PDT) In-Reply-To: References: Date: Fri, 11 Oct 2013 09:30:07 +0800 Message-ID: Subject: Re: Correlation values for Atheros adaptive noise immunity From: w To: Adrian Chadd Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable 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: Fri, 11 Oct 2013 01:30:08 -0000 Do you have the open source link for the PHY documentation so I could read = it? Actually my goal is quite simple I think: To test the effectiveness of ANI. Thanks very much. ~ w ~ On Fri, Oct 11, 2013 at 4:43 AM, Adrian Chadd wrote: > Yeah, it's all a bit confusing. I'd have to re-read the PHY documentation= i > have here in order to really understand whta's going on. > > What are you trying to achieve herE? > > > -adrian > > > > On 9 October 2013 20:03, w wrote: >> >> Update: looking at the patent again: >> http://www.freepatentsonline.com/7349503.html >> >> Note that bb_m1thres and bb_m2thres refer to normalized, >> self-correlated thresholds, bb_m2count_thr refers to the number of >> self-correlation values (wherein a typical count would not exceed 31), >> and bb_use_self_corr_low refers to an enabling bit value. >> >> (but the variables are still quite confusing.) >> >> >> ~ w ~ >> >> On Thu, Oct 10, 2013 at 10:12 AM, w wrote: >> > Yup, I read the patent. I have also read the Atheros documentation for >> > ANI (for a different hardware version but it says the operation is >> > similar). >> > >> > Are we able to see physical layer parameters like signal level / >> > correlation / channel state information, >> > or are they hidden inside the hardware? >> > >> > ~ w ~ >> > >> > >> > >> > On Thu, Oct 10, 2013 at 10:05 AM, Adrian Chadd >> > wrote: >> >> I'm not sure. I think it's a signal level. Have you read the ANI >> >> patent(s) ? >> >> >> >> >> >> >> >> -adrian >> >> >> >> >> >> >> >> On 9 October 2013 19:04, w wrote: >> >>> >> >>> Is there any way I can printk the correlation values for ar5416_ani.= c? >> >>> >> >>> I couldn=92t find the variable that contains the correlation value. >> >>> Line 267 of the ar5416_ani.c file says: >> >>> OS_REG_RMW_FIELD(ah, AR_PHY_SFCORR, >> >>> AR_PHY_SFCORR_M1_THRESH, m1Thresh[on]); >> >>> >> >>> I don=92t know what the variables mean or what the function means or >> >>> what data type the variables are because I want to printk them. >> >>> >> >>> References: >> >>> >> >>> >> >>> >> >>> http://svnweb.freebsd.org/base/head/sys/dev/ath/ath_hal/ar5416/ar541= 6_ani.c?view=3Dmarkup >> >>> >> >>> https://wiki.freebsd.org/dev/ath_hal%284%29/AutomaticNoiseImmunity >> >>> >> >>> ~ w ~ >> >>> _______________________________________________ >> >>> freebsd-wireless@freebsd.org mailing list >> >>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> >>> To unsubscribe, send any mail to >> >>> "freebsd-wireless-unsubscribe@freebsd.org" >> >> >> >> >> _______________________________________________ >> freebsd-wireless@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to >> "freebsd-wireless-unsubscribe@freebsd.org" > > From owner-freebsd-wireless@FreeBSD.ORG Fri Oct 11 01:34:22 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C64196F9 for ; Fri, 11 Oct 2013 01:34:22 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qe0-x22a.google.com (mail-qe0-x22a.google.com [IPv6:2607:f8b0:400d:c02::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 834242C5C for ; Fri, 11 Oct 2013 01:34:22 +0000 (UTC) Received: by mail-qe0-f42.google.com with SMTP id gc15so2758000qeb.15 for ; Thu, 10 Oct 2013 18:34:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=H22bSzuWssBN+yWynoquzw5bCO+zydZkxbaoSPAcJqk=; b=h5t0YrF2rA7isAchNPPD39NlbRq4APsDMxuB4bVgJqtU0II53rG1t1tnUqDqMTjWNM Xo+dQ393412Z8JyLnUMeVuOq7tt3OZp+R/jWujQk0gIxquoHz3CwuXPgmIAIoTXy67a2 2mQV3H3F9mrcSOD7EKpy3afgQbX5Srcgpj6kyvyqxbDop6/CqvkbRpYE90vDomOESJlf 2k8ySC9TikncPxFIEhLnyDYsSKuSrmXVV4XOrSxXhkOp/7zQ6BtJaMuxNpQDd+2PEF3z 2b8xDargH8v3l8i5wPh5BVfauBMyqMC5VQaYQAOx0GJRADeLIO16d9N5zRWNtTCTiGhC mkUw== MIME-Version: 1.0 X-Received: by 10.49.12.14 with SMTP id u14mr4737677qeb.74.1381455261710; Thu, 10 Oct 2013 18:34:21 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Thu, 10 Oct 2013 18:34:21 -0700 (PDT) In-Reply-To: References: Date: Thu, 10 Oct 2013 18:34:21 -0700 X-Google-Sender-Auth: EFpD7Chf2cru6sms4FFDR-osfBs Message-ID: Subject: Re: Correlation values for Atheros adaptive noise immunity From: Adrian Chadd To: w Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Fri, 11 Oct 2013 01:34:22 -0000 I don't have any open source PHY documentation. :) I'd have to write it. Which isn't a bad thing; I'm happy to go and re-read what I (legally, legitimately!) have from Atheros about their PHY design and ANI and write up what's implemented in the driver. The thing with ANI is that a lot of the parameters (like self-correlation thresholds) have to do with how signal detection in the PHY works. So it's not specifically noise immunity as much as it's tweaking the sensitivity range and thresholds of the receiver hardware. There's some interesting things that should be re-investigated (ie, the m1/m2 thresholds and how weak signal detection works); I vaguely recall when I was working there that ANI was doing it "wrong". I'll setup a meeting or two with the PHY team when I'm back in California and jot down some further notes about this. -adrian (note: so I'm legally allowed to have all this stuff and I'm legally allowed to code up open source drivers with it, but what I can't do is share the documentation I have. So no, I won't share it. But whatever goes into open source to improve their chips is open/fair game. Hence, I can write documentation and discuss whatever ends up in the open source drivers..) On 10 October 2013 18:30, w wrote: > Do you have the open source link for the PHY documentation so I could rea= d > it? > > Actually my goal is quite simple I think: To test the effectiveness of AN= I. > > Thanks very much. > > ~ w ~ > > On Fri, Oct 11, 2013 at 4:43 AM, Adrian Chadd wrote: > > Yeah, it's all a bit confusing. I'd have to re-read the PHY > documentation i > > have here in order to really understand whta's going on. > > > > What are you trying to achieve herE? > > > > > > -adrian > > > > > > > > On 9 October 2013 20:03, w wrote: > >> > >> Update: looking at the patent again: > >> http://www.freepatentsonline.com/7349503.html > >> > >> Note that bb_m1thres and bb_m2thres refer to normalized, > >> self-correlated thresholds, bb_m2count_thr refers to the number of > >> self-correlation values (wherein a typical count would not exceed 31), > >> and bb_use_self_corr_low refers to an enabling bit value. > >> > >> (but the variables are still quite confusing.) > >> > >> > >> ~ w ~ > >> > >> On Thu, Oct 10, 2013 at 10:12 AM, w wrote: > >> > Yup, I read the patent. I have also read the Atheros documentation f= or > >> > ANI (for a different hardware version but it says the operation is > >> > similar). > >> > > >> > Are we able to see physical layer parameters like signal level / > >> > correlation / channel state information, > >> > or are they hidden inside the hardware? > >> > > >> > ~ w ~ > >> > > >> > > >> > > >> > On Thu, Oct 10, 2013 at 10:05 AM, Adrian Chadd > >> > wrote: > >> >> I'm not sure. I think it's a signal level. Have you read the ANI > >> >> patent(s) ? > >> >> > >> >> > >> >> > >> >> -adrian > >> >> > >> >> > >> >> > >> >> On 9 October 2013 19:04, w wrote: > >> >>> > >> >>> Is there any way I can printk the correlation values for > ar5416_ani.c? > >> >>> > >> >>> I couldn=92t find the variable that contains the correlation value= . > >> >>> Line 267 of the ar5416_ani.c file says: > >> >>> OS_REG_RMW_FIELD(ah, AR_PHY_SFCORR, > >> >>> AR_PHY_SFCORR_M1_THRESH, m1Thresh[on]); > >> >>> > >> >>> I don=92t know what the variables mean or what the function means = or > >> >>> what data type the variables are because I want to printk them. > >> >>> > >> >>> References: > >> >>> > >> >>> > >> >>> > >> >>> > http://svnweb.freebsd.org/base/head/sys/dev/ath/ath_hal/ar5416/ar5416_ani= .c?view=3Dmarkup > >> >>> > >> >>> https://wiki.freebsd.org/dev/ath_hal%284%29/AutomaticNoiseImmunity > >> >>> > >> >>> ~ w ~ > >> >>> _______________________________________________ > >> >>> freebsd-wireless@freebsd.org mailing list > >> >>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > >> >>> To unsubscribe, send any mail to > >> >>> "freebsd-wireless-unsubscribe@freebsd.org" > >> >> > >> >> > >> _______________________________________________ > >> freebsd-wireless@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > >> To unsubscribe, send any mail to > >> "freebsd-wireless-unsubscribe@freebsd.org" > > > > > From owner-freebsd-wireless@FreeBSD.ORG Fri Oct 11 04:01:15 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3168DBE6; Fri, 11 Oct 2013 04:01:15 +0000 (UTC) (envelope-from tx2023@gmail.com) Received: from mail-pb0-x22e.google.com (mail-pb0-x22e.google.com [IPv6:2607:f8b0:400e:c01::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0190F23DC; Fri, 11 Oct 2013 04:01:14 +0000 (UTC) Received: by mail-pb0-f46.google.com with SMTP id rq2so3561702pbb.5 for ; Thu, 10 Oct 2013 21:01:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=jhPozvZeaQ+W8muaVZPKL0bEzQYGrun9jX7g823wNqI=; b=Y+uj7o87k072JdEk0ieTh3slf9bOpvDdssi2WgnkFlhTs+D+8h/HZLfuRSgmgmKSz5 9GGpcex6qqLXM81bgMhWs3ZORLJkkhQ4J/LWQR2XOcR60VE0lI5bvCJM2iXXtVRLZgXS XHmwDKZ789D7O0N38qMjz1Pk3M660NAHlZGNDXIji2OqpxV2Uo9Bm7g7+LCbnH1ZJuvt hK2SqUeuI2SJjJOdCo91l+69G5FY2dppd9KiUa+wzyqyVJhgKEQjz+NjRb2ScIfSQTOk hlKv7ozw0NYJjA0LRSL6QwdqgW3J3vXY8GjR+PG8VsFlcUpSWKyy6TjAJAI7RmPRw1qX 2MHQ== MIME-Version: 1.0 X-Received: by 10.66.161.38 with SMTP id xp6mr19025711pab.145.1381464074643; Thu, 10 Oct 2013 21:01:14 -0700 (PDT) Received: by 10.68.13.226 with HTTP; Thu, 10 Oct 2013 21:01:14 -0700 (PDT) In-Reply-To: References: Date: Fri, 11 Oct 2013 12:01:14 +0800 Message-ID: Subject: Re: Correlation values for Atheros adaptive noise immunity From: w To: Adrian Chadd Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable 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: Fri, 11 Oct 2013 04:01:15 -0000 With open source, we should be able to change it from "wrong" to "right" :) I just spotted a little more bugs to be corrected: \freebsd\sys\dev\ath\ath_hal\ar5416\ar5416_ani.c Search "+1 <" (3 hits in 1 file) Line 382: if (aniState->noiseImmunityLevel+1 < params->maxNoiseImmunityLevel) { Line 388: if (aniState->spurImmunityLevel+1 < params->maxSpurImmunityLevel) { Line 480: aniState->noiseImmunityLevel+1 < params->maxNoiseImmunityLevel)) { I think there shouldn=92t be a +1 before the the < sign because the variables are integers. Thanks again for your help. ~ w ~ On Fri, Oct 11, 2013 at 9:34 AM, Adrian Chadd wrote: > I don't have any open source PHY documentation. :) I'd have to write it. > > Which isn't a bad thing; I'm happy to go and re-read what I (legally, > legitimately!) have from Atheros about their PHY design and ANI and write= up > what's implemented in the driver. > > The thing with ANI is that a lot of the parameters (like self-correlation > thresholds) have to do with how signal detection in the PHY works. So it'= s > not specifically noise immunity as much as it's tweaking the sensitivity > range and thresholds of the receiver hardware. > > There's some interesting things that should be re-investigated (ie, the > m1/m2 thresholds and how weak signal detection works); I vaguely recall w= hen > I was working there that ANI was doing it "wrong". I'll setup a meeting o= r > two with the PHY team when I'm back in California and jot down some furth= er > notes about this. > > > > -adrian > > (note: so I'm legally allowed to have all this stuff and I'm legally allo= wed > to code up open source drivers with it, but what I can't do is share the > documentation I have. So no, I won't share it. But whatever goes into ope= n > source to improve their chips is open/fair game. Hence, I can write > documentation and discuss whatever ends up in the open source drivers..) > > > > On 10 October 2013 18:30, w wrote: >> >> Do you have the open source link for the PHY documentation so I could re= ad >> it? >> >> Actually my goal is quite simple I think: To test the effectiveness of >> ANI. >> >> Thanks very much. >> >> ~ w ~ >> >> On Fri, Oct 11, 2013 at 4:43 AM, Adrian Chadd wrote= : >> > Yeah, it's all a bit confusing. I'd have to re-read the PHY >> > documentation i >> > have here in order to really understand whta's going on. >> > >> > What are you trying to achieve herE? >> > >> > >> > -adrian >> > >> > >> > >> > On 9 October 2013 20:03, w wrote: >> >> >> >> Update: looking at the patent again: >> >> http://www.freepatentsonline.com/7349503.html >> >> >> >> Note that bb_m1thres and bb_m2thres refer to normalized, >> >> self-correlated thresholds, bb_m2count_thr refers to the number of >> >> self-correlation values (wherein a typical count would not exceed 31)= , >> >> and bb_use_self_corr_low refers to an enabling bit value. >> >> >> >> (but the variables are still quite confusing.) >> >> >> >> >> >> ~ w ~ >> >> >> >> On Thu, Oct 10, 2013 at 10:12 AM, w wrote: >> >> > Yup, I read the patent. I have also read the Atheros documentation >> >> > for >> >> > ANI (for a different hardware version but it says the operation is >> >> > similar). >> >> > >> >> > Are we able to see physical layer parameters like signal level / >> >> > correlation / channel state information, >> >> > or are they hidden inside the hardware? >> >> > >> >> > ~ w ~ >> >> > >> >> > >> >> > >> >> > On Thu, Oct 10, 2013 at 10:05 AM, Adrian Chadd >> >> > wrote: >> >> >> I'm not sure. I think it's a signal level. Have you read the ANI >> >> >> patent(s) ? >> >> >> >> >> >> >> >> >> >> >> >> -adrian >> >> >> >> >> >> >> >> >> >> >> >> On 9 October 2013 19:04, w wrote: >> >> >>> >> >> >>> Is there any way I can printk the correlation values for >> >> >>> ar5416_ani.c? >> >> >>> >> >> >>> I couldn=92t find the variable that contains the correlation valu= e. >> >> >>> Line 267 of the ar5416_ani.c file says: >> >> >>> OS_REG_RMW_FIELD(ah, AR_PHY_SFCORR, >> >> >>> AR_PHY_SFCORR_M1_THRESH, m1Thresh[on]); >> >> >>> >> >> >>> I don=92t know what the variables mean or what the function means= or >> >> >>> what data type the variables are because I want to printk them. >> >> >>> >> >> >>> References: >> >> >>> >> >> >>> >> >> >>> >> >> >>> >> >> >>> http://svnweb.freebsd.org/base/head/sys/dev/ath/ath_hal/ar5416/ar= 5416_ani.c?view=3Dmarkup >> >> >>> >> >> >>> https://wiki.freebsd.org/dev/ath_hal%284%29/AutomaticNoiseImmunit= y >> >> >>> >> >> >>> ~ w ~ >> >> >>> _______________________________________________ >> >> >>> freebsd-wireless@freebsd.org mailing list >> >> >>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> >> >>> To unsubscribe, send any mail to >> >> >>> "freebsd-wireless-unsubscribe@freebsd.org" >> >> >> >> >> >> >> >> _______________________________________________ >> >> freebsd-wireless@freebsd.org mailing list >> >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> >> To unsubscribe, send any mail to >> >> "freebsd-wireless-unsubscribe@freebsd.org" >> > >> > > > From owner-freebsd-wireless@FreeBSD.ORG Fri Oct 11 18:18:59 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3BDE995F; Fri, 11 Oct 2013 18:18:59 +0000 (UTC) (envelope-from ksramanujan@gmail.com) Received: from mail-ie0-x22b.google.com (mail-ie0-x22b.google.com [IPv6:2607:f8b0:4001:c03::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0399228FD; Fri, 11 Oct 2013 18:18:58 +0000 (UTC) Received: by mail-ie0-f171.google.com with SMTP id at1so8837332iec.2 for ; Fri, 11 Oct 2013 11:18:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=BiabNxD+Gh7oEZ2hafeqZGxqJWwYxcG9uDn6lh6Az/8=; b=hPoFVcR8AUwLlF+c3PZWHIScvQxUdYh/c8in/uxEOW3e3xy/opXD9dJNMvV2FTA1WR L8RLEc0UzeL86R+GIlCc4NKCQmodcu9dSvseCxVeYWAGnifL2c4hoQyvYFOsdfxYPshG M5vpfV47/nJX6fYSt4nIj2KyT0NkTq4PUTZiJMMlBmszUviCpEetZRNXxq7+12WK00Xr P4gC3nlKgZ457s84mkK34K9fBdkv+RwN3v2Y9qdqT6J/pn+8I/EKyTZrLIt90QCg8TIT cbDbCkmT3EItzOV7r/ri0YDQibBBr7MVx3nWY0473289xUbSJ6SIWfqbMdwmyF3/dqKc sDzQ== MIME-Version: 1.0 X-Received: by 10.50.103.6 with SMTP id fs6mr3916897igb.16.1381515538182; Fri, 11 Oct 2013 11:18:58 -0700 (PDT) Received: by 10.64.82.73 with HTTP; Fri, 11 Oct 2013 11:18:58 -0700 (PDT) In-Reply-To: References: Date: Fri, 11 Oct 2013 14:18:58 -0400 Message-ID: Subject: Re: Ralink RT2860 frame aggregation From: Ramanujan Seshadri To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Fri, 11 Oct 2013 18:18:59 -0000 It's in the NIC. But it seems that it sometimes aggregates more than the set BA win size (in the driver). In fact i was wondering - if it can actually achieve up to 80 Mbps throughput with just 8 frames aggregated. In fact the aggregation size doesn't seem to matter much for the throughput because any aggregation from 5-8 seems to get the same throughput. So, i was wondering if this is something weird in NIC or can we do some thing to control it in the driver ? ram On Thu, Oct 10, 2013 at 4:41 PM, Adrian Chadd wrote: > I forget .. is the driver or the NIC itself doing aggregation? > > > -a > > > On 10 October 2013 10:33, Ramanujan Seshadri wrote: > >> Hello all, >> i was testing some features of ralink rt2860 driver. i saw a bit weird >> results. below is the result of what i saw. The throughput achieved >> doesn't >> change much when the MPDU aggregation in an AMPDU goes from 3 to 8. And >> also, the driver doesn't seem to aggregate more than 8 MPDU's in an AMPDU >> even when the BA win size is set to max of 64. i was testing this by >> fixing >> the rate at MCS 15 >> >> Is there anything else i need to do to force the driver to aggregate more >> MPDU's in an AMPDU ? >> >> >> >> BA Win Size No. of MPDU's Throughput(Mbps) >> aggregated >> >> 1. 64 7-8 85.7 >> >> 2. 32 6-7 84.2 >> >> 3. 16 6-7 81.7 >> >> 4. 8 6-7 79.9 >> >> 5. 4 5 84.7 >> >> 6. 2 3 71.8 >> >> 7. 1 2 73.5 >> >> >> Thanks >> ram >> _______________________________________________ >> freebsd-wireless@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to " >> freebsd-wireless-unsubscribe@freebsd.org" >> > >