From owner-freebsd-wireless@FreeBSD.ORG Sun Apr 8 05:54:20 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 97FD51065670; Sun, 8 Apr 2012 05:54:20 +0000 (UTC) (envelope-from adrian@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6AB5C8FC12; Sun, 8 Apr 2012 05:54:20 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q385sKKw051438; Sun, 8 Apr 2012 05:54:20 GMT (envelope-from adrian@freefall.freebsd.org) Received: (from adrian@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q385sKSB051434; Sun, 8 Apr 2012 05:54:20 GMT (envelope-from adrian) Date: Sun, 8 Apr 2012 05:54:20 GMT Message-Id: <201204080554.q385sKSB051434@freefall.freebsd.org> To: andrew@atrens.ca, adrian@FreeBSD.org, freebsd-wireless@FreeBSD.org From: adrian@FreeBSD.org Cc: Subject: Re: kern/166642: [ieee80211] [patch] in 802.11n mode for FreeBSD AP, having a station in powersave cripples AP TX. X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Apr 2012 05:54:20 -0000 Synopsis: [ieee80211] [patch] in 802.11n mode for FreeBSD AP, having a station in powersave cripples AP TX. State-Changed-From-To: open->patched State-Changed-By: adrian State-Changed-When: Sun Apr 8 05:53:39 UTC 2012 State-Changed-Why: I've patched this in r234009. I busted things, my bad. :-) http://www.freebsd.org/cgi/query-pr.cgi?pr=166642 From owner-freebsd-wireless@FreeBSD.ORG Sun Apr 8 11:05:54 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 966121065694 for ; Sun, 8 Apr 2012 11:05:54 +0000 (UTC) (envelope-from venture37@gmail.com) Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by mx1.freebsd.org (Postfix) with ESMTP id 162258FC14 for ; Sun, 8 Apr 2012 11:05:53 +0000 (UTC) Received: by wibhj6 with SMTP id hj6so1411860wib.13 for ; Sun, 08 Apr 2012 04:05:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=ZCIweWtBoVURECIbIijYRYLfgoJS1hHL9NYmNwbI8SE=; b=dlIm7ZqNJL8/q8JGpXf8Si6mXJi7Io0X8PMPOhtvWeNwtTkzcQB/hjg8DhjNmHrPDZ anj3SM7TxWzdAjQ4ApBkvjU3Sr3sC9nQGSEvrvCJsuthK5+80z3uZ7OdkqiWrBGDpXUZ BWunbxVlFhbjFUP0E82XdpkVGZ6tguNxhdhyKIbe/H7mfFqaaisQXmbzHF8lyTIJou6k DRqDeZkRpfpL6NrW6kLCNFbwB4c4o9hnMhhSuWyQk+uNYj+SFHrDMIvmrDL9GxEFhKH+ Ch3VXI3mgT1WieLPBHmlcFKSdeJhvPlm3PoqH4C4VL012HXX642ObTaf616Zgnc2c8Yi zASQ== Received: by 10.180.83.72 with SMTP id o8mr8546070wiy.5.1333883152879; Sun, 08 Apr 2012 04:05:52 -0700 (PDT) Received: from Sevans-MacBook-Pro.local (cpc2-brig17-2-0-cust527.3-3.cable.virginmedia.com. [81.101.198.16]) by mx.google.com with ESMTPS id n8sm35064574wix.10.2012.04.08.04.05.51 (version=SSLv3 cipher=OTHER); Sun, 08 Apr 2012 04:05:52 -0700 (PDT) Message-ID: <4F81710E.2070402@gmail.com> Date: Sun, 08 Apr 2012 12:05:50 +0100 From: Sevan / Venture37 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: freebsd-wireless@freebsd.org References: <4F8052EB.5090007@gmail.com> <4F806763.7040404@gmail.com> <4F8095D8.5020701@gmail.com> <4F80A38C.3080602@gmail.com> <4F80A81C.2070602@gmail.com> <4F80A9B4.2000500@gmail.com> <4F80AEC3.2050602@gmail.com> <4F80C5FC.70607@gmail.com> In-Reply-To: <4F80C5FC.70607@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: ath(4) fails to attach X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Apr 2012 11:05:54 -0000 On 07/04/2012 23:55, Sevan / Venture37 wrote: > On 07/04/2012 23:22, Adrian Chadd wrote: >> Damn. What the heck? What's the panic message, and which interrupt? managed to reproduce the crash, if I boot i386 9.0-Release iso reboot then attempt to boot the i386 snapshot of -HEAD, the snapshot will panic on boot http://imageshack.us/photo/my-images/17/img1035qr.jpg/ http://imageshack.us/photo/my-images/267/img1034qf.jpg/ http://imageshack.us/photo/my-images/9/img1033qq.jpg/ Sevan From owner-freebsd-wireless@FreeBSD.ORG Sun Apr 8 15:25:42 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 30001106564A; Sun, 8 Apr 2012 15:25:42 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id BCADF8FC14; Sun, 8 Apr 2012 15:25:41 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (89.112.15.178.pppoe.eltel.net [89.112.15.178]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 8419E4AC1C; Sun, 8 Apr 2012 19:25:40 +0400 (MSK) Date: Sun, 8 Apr 2012 19:25:39 +0400 From: Lev Serebryakov X-Priority: 3 (Normal) Message-ID: <165226504.20120408192539@serebryakov.spb.ru> To: Adrian Chadd In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: request for testing: please test -head ath 11n stuff X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Apr 2012 15:25:42 -0000 Hello, Adrian. You wrote 7 =E0=EF=F0=E5=EB=FF 2012 =E3., 10:08:47: > * BAR TX handling; > * RTS aggregation limitations for AR5416 (8K aggregates); > * Fix duration and HT protection mode handling; > * flip on HT protection mode (RTS) by default, configurable by 'htprotmod= e'. > I'd appreciate it if users tested this code out. > Next: re-working the power save queue handling stuff in ath(4). So far, so good. My 9220 stops to blame about stalled DMA, missed beacons, etc. Also, I've put my hands on Cisco Spectre Expert card for several hours (ultra-expensive hardware specter analyzer in form-factor of PC Card) and becomes sure, that my environment is complete mess. ``Channel 6'' and around is overloaded with 100% duty cycle and very powerful signal, and others twop 802.11g "true" channels are not free of noise too :( --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Sun Apr 8 19:37:00 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B66C610656D9; Sun, 8 Apr 2012 19:37:00 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 4ECB88FC0C; Sun, 8 Apr 2012 19:37:00 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (89.112.15.178.pppoe.eltel.net [89.112.15.178]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 2CE744AC1C; Sun, 8 Apr 2012 23:36:59 +0400 (MSK) Date: Sun, 8 Apr 2012 23:36:57 +0400 From: Lev Serebryakov X-Priority: 3 (Normal) Message-ID: <1322303419.20120408233657@serebryakov.spb.ru> To: Adrian Chadd , freebsd-wireless@freebsd.org In-Reply-To: <165226504.20120408192539@serebryakov.spb.ru> References: <165226504.20120408192539@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: Subject: Re: request for testing: please test -head ath 11n stuff X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Apr 2012 19:37:00 -0000 Hello, Lev. You wrote 8 =E0=EF=F0=E5=EB=FF 2012 =E3., 19:25:39: >> * BAR TX handling; >> * RTS aggregation limitations for AR5416 (8K aggregates); >> * Fix duration and HT protection mode handling; >> * flip on HT protection mode (RTS) by default, configurable by 'htprotmo= de'. >> I'd appreciate it if users tested this code out. >> Next: re-working the power save queue handling stuff in ath(4). > So far, so good. My 9220 stops to blame about stalled DMA, missed > beacons, etc. Ooops :( Apr 8 22:42:23 gateway kernel: ath0: stuck beacon; resetting (bmiss count = 4) Apr 8 22:59:52 gateway kernel: ath0: stuck beacon; resetting (bmiss count = 4) --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Sun Apr 8 19:41:09 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4919106566B; Sun, 8 Apr 2012 19:41:09 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by mx1.freebsd.org (Postfix) with ESMTP id B05978FC16; Sun, 8 Apr 2012 19:41:09 +0000 (UTC) Received: by dadz14 with SMTP id z14so15732687dad.17 for ; Sun, 08 Apr 2012 12:41:09 -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 :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=JyF+Y6MgiW8LSfEIaMXmmuUF2nTwRcZ0q759XxILmNU=; b=MDAabRY0jbogvZ3UzlSIH8gNhRoFmOTVwmkz3NWw7LQeCFt6jngwD6gW+yqMBudCsu opf2dJgeW0XJQD8slV49F6r5+iinchgVYkRhD9B1vlubNLECuefuuBtyZH7XIiA0EWhv e10Pu2sZlrGKPQt5uw7mlfwcMV/XRfByZb1nynJmZN/p3M3T/pjAYmhVKupjzdI0vny3 XRtRnabwXu2HuIWz0nlfIKen8gvu06RcVrw8I2UtDk7AH/FwSyOZo2Pqk58Kn0lMC8KI ESzxbTdY2tD1U/p9gx5ocMDg2tb9RUq/cGJZNgfGy1pKunVvZKgtfoZVwC3Ccraz0Opj T0Ow== MIME-Version: 1.0 Received: by 10.68.131.67 with SMTP id ok3mr2358589pbb.159.1333914069169; Sun, 08 Apr 2012 12:41:09 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.142.134.6 with HTTP; Sun, 8 Apr 2012 12:41:09 -0700 (PDT) In-Reply-To: <1322303419.20120408233657@serebryakov.spb.ru> References: <165226504.20120408192539@serebryakov.spb.ru> <1322303419.20120408233657@serebryakov.spb.ru> Date: Sun, 8 Apr 2012 12:41:09 -0700 X-Google-Sender-Auth: B1F5JKjmT228pvh4CLUjl_bPB-c Message-ID: From: Adrian Chadd To: Lev Serebryakov Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: request for testing: please test -head ath 11n stuff X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Apr 2012 19:41:10 -0000 2012/4/8 Lev Serebryakov : > Apr =A08 22:42:23 gateway kernel: ath0: stuck beacon; resetting (bmiss co= unt 4) > Apr =A08 22:59:52 gateway kernel: ath0: stuck beacon; resetting (bmiss co= unt 4) If you ahve a noisy environment, I can't really stop them from happening. I'll work on trying to add some debugging to narrow down WHY (at least to try and indicate if it's a MAC hang, BB hang, RX_CLEAR hang, etc) but that's about all I can do. I'd grab that expensive piece of kit of yours and go _find_ the noise sources. :) Adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 9 01:51:28 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7A85A106566C for ; Mon, 9 Apr 2012 01:51:28 +0000 (UTC) (envelope-from nm.knife@gmail.com) Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by mx1.freebsd.org (Postfix) with ESMTP id 0EB278FC08 for ; Mon, 9 Apr 2012 01:51:27 +0000 (UTC) Received: by wibhq7 with SMTP id hq7so1749835wib.13 for ; Sun, 08 Apr 2012 18:51:27 -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=UTkuKqDdH8bOODY/UZ4y2r76VM/ghxB7NsrfnJKakZg=; b=XobcWHE+FAQda647wHlQJg9LoudnQOKI4HD9vlUZK39c/EhHha6FaRwr0BEh5j+ZRF W8Q9+Znh4MLdXWUHsZIPucuoOOYgRYs+CVMdaJVeCPjq91UO6joMmaIP5x9oIU/3CZKO jMlVk7atuVKr/TgyZvgpg7Eybo1kic9Oy0nW3ATWj9mSg/b4xVVAkyJwoM+CJFQhM+nq WbW1Q/1JZQykSq3W04eMXf066lrUaddzgRlJwF4e86coy00Xq9AF8aoSaSqpKnWDFkvu +1YaNFr3RDn3l3DtunVzkEqFpCs9T9yqo67azHs+SBMX85tnuAEZanEv1ZbFvx3MTYx6 RKUQ== MIME-Version: 1.0 Received: by 10.180.101.8 with SMTP id fc8mr12356169wib.12.1333936286948; Sun, 08 Apr 2012 18:51:26 -0700 (PDT) Received: by 10.227.58.68 with HTTP; Sun, 8 Apr 2012 18:51:26 -0700 (PDT) Date: Sun, 8 Apr 2012 18:51:26 -0700 Message-ID: From: =?windows-1251?B?y/7h7uzo8CDD8Ojj7vDu4g==?= To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Intel 6250 and WiMax X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2012 01:51:28 -0000 Hello, I see that a couple previous threads don't guarantee WiMax on the Intel cards. Do you know if there is any news if they work? I want to order WiMax service and was wondering if FreeBSD 9 has support for it. The card is Intel 6250. Cheers. -- Lyubomir Grigorov (bgalakazam) From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 9 03:11:59 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0D446106564A; Mon, 9 Apr 2012 03:11:59 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D459C8FC08; Mon, 9 Apr 2012 03:11:58 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q393BwwZ071075; Mon, 9 Apr 2012 03:11:58 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q393BwVd071056; Mon, 9 Apr 2012 03:11:58 GMT (envelope-from linimon) Date: Mon, 9 Apr 2012 03:11:58 GMT Message-Id: <201204090311.q393BwVd071056@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/164951: [ath] [patch] Problem build of if_ath driver with certain mode X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2012 03:11:59 -0000 Old Synopsis: Problem build of if_ath driver with certain mode New Synopsis: [ath] [patch] Problem build of if_ath driver with certain mode Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Mon Apr 9 03:11:29 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=164951 From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 9 03:20:59 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4F1A3106566C for ; Mon, 9 Apr 2012 03:20:59 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 1CEEC8FC14 for ; Mon, 9 Apr 2012 03:20:59 +0000 (UTC) Received: by pbcwz17 with SMTP id wz17so4610455pbc.13 for ; Sun, 08 Apr 2012 20:20:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:to:reply-to:subject:in-reply-to:x-mailer :mime-version:content-type; bh=VBGHspmpDrzGbG+mKOkGDEQvPXP1+dtW+U32qDBDxfE=; b=Q0hS5Y4sqDjiV0afsv6Js/r9Y2um9gsO65QaxcA6Zlnr5bJizuGNwb9GocSytYJwZ0 QS83IZi0616eC15vnnP0PsOhWNKqFzKePNKmiukufyYXz4DFugLUMYsU5DqFFbDVnT2O T89GxLANlX8AlqQSthF+bbEn3r1EMIwyi5pkysIl0GsuvmaMxXhv2oY8OuWTffuqs2VN If8kRKcRw1tZFLezJtFleGK61morSpB2yRlxYir11cBdzcVCC5MU5t/QADTe43Fv8T2k OZwaZTLVOezTHRF/raZeGu6U5hrfeT9vaW45wl7X03w+8wVXMeG4oRVis+GCZLIxIpwE ssdg== Received: by 10.68.226.131 with SMTP id rs3mr5673347pbc.52.1333941658518; Sun, 08 Apr 2012 20:20:58 -0700 (PDT) Received: from www.palm.com ([166.134.26.224]) by mx.google.com with ESMTPS id b4sm13648289pbc.7.2012.04.08.20.20.53 (version=SSLv3 cipher=OTHER); Sun, 08 Apr 2012 20:20:57 -0700 (PDT) Message-ID: <4f825599.e40c440a.4632.797d@mx.google.com> Date: Sun, 8 Apr 2012 20:20:48 -0700 From: "Adrian Chadd" To: "=?UTF-8?B?0JvRjtCx0L7QvNC40YAg0JPRgNC40LPQvtGA0L7Qsg==?=" , "freebsd-wireless@freebsd.org" In-Reply-To: X-Mailer: Palm webOS v1.0.1 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: Intel 6250 and WiMax X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Adrian Chadd 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, 09 Apr 2012 03:20:59 -0000 I'm not sure.. Do we need a wimax stack with that? Hows the nic work under linux? I would be interested in helping with a wimax stack and driver if there is= sufficient interest and someone else working on the code. Unfortunately the bay area is losing wimax coverage, so I don't know how fe= asible it would be for me to help.. Adrian Sent from my Palm Pre on AT&T On Apr 8, 2012 6:51 PM, =D0=9B=D1=8E=D0=B1=D0=BE=D0=BC=D0=B8=D1=80 =D0=93= =D1=80=D0=B8=D0=B3=D0=BE=D1=80=D0=BE=D0=B2 <nm.knife@gmail.com> wrote= :=20 Hello, I see that a couple previous threads don't guarantee WiMax on the Intel cards. Do you know if there is any news if they work? I want to order WiMax service and was wondering if FreeBSD 9 has support for it. The card is Intel 6250. Cheers. --=20 Lyubomir Grigorov (bgalakazam) _______________________________________________ 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 Apr 9 05:29:32 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 93DE4106566C for ; Mon, 9 Apr 2012 05:29:32 +0000 (UTC) (envelope-from nm.knife@gmail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 1FA228FC08 for ; Mon, 9 Apr 2012 05:29:31 +0000 (UTC) Received: by wgbds12 with SMTP id ds12so3904018wgb.31 for ; Sun, 08 Apr 2012 22:29:31 -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=Xj4Mo2Jmqc4dF4iTlXN011sV6DFUrHvGDiF1z6PIC7E=; b=ENUDmtSrOG2+Nha80Seu0/1AIHtHA9lEyFhFQN748xZvEKxf6iA5ZpCUbcUo/rOrBc yjhoEkW8Ru04e4+PmijQp7XTfMnUmEE6/aJcA/LjuT59JDI5f1c9h/Yi7jHH5WG7Komq M+6+l3wYjki2/+k1m61iB1QupCTi3hIQC/vO9kj37l2Xan1OjzpoUL67EhiIgEDXWruA 6/ERJ1i/pObGg3YvvuFPRuGxS4fUFSqQaP2TtrUhHRImGU1WzCQZcB7ZPVS4MmYEfWXc vBHlu5MYj6G1jxUd08Y3TvK/+ayLS04V2EAlRhOyat+Bx/GRs66pUUlsgeRsJ6VAMONj RigQ== MIME-Version: 1.0 Received: by 10.216.139.79 with SMTP id b57mr3183568wej.37.1333949370977; Sun, 08 Apr 2012 22:29:30 -0700 (PDT) Received: by 10.227.58.68 with HTTP; Sun, 8 Apr 2012 22:29:30 -0700 (PDT) In-Reply-To: <4f825599.e40c440a.4632.797d@mx.google.com> References: <4f825599.e40c440a.4632.797d@mx.google.com> Date: Sun, 8 Apr 2012 22:29:30 -0700 Message-ID: From: =?windows-1251?B?y/7h7uzo8CDD8Ojj7vDu4g==?= To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: Intel 6250 and WiMax X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2012 05:29:32 -0000 > Unfortunately the bay area is losing wimax coverage, so I don't know how feasible it would be for me to help.. Oh, I thought CLEAR will keep it up for at least a couple years? If not, I should just get a 6300 to take advantage of my 3x3 antenna. (and don't order their service) I know WiMax is an a downward spiral but it is steal cheaper than ANY 4G w/wo LTE and there is also no modem needed. I really don't know why they have to totally drop WiMax, at least for laptops... oh well. P.S. I can always dualboot and test anything that may need testing, but if there is no interest, then I guess it's pointless. I do need mobile broadband, however, and CLEAR is the cheapest as it is right now. Also, no limits. From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 9 05:33:05 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 24FA01065670 for ; Mon, 9 Apr 2012 05:33:05 +0000 (UTC) (envelope-from nm.knife@gmail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id A0E578FC12 for ; Mon, 9 Apr 2012 05:33:04 +0000 (UTC) Received: by wgbds12 with SMTP id ds12so3905748wgb.31 for ; Sun, 08 Apr 2012 22:33:03 -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=of9nF98Axz4jxiurlOkeqhinPkwk5W22D2SeYCTaz6Y=; b=ESQJXjeUjnWMIG8Zy1bevHZ+/VyqYplbGUOmGsAARuRAuprO7udRprSrrLsFSEBBcz 8fci8qiUpWjJSWAujOao7viadvHFHWhdwlZplmEZ7kbykn/KDzc8zESPSA7zKFL0r5q0 gINDcY8g/b97nalqVu1mW9V4Lbcdwji6m2W997BE69NVXXGdUGS1dWms5GGX4eGe0jIr WiVlhmMPSWgNRCEUa2FURwZm7rbAFZB2emoJgVHy+zCURVJZFrrLzntgBH1LR5Kl5CTd nxiyRpkUFfouk8XGRvvdOeVK3doQ9X5eqztLXM5iKs0GFbY8nH/vxuxlocC9+Me/0PYf aoMA== MIME-Version: 1.0 Received: by 10.216.138.202 with SMTP id a52mr3362276wej.53.1333949583832; Sun, 08 Apr 2012 22:33:03 -0700 (PDT) Received: by 10.227.58.68 with HTTP; Sun, 8 Apr 2012 22:33:03 -0700 (PDT) In-Reply-To: References: <4f825599.e40c440a.4632.797d@mx.google.com> Date: Sun, 8 Apr 2012 22:33:03 -0700 Message-ID: From: =?windows-1251?B?y/7h7uzo8CDD8Ojj7vDu4g==?= To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: Intel 6250 and WiMax X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2012 05:33:05 -0000 P.S. 6250 has Wimax support in GNU/Linux under Fedora 14+ and Ubuntu, so about 1 year now. -- Lyubomir Grigorov (bgalakazam) From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 9 05:48:20 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 94354106564A for ; Mon, 9 Apr 2012 05:48:20 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by mx1.freebsd.org (Postfix) with ESMTP id 600028FC0A for ; Mon, 9 Apr 2012 05:48:20 +0000 (UTC) Received: by dadz14 with SMTP id z14so16819669dad.17 for ; Sun, 08 Apr 2012 22:48:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:to:cc:reply-to:subject:in-reply-to:x-mailer :mime-version:content-type; bh=oIpOvXjiaeYzd0ZWvWsbPeBR59TkWXZdkfDhlM67e8E=; b=1E3W2nB1RIW81Ko2ir8BAcoSM73EMxFM/hMnW/AyOEAIUwubJItXV2/TCyObi3CZPI xt31ZsBReVa1J/asBRIfJBpBBJcmAJKcjY5SAPA0l278qjARpN1Vs5OohGrVNC/vv7bA BvuPU4gvd9DrOcNUcuqJ90C5VKX42vKXMsl3NXlh4LMUYqnx5/keiNXEJzuiRjWOXLrY huoIYueft79rTgQERY16K+mXzR/4PVr4ij4DpFDbIJUOfnl4p5FZylshxBysd9qW5Uzp x8Y+DlEvFF6+K2df9mo5RDWBjb4h64G9lG7OobzqFVhPHKFh+e2gmqZEy2UsPtk0rQBZ e1oA== Received: by 10.68.234.37 with SMTP id ub5mr3004741pbc.103.1333950499915; Sun, 08 Apr 2012 22:48:19 -0700 (PDT) Received: from www.palm.com ([166.134.26.224]) by mx.google.com with ESMTPS id l1sm13968892pbe.54.2012.04.08.22.48.15 (version=SSLv3 cipher=OTHER); Sun, 08 Apr 2012 22:48:19 -0700 (PDT) Message-ID: <4f827823.4114440a.4f0e.ffff874a@mx.google.com> Date: Sun, 8 Apr 2012 22:48:25 -0700 From: "Adrian Chadd" To: "=?UTF-8?B?0JvRjtCx0L7QvNC40YAg0JPRgNC40LPQvtGA0L7Qsg==?=" In-Reply-To: X-Mailer: Palm webOS v1.0.1 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "freebsd-wireless@freebsd.org" Subject: Re: Intel 6250 and WiMax X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Adrian Chadd 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, 09 Apr 2012 05:48:20 -0000 Right. I bet there's a wimax stack we would have to port. I'd love to see it happen.. I'm just still knee deep with 11n, then will li= kely do something with 11ac. Adrian Sent from my Palm Pre on AT&T On Apr 8, 2012 10:33 PM, =D0=9B=D1=8E=D0=B1=D0=BE=D0=BC=D0=B8=D1=80 =D0=93= =D1=80=D0=B8=D0=B3=D0=BE=D1=80=D0=BE=D0=B2 <nm.knife@gmail.com> wrote= :=20 P.S. 6250 has Wimax support in GNU/Linux under Fedora 14+ and Ubuntu, so ab= out 1 year now. --=20 Lyubomir Grigorov (bgalakazam) From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 9 08:26:09 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 75685106564A for ; Mon, 9 Apr 2012 08:26:09 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id 3032C8FC0C for ; Mon, 9 Apr 2012 08:26:09 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (89.112.15.178.pppoe.eltel.net [89.112.15.178]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id C715C4AC32; Mon, 9 Apr 2012 12:26:07 +0400 (MSK) Date: Mon, 9 Apr 2012 12:26:04 +0400 From: Lev Serebryakov X-Priority: 3 (Normal) Message-ID: <1499821016.20120409122604@serebryakov.spb.ru> To: "Adrian Chadd" In-Reply-To: <4f825599.e40c440a.4632.797d@mx.google.com> References: <4f825599.e40c440a.4632.797d@mx.google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-wireless@freebsd.org" Subject: Re: Intel 6250 and WiMax X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2012 08:26:09 -0000 Hello, Adrian. You wrote 9 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2012 =D0=B3., 7:20:48: > I'm not sure.. Do we need a wimax stack with that? Here are driver for Samsung WiMax USB dongle, and it works as-is, without any WiMax stack, as simple ethernet NIC. But, maybe, non-usb devices are other story, I don't know. --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 9 08:32:02 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 088AF106564A; Mon, 9 Apr 2012 08:32:02 +0000 (UTC) (envelope-from lev@serebryakov.spb.ru) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 9432E8FC0C; Mon, 9 Apr 2012 08:32:01 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (89.112.15.178.pppoe.eltel.net [89.112.15.178]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 63ABB4AC1C; Mon, 9 Apr 2012 12:32:00 +0400 (MSK) Date: Mon, 9 Apr 2012 12:31:58 +0400 From: Lev Serebryakov X-Priority: 3 (Normal) Message-ID: <1353140683.20120409123158@serebryakov.spb.ru> To: Adrian Chadd In-Reply-To: References: <165226504.20120408192539@serebryakov.spb.ru> <1322303419.20120408233657@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: request for testing: please test -head ath 11n stuff X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2012 08:32:02 -0000 Hello, Adrian. You wrote 8 =E0=EF=F0=E5=EB=FF 2012 =E3., 23:41:09: > I'd grab that expensive piece of kit of yours and go _find_ the noise > sources. :) In 10-store multi-apartment building (5 apartments on the floor per stairway, 5 stairways, total 5*5*10 =3D 250 apartments), made from mixture of steel-reinforced concrete and gas concrete? Are you kidding? :( --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 9 08:51:43 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EB877106564A for ; Mon, 9 Apr 2012 08:51:43 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 717B78FC14 for ; Mon, 9 Apr 2012 08:51:43 +0000 (UTC) Received: by wgbds12 with SMTP id ds12so4028417wgb.31 for ; Mon, 09 Apr 2012 01:51:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id :x-gm-message-state; bh=+nK2r6118y/W5aNUnyIRcnzzz4/Y9foYODPJC3IJS6c=; b=XKkD6ApgTVpJ78ZH8sA7oVBj6Cz106ZsEV8OjUdqNwFYLYD+IipUzfZkHtwI8By8Ge 759FtdY6IgZXK22bAZIp1MVqjXxUQ6bqU7gaLdKvTEJZ4SNqnaSHe4fo/OmaplfT526X z+fzEHbtG9IEJWazvlhPH0uLcPxAE6UL+MLSmRS/U2RGu0FHn8BH+1UjxnXeS+OVd/sa YGmyexNuX+/tpyW+y+Up6kqT3BymwUPQWSVNYKgfY67EtpEJHVkrFSc0ZndyxgfIWW2h Huv6VpER+b09XEOHZUdJG3Xo8Xwi8T38BwrKMoC6UK9jt2hKuuzm9Git1hjOcYpcqZth OHkw== Received: by 10.180.83.198 with SMTP id s6mr14190387wiy.8.1333961502613; Mon, 09 Apr 2012 01:51:42 -0700 (PDT) Received: from amy.lab.techwires.net (dslb-088-065-060-108.pools.arcor-ip.net. [88.65.60.108]) by mx.google.com with ESMTPS id ea6sm28557795wib.5.2012.04.09.01.51.41 (version=SSLv3 cipher=OTHER); Mon, 09 Apr 2012 01:51:41 -0700 (PDT) Sender: Bernhard Schmidt From: Bernhard Schmidt To: freebsd-wireless@freebsd.org Date: Mon, 9 Apr 2012 10:52:01 +0200 User-Agent: KMail/1.13.7 (FreeBSD/9.0-STABLE; KDE/4.7.4; amd64; ; ) References: <4f825599.e40c440a.4632.797d@mx.google.com> <1499821016.20120409122604@serebryakov.spb.ru> In-Reply-To: <1499821016.20120409122604@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201204091052.02078.bschmidt@freebsd.org> X-Gm-Message-State: ALoCoQlaUYn6cKmkKpwpVVj6I46V3LOtCjUTxFJ6s3ASrFe7Rc7OB6F6Cg6zADl0TR5VicBof16j Cc: Subject: Re: Intel 6250 and WiMax X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2012 08:51:44 -0000 On Monday 09 April 2012 10:26:04 Lev Serebryakov wrote: > Hello, Adrian. > You wrote 9 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2012 =D0=B3., 7:20:48: >=20 > > I'm not sure.. Do we need a wimax stack with that? We do. Linux has a stack in net/wimax and the driver for the Intel devices is in drivers/net/wimax/i2400m In other words, no, we currently do not support the WiMax stuff of any of the Intel cards nor any other device afaik. > Here are driver for Samsung WiMax USB dongle, and it works as-is, > without any WiMax stack, as simple ethernet NIC. But, maybe, non-usb > devices are other story, I don't know. Guess it depends on the device driver, it might contain its own stack. =2D-=20 Bernhard From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 9 08:59:46 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A0040106564A; Mon, 9 Apr 2012 08:59:46 +0000 (UTC) (envelope-from lev@serebryakov.spb.ru) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 5E1118FC08; Mon, 9 Apr 2012 08:59:46 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (89.112.15.178.pppoe.eltel.net [89.112.15.178]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 82CB14AC1C; Mon, 9 Apr 2012 12:59:45 +0400 (MSK) Date: Mon, 9 Apr 2012 12:59:43 +0400 From: Lev Serebryakov X-Priority: 3 (Normal) Message-ID: <992091892.20120409125943@serebryakov.spb.ru> To: Bernhard Schmidt In-Reply-To: <201204091052.02078.bschmidt@freebsd.org> References: <4f825599.e40c440a.4632.797d@mx.google.com> <1499821016.20120409122604@serebryakov.spb.ru> <201204091052.02078.bschmidt@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: Intel 6250 and WiMax X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2012 08:59:46 -0000 Hello, Bernhard. You wrote 9 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2012 =D0=B3., 12:52:01: >> Here are driver for Samsung WiMax USB dongle, and it works as-is, >> without any WiMax stack, as simple ethernet NIC. But, maybe, non-usb >> devices are other story, I don't know. > Guess it depends on the device driver, it might contain its own > stack. It looks like Samsung USB stick contains stack in firmware, because driver is VERY simple and has size of several KILOBYTES of C code, really, only couple of USB commands like "set SSID", "get signal strength", "send frame" and "poll for received frame", and it's all. --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 9 11:07:26 2012 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 268121065670 for ; Mon, 9 Apr 2012 11:07:26 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 10A818FC27 for ; Mon, 9 Apr 2012 11:07:26 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q39B7POr039790 for ; Mon, 9 Apr 2012 11:07:25 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q39B7PfB039788 for freebsd-wireless@FreeBSD.org; Mon, 9 Apr 2012 11:07:25 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 9 Apr 2012 11:07:25 GMT Message-Id: <201204091107.q39B7PfB039788@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 Cc: Subject: Current problem reports assigned to freebsd-wireless@FreeBSD.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2012 11:07:26 -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/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/164951 wireless [ath] [patch] Problem build of if_ath driver with cert o kern/164721 wireless [ath] ath device timeouts o kern/164499 wireless [wi] [patch] if_wi needs fix for big endian architectu 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/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/145826 wireless [panic] [ath] Unable to configure adhoc mode on ath0/w o kern/144987 wireless [wpi] [panic] injecting packets with wlaninject using 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 p bin/137484 wireless [patch] Integer overflow in wpa_supplicant(8) base64 e 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 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 96 problems total. From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 9 18:29:00 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 45B721065670 for ; Mon, 9 Apr 2012 18:29:00 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by mx1.freebsd.org (Postfix) with ESMTP id 1224B8FC12 for ; Mon, 9 Apr 2012 18:29:00 +0000 (UTC) Received: by dadz14 with SMTP id z14so19032075dad.17 for ; Mon, 09 Apr 2012 11:28:59 -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 :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=SrRKVWUGbovBjeZdazJQrfc5TGnjiNdo5ESJuwYMUyY=; b=vKEriGjfAz/skjF7TzJ+Pi5D9WNgbXPlc7v3iWxqowiMNg/CfZAa14B1Q+3QDtJhWj mmpoa3JNI3wE7byn6bFrgBbiFBx34nuqnSDWP0Gpj/aS1d8z0P2Fn+upLD2zpnfI7a7K jbc/VQnxbdfPcJvHWJ5sseVhizW7MobyFZlfyRmnDe0dd2zX0IQz8G37PXW7LRotCnOn o2bgTFz4txMxih3JYz8Ua3ezcvCH/YDJstRqyXadGKhxzGvVTbAxN7/2a87D9K686YIn eCtcig3OKrMKr7fGjtG4k8lhzKokhZ+4cGQTkXk9lmkHV4+KU03snCySnt9GjPrf3mwo tHhA== MIME-Version: 1.0 Received: by 10.68.200.137 with SMTP id js9mr21778263pbc.110.1333996139877; Mon, 09 Apr 2012 11:28:59 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.142.223.15 with HTTP; Mon, 9 Apr 2012 11:28:59 -0700 (PDT) In-Reply-To: <4F81710E.2070402@gmail.com> References: <4F8052EB.5090007@gmail.com> <4F806763.7040404@gmail.com> <4F8095D8.5020701@gmail.com> <4F80A38C.3080602@gmail.com> <4F80A81C.2070602@gmail.com> <4F80A9B4.2000500@gmail.com> <4F80AEC3.2050602@gmail.com> <4F80C5FC.70607@gmail.com> <4F81710E.2070402@gmail.com> Date: Mon, 9 Apr 2012 11:28:59 -0700 X-Google-Sender-Auth: 6sCqZd9jq9t_n09eI34RykEuqRo Message-ID: From: Adrian Chadd To: "Sevan / Venture37" Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: ath(4) fails to attach X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2012 18:29:00 -0000 I think there's likely something weird here going on with ACPI/resource enumeration. Would you please create a PR with this info and then bring up this on the freebsd-mobile mailing list? I bet your ath(4) issues will magically be solved once the ACPI/resource enumeration issues are sorted out. Adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 9 18:30:15 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2E27A106564A; Mon, 9 Apr 2012 18:30:15 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by mx1.freebsd.org (Postfix) with ESMTP id E19F78FC12; Mon, 9 Apr 2012 18:30:14 +0000 (UTC) Received: by dadz14 with SMTP id z14so19035602dad.17 for ; Mon, 09 Apr 2012 11:30:14 -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 :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=JUEjbnHf01oZF9TNZoNhQjneo9jtBIFvsT1Dte91iCk=; b=OZtR5xFgMRjLzaIFe1YtVPKaQ2NoXRILYoLEiTGVgTd3ulXAeEjWaB/VhZ3Il7jEPu +1896X2i683R3CGrSCUdhBeT/x+lL0uUpnY4LLAgjZvY0T3FIMogZ7ihX4SR61mbqlCh c5r6JLVJLj+wVaUbYNVvnQtaaTQYYjO3verV2coTQXYfWId2z0QdnyU7jUQr3MuVQTDV JrbfTgYp/mVPPQZlHTHGplddgNn3mjLhtIViltJuPSA0W0gbjZYcol5HpML5a3nV9Y4s j3yen5giPWlQ4uPyFcFelz5j2atSxmG2+FFwD+U118Jnsn4/zGDfm+I67eCQiseDH5lE Kvig== MIME-Version: 1.0 Received: by 10.68.131.67 with SMTP id ok3mr1431759pbb.159.1333996214609; Mon, 09 Apr 2012 11:30:14 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.142.223.15 with HTTP; Mon, 9 Apr 2012 11:30:14 -0700 (PDT) In-Reply-To: <1353140683.20120409123158@serebryakov.spb.ru> References: <165226504.20120408192539@serebryakov.spb.ru> <1322303419.20120408233657@serebryakov.spb.ru> <1353140683.20120409123158@serebryakov.spb.ru> Date: Mon, 9 Apr 2012 11:30:14 -0700 X-Google-Sender-Auth: I7RCWSxcU7oanR7WVgV04brqpQk Message-ID: From: Adrian Chadd To: Lev Serebryakov Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: request for testing: please test -head ath 11n stuff X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2012 18:30:15 -0000 2012/4/9 Lev Serebryakov : > Hello, Adrian. > You wrote 8 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2012 =D0=B3., 23:41:09: > >> I'd grab that expensive piece of kit of yours and go _find_ the noise >> sources. :) > =C2=A0In 10-store multi-apartment building (5 apartments on the floor per > stairway, 5 stairways, total 5*5*10 =3D 250 apartments), made from > mixture of steel-reinforced concrete and gas concrete? Are you > kidding? :( Well, it could be that there's just too much wifi going on. It could be that someone has some kind of very dodgy looking wifi setup with power amplifiers that are distorting, or a 2ghz video bridge thing, or whatnot. Does that fancy bit of equipment work in some kind of spectrum analyser mode? I wonder what _kind_ of signal you're seeing. Adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 9 19:17:02 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 627431065677 for ; Mon, 9 Apr 2012 19:17:02 +0000 (UTC) (envelope-from nm.knife@gmail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id DEC488FC17 for ; Mon, 9 Apr 2012 19:17:01 +0000 (UTC) Received: by wgbds12 with SMTP id ds12so4565995wgb.31 for ; Mon, 09 Apr 2012 12:17:00 -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 :content-type; bh=zHcSAp00cLRIZwfUg9qv79HJnb4kR+/aADF+wkofSEw=; b=BvxB9jnZsTznbDaIyvWl9sJDdCWjhvCAfDsKNLq5bZNmjRiGb5ST8GBlm5EolAheLM eGtZd+lijEuPQjPC+W3c1f2XfcfSXToF+10aG8bS3hfgf+FtC9H0v5Hf/35katyo91dg JMTfIpQg7qOUDNwGtjI7CdSdOV5zBFH8lg8u/3aUhwe+5ZwV7vTxrCXWGHU5KCzmDTO6 6ADAK8K6WhX7FYwPYWYtli/suEzQd1oyEy1OtuP7q8X1bko5iYKFqHtpmPIkB8Yicvvh PbCnob0YyM6P3mVGFxnHyoiTE1KapIwOMZNzgOW/OGrD2H4dnhSG6j+HGWlNgaSncgIn PZpA== MIME-Version: 1.0 Received: by 10.180.86.132 with SMTP id p4mr377438wiz.15.1333999020793; Mon, 09 Apr 2012 12:17:00 -0700 (PDT) Received: by 10.227.58.68 with HTTP; Mon, 9 Apr 2012 12:17:00 -0700 (PDT) In-Reply-To: <992091892.20120409125943@serebryakov.spb.ru> References: <4f825599.e40c440a.4632.797d@mx.google.com> <1499821016.20120409122604@serebryakov.spb.ru> <201204091052.02078.bschmidt@freebsd.org> <992091892.20120409125943@serebryakov.spb.ru> Date: Mon, 9 Apr 2012 12:17:00 -0700 Message-ID: From: =?windows-1251?B?y/7h7uzo8CDD8Ojj7vDu4g==?= To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Intel 6250 and WiMax X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2012 19:17:02 -0000 > We do. Linux has a stack in net/wimax and the driver for the > Intel devices is in drivers/net/wimax/i2400m > In other words, no, we currently do not support the WiMax stuff > of any of the Intel cards nor any other device afaik Hmm, I suppose I can always order the carry-it-anywhere hub as a solution. Or use Windows / GNU/Linux. Since it seems this isn't something short and easy, and given the status of WiMax, probably not something that will happen for FreeBSD soon/ever. Thanks for the info all. -- Lyubomir Grigorov (bgalakazam) From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 9 19:26:23 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 927F2106566B; Mon, 9 Apr 2012 19:26:23 +0000 (UTC) (envelope-from lev@freebsd.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id 4BDD68FC08; Mon, 9 Apr 2012 19:26:23 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (89.112.15.178.pppoe.eltel.net [89.112.15.178]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 3EC384AC32; Mon, 9 Apr 2012 23:26:16 +0400 (MSK) Date: Mon, 9 Apr 2012 23:26:13 +0400 From: Lev Serebryakov X-Priority: 3 (Normal) Message-ID: <5110227587.20120409232613@serebryakov.spb.ru> To: Adrian Chadd In-Reply-To: References: <165226504.20120408192539@serebryakov.spb.ru> <1322303419.20120408233657@serebryakov.spb.ru> <1353140683.20120409123158@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: request for testing: please test -head ath 11n stuff X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2012 19:26:23 -0000 Hello, Adrian. You wrote 9 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2012 =D0=B3., 22:30:14: > Does that fancy bit of equipment work in some kind of spectrum > analyser mode? I wonder what _kind_ of signal you're seeing. It works only in spectrum analyzer mode (it doesn't know anything about WiFi & Ko, all WiFi-related "annotating" info is extracted from regular WiFi adapter), and it shows very limited in bandwidth (exactly channel 6-centered 802.11g transmission, with almost no signal outside this band) very strong (-10 -- -15 dBi) signal, when my AP was detected as -40 dBi (when my AP is on channel 1 and transmitting, it becomes strongest signal on this channel, so it could be easily seen at spectorgram). This channel is occuped by 4 or 5 different hotspots according to WiFi card, but all of them have very low RSSI. It think, it could be surveillance / security camera with non-WiFi 2.4 Ghs transmitter, as signal is very uniform -- when WiFi AP or client are transmitting here are some regular spots without signal on spectorgram and some variance in signal strength, but this signal is very stable, without pauses or any significant variation. Unfortunately, I didn't take any screenshots, and this card was at my home only for 3 hours :) --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 9 21:06:51 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B5C2F106564A for ; Mon, 9 Apr 2012 21:06:51 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 83D338FC12 for ; Mon, 9 Apr 2012 21:06:51 +0000 (UTC) Received: by mail-pb0-f54.google.com with SMTP id wz17so5550265pbc.13 for ; Mon, 09 Apr 2012 14:06:51 -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 :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=7i+IJpqPsa8hS6kA13cI7Uafy0C79odWUfu4oecW+oE=; b=BnJxiIld6jrrKDStoh3raRcunY/fpL7cRxxLBwCgfyCx0SN9BZW3oVbbZVfRhPr0Gl 7LiG+7OV7Eo0wIYNB5SLyDnSKL5SZWSSLUSOzqYJUCG0be/KH07Da6P9yfHP4M6CApPs c6PyRBHhmpAk+HSA1y91B2/hRgul2fxvhjfuM6rFaGG5UaIug3ZYPYpKe7Fael8yPiv2 eJP+0rUauRZb6zd8uMvnnxuA71Zh8cgO5lcjc6OR9fBo036dC1k0W6cDyCIUfExk1uJk a8q3oTt+l6tVODk2djKifj9HPh52g9C4+hhalUPLoOd1du9fkBfUSVX4+XgXhgGUn7L5 Sysw== MIME-Version: 1.0 Received: by 10.68.134.133 with SMTP id pk5mr3042523pbb.17.1334005611375; Mon, 09 Apr 2012 14:06:51 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.142.223.15 with HTTP; Mon, 9 Apr 2012 14:06:51 -0700 (PDT) In-Reply-To: References: <4f825599.e40c440a.4632.797d@mx.google.com> <1499821016.20120409122604@serebryakov.spb.ru> <201204091052.02078.bschmidt@freebsd.org> <992091892.20120409125943@serebryakov.spb.ru> Date: Mon, 9 Apr 2012 14:06:51 -0700 X-Google-Sender-Auth: tk4JAEsMaQAgBDKt7yM6MrtzFC4 Message-ID: From: Adrian Chadd To: =?windows-1251?B?y/7h7uzo8CDD8Ojj7vDu4g==?= Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: Intel 6250 and WiMax X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2012 21:06:51 -0000 2012/4/9 =CB=FE=E1=EE=EC=E8=F0 =C3=F0=E8=E3=EE=F0=EE=E2 : >> We do. Linux has a stack in net/wimax and the driver for the >> Intel devices is in drivers/net/wimax/i2400m >> In other words, no, we currently do not support the WiMax stuff >> of any of the Intel cards nor any other device afaik > > Hmm, I suppose I can always order the carry-it-anywhere hub as a solution= . > Or use Windows / GNU/Linux. Since it seems this isn't something short and > easy, and given the status of WiMax, probably not something that will > happen for FreeBSD soon/ever. I really am encouraging someone to look into this. I'd love to see wimax stack+support in FreeBSD. If you can come up with a useful sounding proposal, the freebsd foundation may even sponsor the work. adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 9 23:08:00 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4C28F1065672 for ; Mon, 9 Apr 2012 23:08:00 +0000 (UTC) (envelope-from cpatrick08@rocketmail.com) Received: from nm13.bullet.mail.bf1.yahoo.com (nm13.bullet.mail.bf1.yahoo.com [98.139.212.172]) by mx1.freebsd.org (Postfix) with SMTP id AAD238FC0A for ; Mon, 9 Apr 2012 23:07:59 +0000 (UTC) Received: from [98.139.212.149] by nm13.bullet.mail.bf1.yahoo.com with NNFMP; 09 Apr 2012 23:07:53 -0000 Received: from [98.139.212.235] by tm6.bullet.mail.bf1.yahoo.com with NNFMP; 09 Apr 2012 23:07:52 -0000 Received: from [127.0.0.1] by omp1044.mail.bf1.yahoo.com with NNFMP; 09 Apr 2012 23:07:52 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 976067.26577.bm@omp1044.mail.bf1.yahoo.com Received: (qmail 28928 invoked by uid 60001); 9 Apr 2012 23:07:52 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rocketmail.com; s=s1024; t=1334012872; bh=MPJNMuoegI9/aRJNLs6W2HDHwJZP+XNO5HidRAptzJk=; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=IZv4UrP2n0klCAF7DtxEM7svHCxZA+ogqApKQciU7AsCv9kPBgI5sT1gMsDQ9WysreUoJBMnYIz7YMDrwM3CKTjzqABWmZZEYBBlmoGfvchOhwbWVkMXnCHpo1dmhbCQpBPrgTNUylUXkcC4MnqTOZJnnnE+VEBRDVl51Kf2VOg= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rocketmail.com; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=J+2vQuQMq2YMIsVIT0VnW31bwR1SPZp10aVSv5YrPypV2Bh4VkFgnWOchLhW4eSuSwF3do9WGxhTObaCg5fOoM0/zrDB/vREKIbqwlaK6gSXQsBzA1Ggb5tNoOcr27RP/VxvTRDvSnu8HSIBCA+67PkOwsbwfDxFdO56nWmBOIE=; X-YMail-OSG: HHs2bG8VM1nnHCEA9qj_q_klyVzNqOtMtTmyAN8HeZEodX2 5A4GUf6ofUPeSsbbNcOMIs32.XAWBIhQGVSpNChPSUkdFyLDDk9rQVJy77TG uOJTZklwFKYPZeNs7RB69sUMQfWALYe.kpWLsIxwZ3Pvq4Af1qpOYxTREyaZ MbaPodZeMJvCYNmFdps1WDi03l2nKQ1cDxZW_MdN9h4e8gL9WVyJLA_RFyB7 tsvHzbW.7CkoO16ocXR0_OE9C.XZZc8mvXGID.alQZbVVzhJ3MmFgImy1guV IaJlcVnZ5Mt2.7QJ4yidcFi8t99r.zDkolg9ni64NC7ycP1brK7fGRG_ZatM GcX5pYgZr8P27YHdvM7dmNUbeBUGIKpgGRMttOrfkyciSKcviBgALLTFY_v8 WeTOR07O3m.i0HI8.ACfn88w0fKowy6mehp1In96C0tbWnPJu1z8- Received: from [98.67.96.24] by web162205.mail.bf1.yahoo.com via HTTP; Mon, 09 Apr 2012 16:07:52 PDT X-Mailer: YahooMailWebService/0.8.117.340979 Message-ID: <1334012872.3688.YahooMailNeo@web162205.mail.bf1.yahoo.com> Date: Mon, 9 Apr 2012 16:07:52 -0700 (PDT) From: Christopher Patrick To: "freebsd-wireless@freebsd.org" MIME-Version: 1.0 X-Mailman-Approved-At: Mon, 09 Apr 2012 23:18:17 +0000 Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: RTL8188CE wireless card X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Christopher Patrick 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, 09 Apr 2012 23:08:00 -0000 I was wondering if the RTL8188CE wireless card works with Freebsd 9 and if not if you could add support for the card soon From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 10 01:55:09 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 28C84106564A for ; Tue, 10 Apr 2012 01:55:09 +0000 (UTC) (envelope-from moonlightakkiy@yahoo.ca) Received: from nm23-vm1.bullet.mail.ne1.yahoo.com (nm23-vm1.bullet.mail.ne1.yahoo.com [98.138.91.50]) by mx1.freebsd.org (Postfix) with SMTP id BC3C28FC1A for ; Tue, 10 Apr 2012 01:55:08 +0000 (UTC) Received: from [98.138.90.52] by nm23.bullet.mail.ne1.yahoo.com with NNFMP; 10 Apr 2012 01:55:07 -0000 Received: from [98.138.84.34] by tm5.bullet.mail.ne1.yahoo.com with NNFMP; 10 Apr 2012 01:55:07 -0000 Received: from [127.0.0.1] by smtp102.mail.ne1.yahoo.com with NNFMP; 10 Apr 2012 01:55:07 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s1024; t=1334022907; bh=RmO/x/KrAKHfSAU4rMCuXIJO3Urvy9QCGYif3tOPWZM=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Received:MIME-Version:Received:Received:Date:Message-ID:Subject:From:To:Cc:Content-Type:Content-Transfer-Encoding; b=4L3DhI9QRoajFFe889lWr/NrPWQrNY1mtY0HCk463INAnHk7Yier+1ahHtHD8rLA7Vr8eRUwf9BPa4a3c1ZpTFukbzFsT9hxLWRtoFJFVsm4quZv63Va5xVIN5CB7tT0BxGaOh0/Wt0dJb5EqIeeDW7/vFoACqh9wqfVn8PSjkc= X-Yahoo-Newman-Id: 565279.37179.bm@smtp102.mail.ne1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: zvNRKFMVM1mSy9t9Qp1NSYCAMPw98KzPUqAe5fN1ZuSZT_L 9n3m8gatntqbyBSY4A5294EgUiv.EW.MU8PPcpBW7rZsmDV47yh4sX50iTBu WJ1zdCtGFVSWZQjUoZZSsOLLJy7hOtJOVAdlJ9yZX4hPTPAagFoyZeSkF9ks WscTPTtQc4RfP6mWyVdLH6ibhQjRFUR5KWTIOEVr3bSoj.Hv3.ypPNijeJN8 6lCMgkKsvNTaCYZydZXNoCjf7DRGcJX6W2ko.SqNxDAL01FXadIJIviG044U vT.3iIUzDTqOQbAtUxBL6smMUhMKbkp2zSc2uR2r7sRSmgPWXnCvMVe_bMv7 HlCdksMR7KwLruEGSILQ9_5jz1mUnhpX27c9oYz9GAbJSCYWqA5j2.S3drJN pcAykAdIdZOKwtKaubqrC3z6j2Um6TQk- X-Yahoo-SMTP: Xr6qjFWswBAEmd20sAvB4Q3keqXvXsIH9TjJ Received: from mail-ob0-f182.google.com (moonlightakkiy@209.85.214.182 with plain) by smtp102.mail.ne1.yahoo.com with SMTP; 09 Apr 2012 18:55:07 -0700 PDT Received: by obbwc18 with SMTP id wc18so8675377obb.13 for ; Mon, 09 Apr 2012 18:55:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.60.18.197 with SMTP id y5mr13289022oed.58.1334022906941; Mon, 09 Apr 2012 18:55:06 -0700 (PDT) Received: by 10.182.208.39 with HTTP; Mon, 9 Apr 2012 18:55:06 -0700 (PDT) Date: Mon, 9 Apr 2012 19:55:06 -0600 Message-ID: From: PseudoCylon To: Lev Serebryakov , Bernhard Schmidt Content-Type: text/plain; charset=TIS-620 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: Intel 6250 and WiMax X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Apr 2012 01:55:09 -0000 > ------------------------------ > > Message: 13 > Date: Mon, 9 Apr 2012 12:59:43 +0400 > From: Lev Serebryakov > Subject: Re: Intel 6250 and WiMax > To: Bernhard Schmidt > Cc: freebsd-wireless@freebsd.org > Message-ID: <992091892.20120409125943@serebryakov.spb.ru> > Content-Type: text/plain; charset=3Dutf-8 > > Hello, Bernhard. > You wrote 9 =D0=B0=D0=BF=D1 EURO =D0=B5=D0=BB=D1 2012 =D0=B3., 12:52:01: > >>> Here are driver for Samsung WiMax USB dongle, and it works as-is, >>> without any WiMax stack, as simple ethernet NIC. But, maybe, non-usb >>> devices are other story, I don't know. >> Guess it depends on the device driver, it might contain its own >> stack. > It looks like Samsung USB stick contains stack in firmware, because > driver is VERY simple and has size of several KILOBYTES of C code, > really, only couple of USB commands like "set SSID", "get signal > strength", "send frame" and "poll for received frame", and it's all. > It wasn't particularly WiMax, but when I worked on HSPA+ device, usie(4) it worked like that, set up usb xfers and throw ethernet packets at the device, that was it. Probably, one simple generic stack would work for most of them if needed. The problem I had was there is no mechanism to pass device info (i.e link state up/down, signal strength, IP addresses) to other part of the system. I thought about adding it, but I haven't because there isn't lots of demand. AK From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 10 02:13:22 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E514D1065673; Tue, 10 Apr 2012 02:13:22 +0000 (UTC) (envelope-from sendtomatt@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id AC7D68FC15; Tue, 10 Apr 2012 02:13:22 +0000 (UTC) Received: by pbcwz17 with SMTP id wz17so5774784pbc.13 for ; Mon, 09 Apr 2012 19:13:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=gDaIJO0xzqrt4SVqUShz434F9TE1bkjvV48yXp0MhZs=; b=IRPttYjv2XFb7T1yHD1jRKgtR7N3GNlzQHNIw/52bs7Bl7wxZVsvXUKeUxFlXltOOW XJIB9ozLD9tkjVa5FnAte614mAyD3ArSuir6Gw+8rllbvE3CE9m2DSJPhZ97jRBq7pWg VGJDgn6yWFK1Zd34pW0eN6NHakkMg7QuS8VHc/Dww39koia3AVeVEi9/PsVJfgU4NOPi Zf+FKt82Rc2kpcK+hGOoxpMrZOdxSnrYp5j2Z1LNy6K6uQ8eor8fiYJiKVegQIYFHu4/ wnHI8onbLaQ1Z5YUN75iE2gKWxt4T331LVHMaxiSdGxnhK5l70ELwQYWXQEXUaNY0OiH t2UQ== Received: by 10.68.239.233 with SMTP id vv9mr24803105pbc.75.1334024002230; Mon, 09 Apr 2012 19:13:22 -0700 (PDT) Received: from bakeneko.local (70-36-223-239.dsl.dynamic.sonic.net. [70.36.223.239]) by mx.google.com with ESMTPS id ng1sm1681079pbc.68.2012.04.09.19.13.19 (version=SSLv3 cipher=OTHER); Mon, 09 Apr 2012 19:13:20 -0700 (PDT) Message-ID: <4F839730.2020503@gmail.com> Date: Mon, 09 Apr 2012 19:13:04 -0700 From: matt User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.3) Gecko/20120326 Thunderbird/10.0.3 MIME-Version: 1.0 To: PseudoCylon References: In-Reply-To: X-Enigmail-Version: 1.3.5 Content-Type: text/plain; charset=TIS-620 Content-Transfer-Encoding: 8bit Cc: freebsd-wireless@freebsd.org, Lev Serebryakov , Bernhard Schmidt Subject: Re: Intel 6250 and WiMax X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Apr 2012 02:13:23 -0000 On 04/09/12 18:55, PseudoCylon wrote: >> ------------------------------ >> >> Message: 13 >> Date: Mon, 9 Apr 2012 12:59:43 +0400 >> From: Lev Serebryakov >> Subject: Re: Intel 6250 and WiMax >> To: Bernhard Schmidt >> Cc: freebsd-wireless@freebsd.org >> Message-ID: <992091892.20120409125943@serebryakov.spb.ru> >> Content-Type: text/plain; charset=utf-8 >> >> Hello, Bernhard. >> You wrote 9 Ð°Ð¿Ñ EURO ÐµÐ»Ñ 2012 г., 12:52:01: >> >>>> Here are driver for Samsung WiMax USB dongle, and it works as-is, >>>> without any WiMax stack, as simple ethernet NIC. But, maybe, non-usb >>>> devices are other story, I don't know. >>> Guess it depends on the device driver, it might contain its own >>> stack. >> It looks like Samsung USB stick contains stack in firmware, because >> driver is VERY simple and has size of several KILOBYTES of C code, >> really, only couple of USB commands like "set SSID", "get signal >> strength", "send frame" and "poll for received frame", and it's all. >> > It wasn't particularly WiMax, but when I worked on HSPA+ device, > usie(4) it worked like that, set up usb xfers and throw ethernet > packets at the device, that was it. Probably, one simple generic stack > would work for most of them if needed. > > The problem I had was there is no mechanism to pass device info (i.e > link state up/down, signal strength, IP addresses) to other part of > the system. I thought about adding it, but I haven't because there > isn't lots of demand. > > > AK > _______________________________________________ > 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" For what it's worth i2400m was so poor at loading its own firmware that I had to remove it from my gentoo kernel config because it was adding mysterious 40 second delays to boot...probably PEBKAC but not inspiring. I did have it working under 2.6.39, I had a wmx0 device which returned nothing on a scan (no WiMAX transmitters here in northern, northern california I guess). What is interesting about WiMAX: The phy should be able to receive/transmit on a ton of frequencies outside of wifi (I think down to 900mhz) The hardware (transmitter/base stations) are supposedly going for cheaper as LTE takes predominance...I could see uses here for an AWESOME personal LAN :) Since hardware is available, setting up a WISP could be fun, not sure on licensing. Matt From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 10 05:24:16 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9B5BF106564A; Tue, 10 Apr 2012 05:24:16 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id C06F58FC16; Tue, 10 Apr 2012 05:24:15 +0000 (UTC) Received: by wern13 with SMTP id n13so3956243wer.13 for ; Mon, 09 Apr 2012 22:24:15 -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=jDF39y1fPAYhu8GWItZG6hAf2hUa17Dra6crub4d1A8=; b=Dak5zvdwCfFHD3554nUH5+vy5X25z+LvPDvFkJiyN22rnVJAksn4x7RturBAYRaxOj UrkZ6pQ+wwJ3E8JswJoFW6L6nGDCANwfq9mkaAQwJ0DHdlLth5oyy8Xhwv6WLzxjd+Sw mCc1bE5lshY9Vepws4JIQgApPARwFsZ6ClrfI1BpfWXwOJvXXdgDzUlYKx8jWb8awBxX xTHcV+wbsS5rjanW8SVi54I1uR3qeOqd8yLUTUciJPdlydQyzrJvQjS2A0KHIOycxXMD X+7uyUwrFVWGuS/Yrqoh1FJ1pAVRCEfZH/ztrFJcRre4xt9LfUXxUscRs2D8ypjEK6pC nOXA== MIME-Version: 1.0 Received: by 10.216.135.223 with SMTP id u73mr5336265wei.117.1334035454918; Mon, 09 Apr 2012 22:24:14 -0700 (PDT) Received: by 10.223.54.207 with HTTP; Mon, 9 Apr 2012 22:24:14 -0700 (PDT) In-Reply-To: <5110227587.20120409232613@serebryakov.spb.ru> References: <165226504.20120408192539@serebryakov.spb.ru> <1322303419.20120408233657@serebryakov.spb.ru> <1353140683.20120409123158@serebryakov.spb.ru> <5110227587.20120409232613@serebryakov.spb.ru> Date: Mon, 9 Apr 2012 22:24:14 -0700 Message-ID: From: Kevin Oberman To: Lev Serebryakov Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: request for testing: please test -head ath 11n stuff X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Apr 2012 05:24:16 -0000 On Mon, Apr 9, 2012 at 12:26 PM, Lev Serebryakov wrote: > Hello, Adrian. > You wrote 9 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2012 =D0=B3., 22:30:14: > >> Does that fancy bit of equipment work in some kind of spectrum >> analyser mode? I wonder what _kind_ of signal you're seeing. > =C2=A0It works only in spectrum analyzer mode (it doesn't know anything > about WiFi & Ko, all WiFi-related "annotating" info is extracted from > regular WiFi adapter), and it shows very limited in bandwidth (exactly > channel 6-centered 802.11g transmission, with almost no signal outside > this band) very strong (-10 -- -15 dBi) signal, when my AP was > detected as -40 dBi (when my AP is on channel 1 and transmitting, it > becomes strongest signal on this channel, so it could be easily seen > at spectorgram). This channel is occuped by 4 or 5 different hotspots > according to WiFi card, but all of them have very low RSSI. > > =C2=A0It think, it could be surveillance / security camera with non-WiFi > 2.4 Ghs transmitter, as signal is very uniform -- when WiFi AP or > client are transmitting here are some regular spots without signal on > spectorgram and some variance in signal strength, but this signal is > very stable, without pauses or any significant variation. > > =C2=A0Unfortunately, I didn't take any screenshots, and this card was at = my > home only for 3 hours :) I suspect that the camera is the culprit. Back about 8 or 9 years ago I was working on the network at the SuperComputing show and a booth was using a wireless camera on the 4.2 band. It totally wiped out WiFi all around that booth. Fortunately, the contract signed by exhibitors gave the show authority over all wireless and the camera was turned off. --=20 R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 10 06:21:44 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D4B1E106566B; Tue, 10 Apr 2012 06:21:44 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 69EA58FC0A; Tue, 10 Apr 2012 06:21:44 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (89.112.15.178.pppoe.eltel.net [89.112.15.178]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 3EAFE4AC1C; Tue, 10 Apr 2012 10:21:43 +0400 (MSK) Date: Tue, 10 Apr 2012 10:21:40 +0400 From: Lev Serebryakov X-Priority: 3 (Normal) Message-ID: <973223342.20120410102140@serebryakov.spb.ru> To: PseudoCylon In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=windows-874 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org, Bernhard Schmidt Subject: Re: Intel 6250 and WiMax X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Apr 2012 06:21:44 -0000 Hello, PseudoCylon. You wrote 10 ?????? 2012 ?., 5:55:06: >> It looks like Samsung USB stick contains stack in firmware, because >> driver is VERY simple and has size of several KILOBYTES of C code, >> really, only couple of USB commands like "set SSID", "get signal >> strength", "send frame" and "poll for received frame", and it's all. >> > It wasn't particularly WiMax, but when I worked on HSPA+ device, > usie(4) it worked like that, set up usb xfers and throw ethernet > packets at the device, that was it. Probably, one simple generic stack > would work for most of them if needed. > The problem I had was there is no mechanism to pass device info (i.e > link state up/down, signal strength, IP addresses) to other part of > the system. I thought about adding it, but I haven't because there > isn't lots of demand. WiMax driver senses "up/down" state and IP is assigned by generic base-system dhclinet :) --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 10 06:27:13 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B8DC61065672; Tue, 10 Apr 2012 06:27:13 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 79EB18FC12; Tue, 10 Apr 2012 06:27:13 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (89.112.15.178.pppoe.eltel.net [89.112.15.178]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id A30594AC1C; Tue, 10 Apr 2012 10:27:12 +0400 (MSK) Date: Tue, 10 Apr 2012 10:27:10 +0400 From: Lev Serebryakov X-Priority: 3 (Normal) Message-ID: <1016606749.20120410102710@serebryakov.spb.ru> To: matt In-Reply-To: <4F839730.2020503@gmail.com> References: <4F839730.2020503@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-874 Content-Transfer-Encoding: quoted-printable Cc: PseudoCylon , freebsd-wireless@freebsd.org, Bernhard Schmidt Subject: Re: Intel 6250 and WiMax X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Apr 2012 06:27:13 -0000 Hello, matt. You wrote 10 ?????? 2012 ?., 6:13:04: > I did have it working under 2.6.39, I had a wmx0 device which returned > nothing on a scan (no WiMAX transmitters here in northern, northern > california I guess). USB Sticks, which are available in Russia (we have WiMax operator "Yota" here) doesn't have "scan" mode at all: you should type-in SSID and frequency from documentation from provider (Yota). Maybe, they have one, but it is not documented anywhere. I have some friends of mine working in Yota as engineers, and they say, that even Yota engineers doesn't have ANY documentation on these devices, Samsung refuses any requests for datahseet, etc. Driver I have on hands was reverse-engineered by snooping USB traffic on Windows. > Since hardware is available, setting up a WISP could be fun, not sure on > licensing. Oh, really? I could not find any affordable AP hardware for WiMax :( --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 10 06:38:21 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CB633106566C; Tue, 10 Apr 2012 06:38:21 +0000 (UTC) (envelope-from nm.knife@gmail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 3475F8FC15; Tue, 10 Apr 2012 06:38:21 +0000 (UTC) Received: by wgbds12 with SMTP id ds12so4973956wgb.31 for ; Mon, 09 Apr 2012 23:38:20 -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=WmUyW9CbTL1fpo/sfzJxrHCTe4V/8A7VSnO8afkLucg=; b=afHca/O26gpOb7QtTzI8G9/0p06tpBjcofVp1eyP2Ax4FQwFvBWw1VLfDRC3sHSIjK YhEEJzwGooJdecvDRnycL0WIAWwdAEgG5dWa+aX4Cb5WkeJrV1+zE7Y7g3XU6nYLg0e6 BI6xHWm1qZlvM4yOQvP4KgR7DHgdE7tO9RUbJUVQkuSPYKRfcyq8VOZLEyNbs3OtWajc Dkx3mwgcsu8MEX5EqdgTR3opFzG4fksDqGJ0evmLet8ftLmK+YPju0cVV/TMdazqrSYb 0aOMo/JM5LwpSY3r7x7il4ViH14R8GsSLjhWlRP9L5w3vSdWZwkVrYrBZr1ZnrxenvLf Aj7g== MIME-Version: 1.0 Received: by 10.216.138.202 with SMTP id a52mr5519493wej.53.1334039900244; Mon, 09 Apr 2012 23:38:20 -0700 (PDT) Received: by 10.227.58.68 with HTTP; Mon, 9 Apr 2012 23:38:20 -0700 (PDT) In-Reply-To: <1016606749.20120410102710@serebryakov.spb.ru> References: <4F839730.2020503@gmail.com> <1016606749.20120410102710@serebryakov.spb.ru> Date: Mon, 9 Apr 2012 23:38:20 -0700 Message-ID: From: =?windows-1251?B?y/7h7uzo8CDD8Ojj7vDu4g==?= To: Lev Serebryakov Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: Intel 6250 and WiMax X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Apr 2012 06:38:21 -0000 > Since hardware is available, setting up a WISP could be fun, not sure on > licensing. > Oh, really? I could not find any affordable AP hardware for > WiMax :( > I am interested about this too. My grandparents village in Bulgaria is a perfect test site :). Maybe if prices keep going down and down. I like WiMax as in idea, I don't like that they are trying to replace it with LTE just because of cell phones. -- Lyubomir Grigorov (bgalakazam) From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 10 06:46:41 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 496FD106566B for ; Tue, 10 Apr 2012 06:46:41 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id B97EC8FC15 for ; Tue, 10 Apr 2012 06:46:40 +0000 (UTC) Received: by lagv3 with SMTP id v3so5522086lag.13 for ; Mon, 09 Apr 2012 23:46:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=ia47aMv2UfH43efqmOiuP5Ollw52xI+pCghoE0gSiDE=; b=BLJmlltNc94IrHKxq8IO4EB4CMQUlGUVHA0J0lmZ/TiV7VbjZA1lfKScts5rZ2piB2 C+jOZW+xN4S7hqrQ1QexO9aRkGuZldZTdgYMc4VxQoxYS3o0+rG3d53I6bOdM/pvjoPr lu7ncT2rfJgBBFgG+q+h+mqcKxOfBk12KRB2Yv5RpKbvaf9RznOaDYh2bNfGy+F26V/v kNw0OtEhAgtP2dsNefXA91jFy796+YI5UAznKT9OPkpyPsDm4LBwVIaQ2iUXOWmA9fr9 ZqPeP++YfuCEkuGKHXM0Icl1XwTQIpFpyMIFdogUnGo09XocneIPZyJINVyjQOsDFe/7 NhTw== MIME-Version: 1.0 Received: by 10.112.45.138 with SMTP id n10mr914097lbm.14.1334040399490; Mon, 09 Apr 2012 23:46:39 -0700 (PDT) Received: by 10.152.144.195 with HTTP; Mon, 9 Apr 2012 23:46:39 -0700 (PDT) X-Originating-IP: [79.140.39.245] In-Reply-To: <1334012872.3688.YahooMailNeo@web162205.mail.bf1.yahoo.com> References: <1334012872.3688.YahooMailNeo@web162205.mail.bf1.yahoo.com> Date: Tue, 10 Apr 2012 08:46:39 +0200 Message-ID: From: Bernhard Schmidt To: Christopher Patrick Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQmUzYmKmfXXyfdwG5Exayp+E+pTG8HPpzjLAir/YiuUCK9vabSi7zT6lfpQYRO0Yg8vYyWz Cc: "freebsd-wireless@freebsd.org" Subject: Re: RTL8188CE wireless card X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Apr 2012 06:46:41 -0000 On Tue, Apr 10, 2012 at 01:07, Christopher Patrick wrote: > I was wondering if the RTL8188CE wireless card works with Freebsd 9 and if not if you could add support for the card soon Nope, not (yet) supported. OpenBSD has a driver named urtwn for those devices, though, I'm not aware that someone is currently into porting it. -- Bernhard From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 10 07:12:52 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5C3811065675; Tue, 10 Apr 2012 07:12:52 +0000 (UTC) (envelope-from nm.knife@gmail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id B79CC8FC08; Tue, 10 Apr 2012 07:12:51 +0000 (UTC) Received: by wgbds12 with SMTP id ds12so5000282wgb.31 for ; Tue, 10 Apr 2012 00:12:51 -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=xHxbV2FllXYZDrMnRcGnzlX8JqfcN8CvfvQoTSokFo4=; b=tdCt0JpnPbJftjeJydIK3WyW/JEIp6X84I1gCu32YOGzF1X6m7CiEoltUaoerFCnnT Wy0GOzxHwOrB2BbkEBwP9xOiV0sjWUGqnQ9nDPfCyTZIQWCmyM3kagVOcp2QM7zhjAlC dKRv3sLs39B3OCbEbJ5RQLSny+kltFDXi5UbUn7kQRovpNnIQ1mCd7q4UN5FuGrJNmRB Toz1bWZ4s5Dq7OjBOw43ArP8Ce4I6eKDdQ+8mk7jHOgLoRLkYvLN2NAqDRxPV2X9I6bS a1pzLLJOTEQtle6h8FqBjXku3LHV3o4h0TVLZadVSlfEzjy8p+N2641li8hplvBx80cx DDLQ== MIME-Version: 1.0 Received: by 10.180.101.8 with SMTP id fc8mr4287991wib.12.1334041970938; Tue, 10 Apr 2012 00:12:50 -0700 (PDT) Received: by 10.227.58.68 with HTTP; Tue, 10 Apr 2012 00:12:50 -0700 (PDT) In-Reply-To: References: <4f825599.e40c440a.4632.797d@mx.google.com> <1499821016.20120409122604@serebryakov.spb.ru> <201204091052.02078.bschmidt@freebsd.org> <992091892.20120409125943@serebryakov.spb.ru> Date: Tue, 10 Apr 2012 00:12:50 -0700 Message-ID: From: =?windows-1251?B?y/7h7uzo8CDD8Ojj7vDu4g==?= To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: Intel 6250 and WiMax X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Apr 2012 07:12:52 -0000 If one of you is willing to start this, I am willing to donate a 6250, if you don't have one. I would like to see WiMax in FreeBSD as well. I really am encouraging someone to look into this. I'd love to see > wimax stack+support in FreeBSD. > > If you can come up with a useful sounding proposal, the freebsd > foundation may even sponsor the work. > > -- Lyubomir Grigorov (bgalakazam) From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 10 19:50:04 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 652FF106566B for ; Tue, 10 Apr 2012 19:50:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 490A18FC14 for ; Tue, 10 Apr 2012 19:50:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q3AJo41V017693 for ; Tue, 10 Apr 2012 19:50:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q3AJo4JZ017692; Tue, 10 Apr 2012 19:50:04 GMT (envelope-from gnats) Date: Tue, 10 Apr 2012 19:50:04 GMT Message-Id: <201204101950.q3AJo4JZ017692@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: kern/164951: commit references a PR X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service 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, 10 Apr 2012 19:50:04 -0000 The following reply was made to PR kern/164951; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/164951: commit references a PR Date: Tue, 10 Apr 2012 19:47:59 +0000 (UTC) Author: adrian Date: Tue Apr 10 19:47:44 2012 New Revision: 234110 URL: http://svn.freebsd.org/changeset/base/234110 Log: Fix compilation with IEEE80211_ENABLE_SUPERG defined. PR: kern/164951 Modified: head/sys/dev/ath/if_ath.c Modified: head/sys/dev/ath/if_ath.c ============================================================================== --- head/sys/dev/ath/if_ath.c Tue Apr 10 19:25:43 2012 (r234109) +++ head/sys/dev/ath/if_ath.c Tue Apr 10 19:47:44 2012 (r234110) @@ -4906,6 +4906,7 @@ ath_tx_processq(struct ath_softc *sc, st struct ath_tx_status *ts; struct ieee80211_node *ni; struct ath_node *an; + struct ieee80211com *ic = sc->sc_ifp->if_l2com; int nacked; HAL_STATUS status; _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 10 21:43:22 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B713B106566B for ; Tue, 10 Apr 2012 21:43:22 +0000 (UTC) (envelope-from chrishutchinson1@yahoo.com) Received: from nm26-vm0.bullet.mail.sp2.yahoo.com (nm26-vm0.bullet.mail.sp2.yahoo.com [98.139.91.230]) by mx1.freebsd.org (Postfix) with SMTP id 88ABB8FC08 for ; Tue, 10 Apr 2012 21:43:22 +0000 (UTC) Received: from [98.139.91.66] by nm26.bullet.mail.sp2.yahoo.com with NNFMP; 10 Apr 2012 21:43:22 -0000 Received: from [208.71.42.198] by tm6.bullet.mail.sp2.yahoo.com with NNFMP; 10 Apr 2012 21:43:22 -0000 Received: from [127.0.0.1] by smtp209.mail.gq1.yahoo.com with NNFMP; 10 Apr 2012 21:43:22 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1334094202; bh=0oC6TyLVzwPSiEsf46izjV8wCNmisQG3Un4uAZP8TGw=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Date:From:To:Subject:Message-ID:In-Reply-To:References:X-Mailer:Mime-Version:Content-Type:Content-Transfer-Encoding; b=y+2+5uOAZf8Cq4+hUh4c8ek2BWmFmtewYGJCuXKBSCjnt6sDBRGTz1lLxcxlUYkbr0ldCy/PfTV38R9M+M0IllsCN+l8WZGMnesy6s40T4dOrFVNiVI9WrUogKHzmSozM+M12LGqXQ4U/+RHe1wk/9PzWvi6H838hF7tjHwIQoM= X-Yahoo-Newman-Id: 179582.93262.bm@smtp209.mail.gq1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: kncwsfYVM1miTtIkH0lQ.vP.NfBB1UvdvZgTjAhx2a88990 _ZZim6IEHq7Ig04mFN4l89.VW7r6mHmsqC2SJz7cSnXnFGswd10qhLSHHRX7 N_uSPTB7g_8Qf6Qgkof7AtdFb92X1fhVKr37Ia5XECjq50NcKxrYQ3OFFNH3 Voq7npoBzgf3wnjUbhhGpDg3CSgcu_57qiPQidowlIh_FqiY7.HXqD58DL6z sZWZYUivKLLOZAC_87MxBjsDecAlprsfd2NW_09WmAiJG6uVEMqdJWyB33qF eLtIZJgCk_iQrWZ9FMvvLiDfVoF9XE6pW70MXzajy7mufDUaAwwXoCWoS6o8 wbyuJXROF_nTDU6DeNbINZYYsafdvLW8fq4wkZX3tnH9d2kH3YzifMEm8_TZ Cafc- X-Yahoo-SMTP: uW3vktqswBBwhzUUqSfIo9IQDlOyJjOVATmsCrk- Received: from virus.local (chrishutchinson1@107.62.164.136 with login) by smtp209.mail.gq1.yahoo.com with SMTP; 10 Apr 2012 14:43:21 -0700 PDT Date: Tue, 10 Apr 2012 14:43:34 -0700 From: Chris To: freebsd-wireless@freebsd.org Message-ID: <20120410144334.6789d923@virus.local> In-Reply-To: References: <4f825599.e40c440a.4632.797d@mx.google.com> <1499821016.20120409122604@serebryakov.spb.ru> <201204091052.02078.bschmidt@freebsd.org> <992091892.20120409125943@serebryakov.spb.ru> X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.6; amd64-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: 8bit Subject: Re: Intel 6250 and WiMax X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Apr 2012 21:43:22 -0000 On Mon, 9 Apr 2012 14:06:51 -0700 Adrian Chadd wrote: > 2012/4/9 Ëþáîìèð Ãðèãîðîâ : > >> We do. Linux has a stack in net/wimax and the driver for the > >> Intel devices is in drivers/net/wimax/i2400m > >> In other words, no, we currently do not support the WiMax stuff > >> of any of the Intel cards nor any other device afaik > > > > Hmm, I suppose I can always order the carry-it-anywhere hub as a > > solution. Or use Windows / GNU/Linux. Since it seems this isn't > > something short and easy, and given the status of WiMax, probably > > not something that will happen for FreeBSD soon/ever. > > I really am encouraging someone to look into this. I'd love to see > wimax stack+support in FreeBSD. > > If you can come up with a useful sounding proposal, the freebsd > foundation may even sponsor the work. Greetings, I also have the ability to use WiMax on my "Smartphone" (Spr!nt - HTC-EVO 4G). In fact, I'm currently using the phone as a "hotspot" (router/gateway) to connect to the interweb, in order to collect/respond to my mail. For those already familiar, I'm not using the vendor provided (androd/froyo-2.2) HotSpot, but rather an opensource tether app - in this case wireless, not USB. To the point, I'd be willing, and able to contribute to further development on this front. My phone is "rooted", and I'm quite familiar with the system -- it's a heavily hacked (by me) stock ROM. My development system is FreeBSD 8.2-STABLE /AMD64. I would prefer to collaborate with others on this. Thank you for all your time, and consideration. --Chris P.S. the vendors name above, was intentionally obscured. :) > > > > adrian > _______________________________________________ > 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 Wed Apr 11 02:53:28 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2FE4A106566C for ; Wed, 11 Apr 2012 02:53:28 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 006388FC0C for ; Wed, 11 Apr 2012 02:53:27 +0000 (UTC) Received: by pbcwz17 with SMTP id wz17so732998pbc.13 for ; Tue, 10 Apr 2012 19:53:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=zWMQpP6kiPHCcLkMpfp6ffgKJ1hxAQmcEOKbRPLWi6Q=; b=qGf7rzkzqRWJu1HeN+R50r3bne8nmpzScDBrFbuqv7jQGM0tPeyMK7VvHnKupLF/gk ov790qSLu8lFV7ae4snKTTcIMSN0tJP6QIgpw7eZEjkyDDEg5AHrfJSV6h7mM4igduZG V+be7DM548XHe0QNLc1ybQwd8wgeZcYtxxhWH4TrpmPQydprv9uctY4WD0+WrR+moNq4 iGE9pvDUb66lDB5n1MJ+Fg5TL7BNatwynJdMWK5SplqXojze4ar75Ah9SUP/I8ZphAIp grI2MYWZAZdXk2eo9bT14x3qziAvniOR2OehFRuJg/JaSjObmRnOVrijXUllLbOt85LA mdsQ== MIME-Version: 1.0 Received: by 10.68.204.234 with SMTP id lb10mr10805247pbc.161.1334112807660; Tue, 10 Apr 2012 19:53:27 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.143.9.11 with HTTP; Tue, 10 Apr 2012 19:53:27 -0700 (PDT) Date: Tue, 10 Apr 2012 19:53:27 -0700 X-Google-Sender-Auth: G2H9NtZG8rI2lqX_g6mQhjZvkfs Message-ID: From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: multipart/mixed; boundary=047d7b2e4820fdad7f04bd5e57a6 Subject: [RFC] net80211/ath/iwn: move ni_tx_ampdu to be per-tid, rather than per WME AC X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2012 02:53:28 -0000 --047d7b2e4820fdad7f04bd5e57a6 Content-Type: text/plain; charset=ISO-8859-1 Hi, This patch changes ni_tx_ampdu to be per-TID rather than per-AC. It includes: * changes to net80211 to use the QoS frame TID, rather than calculating it from the AC (which may have been calculated from the TID in the first place); * the one changes to ath(4) to use it; * a couple of changes to iwn which was using ni_tx_ampdu state. I'd like to commit this to -HEAD. Thanks, Adrian --047d7b2e4820fdad7f04bd5e57a6 Content-Type: application/octet-stream; name="net80211-ath-txagg-tid-fix-1.diff" Content-Disposition: attachment; filename="net80211-ath-txagg-tid-fix-1.diff" Content-Transfer-Encoding: base64 X-Attachment-Id: f_h0vsbleu0 SW5kZXg6IHN5cy9uZXQ4MDIxMS9pZWVlODAyMTFfaHQuYwo9PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09Ci0tLSBzeXMvbmV0 ODAyMTEvaWVlZTgwMjExX2h0LmMJKHJldmlzaW9uIDIzNDEwOCkKKysrIHN5cy9uZXQ4MDIxMS9p ZWVlODAyMTFfaHQuYwkod29ya2luZyBjb3B5KQpAQCAtMTAyMyw3ICsxMDIzLDcgQEAKIGllZWU4 MDIxMV9odF9ub2RlX2luaXQoc3RydWN0IGllZWU4MDIxMV9ub2RlICpuaSkKIHsKIAlzdHJ1Y3Qg aWVlZTgwMjExX3R4X2FtcGR1ICp0YXA7Ci0JaW50IGFjOworCWludCB0aWQ7CiAKIAlpZiAobmkt Pm5pX2ZsYWdzICYgSUVFRTgwMjExX05PREVfSFQpIHsKIAkJLyoKQEAgLTEwMzMsOSArMTAzMywx MCBAQAogCQkgKi8KIAkJaWVlZTgwMjExX2h0X25vZGVfY2xlYW51cChuaSk7CiAJfQotCWZvciAo YWMgPSAwOyBhYyA8IFdNRV9OVU1fQUM7IGFjKyspIHsKLQkJdGFwID0gJm5pLT5uaV90eF9hbXBk dVthY107Ci0JCXRhcC0+dHhhX2FjID0gYWM7CisJZm9yICh0aWQgPSAwOyB0aWQgPCBXTUVfTlVN X1RJRDsgdGlkKyspIHsKKwkJdGFwID0gJm5pLT5uaV90eF9hbXBkdVt0aWRdOworCQl0YXAtPnR4 YV9hYyA9IFRJRF9UT19XTUVfQUModGlkKTsKKwkJdGFwLT50eGFfdGlkID0gdGlkOwogCQl0YXAt PnR4YV9uaSA9IG5pOwogCQkvKiBOQjogZnVydGhlciBpbml0aWFsaXphdGlvbiBkZWZlcnJlZCAq LwogCX0KQEAgLTEwNTUsNyArMTA1Niw3IEBACiAJS0FTU0VSVChuaS0+bmlfZmxhZ3MgJiBJRUVF ODAyMTFfTk9ERV9IVCwgKCJub3QgYW4gSFQgbm9kZSIpKTsKIAogCS8qIFhYWCBvcHRpbWl6ZSB0 aGlzICovCi0JZm9yIChpID0gMDsgaSA8IFdNRV9OVU1fQUM7IGkrKykgeworCWZvciAoaSA9IDA7 IGkgPCBXTUVfTlVNX1RJRDsgaSsrKSB7CiAJCXN0cnVjdCBpZWVlODAyMTFfdHhfYW1wZHUgKnRh cCA9ICZuaS0+bmlfdHhfYW1wZHVbaV07CiAJCWlmICh0YXAtPnR4YV9mbGFncyAmIElFRUU4MDIx MV9BR0dSX1NFVFVQKQogCQkJYW1wZHVfdHhfc3RvcCh0YXApOwpAQCAtMTE2MCw3ICsxMTYxLDcg QEAKIHsKIAlzdHJ1Y3QgaWVlZTgwMjExdmFwICp2YXAgPSBuaS0+bmlfdmFwOwogCXN0cnVjdCBp ZWVlODAyMTFfdHhfYW1wZHUgKnRhcDsKLQlpbnQgYWM7CisJaW50IHRpZDsKIAogCUtBU1NFUlQo dmFwLT5pdl9mbGFnc19odCAmIElFRUU4MDIxMV9GSFRfSFQsICgibm8gSFQgcmVxdWVzdGVkIikp OwogCkBAIC0xMTk4LDkgKzExOTksMTAgQEAKIAluaS0+bmlfaHRvcG1vZGUgPSAwOwkJLyogWFhY IG5lZWQgcHJvdGVjdGlvbiBzdGF0ZSAqLwogCW5pLT5uaV9odHN0YmMgPSAwOwkJLyogWFhYIG5l ZWQgaW5mbyAqLwogCi0JZm9yIChhYyA9IDA7IGFjIDwgV01FX05VTV9BQzsgYWMrKykgewotCQl0 YXAgPSAmbmktPm5pX3R4X2FtcGR1W2FjXTsKLQkJdGFwLT50eGFfYWMgPSBhYzsKKwlmb3IgKHRp ZCA9IDA7IHRpZCA8IFdNRV9OVU1fVElEOyB0aWQrKykgeworCQl0YXAgPSAmbmktPm5pX3R4X2Ft cGR1W3RpZF07CisJCXRhcC0+dHhhX2FjID0gVElEX1RPX1dNRV9BQyh0aWQpOworCQl0YXAtPnR4 YV90aWQgPSB0aWQ7CiAJfQogCS8qIE5COiBBTVBEVSB0eC9yeCBnb3Zlcm5lZCBieSBJRUVFODAy MTFfRkhUX0FNUERVX3tUWCxSWH0gKi8KIAluaS0+bmlfZmxhZ3MgfD0gSUVFRTgwMjExX05PREVf SFQgfCBJRUVFODAyMTFfTk9ERV9BTVBEVTsKQEAgLTE5MDksNyArMTkxMSw3IEBACiAJYmF0aW1l b3V0ID0gTEVfUkVBRF8yKGZybSs3KTsKIAogCWFjID0gVElEX1RPX1dNRV9BQyh0aWQpOwotCXRh cCA9ICZuaS0+bmlfdHhfYW1wZHVbYWNdOworCXRhcCA9ICZuaS0+bmlfdHhfYW1wZHVbdGlkXTsK IAlpZiAoKHRhcC0+dHhhX2ZsYWdzICYgSUVFRTgwMjExX0FHR1JfWENIR1BFTkQpID09IDApIHsK IAkJSUVFRTgwMjExX0RJU0NBUkRfTUFDKHZhcCwKIAkJICAgIElFRUU4MDIxMV9NU0dfQUNUSU9O IHwgSUVFRTgwMjExX01TR18xMU4sCkBAIC0xOTg2LDcgKzE5ODgsNyBAQAogCiAJaWYgKChiYXBh cmFtc2V0ICYgSUVFRTgwMjExX0RFTEJBUFNfSU5JVCkgPT0gMCkgewogCQlhYyA9IFRJRF9UT19X TUVfQUModGlkKTsKLQkJdGFwID0gJm5pLT5uaV90eF9hbXBkdVthY107CisJCXRhcCA9ICZuaS0+ bmlfdHhfYW1wZHVbdGlkXTsKIAkJaWMtPmljX2FkZGJhX3N0b3AobmksIHRhcCk7CiAJfSBlbHNl IHsKIAkJcmFwID0gJm5pLT5uaV9yeF9hbXBkdVt0aWRdOwpAQCAtMjA5OSw3ICsyMTAxLDcgQEAK IAl0YXAtPnR4YV9mbGFncyAmPSB+SUVFRTgwMjExX0FHR1JfTkFLOwogCiAJZGlhbG9ndG9rZW4g PSAodG9rZW5zKzEpICUgNjM7CQkvKiBYWFggKi8KLQl0aWQgPSBXTUVfQUNfVE9fVElEKHRhcC0+ dHhhX2FjKTsKKwl0aWQgPSB0YXAtPnR4YV90aWQ7CiAJdGFwLT50eGFfc3RhcnQgPSBuaS0+bmlf dHhzZXFzW3RpZF07CiAKIAlhcmdzWzBdID0gZGlhbG9ndG9rZW47CkBAIC0yMTUyLDcgKzIxNTQs NyBAQAogCQl2YXAtPml2X3N0YXRzLmlzX2FtcGR1X3N0b3ArKzsKIAogCQlpYy0+aWNfYWRkYmFf c3RvcChuaSwgdGFwKTsKLQkJYXJnc1swXSA9IFdNRV9BQ19UT19USUQodGFwLT50eGFfYWMpOwor CQlhcmdzWzBdID0gdGFwLT50eGFfdGlkOwogCQlhcmdzWzFdID0gSUVFRTgwMjExX0RFTEJBUFNf SU5JVDsKIAkJYXJnc1syXSA9IHJlYXNvbjsJCQkvKiBYWFggcmVhc29uIGNvZGUgKi8KIAkJaWMt PmljX3NlbmRfYWN0aW9uKG5pLCBJRUVFODAyMTFfQUNUSU9OX0NBVF9CQSwKQEAgLTIyMzcsNyAr MjIzOSw3IEBACiAJCSAgICB0YXAtPnR4YV9zdGFydCwKIAkJICAgIElFRUU4MDIxMV9TRVFfQURE KHRhcC0+dHhhX3N0YXJ0LCB0YXAtPnR4YV93bmQtMSksCiAJCSAgICB0YXAtPnR4YV9xZnJhbWVz LCB0YXAtPnR4YV9zZXFwZW5kaW5nLAotCQkgICAgV01FX0FDX1RPX1RJRCh0YXAtPnR4YV9hYykp OworCQkgICAgdGFwLT50eGFfdGlkKTsKIAogCQkvKiBOQjogdGltZXIgYWxyZWFkeSBzdG9wcGVk IGluIGJhcl90eF9jb21wbGV0ZSAqLwogCQl0YXAtPnR4YV9zdGFydCA9IHRhcC0+dHhhX3NlcXBl bmRpbmc7CkBAIC0yMjkyLDcgKzIyOTQsNyBAQAogCUlFRUU4MDIxMV9BRERSX0NPUFkoYmFyLT5p X3JhLCBuaS0+bmlfbWFjYWRkcik7CiAJSUVFRTgwMjExX0FERFJfQ09QWShiYXItPmlfdGEsIHZh cC0+aXZfbXlhZGRyKTsKIAotCXRpZCA9IFdNRV9BQ19UT19USUQodGFwLT50eGFfYWMpOworCXRp ZCA9IHRhcC0+dHhhX3RpZDsKIAliYXJjdGwgCT0gKHRhcC0+dHhhX2ZsYWdzICYgSUVFRTgwMjEx X0FHR1JfSU1NRURJQVRFID8KIAkJCTAgOiBJRUVFODAyMTFfQkFSX05PQUNLKQogCQl8IElFRUU4 MDIxMV9CQVJfQ09NUApJbmRleDogc3lzL25ldDgwMjExL2llZWU4MDIxMV9odC5oCj09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT0KLS0tIHN5cy9uZXQ4MDIxMS9pZWVlODAyMTFfaHQuaAkocmV2aXNpb24gMjM0MTA4KQorKysg c3lzL25ldDgwMjExL2llZWU4MDIxMV9odC5oCSh3b3JraW5nIGNvcHkpCkBAIC00NSw2ICs0NSw3 IEBACiAjZGVmaW5lCUlFRUU4MDIxMV9BR0dSX05BSwkJMHgwMDEwCS8qIHBlZXIgTkFLJ2QgQURE QkEgcmVxdWVzdCAqLwogI2RlZmluZQlJRUVFODAyMTFfQUdHUl9CQVJQRU5ECQkweDAwMjAJLyog QkFSIHJlc3BvbnNlIHBlbmRpbmcgKi8KIAl1aW50OF90CQl0eGFfYWM7CisJdWludDhfdAkJdHhh X3RpZDsKIAl1aW50OF90CQl0eGFfdG9rZW47CS8qIGRpYWxvZyB0b2tlbiAqLwogCWludAkJdHhh X2xhc3RzYW1wbGU7CS8qIHRpY2tzIEAgbGFzdCB0cmFmZmljIHNhbXBsZSAqLwogCWludAkJdHhh X3BrdHM7CS8qIHBhY2tldHMgb3ZlciBsYXN0IHNhbXBsZSBpbnRlcnZhbCAqLwpJbmRleDogc3lz L25ldDgwMjExL2llZWU4MDIxMV9ub2RlLmgKPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQotLS0gc3lzL25ldDgwMjExL2ll ZWU4MDIxMV9ub2RlLmgJKHJldmlzaW9uIDIzNDEwOCkKKysrIHN5cy9uZXQ4MDIxMS9pZWVlODAy MTFfbm9kZS5oCSh3b3JraW5nIGNvcHkpCkBAIC0yMTQsNyArMjE0LDcgQEAKIAl1aW50OF90CQkJ bmlfaHRzdGJjOwkvKiBIVCAqLwogCXVpbnQ4X3QJCQluaV9jaHc7CQkvKiBuZWdvdGlhdGVkIGNo YW5uZWwgd2lkdGggKi8KIAlzdHJ1Y3QgaWVlZTgwMjExX2h0cmF0ZXNldCBuaV9odHJhdGVzOwkv KiBuZWdvdGlhdGVkIGh0IHJhdGUgc2V0ICovCi0Jc3RydWN0IGllZWU4MDIxMV90eF9hbXBkdSBu aV90eF9hbXBkdVtXTUVfTlVNX0FDXTsKKwlzdHJ1Y3QgaWVlZTgwMjExX3R4X2FtcGR1IG5pX3R4 X2FtcGR1W1dNRV9OVU1fVElEXTsKIAlzdHJ1Y3QgaWVlZTgwMjExX3J4X2FtcGR1IG5pX3J4X2Ft cGR1W1dNRV9OVU1fVElEXTsKIAogCS8qIG90aGVycyAqLwpJbmRleDogc3lzL25ldDgwMjExL2ll ZWU4MDIxMV9vdXRwdXQuYwo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09Ci0tLSBzeXMvbmV0ODAyMTEvaWVlZTgwMjExX291 dHB1dC5jCShyZXZpc2lvbiAyMzQxMDgpCisrKyBzeXMvbmV0ODAyMTEvaWVlZTgwMjExX291dHB1 dC5jCSh3b3JraW5nIGNvcHkpCkBAIC0zMjQsNyArMzI0LDggQEAKIAkJICAgICh2YXAtPml2X2Zs YWdzX2h0ICYgSUVFRTgwMjExX0ZIVF9BTVBEVV9UWCkgJiYKIAkJICAgIChtLT5tX2ZsYWdzICYg TV9FQVBPTCkgPT0gMCkgewogCQkJY29uc3QgaW50IGFjID0gTV9XTUVfR0VUQUMobSk7Ci0JCQlz dHJ1Y3QgaWVlZTgwMjExX3R4X2FtcGR1ICp0YXAgPSAmbmktPm5pX3R4X2FtcGR1W2FjXTsKKwkJ CWNvbnN0IGludCB0aWQgPSBXTUVfQUNfVE9fVElEKGFjKTsKKwkJCXN0cnVjdCBpZWVlODAyMTFf dHhfYW1wZHUgKnRhcCA9ICZuaS0+bmlfdHhfYW1wZHVbdGlkXTsKIAogCQkJaWVlZTgwMjExX3R4 YW1wZHVfY291bnRfcGFja2V0KHRhcCk7CiAJCQlpZiAoSUVFRTgwMjExX0FNUERVX1JVTk5JTkco dGFwKSkgewpAQCAtNTg5LDcgKzU5MCw3IEBACiAJfQogCSoodWludDE2X3QgKikmd2gtPmlfZHVy WzBdID0gMDsKIAotCXRhcCA9ICZuaS0+bmlfdHhfYW1wZHVbVElEX1RPX1dNRV9BQyh0aWQpXTsK Kwl0YXAgPSAmbmktPm5pX3R4X2FtcGR1W3RpZF07CiAJaWYgKHRpZCAhPSBJRUVFODAyMTFfTk9O UU9TX1RJRCAmJiBJRUVFODAyMTFfQU1QRFVfUlVOTklORyh0YXApKQogCQltLT5tX2ZsYWdzIHw9 IE1fQU1QRFVfTVBEVTsKIAllbHNlIHsKSW5kZXg6IHN5cy9uZXQ4MDIxMS9pZWVlODAyMTFfc3Vw ZXJnLmMKPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PQotLS0gc3lzL25ldDgwMjExL2llZWU4MDIxMV9zdXBlcmcuYwkocmV2 aXNpb24gMjM0MTA4KQorKysgc3lzL25ldDgwMjExL2llZWU4MDIxMV9zdXBlcmcuYwkod29ya2lu ZyBjb3B5KQpAQCAtNTYyLDkgKzU2MiwxMSBAQAogCUlFRUU4MDIxMV9MT0NLKGljKTsKIAloZWFk ID0gc3EtPmhlYWQ7CiAJd2hpbGUgKChtID0gc3EtPmhlYWQpICE9IE5VTEwgJiYgTV9BR0VfR0VU KG0pIDwgcXVhbnRhKSB7CisJCWludCBhYyA9IE1fV01FX0dFVEFDKG0pOworCQlpbnQgdGlkID0g V01FX0FDX1RPX1RJRChhYyk7CiAJCS8qIGNsZWFyIHRhcCByZWYgdG8gZnJhbWUgKi8KIAkJbmkg PSAoc3RydWN0IGllZWU4MDIxMV9ub2RlICopIG0tPm1fcGt0aGRyLnJjdmlmOwotCQl0YXAgPSAm bmktPm5pX3R4X2FtcGR1W01fV01FX0dFVEFDKG0pXTsKKwkJdGFwID0gJm5pLT5uaV90eF9hbXBk dVt0aWRdOwogCQlLQVNTRVJUKHRhcC0+dHhhX3ByaXZhdGUgPT0gbSwgKCJzdGFnaW5nIHF1ZXVl IGVtcHR5IikpOwogCQl0YXAtPnR4YV9wcml2YXRlID0gTlVMTDsKIApAQCAtNjYxLDYgKzY2Myw3 IEBACiAJc3RydWN0IGllZWU4MDIxMV90eF9hbXBkdSAqdGFwOwogCXN0cnVjdCBtYnVmICptc3Rh Z2VkOwogCXVpbnQzMl90IHR4dGltZSwgbGltaXQ7CisJaW50IHRpZCA9IFdNRV9BQ19UT19USUQo cHJpKTsKIAogCS8qCiAJICogQ2hlY2sgaWYgdGhlIHN1cHBsaWVkIGZyYW1lIGNhbiBiZSBhZ2dy ZWdhdGVkLgpAQCAtNjcwLDcgKzY3Myw3IEBACiAJICogICAgIGJlIGFnZ3JlZ2F0ZWQgd2l0aCBv dGhlciB0eXBlcyBvZiBmcmFtZXMgd2hlbiBlbmNyeXB0aW9uIGlzIG9uPwogCSAqLwogCUlFRUU4 MDIxMV9MT0NLKGljKTsKLQl0YXAgPSAmbmktPm5pX3R4X2FtcGR1W3ByaV07CisJdGFwID0gJm5p LT5uaV90eF9hbXBkdVt0aWRdOwogCW1zdGFnZWQgPSB0YXAtPnR4YV9wcml2YXRlOwkJLyogTkI6 IHdlIHJldXNlIEFNUERVIHN0YXRlICovCiAJaWVlZTgwMjExX3R4YW1wZHVfY291bnRfcGFja2V0 KHRhcCk7CiAKQEAgLTc4MywxMiArNzg2LDEzIEBACiAJc3RydWN0IGllZWU4MDIxMV9zdXBlcmcg KnNnID0gaWMtPmljX3N1cGVyZzsKIAlzdHJ1Y3QgaWVlZTgwMjExX3R4X2FtcGR1ICp0YXA7CiAJ c3RydWN0IG1idWYgKm0sICpoZWFkOwotCWludCBhYzsKKwlpbnQgdGlkOwogCiAJSUVFRTgwMjEx X0xPQ0soaWMpOwogCWhlYWQgPSBOVUxMOwotCWZvciAoYWMgPSAwOyBhYyA8IFdNRV9OVU1fQUM7 IGFjKyspIHsKLQkJdGFwID0gJm5pLT5uaV90eF9hbXBkdVthY107CisJZm9yICh0aWQgPSAwOyB0 aWQgPCBXTUVfTlVNX1RJRDsgdGlkKyspIHsKKwkJaW50IGFjID0gVElEX1RPX1dNRV9BQyh0aWQp OworCQl0YXAgPSAmbmktPm5pX3R4X2FtcGR1W3RpZF07CiAJCW0gPSB0YXAtPnR4YV9wcml2YXRl OwogCQlpZiAobSAhPSBOVUxMKSB7CiAJCQl0YXAtPnR4YV9wcml2YXRlID0gTlVMTDsKSW5kZXg6 IHN5cy9uZXQ4MDIxMS9pZWVlODAyMTFfZGRiLmMKPT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQotLS0gc3lzL25ldDgwMjEx L2llZWU4MDIxMV9kZGIuYwkocmV2aXNpb24gMjM0MTA4KQorKysgc3lzL25ldDgwMjExL2llZWU4 MDIxMV9kZGIuYwkod29ya2luZyBjb3B5KQpAQCAtMjkzLDcgKzI5Myw3IEBACiAJCW5pLT5uaV9o dG9wbW9kZSwgbmktPm5pX2h0c3RiYywgbmktPm5pX2Nodyk7CiAKIAkvKiBYWFggYW1wZHUgc3Rh dGUgKi8KLQlmb3IgKGkgPSAwOyBpIDwgV01FX05VTV9BQzsgaSsrKQorCWZvciAoaSA9IDA7IGkg PCBXTUVfTlVNX1RJRDsgaSsrKQogCQlpZiAobmktPm5pX3R4X2FtcGR1W2ldLnR4YV9mbGFncyAm IElFRUU4MDIxMV9BR0dSX1NFVFVQKQogCQkJX2RiX3Nob3dfdHhhbXBkdSgiXHQiLCBpLCAmbmkt Pm5pX3R4X2FtcGR1W2ldKTsKIAlmb3IgKGkgPSAwOyBpIDwgV01FX05VTV9USUQ7IGkrKykKSW5k ZXg6IHN5cy9tb2R1bGVzL3dsYW4vTWFrZWZpbGUKPT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQotLS0gc3lzL21vZHVsZXMv d2xhbi9NYWtlZmlsZQkocmV2aXNpb24gMjM0MTA4KQorKysgc3lzL21vZHVsZXMvd2xhbi9NYWtl ZmlsZQkod29ya2luZyBjb3B5KQpAQCAtMTIsNyArMTIsNyBAQAogCWllZWU4MDIxMV9yYXRlY3Rs X25vbmUuYyBpZWVlODAyMTFfcmVnZG9tYWluLmMgXAogCWllZWU4MDIxMV9odC5jIGllZWU4MDIx MV9od21wLmMgaWVlZTgwMjExX2FkaG9jLmMgaWVlZTgwMjExX2hvc3RhcC5jIFwKIAlpZWVlODAy MTFfbW9uaXRvci5jIGllZWU4MDIxMV9zdGEuYyBpZWVlODAyMTFfd2RzLmMgaWVlZTgwMjExX2Rk Yi5jIFwKLQlpZWVlODAyMTFfdGRtYS5jCisJaWVlZTgwMjExX3RkbWEuYyBpZWVlODAyMTFfYWxx LmMgaWVlZTgwMjExX3N1cGVyZy5jCiBTUkNTKz0JYnVzX2lmLmggZGV2aWNlX2lmLmggb3B0X2Rk Yi5oIG9wdF9pbmV0Lmggb3B0X2luZXQ2Lmggb3B0X2lweC5oIFwKIAlvcHRfdGRtYS5oIG9wdF93 bGFuLmgKIApJbmRleDogc3lzL2Rldi9hdGgvaWZfYXRoX3R4LmMKPT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQotLS0gc3lz L2Rldi9hdGgvaWZfYXRoX3R4LmMJKHJldmlzaW9uIDIzNDEwOCkKKysrIHN5cy9kZXYvYXRoL2lm X2F0aF90eC5jCSh3b3JraW5nIGNvcHkpCkBAIC00MjE0LDE0ICs0MjE0LDExIEBACiB7CiAJc3Ry dWN0IGllZWU4MDIxMV9ub2RlICpuaSA9ICZhbi0+YW5fbm9kZTsKIAlzdHJ1Y3QgaWVlZTgwMjEx X3R4X2FtcGR1ICp0YXA7Ci0JaW50IGFjOwogCiAJaWYgKHRpZCA9PSBJRUVFODAyMTFfTk9OUU9T X1RJRCkKIAkJcmV0dXJuIE5VTEw7CiAKLQlhYyA9IFRJRF9UT19XTUVfQUModGlkKTsKLQotCXRh cCA9ICZuaS0+bmlfdHhfYW1wZHVbYWNdOworCXRhcCA9ICZuaS0+bmlfdHhfYW1wZHVbdGlkXTsK IAlyZXR1cm4gdGFwOwogfQogCkluZGV4OiBzeXMvZGV2L2l3bi9pZl9pd24uYwo9PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 Ci0tLSBzeXMvZGV2L2l3bi9pZl9pd24uYwkocmV2aXNpb24gMjM0MTA4KQorKysgc3lzL2Rldi9p d24vaWZfaXduLmMJKHdvcmtpbmcgY29weSkKQEAgLTMzMDksOSArMzMwOSwxMiBAQAogCX0KIAlh YyA9IE1fV01FX0dFVEFDKG0pOwogCisJLyoKKwkgKiBYWFggd2hhdCBhYm91dCB0aGUgbm9uLVFv UyBUSUQ/CisJICovCiAJaWYgKElFRUU4MDIxMV9RT1NfSEFTX1NFUSh3aCkgJiYKLQkgICAgSUVF RTgwMjExX0FNUERVX1JVTk5JTkcoJm5pLT5uaV90eF9hbXBkdVthY10pKSB7Ci0JCXN0cnVjdCBp ZWVlODAyMTFfdHhfYW1wZHUgKnRhcCA9ICZuaS0+bmlfdHhfYW1wZHVbYWNdOworCSAgICBJRUVF ODAyMTFfQU1QRFVfUlVOTklORygmbmktPm5pX3R4X2FtcGR1W3RpZF0pKSB7CisJCXN0cnVjdCBp ZWVlODAyMTFfdHhfYW1wZHUgKnRhcCA9ICZuaS0+bmlfdHhfYW1wZHVbdGlkXTsKIAogCQlyaW5n ID0gJnNjLT50eHFbKihpbnQgKil0YXAtPnR4YV9wcml2YXRlXTsKIAkJKih1aW50MTZfdCAqKXdo LT5pX3NlcSA9CkBAIC01NjEyLDcgKzU2MTUsNyBAQAogaXduX2FtcGR1X3R4X3N0YXJ0KHN0cnVj dCBpZWVlODAyMTFjb20gKmljLCBzdHJ1Y3QgaWVlZTgwMjExX25vZGUgKm5pLAogICAgIHVpbnQ4 X3QgdGlkKQogewotCXN0cnVjdCBpZWVlODAyMTFfdHhfYW1wZHUgKnRhcCA9ICZuaS0+bmlfdHhf YW1wZHVbVElEX1RPX1dNRV9BQyh0aWQpXTsKKwlzdHJ1Y3QgaWVlZTgwMjExX3R4X2FtcGR1ICp0 YXAgPSAmbmktPm5pX3R4X2FtcGR1W3RpZF07CiAJc3RydWN0IGl3bl9zb2Z0YyAqc2MgPSBuaS0+ bmlfaWMtPmljX2lmcC0+aWZfc29mdGM7CiAJc3RydWN0IGl3bl9vcHMgKm9wcyA9ICZzYy0+b3Bz OwogCXN0cnVjdCBpd25fbm9kZSAqd24gPSAodm9pZCAqKW5pOwo= --047d7b2e4820fdad7f04bd5e57a6-- From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 11 09:27:52 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 12F571065676 for ; Wed, 11 Apr 2012 09:27:52 +0000 (UTC) (envelope-from moonlightakkiy@yahoo.ca) Received: from nm13-vm1.bullet.mail.ne1.yahoo.com (nm13-vm1.bullet.mail.ne1.yahoo.com [98.138.91.62]) by mx1.freebsd.org (Postfix) with SMTP id B66AB8FC0A for ; Wed, 11 Apr 2012 09:27:51 +0000 (UTC) Received: from [98.138.90.57] by nm13.bullet.mail.ne1.yahoo.com with NNFMP; 11 Apr 2012 09:27:51 -0000 Received: from [98.138.226.61] by tm10.bullet.mail.ne1.yahoo.com with NNFMP; 11 Apr 2012 09:27:51 -0000 Received: from [127.0.0.1] by smtp212.mail.ne1.yahoo.com with NNFMP; 11 Apr 2012 09:27:51 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s1024; t=1334136471; bh=VrEyrj1efU/xJJDdGsOgpdxlKMWR/N1RjC7/DlqWff0=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Received:MIME-Version:Received:Received:In-Reply-To:References:Date:Message-ID:Subject:From:To:Cc:Content-Type:Content-Transfer-Encoding; b=1WJgSt8bK3Wqlj5vnsP41oQ8rvXG/CJoNDVu3iOI77wtWoilkmtACgD2SbOrhMuPM+xtQRtPVmLLVuYzHKINMoc9PCZDPGJ/C/M0ujLyMPXZ5ZS5AIQsMHAQbSWC+XYJ43eu0MUwX56niT3exfr6nej3vehyv3JUlTl/u67VuCo= X-Yahoo-Newman-Id: 212393.73504.bm@smtp212.mail.ne1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: kaJ2R20VM1mOUC8wq7InIq89.L6tVQ_SdREtMiihyJNyZwY fm4N10M8FmD33EtArdYJKY22KiCglPw5DR5fePzCyTsGDXdkKRgIE.0Kk__i BHfJ0zoHmt4gFS50yL38xW3XAnDdCfwBX4ctJmK3ZgsgSgydySg3aaBCGNp1 lumL2Gbjnmrxgdvi3wmyw_apecbCPF0z6bRBGm.aA_7gDxXoIDpVckGZ7Z0Z EhdnuZST3U.YLLjbH_KY9nFftXDFmKfPmrveeBOnGWs9cqYxMQ7ntxsB9Jzj lCxTvZlferqssJ72WGZ2BwWepV1wQl5ToTRIp5wpKuHvR7uakfh8FNvKPgbM Mo2ZRduy2PEYmmXfSpAkfJk2KlPGzLmZO3LvyCvD3T2C7xUYM55hDMNVHCGj Oz7h.Fke.HUPuaib_VT4dsAeh_.sCJVoXXxk- X-Yahoo-SMTP: Xr6qjFWswBAEmd20sAvB4Q3keqXvXsIH9TjJ Received: from mail-ob0-f182.google.com (moonlightakkiy@209.85.214.182 with plain) by smtp212.mail.ne1.yahoo.com with SMTP; 11 Apr 2012 02:27:51 -0700 PDT Received: by obbwc18 with SMTP id wc18so1276903obb.13 for ; Wed, 11 Apr 2012 02:27:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.60.14.136 with SMTP id p8mr20305137oec.68.1334136470517; Wed, 11 Apr 2012 02:27:50 -0700 (PDT) Received: by 10.182.208.39 with HTTP; Wed, 11 Apr 2012 02:27:50 -0700 (PDT) In-Reply-To: <1016606749.20120410102710@serebryakov.spb.ru> References: <4F839730.2020503@gmail.com> <1016606749.20120410102710@serebryakov.spb.ru> Date: Wed, 11 Apr 2012 03:27:50 -0600 Message-ID: From: PseudoCylon To: Adrian Chadd , =?windows-1251?B?y/7h7uzo8CDD8Ojj7vDu4g==?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: Intel 6250 and WiMax X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2012 09:27:52 -0000 > ------------------------------ > > Message: 5 > Date: Mon, 9 Apr 2012 14:06:51 -0700 > From: Adrian Chadd > Subject: Re: Intel 6250 and WiMax > To: ??????? ???????? > Cc: freebsd-wireless@freebsd.org > Message-ID: > =C2=A0 =C2=A0 =C2=A0 =C2=A0 > Content-Type: text/plain; charset=3Dwindows-1251 > > 2012/4/9 =EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=C3=B0 =EF= =BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=C3=A2 : >>> We do. Linux has a stack in net/wimax and the driver for the >>> Intel devices is in drivers/net/wimax/i2400m >>> In other words, no, we currently do not support the WiMax stuff >>> of any of the Intel cards nor any other device afaik >> >> Hmm, I suppose I can always order the carry-it-anywhere hub as a solutio= n. >> Or use Windows / GNU/Linux. Since it seems this isn't something short an= d >> easy, and given the status of WiMax, probably not something that will >> happen for FreeBSD soon/ever. > > I really am encouraging someone to look into this. I'd love to see > wimax stack+support in FreeBSD. At a quick look, linux wimax stack doesn't do much. Basically, it handles attach/detach and some state changes (INIT and RUN). I could work on adding this degree of supports as a weekend project (slow progress) if no one does it. Though, only usie and uhso could get benefits, i.e. call if_alloc() with other than IFT_OTHER, no manual configuration, and relevant ifconfig out put, like carrier: mega telco media: GSM status: connected bar: . : i | How should we name it, net80216 netwimax netwman netmnet (mobile net) netwnet (wireless net) or else? For those looking for device drivers, even though wimax stack is added, someone still have to write the drivers to make your device work. > > If you can come up with a useful sounding proposal, the freebsd > foundation may even sponsor the work. Then, will the foundation send me one like this? http://forums.freebsd.org/showpost.php?p=3D84303&postcount=3D29 AK From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 11 13:04:53 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 615CA106566B; Wed, 11 Apr 2012 13:04:53 +0000 (UTC) (envelope-from venture37@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id A4B1E8FC15; Wed, 11 Apr 2012 13:04:52 +0000 (UTC) Received: by bkcjc3 with SMTP id jc3so886881bkc.13 for ; Wed, 11 Apr 2012 06:04:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=fe/t4NrG5PwWhnmzqvwaYSOt8B1YuTKzJMKp68EEC1A=; b=oCzsPFnYw9iLpwSSMoXte8KVcX0upIf3ecTBdUyfCuUg9PqnIU/nUMXkOvKTOYWq9x wEOwl/3jrU+DI68RuIfaLDjrvpF4pdRgWQBUsqL7AyuqqR56rBnPKAMdR6jwHmqI92QP +5p567R0KB2aV/fovRtKZbsnztg9xFlzesH/hJAsln4NQEUGhUq6P2U1WQqoAXt3Sefe OiKK0qZpWQpZ+wTHuXJIwZONbXWOWPaEt2TFg2n2PQoRRygXLL4Hk6O8tz5PpkPRBmtb WWEqUIi8vPT1nqZxLeFu0OO/ZaFbKOBC89M9cOKIsR6UFvylnB0CidoysfBMEwbHEOk2 1odA== Received: by 10.204.130.1 with SMTP id q1mr6119181bks.70.1334149491474; Wed, 11 Apr 2012 06:04:51 -0700 (PDT) Received: from Sevans-Mac-mini.local (n3.venture37.net. [91.103.132.218]) by mx.google.com with ESMTPS id gu12sm4801075bkc.1.2012.04.11.06.04.49 (version=SSLv3 cipher=OTHER); Wed, 11 Apr 2012 06:04:50 -0700 (PDT) Message-ID: <4F85816B.2070206@gmail.com> Date: Wed, 11 Apr 2012 14:04:43 +0100 From: Sevan / Venture37 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: Adrian Chadd References: <4F8052EB.5090007@gmail.com> <4F806763.7040404@gmail.com> <4F8095D8.5020701@gmail.com> <4F80A38C.3080602@gmail.com> <4F80A81C.2070602@gmail.com> <4F80A9B4.2000500@gmail.com> <4F80AEC3.2050602@gmail.com> <4F80C5FC.70607@gmail.com> <4F81710E.2070402@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-wireless@freebsd.org Subject: Re: ath(4) fails to attach X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2012 13:04:53 -0000 On 09/04/2012 19:28, Adrian Chadd wrote: > I bet your ath(4) issues will magically be solved once the > ACPI/resource enumeration issues are sorted out. update src just now & built a new kernel, ath(4) now attaches to the card :) Are the invalid modes reported below of concern? Sevan ath0: irq 16 at device 0.0 on cardbus0 ar5212Attach: sc 0xffffff80050df000 st 0x1 sh 0xfffffe00d4000000 ar5212SetPowerMode: AWAKE -> AWAKE (set chip ) ar5212SetPowerMode: AWAKE -> AWAKE (set chip ) ar5212SetPowerMode: AWAKE -> AWAKE (set chip ) ar5212SetPowerMode: AWAKE -> AWAKE (set chip ) EEPROM protect 0x0 ar5212Attach: return getchannels: cc 0 regDmn 0xf0 mode 0xffffff ecm getregstate: EEPROM cc 0 rd 0x10 getchannels: !avail mode 0x1e6f (0x8000) flags 0x10480 getchannels: !avail mode 0x1e6f (0x20000) flags 0x20480 getchannels: !avail mode 0x1e6f (0x40000) flags 0x40480 getchannels: !avail mode 0x1e6f (0x10000) flags 0x10140 getchannels: !avail mode 0x1e6f (0x80000) flags 0x20140 getchannels: !avail mode 0x1e6f (0x100000) flags 0x40140 assignPrivateChannels: private[ 0] 5210/0x2150 -> channel 5210 assignPrivateChannels: private[ 1] 5250/0x2150 -> channel 5250 assignPrivateChannels: private[ 2] 5290/0x2150 -> channel 5290 assignPrivateChannels: private[ 3] 5760/0x2150 -> channel 5760 assignPrivateChannels: private[ 4] 5800/0x2150 -> channel 5800 assignPrivateChannels: private[ 5] 5180/0x140 -> channel 5180 assignPrivateChannels: private[ 6] 5200/0x140 -> channel 5200 assignPrivateChannels: private[ 7] 5220/0x140 -> channel 5220 assignPrivateChannels: private[ 8] 5240/0x140 -> channel 5240 assignPrivateChannels: private[ 9] 5260/0x140 -> channel 5260 assignPrivateChannels: private[ 10] 5280/0x140 -> channel 5280 assignPrivateChannels: private[ 11] 5300/0x140 -> channel 5300 assignPrivateChannels: private[ 12] 5320/0x140 -> channel 5320 assignPrivateChannels: private[ 13] 5745/0x140 -> channel 5745 assignPrivateChannels: private[ 14] 5765/0x140 -> channel 5765 assignPrivateChannels: private[ 15] 5785/0x140 -> channel 5785 assignPrivateChannels: private[ 16] 5805/0x140 -> channel 5805 assignPrivateChannels: private[ 17] 5825/0x140 -> channel 5825 assignPrivateChannels: private[ 18] 2412/0xa0 -> channel 2412 assignPrivateChannels: private[ 19] 2417/0xa0 -> channel 2417 assignPrivateChannels: private[ 20] 2422/0xa0 -> channel 2422 assignPrivateChannels: private[ 21] 2427/0xa0 -> channel 2427 assignPrivateChannels: private[ 22] 2432/0xa0 -> channel 2432 assignPrivateChannels: private[ 23] 2437/0xa0 -> channel 2437 assignPrivateChannels: private[ 24] 2442/0xa0 -> channel 2442 assignPrivateChannels: private[ 25] 2447/0xa0 -> channel 2447 assignPrivateChannels: private[ 26] 2452/0xa0 -> channel 2452 assignPrivateChannels: private[ 27] 2457/0xa0 -> channel 2457 assignPrivateChannels: private[ 28] 2462/0xa0 -> channel 2462 assignPrivateChannels: 46 public, 29 private channels ath_hal_init_channels: cc 0 ath_hal_update_dfsdomain ah_dfsDomain: 0 ar5212GetRateTable: invalid mode 0x10000 ar5212GetRateTable: invalid mode 0x8000 ar5212SetupTxQueue: queue 9 ar5212SetupTxQueue: queue 8 ar5212SetupTxQueue: queue 0 ar5212SetupTxQueue: queue 1 ar5212SetupTxQueue: queue 2 ar5212SetupTxQueue: queue 3 ath0: AR5212 mac 5.6 RF5112 phy 4.1 ath0: 2GHz radio: 0x0000; 5GHz radio: 0x0036 From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 11 13:16:08 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1ED991065674; Wed, 11 Apr 2012 13:16:08 +0000 (UTC) (envelope-from venture37@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 5D4008FC0A; Wed, 11 Apr 2012 13:16:07 +0000 (UTC) Received: by bkcjc3 with SMTP id jc3so901264bkc.13 for ; Wed, 11 Apr 2012 06:16:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=I9dK9P0EAi2hEfqnf2TdIZPH8tFP5J3EjPAy1RnXt4o=; b=Un2UO6MUkL+wFDNkuTI1TnKzZ7fnSY9M5F+I/rtm5g08tNR2aqVEHTsRqwHDnkwNZD cbbhWPkl905+22iKfAKv99UKzKTx/5gD/jLOSfB1n5N8KaCShplMj+yN75P57Aay7j6h ZMBuy82sS8YA5NYEpg+pQuseP72dNoVppFere9VOtlIYcwXeF09YQaU2ejMfsSvcqD+4 kZL6N19V7GejcxoJFJX3C9HrOqM8DKtu6wEvrGmO1shg3MYCiqacjemMjJzSvy9GDONZ fxPI9Kv4zKGbmX7NAhP8g2+b+gg7/ToPU8EdUzS7lr9YTQMfvd4WspJ3PsrFNjlyRhyq qiAA== Received: by 10.204.131.84 with SMTP id w20mr5978872bks.65.1334150166277; Wed, 11 Apr 2012 06:16:06 -0700 (PDT) Received: from Sevans-Mac-mini.local (n3.venture37.net. [91.103.132.218]) by mx.google.com with ESMTPS id cy11sm4821247bkb.7.2012.04.11.06.16.04 (version=SSLv3 cipher=OTHER); Wed, 11 Apr 2012 06:16:05 -0700 (PDT) Message-ID: <4F858413.4010505@gmail.com> Date: Wed, 11 Apr 2012 14:16:03 +0100 From: Sevan / Venture37 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: Adrian Chadd References: <4F8052EB.5090007@gmail.com> <4F806763.7040404@gmail.com> <4F8095D8.5020701@gmail.com> <4F80A38C.3080602@gmail.com> <4F80A81C.2070602@gmail.com> <4F80A9B4.2000500@gmail.com> <4F80AEC3.2050602@gmail.com> <4F80C5FC.70607@gmail.com> <4F81710E.2070402@gmail.com> <4F85816B.2070206@gmail.com> In-Reply-To: <4F85816B.2070206@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-wireless@freebsd.org Subject: Re: ath(4) fails to attach X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2012 13:16:08 -0000 On 11/04/2012 14:04, Sevan / Venture37 wrote: > update src just now & built a new kernel, ath(4) now attaches to the > card :) > Are the invalid modes reported below of concern? the driver attaches & I can use a wlan interface to bind to it & scan successfully for APs, but when I mark the inteface up the kernel starts spitting out messages & doesn't stop until the instance of wlan(4) is destroyed. ar5212SetPowerMode: AWAKE -> AWAKE (set chip ) ar5212SetPowerMode: AWAKE -> AWAKE (set chip ) ar5212SetPowerMode: AWAKE -> AWAKE (set chip ) ar5212SetPowerMode: AWAKE -> AWAKE (set chip ) ar5212SetRateTable: cck: MaxRD: 54 MaxCTL: 40 TPC_Reduction 0 chan=2412 (0xa0) maxAvailPower=38 pwr6_24=38, maxPower=38 ar5112SetRfRegs: chan 2412/0xa0 modesIndex 3 ar5212SetAntennaSwitchInternal: Setting fast diversity on. ar5212ResetTxQueue: reset queue 0 setTxQInterrupts: tx ok 0x0 err 0x0 desc 0x1 eol 0x1 urn 0x0 ar5212ResetTxQueue: reset queue 1 setTxQInterrupts: tx ok 0x0 err 0x0 desc 0x3 eol 0x3 urn 0x0 ar5212ResetTxQueue: reset queue 2 setTxQInterrupts: tx ok 0x0 err 0x0 desc 0x7 eol 0x7 urn 0x0 ar5212ResetTxQueue: reset queue 3 setTxQInterrupts: tx ok 0x0 err 0x0 desc 0xf eol 0xf urn 0x0 ar5212ResetTxQueue: inactive queue 4 ar5212ResetTxQueue: inactive queue 5 ar5212ResetTxQueue: inactive queue 6 ar5212ResetTxQueue: inactive queue 7 ar5212ResetTxQueue: reset queue 8 ar5212ResetTxQueue: defaulting to rdytime = 62 uS setTxQInterrupts: tx ok 0x0 err 0x0 desc 0x10f eol 0x10f urn 0x0 ar5212ResetTxQueue: reset queue 9 setTxQInterrupts: tx ok 0x0 err 0x0 desc 0x30f eol 0x10f urn 0x0 ar5212Reset: done ar5212AniReset: chan 2412/0xa0 restore 1 opmode 1 enableAniMIBCounters: Enable mib counters: OfdmPhyErrBase 0xbffe0c cckPhyErrBase 0xbfff38 ar5212SetInterrupts: 0x80965 => 0xc0000071 ar5212SetInterrupts: new IMR 0x804b7 ar5212SetInterrupts: enable IER ar5212SetInterrupts: 0xc0000071 => 0xc0000071 ar5212SetInterrupts: disable IER ar5212SetInterrupts: new IMR 0x804b7 ar5212SetInterrupts: enable IER ar5212SetInterrupts: 0xc0000071 => 0x0 ar5212SetInterrupts: disable IER ar5212SetInterrupts: new IMR 0x0 ath0: ath_rx_tasklet: sc_inreset_cnt > 0; skipping ar5212SetPowerMode: AWAKE -> AWAKE (set chip ) ar5212SetPowerMode: AWAKE -> AWAKE (set chip ) ar5212SetPowerMode: AWAKE -> AWAKE (set chip ) ar5212SetPowerMode: AWAKE -> AWAKE (set chip ) ar5212SetRateTable: MaxRD: 54 TurboMax: 32 MaxCTL: 33 TPC_Reduction 0 chan=2412 (0x480) maxAvailPower=33 pwr6_24=38, maxPower=33 ar5212SetRateTable: cck: MaxRD: 54 MaxCTL: 40 TPC_Reduction 0 chan=2412 (0x480) maxAvailPower=38 pwr6_24=38, maxPower=38 ar5112SetRfRegs: chan 2412/0x480 modesIndex 4 ar5212SetAntennaSwitchInternal: Setting fast diversity on. ar5212ResetTxQueue: reset queue 0 setTxQInterrupts: tx ok 0x0 err 0x0 desc 0x30f eol 0x10f urn 0x0 ar5212ResetTxQueue: reset queue 1 setTxQInterrupts: tx ok 0x0 err 0x0 desc 0x30f eol 0x10f urn 0x0 ar5212ResetTxQueue: reset queue 2 setTxQInterrupts: tx ok 0x0 err 0x0 desc 0x30f eol 0x10f urn 0x0 ar5212ResetTxQueue: reset queue 3 setTxQInterrupts: tx ok 0x0 err 0x0 desc 0x30f eol 0x10f urn 0x0 ar5212ResetTxQueue: inactive queue 4 ar5212ResetTxQueue: inactive queue 5 ar5212ResetTxQueue: inactive queue 6 ar5212ResetTxQueue: inactive queue 7 ar5212ResetTxQueue: reset queue 8 ar5212ResetTxQueue: defaulting to rdytime = 62 uS setTxQInterrupts: tx ok 0x0 err 0x0 desc 0x30f eol 0x10f urn 0x0 ar5212ResetTxQueue: reset queue 9 setTxQInterrupts: tx ok 0x0 err 0x0 desc 0x30f eol 0x10f urn 0x0 ar5212Reset: done From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 11 15:08:50 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C8031106566C; Wed, 11 Apr 2012 15:08:50 +0000 (UTC) (envelope-from sendtomatt@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8CF9B8FC15; Wed, 11 Apr 2012 15:08:50 +0000 (UTC) Received: by pbcwz17 with SMTP id wz17so1471100pbc.13 for ; Wed, 11 Apr 2012 08:08:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=HjA5U52WgtxbgXgXg2rhXQjfVagLRhf5N3j3RAs9/Q8=; b=RJhIZMAQ87ennhqhIAP+F5V+ZYMM4hadrbTjbss5qIh1NDQFxiODzgIxLX8m6XtViB h3aqQUqKZJOyGbKfDPMpaN7PFpLerslTl3uBW5iTSudPuiiblplsZHQFRt74KLuRvayw TRz7r7rP8AluQVMohmZbL+9ZJmNb8uyNnXbWiSNGwB0/6Abb1YyvgDtswn81rlJFPAeJ JA0m9tDsjHVP/AWqCTsvK3gnrq9jl4Eijm4c26oUzbG9w8e/ZGoYS7ujAFOD9uwORzDg yB0Nw5NAdubqe7j4hPedG2rmPPT1YlnUELcTVZx7PKy1jloR5QwJtFiO7LxZT2X9CpvT 6JBg== Received: by 10.68.229.73 with SMTP id so9mr4360205pbc.163.1334156930150; Wed, 11 Apr 2012 08:08:50 -0700 (PDT) Received: from bakeneko.local (70-36-223-239.dsl.dynamic.sonic.net. [70.36.223.239]) by mx.google.com with ESMTPS id b10sm3108548pbr.46.2012.04.11.08.08.48 (version=SSLv3 cipher=OTHER); Wed, 11 Apr 2012 08:08:49 -0700 (PDT) Message-ID: <4F859E6E.2030006@gmail.com> Date: Wed, 11 Apr 2012 08:08:30 -0700 From: matt User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.3) Gecko/20120326 Thunderbird/10.0.3 MIME-Version: 1.0 To: PseudoCylon References: <4F839730.2020503@gmail.com> <1016606749.20120410102710@serebryakov.spb.ru> In-Reply-To: X-Enigmail-Version: 1.3.5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: =?UTF-8?B?0JvRjtCx0L7QvNC40YAg0JPRgA==?=, freebsd-wireless@freebsd.org Subject: Re: Intel 6250 and WiMax X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2012 15:08:51 -0000 On 04/11/12 02:27, PseudoCylon wrote: >> ------------------------------ >> >> Message: 5 >> Date: Mon, 9 Apr 2012 14:06:51 -0700 >> From: Adrian Chadd >> Subject: Re: Intel 6250 and WiMax >> To: ??????? ???????? >> Cc: freebsd-wireless@freebsd.org >> Message-ID: >> >> Content-Type: text/plain; charset=windows-1251 >> >> 2012/4/9 ������ð �������â : >>>> We do. Linux has a stack in net/wimax and the driver for the >>>> Intel devices is in drivers/net/wimax/i2400m >>>> In other words, no, we currently do not support the WiMax stuff >>>> of any of the Intel cards nor any other device afaik >>> Hmm, I suppose I can always order the carry-it-anywhere hub as a solution. >>> Or use Windows / GNU/Linux. Since it seems this isn't something short and >>> easy, and given the status of WiMax, probably not something that will >>> happen for FreeBSD soon/ever. >> I really am encouraging someone to look into this. I'd love to see >> wimax stack+support in FreeBSD. > At a quick look, linux wimax stack doesn't do much. Basically, it > handles attach/detach and some state changes (INIT and RUN). I could > work on adding this degree of supports as a weekend project (slow > progress) if no one does it. > > Though, only usie and uhso could get benefits, i.e. call if_alloc() > with other than IFT_OTHER, no manual configuration, and relevant > ifconfig out put, like > carrier: mega telco > media: GSM > status: connected > bar: . : i | > > How should we name it, > net80216 > netwimax > netwman > netmnet (mobile net) > netwnet (wireless net) > or else? > > For those looking for device drivers, even though wimax stack is > added, someone still have to write the drivers to make your device > work. > >> If you can come up with a useful sounding proposal, the freebsd >> foundation may even sponsor the work. > Then, will the foundation send me one like this? > http://forums.freebsd.org/showpost.php?p=84303&postcount=29 > > > AK > _______________________________________________ > 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" net80216 for consistency? Matt From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 11 15:31:54 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 52F6D1065673 for ; Wed, 11 Apr 2012 15:31:54 +0000 (UTC) (envelope-from chrishutchinson1@yahoo.com) Received: from nm2.bullet.mail.bf1.yahoo.com (nm2.bullet.mail.bf1.yahoo.com [98.139.212.161]) by mx1.freebsd.org (Postfix) with SMTP id 945B78FC17 for ; Wed, 11 Apr 2012 15:31:53 +0000 (UTC) Received: from [98.139.212.145] by nm2.bullet.mail.bf1.yahoo.com with NNFMP; 11 Apr 2012 15:31:52 -0000 Received: from [98.139.213.5] by tm2.bullet.mail.bf1.yahoo.com with NNFMP; 11 Apr 2012 15:31:52 -0000 Received: from [127.0.0.1] by smtp105.mail.bf1.yahoo.com with NNFMP; 11 Apr 2012 15:31:52 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1334158312; bh=c107PBYEcPWtPhpLts8GP9gFz6vLivNT+DlKlEFHwBM=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References:X-Mailer:Mime-Version:Content-Type:Content-Transfer-Encoding; b=3VEmVtNBYs8iZoNpDsBgBAG+JErOxO3Ug16+2Ife+1zXW6t1koRhbi43UPMisJPEINpXsImmv260pfh/xy1g/00JqmZnKL/QrLy5Xj79acDJY2VLtrwmNFzDCF3ylZsbVFVoE+5gq+qtZkCztGsovS+sHhJ8jfDLWwa2+XX/qas= X-Yahoo-Newman-Id: 530543.68973.bm@smtp105.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: S.yG0YIVM1lxg3oUV.DtmaFz0nYAW21_oLU5Zy4cudF64cj fceib56w8Bqt8aZcV1..Q6YV5Hxd4aCEwwRvLAzr9rvjMC_lKhgEzgKO4qni faFUuYodDulWBlISKESph4PGkxSrAW88TBi_nnTQ7xQT8ilRSUeY1HTH9kwD 6bvy2cDlkSaw1QNT_Hmg1aZ4B8xM34izKAQwDPJs8hHNjBmnVLfMpgZrSzid nPAhsVDIW4X6JbuzDpImy0J1alXaD9EvgdNN8M1xFuACm_SnEeAGGPvoohDh 1uTHiGhKZWt6xsJyY8CDQ1PaXJGOX.o3htSREBSpWUJ2VsjBtko3zwlGzJE0 iVa6FzGxsJSLocXVUkFMRdNOB9qgZGUAMJ2qzkm5R30RtjZVdRcD2bc2W6eI AhMt0nof4GYL5SjJx5GAtoa1uMPnRSfDZccgIqxKR2pwKrd9cgeX44Ctf.bh aYomphpjIq4h4zUX0uoXp_zfDvkeYegyXzvI7c4JSPMNyhuptR2DZI1zzsDz SP43hZzz2T65RQnLi55SqVCVTFg-- X-Yahoo-SMTP: uW3vktqswBBwhzUUqSfIo9IQDlOyJjOVATmsCrk- Received: from virus.local (chrishutchinson1@107.62.164.136 with login) by smtp105.mail.bf1.yahoo.com with SMTP; 11 Apr 2012 08:31:52 -0700 PDT Date: Wed, 11 Apr 2012 08:31:08 -0700 From: Chris To: PseudoCylon , freebsd-wireless@freebsd.org Message-ID: <20120411083108.74d7dd3b@virus.local> In-Reply-To: References: <4F839730.2020503@gmail.com> <1016606749.20120410102710@serebryakov.spb.ru> X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.6; amd64-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: =?UTF-8?Q?=D0=9B=D1=8E=D0=B1=D0=BE?=, =?UTF-8?Q?=D0=BC=D0=B8=D1=80_=D0=93=D1=80=D0=B8=D0=B3=D0=BE=D1=80=D0=BE?= Subject: Re: Intel 6250 and WiMax X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2012 15:31:54 -0000 Greetings... On Wed, 11 Apr 2012 03:27:50 -0600 PseudoCylon wrote: > > ------------------------------ > > > > Message: 5 > > Date: Mon, 9 Apr 2012 14:06:51 -0700 > > From: Adrian Chadd > > Subject: Re: Intel 6250 and WiMax > > To: ??????? ???????? > > Cc: freebsd-wireless@freebsd.org > > Message-ID: > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 > > Content-Type: text/plain; charset=3Dwindows-1251 > > > > 2012/4/9 =EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=C3=B0 = =EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=C3=A2 : > >>> We do. Linux has a stack in net/wimax and the driver for the > >>> Intel devices is in drivers/net/wimax/i2400m > >>> In other words, no, we currently do not support the WiMax stuff > >>> of any of the Intel cards nor any other device afaik > >> > >> Hmm, I suppose I can always order the carry-it-anywhere hub as a > >> solution. Or use Windows / GNU/Linux. Since it seems this isn't > >> something short and easy, and given the status of WiMax, probably > >> not something that will happen for FreeBSD soon/ever. > > > > I really am encouraging someone to look into this. I'd love to see > > wimax stack+support in FreeBSD. >=20 > At a quick look, linux wimax stack doesn't do much. Basically, it > handles attach/detach and some state changes (INIT and RUN). I could > work on adding this degree of supports as a weekend project (slow > progress) if no one does it. >=20 > Though, only usie and uhso could get benefits, i.e. call if_alloc() > with other than IFT_OTHER, no manual configuration, and relevant > ifconfig out put, like > carrier: mega telco > media: GSM > status: connected > bar: . : i | >=20 > How should we name it, > net80216 > netwimax I vote netwimax > netwman > netmnet (mobile net) > netwnet (wireless net) > or else? >=20 > For those looking for device drivers, even though wimax stack is > added, someone still have to write the drivers to make your device > work. Appears NetBSD has some support (since 2009?): http://mail-index.netbsd.org/tech-kern/2009/08/04/msg005647.html >=20 > > > > If you can come up with a useful sounding proposal, the freebsd > > foundation may even sponsor the work. >=20 > Then, will the foundation send me one like this? > http://forums.freebsd.org/showpost.php?p=3D84303&postcount=3D29 I want one too! :) >=20 >=20 > AK --Chris > _______________________________________________ > 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 Wed Apr 11 16:38:25 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CCFB8106566C for ; Wed, 11 Apr 2012 16:38:25 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 963978FC0A for ; Wed, 11 Apr 2012 16:38:25 +0000 (UTC) Received: by pbcwz17 with SMTP id wz17so1572141pbc.13 for ; Wed, 11 Apr 2012 09:38:25 -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 :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=ZkKrPxyB2ofmgyzwseiWLXyp/xoDuu6/QsQjagVb8og=; b=RrU0uVBR3B3WsIP3atK1d10wBOSrZrCSJfF615YDBHa6AXHWJtqRBVVVI06ojObiKu L5H9LWVk/mIoU+iDc62Dbj8ZiJrv2JrBwTCwIft55KkomprnSrHFHqM3AoXEqaKadguO 1Z9jT6FKsrxlOp9Nai0PTGXdJwoNTnJKkttMDkKIdFXcVDobCz+7EIUzIfVTwaAL8RPV ySi+eK0Tr01J8QUvPZkCkRcGOx2uSDfSTLOKwsu1s4GYtnRBQoCeI/TkNHbc4e6B69MV cEN1oHEyjwt2Tts20smznHzRa9SdoWGRd5lS0no+xGWbZzEOOQb7ztaHUACUG3EZNV9r MWcQ== MIME-Version: 1.0 Received: by 10.68.236.164 with SMTP id uv4mr15821140pbc.3.1334162305029; Wed, 11 Apr 2012 09:38:25 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.143.9.11 with HTTP; Wed, 11 Apr 2012 09:38:24 -0700 (PDT) In-Reply-To: <4F858413.4010505@gmail.com> References: <4F8052EB.5090007@gmail.com> <4F806763.7040404@gmail.com> <4F8095D8.5020701@gmail.com> <4F80A38C.3080602@gmail.com> <4F80A81C.2070602@gmail.com> <4F80A9B4.2000500@gmail.com> <4F80AEC3.2050602@gmail.com> <4F80C5FC.70607@gmail.com> <4F81710E.2070402@gmail.com> <4F85816B.2070206@gmail.com> <4F858413.4010505@gmail.com> Date: Wed, 11 Apr 2012 09:38:24 -0700 X-Google-Sender-Auth: 61egJqp23WMLAWz-ySDPNHw4J3c Message-ID: From: Adrian Chadd To: "Sevan / Venture37" Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: ath(4) fails to attach X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2012 16:38:25 -0000 .. disable debugging now :) adrian From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 11 22:25:11 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3ED451065670; Wed, 11 Apr 2012 22:25:11 +0000 (UTC) (envelope-from venture37@gmail.com) Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) by mx1.freebsd.org (Postfix) with ESMTP id 88CA38FC08; Wed, 11 Apr 2012 22:25:10 +0000 (UTC) Received: by wibhr17 with SMTP id hr17so4416636wib.1 for ; Wed, 11 Apr 2012 15:25:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=l7PlZl/Wl3sNtFYZgEOzDSxZZgxZDX6KgjZu8rLUc2M=; b=bvK7RMcNv+S//c7F6kCvGypyqyYRWcEg6TcfwlSVdsuXnHbwYarorz4w7RcKsD4BUp +tHyiiE5yDylUz83ZUknUkQlX0ODcQvFwTWZF0K67PvTSbkFNSsf9McF/jOkHfLtgYNB BdJX5UpBC7gpnAkDhWw3su/Ya/18jicErEmOFKh9BGlWlIKFw8/9vTyivB/+Lm162ViF KwNAFuqbaBk2dNMnAhsbsBTKbnwkwhYM8ieZQLVi8NF9+CAd/BI6yg5rNzlaDWJB/lcO BvKVA+sgUZ95wisxpvyW+757sirKzwGEMFTiJGLhQr19atr7f/nGEZg+MDlF9sXI/iCR K/AQ== Received: by 10.216.134.136 with SMTP id s8mr92558wei.6.1334183109489; Wed, 11 Apr 2012 15:25:09 -0700 (PDT) Received: from Sevans-MacBook-Pro.local (cpc2-brig17-2-0-cust527.3-3.cable.virginmedia.com. [81.101.198.16]) by mx.google.com with ESMTPS id ea6sm47949016wib.5.2012.04.11.15.25.07 (version=SSLv3 cipher=OTHER); Wed, 11 Apr 2012 15:25:07 -0700 (PDT) Message-ID: <4F8604C1.4090902@gmail.com> Date: Wed, 11 Apr 2012 23:25:05 +0100 From: Sevan / Venture37 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: Adrian Chadd References: <4F8052EB.5090007@gmail.com> <4F806763.7040404@gmail.com> <4F8095D8.5020701@gmail.com> <4F80A38C.3080602@gmail.com> <4F80A81C.2070602@gmail.com> <4F80A9B4.2000500@gmail.com> <4F80AEC3.2050602@gmail.com> <4F80C5FC.70607@gmail.com> <4F81710E.2070402@gmail.com> <4F85816B.2070206@gmail.com> <4F858413.4010505@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-wireless@freebsd.org Subject: Re: ath(4) fails to attach X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2012 22:25:11 -0000 On 11/04/2012 17:38, Adrian Chadd wrote: > .. disable debugging now:) > > > > adrian hmm, now its not playing ball with or without ACPI_DEBUG option, I will follow up with a PR as advised earlier, sorry about the noise. Sevan From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 11 22:34:21 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1FE72106566B for ; Wed, 11 Apr 2012 22:34:21 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by mx1.freebsd.org (Postfix) with ESMTP id DC0F38FC16 for ; Wed, 11 Apr 2012 22:34:20 +0000 (UTC) Received: by dadz14 with SMTP id z14so5681467dad.17 for ; Wed, 11 Apr 2012 15:34:20 -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 :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Dorem1H2hzI4L6q4iEKLUv2b45vxAbIpg5Lk0iCMecg=; b=PEGXyVezKuFRaCrM/v6z+OCxBw1qCDWXnHdPo0Thi6u5fFTRjmcphS2uCrpfTWfIfc d81MwqpO8J8+Lz+w3su9dd3JPlO3sPSB+XkxwsfjxUhfhQhBHbELHnJ/zBpUXf1GIh01 Jml6nCmAM70FdHQMVn18stLEqjxSxsYE9XMPt8jupu322hAlHTp+nvpP5mbICBJkPjSi siiBeI7DKpkXaM4qyph8xDvSOTKOlPX/aJA0JAAmPx0Pw1Xm8CVevqub52qjGl3Z/2NE 4KTssH+SDbjJq1gfHMjuWh25fwA6svasTU1+7ocwmfP6LlA+rMJGZIfX88lrSUb9Syq/ wVXg== MIME-Version: 1.0 Received: by 10.68.218.72 with SMTP id pe8mr1433386pbc.45.1334183660697; Wed, 11 Apr 2012 15:34:20 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.143.9.11 with HTTP; Wed, 11 Apr 2012 15:34:20 -0700 (PDT) In-Reply-To: <4F8604C1.4090902@gmail.com> References: <4F8052EB.5090007@gmail.com> <4F806763.7040404@gmail.com> <4F8095D8.5020701@gmail.com> <4F80A38C.3080602@gmail.com> <4F80A81C.2070602@gmail.com> <4F80A9B4.2000500@gmail.com> <4F80AEC3.2050602@gmail.com> <4F80C5FC.70607@gmail.com> <4F81710E.2070402@gmail.com> <4F85816B.2070206@gmail.com> <4F858413.4010505@gmail.com> <4F8604C1.4090902@gmail.com> Date: Wed, 11 Apr 2012 15:34:20 -0700 X-Google-Sender-Auth: tfYm3CxDB46zsI65dUHJO0IXCtM Message-ID: From: Adrian Chadd To: "Sevan / Venture37" Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: ath(4) fails to attach X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2012 22:34:21 -0000 On 11 April 2012 15:25, Sevan / Venture37 wrote: > hmm, now its not playing ball with or without ACPI_DEBUG option, I will > follow up with a PR as advised earlier, sorry about the noise. So it attaches fine with debugging enabled, but not with debugging disabled? Adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 12 00:04:36 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E08B2106566C; Thu, 12 Apr 2012 00:04:36 +0000 (UTC) (envelope-from venture37@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3B32F8FC21; Thu, 12 Apr 2012 00:04:36 +0000 (UTC) Received: by wern13 with SMTP id n13so1222777wer.13 for ; Wed, 11 Apr 2012 17:04:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=nCCmGvYjy/Gyl65O9lUTYjibrdfNG5HkD19lrsSYlNo=; b=qeSQ4HfXjofV4X+S8U6LzeZUg+fLm2K/Q7ZJ31j5P+1aDIfQ8J/Asr0LHv4g2ZnVdl wTth/1hXeN52nN8w8Vxkbtk+luC//kJM67ByfODHCgpARbN7dhT1Lm5sXx2n8/dZXjmU 9BQ+9d3BNxvbbM9Rs46d9Mws6ZTWAcrkm9jRajQBaeNsTfq4FUM6x3/RxyQWv7g5LONw FqLYg3p6jcRP87lEIeO7HYuInJ3UZc6nVOjJ6iGhA8OHHzmTViVrf6GS1nLO1+HsD8Ae 7DAD5DWH9wUMrts1wUPEe3pp5a0Zkn745sLJT38zaW1z+wzOlnnHEyW+S1X/pRehS//t zmGg== Received: by 10.216.139.79 with SMTP id b57mr191781wej.37.1334189075177; Wed, 11 Apr 2012 17:04:35 -0700 (PDT) Received: from Sevans-MacBook-Pro.local (cpc2-brig17-2-0-cust527.3-3.cable.virginmedia.com. [81.101.198.16]) by mx.google.com with ESMTPS id fn2sm15110912wib.0.2012.04.11.17.04.33 (version=SSLv3 cipher=OTHER); Wed, 11 Apr 2012 17:04:33 -0700 (PDT) Message-ID: <4F861C10.5020503@gmail.com> Date: Thu, 12 Apr 2012 01:04:32 +0100 From: Sevan / Venture37 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: Adrian Chadd References: <4F8052EB.5090007@gmail.com> <4F806763.7040404@gmail.com> <4F8095D8.5020701@gmail.com> <4F80A38C.3080602@gmail.com> <4F80A81C.2070602@gmail.com> <4F80A9B4.2000500@gmail.com> <4F80AEC3.2050602@gmail.com> <4F80C5FC.70607@gmail.com> <4F81710E.2070402@gmail.com> <4F85816B.2070206@gmail.com> <4F858413.4010505@gmail.com> <4F8604C1.4090902@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-wireless@freebsd.org Subject: Re: ath(4) fails to attach X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 00:04:37 -0000 On 11/04/2012 23:34, Adrian Chadd wrote: > So it attaches fine with debugging enabled, but not with debugging disabled? Nope, neither. Sevan From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 12 10:16:59 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 89FCD106566B for ; Thu, 12 Apr 2012 10:16:59 +0000 (UTC) (envelope-from blacklongfellow@gmail.com) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id 61A2D8FC0A for ; Thu, 12 Apr 2012 10:16:59 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1SIH5B-0004I5-48 for freebsd-wireless@freebsd.org; Thu, 12 Apr 2012 03:16:53 -0700 Date: Thu, 12 Apr 2012 03:16:53 -0700 (PDT) From: Shaunda To: freebsd-wireless@freebsd.org Message-ID: <1334225813117-5635221.post@n5.nabble.com> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: ath updates - AR5416 (and later) LED fixes X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 10:16:59 -0000 Im wanting to make my old florescent http://www.ledstrips8.com/flexible-led-strip-lighting-c-32.html led strip blue fixture in to a led light fixture? im wanting to make my old florescent light fixture in to a led light fixture im wanting to make my http://www.ledstrips8.com/led-light-bars-c-38.html led strip 12v old florescent light fixture in to a led light fixture but im wanting to know if i just hard wire the http://www.ledstrips8.com/ waterproof led strip light led strip into the power lines of the house The easiest way that I can think of is buy a similar product like this one -- View this message in context: http://freebsd.1045724.n5.nabble.com/ath-updates-AR5416-and-later-LED-fixes-tp5096773p5635221.html Sent from the freebsd-wireless mailing list archive at Nabble.com. From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 12 13:07:17 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 676721065672 for ; Thu, 12 Apr 2012 13:07:17 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 0D64C8FC17 for ; Thu, 12 Apr 2012 13:07:16 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id q3CD7GE0007530 for ; Thu, 12 Apr 2012 07:07:16 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id q3CD7GG3007527 for ; Thu, 12 Apr 2012 07:07:16 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Thu, 12 Apr 2012 07:07:16 -0600 (MDT) From: Warren Block To: freebsd-wireless@freebsd.org Message-ID: 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.2.7 (wonkity.com [127.0.0.1]); Thu, 12 Apr 2012 07:07:16 -0600 (MDT) Subject: ath(4) hardware support list X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 13:07:17 -0000 I'd like to add a list of Atheros supported card part numbers to ath(4). Why? Because it's really hard for a user to tell whether a given card is supported or not before buying. Testing before buying is often impossible. There are two forms of part numbers, for example, AR5BXB63 and AR5008. Is there a practical way to generate this list other than testing? From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 12 13:50:14 2012 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 44EBB106566B for ; Thu, 12 Apr 2012 13:50:14 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2E7C28FC0A for ; Thu, 12 Apr 2012 13:50:14 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q3CDoDTn049577 for ; Thu, 12 Apr 2012 13:50:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q3CDoDHh049576; Thu, 12 Apr 2012 13:50:13 GMT (envelope-from gnats) Date: Thu, 12 Apr 2012 13:50:13 GMT Message-Id: <201204121350.q3CDoDHh049576@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org From: Johann Hugo Cc: Subject: Re: kern/165969: [ath] Slower performance in adhoc mode vs Client/AP mode, same HW X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Johann Hugo 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, 12 Apr 2012 13:50:14 -0000 The following reply was made to PR kern/165969; it has been noted by GNATS. From: Johann Hugo To: bug-followup@freebsd.org, jhugo@meraka.csir.co.za Cc: Subject: Re: kern/165969: [ath] Slower performance in adhoc mode vs Client/AP mode, same HW Date: Thu, 12 Apr 2012 15:42:31 +0200 --Boundary-00=_HvthP91+WvoKOR8 Content-Type: multipart/alternative; boundary="Boundary-01=_HvthPjLCbO6xmZd" Content-Transfer-Encoding: 7bit --Boundary-01=_HvthPjLCbO6xmZd Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit The problem originates from the big 802.11/HAL code changes between FreeBSD-7 and FreeBSD-8. Here is the output of athregs, athregs -d and athregs -q for both FreeBSD 7.4- STABLE and for FreeBSD 8.0-RELEASE. --Boundary-01=_HvthPjLCbO6xmZd Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit

The problem originates from the big 802.11/HAL code changes between FreeBSD-7 and FreeBSD-8.

 

Here is the output of athregs, athregs -d and athregs -q for both FreeBSD 7.4-STABLE and for FreeBSD 8.0-RELEASE.

 

 

--Boundary-01=_HvthPjLCbO6xmZd-- --Boundary-00=_HvthP91+WvoKOR8 Content-Type: text/plain; charset="UTF-8"; name="athregs-FreeBSD-7.4-STABLE.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="athregs-FreeBSD-7.4-STABLE.txt" FreeBSD 7.4-STABLE mesh-2893# iperf -c 192.168.1.1 ------------------------------------------------------------ Client connecting to 192.168.1.1, TCP port 5001 TCP window size: 32.5 KByte (default) ------------------------------------------------------------ [ 3] local 192.168.1.2 port 53140 connected with 192.168.1.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 35.1 MBytes 29.4 Mbits/sec mesh-2893# athregs CR 00000004 RXDP 07c69120 CFG 00000120 IER 00000001 TXCFG 00000015 RXCFG 00000005 MIBC 00000000 TOPS 00000008 RXNPTO 00000008 TXNPTO 00000010 RPGTO 00000000 RPCNT 0000001f MACMISC 00000000 SPC_0 00d65af0 SPC_1 00000000 DMADBG0 88888888 DMADBG1 00000000 DMADBG2 12249249 DMADBG3 00000000 DMADBG4 00000000 DMADBG5 00000000 DMADBG6 001327f0 DMADBG7 00000000 DCM_A 00000004 DCM_D 00000000 DCCFG 00000002 CCFG 00000000 CCUCFG 0010020a CPC0 00000000 CPC1 00000000 CPC2 00000000 CPC3 00000000 CPCOVF 00000000 D_SIFS 00000230 D_SLOT 00000168 D_EIFS 00000e60 D_MISC 0000a0e0 D_SEQ 0000085f D_FPCTL 000003e0 D_TXPSE 00010000 RC 00000000 SCR 00000000 INTPEND 00000000 SFR 00000000 PCICFG 00000054 GPIOCR 00000000 GPIODO 00000000 GPIODI 00000017 SREV 000000a4 PCIEPMC 00000010 SERDES 00000000 SERDES2 00000000 STA_ID0 4f488000 STA_ID1 1882ee2a BSS_ID0 4f488000 BSS_ID1 00009028 SLOTTIME 00000000 TIME_OUT 03e803e8 RSSI_THR 00000781 USEC 128d93a7 BEACON 00000064 CFP_PER 00000000 TIMER0 000016b4 TIMER1 0000b590 TIMER2 0040b550 TIMER3 000016b5 CFP_DUR 00000000 RXFILTER 00000097 MCAST_0 00000001 MCAST_1 00000040 DIAG_SW 00000000 TSF_L32 2059d6b4 TSF_U32 00000000 TST_ADAC 00000000 DEF_ANT 00000001 QOS_MASK 000fc78f SEQ_MASK 0000000f OBSERV2 00000000 OBSERV1 00002888 LAST_TST 205880c7 NAV 00000000 RTS_OK 00000000 RTS_FAIL 00000000 ACK_FAIL 00000000 FCS_FAIL 00000000 BEAC_CNT 00000000 SLEEP1 0510b3ba SLEEP2 0200b3b5 SLEEP3 00030002 BSSMSKL ffffffff BSSMSKU 0000ffff TPC 002e2e2e TFCNT 07ed78e4 RFCNT 01a88586 RCCNT 09e3252a CCCNT 8e5afa1d QUIET1 00001676 QUIET2 00010002 TSF_PARM 00000001 NOACK 00000052 PHY_ERR 00000000 QOS_CTRL 000100aa QOS_SEL 00003210 MISCMODE 00000004 FILTOFDM 00000076 FILTCCK 00000000 PHYCNT1 00bffe0c PHYCMSK1 00020000 PHYCNT2 00bfff38 PHYCMSK2 02000000 mesh-2893# athregs -d D[0] MASK 00000001 IFS 007ffc0f RTRY 0008200a CHNT 00000000 MISC 000100 D[1] MASK 00000002 IFS 002ffc0f RTRY 0008200a CHNT 00100800 MISC 000100 D[2] MASK 00000004 IFS 00203c07 RTRY 0008200a CHNT 00100bc0 MISC 000100 D[3] MASK 00000008 IFS 00201c03 RTRY 0008200a CHNT 001005e0 MISC 000100 D[4] MASK 00000010 IFS 002ffc0f RTRY 00020804 CHNT 00000000 MISC 001002 D[5] MASK 00000020 IFS 002ffc0f RTRY 00020804 CHNT 00000000 MISC 001002 D[6] MASK 00000040 IFS 002ffc0f RTRY 00020804 CHNT 00000000 MISC 001002 D[7] MASK 00000080 IFS 002ffc0f RTRY 00020804 CHNT 00000000 MISC 001002 D[8] MASK 00000100 IFS 002ffc0f RTRY 0008200a CHNT 00000000 MISC 040100 D[9] MASK 00000200 IFS 002ffc1f RTRY 0008200a CHNT 00000000 MISC 250100 mesh-2893# athregs -q Q_TXE 00000200 Q_TXD 00000000 Q_RDYTIMSHD 00000000 Q_ONESHOTARM_SC 00000000 Q_ONESHOTARM_CC 00000000 Q[0] TXDP 00000000 CBR 00000000 RDYT 00000000 MISC 00000800 STS 00000000 Q[1] TXDP 07c8ec40 CBR 00000000 RDYT 00000000 MISC 00000800 STS 00000000 Q[2] TXDP 00000000 CBR 00000000 RDYT 00000000 MISC 00000800 STS 00000000 Q[3] TXDP 00000000 CBR 00000000 RDYT 00000000 MISC 00000800 STS 00000000 Q[4] TXDP 00000000 CBR 00000000 RDYT 00000000 MISC 00000000 STS 00000000 Q[5] TXDP 00000000 CBR 00000000 RDYT 00000000 MISC 00000000 STS 00000000 Q[6] TXDP 00000000 CBR 00000000 RDYT 00000000 MISC 00000000 STS 00000000 Q[7] TXDP 00000000 CBR 00000000 RDYT 00000000 MISC 00000000 STS 00000000 Q[8] TXDP 00000000 CBR 00000000 RDYT 01017000 MISC 00000862 STS 00000000 Q[9] TXDP 07caf000 CBR 00000000 RDYT 00000000 MISC 000008a2 STS 00000000 --Boundary-00=_HvthP91+WvoKOR8 Content-Type: text/plain; charset="UTF-8"; name="athregs-FreeBSD-8.0-RELEASE.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="athregs-FreeBSD-8.0-RELEASE.txt" FreeBSD 8.0-RELEASE mesh-2893# iperf -c 192.168.1.1 ------------------------------------------------------------ Client connecting to 192.168.1.1, TCP port 5001 TCP window size: 32.5 KByte (default) ------------------------------------------------------------ [ 3] local 192.168.1.2 port 29927 connected with 192.168.1.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 24.4 MBytes 20.4 Mbits/sec mesh-2893# athregs CR 00000004 RXDP 07d46c60 CFG 00000120 IER 00000001 TXCFG 00000015 RXCFG 00000005 MIBC 00000000 TOPS 00000008 RXNPTO 00000008 TXNPTO 00000010 RPGTO 00000000 RPCNT 0000001f MACMISC 00000000 SPC_0 00b84261 SPC_1 00000000 DMADBG0 88888888 DMADBG1 00000000 DMADBG2 12249249 DMADBG3 00000000 DMADBG4 00000000 DMADBG5 00000000 DMADBG6 001327f0 DMADBG7 00000000 DCM_A 00000000 DCM_D 00000000 DCCFG 00000002 CCFG 00000000 CCUCFG 0010020a CPC0 00000000 CPC1 00000000 CPC2 00000000 CPC3 00000000 CPCOVF 00000000 D_SIFS 00000230 D_SLOT 00000168 D_EIFS 00000e60 D_MISC 0000a0e0 D_SEQ 00000170 D_FPCTL 000003e0 D_TXPSE 00010000 RC 00000000 SCR 00000000 INTPEND 00000000 SFR 00000000 PCICFG 00000054 GPIOCR 00000000 GPIODO 00000000 GPIODI 00000017 SREV 000000a4 PCIEPMC 00000010 SERDES 00000000 SERDES2 00000000 STA_ID0 4f488000 STA_ID1 1882ee2a BSS_ID0 4f488000 BSS_ID1 00009028 SLOTTIME 00000000 TIME_OUT 03e803e8 RSSI_THR 00000781 USEC 128d93a7 BEACON 00000064 CFP_PER 00000000 TIMER0 000067e0 TIMER1 00033ef0 TIMER2 0001e0f0 TIMER3 000067e1 CFP_DUR 00000000 RXFILTER 00000097 MCAST_0 00000001 MCAST_1 00000040 DIAG_SW 00000000 TSF_L32 e19f0162 TSF_U32 00000073 TST_ADAC 00000000 DEF_ANT 00000001 QOS_MASK 000fc78f SEQ_MASK 0000000f OBSERV2 00000000 OBSERV1 00002898 LAST_TST e0431c1e NAV 00000000 RTS_OK 00000000 RTS_FAIL 00000000 ACK_FAIL 00000000 FCS_FAIL 00000000 BEAC_CNT 00000000 SLEEP1 05133e0a SLEEP2 02033e05 SLEEP3 00030002 BSSMSKL ffffffff BSSMSKU 0000ffff TPC 002a2a2a TFCNT 0ad11813 RFCNT 0267b662 RCCNT 0dba3e01 CCCNT 98426b34 QUIET1 000067c2 QUIET2 00010002 TSF_PARM 00000001 NOACK 00000052 PHY_ERR 00000000 QOS_CTRL 000100aa QOS_SEL 00003210 MISCMODE 00000004 FILTOFDM 000000b5 FILTCCK 00000000 PHYCNT1 00bffe0c PHYCMSK1 00020000 PHYCNT2 00bfff38 PHYCMSK2 02000000 mesh-2893# athregs -d D[0] MASK 00000001 IFS 007ffc0f RTRY 0008200a CHNT 00000000 MISC 000100 D[1] MASK 00000002 IFS 003ffc0f RTRY 0008200a CHNT 00000000 MISC 000100 D[2] MASK 00000004 IFS 00203c07 RTRY 0008200a CHNT 00100bc0 MISC 000100 D[3] MASK 00000008 IFS 00201c03 RTRY 0008200a CHNT 001005e0 MISC 000100 D[4] MASK 00000010 IFS 002ffc0f RTRY 00020804 CHNT 00000000 MISC 001002 D[5] MASK 00000020 IFS 002ffc0f RTRY 00020804 CHNT 00000000 MISC 001002 D[6] MASK 00000040 IFS 002ffc0f RTRY 00020804 CHNT 00000000 MISC 001002 D[7] MASK 00000080 IFS 002ffc0f RTRY 00020804 CHNT 00000000 MISC 001002 D[8] MASK 00000100 IFS 002ffc0f RTRY 0008200a CHNT 00000000 MISC 040100 D[9] MASK 00000200 IFS 003ffc1f RTRY 0008200a CHNT 00000000 MISC 250100 mesh-2893# athregs -q Q_TXE 00000200 Q_TXD 00000000 Q_RDYTIMSHD 00000000 Q_ONESHOTARM_SC 00000000 Q_ONESHOTARM_CC 00000000 Q[0] TXDP 00000000 CBR 00000000 RDYT 00000000 MISC 00000800 STS 00000000 Q[1] TXDP 07c6ea40 CBR 00000000 RDYT 00000000 MISC 00000800 STS 00000000 Q[2] TXDP 00000000 CBR 00000000 RDYT 00000000 MISC 00000800 STS 00000000 Q[3] TXDP 00000000 CBR 00000000 RDYT 00000000 MISC 00000800 STS 00000000 Q[4] TXDP 00000000 CBR 00000000 RDYT 00000000 MISC 00000000 STS 00000000 Q[5] TXDP 00000000 CBR 00000000 RDYT 00000000 MISC 00000000 STS 00000000 Q[6] TXDP 00000000 CBR 00000000 RDYT 00000000 MISC 00000000 STS 00000000 Q[7] TXDP 00000000 CBR 00000000 RDYT 00000000 MISC 00000000 STS 00000000 Q[8] TXDP 00000000 CBR 00000000 RDYT 01017000 MISC 00000862 STS 00000000 Q[9] TXDP 07c6f000 CBR 00000000 RDYT 00000000 MISC 000008a2 STS 00000000 --Boundary-00=_HvthP91+WvoKOR8-- From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 12 14:25:13 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 444F91065737 for ; Thu, 12 Apr 2012 14:25:13 +0000 (UTC) (envelope-from jhugo@meraka.csir.co.za) Received: from marge.meraka.csir.co.za (marge.meraka.csir.co.za [IPv6:2001:4200:7000:3::1]) by mx1.freebsd.org (Postfix) with ESMTP id 22FB78FC21 for ; Thu, 12 Apr 2012 14:25:11 +0000 (UTC) Received: from jeep.localnet (unknown [IPv6:2001:4200:7000:3:223:aeff:fea7:a3c2]) by marge.meraka.csir.co.za (Postfix) with ESMTP id C9AD2D0CC21 for ; Thu, 12 Apr 2012 16:25:09 +0200 (SAST) From: Johann Hugo To: freebsd-wireless@freebsd.org Date: Thu, 12 Apr 2012 16:25:09 +0200 User-Agent: KMail/1.13.7 (FreeBSD/9.0-RELEASE; KDE/4.7.3; amd64; ; ) X-KMail-Markup: true MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_FXuhPtxQ4SdKv90" Message-Id: <201204121625.09572.jhugo@meraka.csir.co.za> X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: hostapd + 802.1X with external Authentication Server X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 14:25:13 -0000 --Boundary-00=_FXuhPtxQ4SdKv90 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi all Has anyone succeeded in configuring hostapd + 802.1X with an external Authentication Server ? I can get it to work with a PSK, but not with an external radius server. I don't see any errors when I run hostapd in the foreground, but it never fowards the authentication packets to the radius server. Hostapd also don't like the "eap_server" keyword in hostapd.conf. The wpa_supplicant of the client never gets past this before it restarts: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=0 Im not sure if I'm missing something, but I get the same results on FreeBSD 8, 9 and 10. Here is my rc.conf, hostapd.conf and the output of running hostapd. Thanks Johann --Boundary-00=_FXuhPtxQ4SdKv90 Content-Type: text/plain; charset="UTF-8"; name="rc.conf" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="rc.conf" hostname="AP-vlan" wlans_ath0="wlan0" create_args_wlan0="wlanmode hostap country ZA" ifconfig_wlan0="146.64.5.5/24 mode 11g channel 6" defaultrouter="146.64.5.1" hostapd_enable="YES" cloned_interfaces="bridge0" ifconfig_bridge0="addm sis0 addm wlan0 up" ifconfig_sis0="up" --Boundary-00=_FXuhPtxQ4SdKv90 Content-Type: text/plain; charset="UTF-8"; name="hostapd.conf" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="hostapd.conf" interface=wlan0 ctrl_interface=/var/run/hostapd ctrl_interface_group=wheel ssid=testAP hw_mode=g channel=6 wpa=1 wpa_pairwise=CCMP TKIP wpa_key_mgmt=WPA-EAP wpa_pairwise=TKIP CCMP rsn_pairwise=CCMP #eap_server=1 #eapol_version=1 #eapol_key_index_workaround=1 ieee8021x=1 own_ip_addr=146.64.5.5 #nas_identifier=testAP auth_server_addr=146.64.8.25 auth_server_port=1812 auth_server_shared_secret=testing123 --Boundary-00=_FXuhPtxQ4SdKv90 Content-Type: text/plain; charset="UTF-8"; name="hostapd.out" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="hostapd.out" AP-vlan:~ # hostapd -d /etc/hostapd.conf Configuration file: /etc/hostapd.conf ctrl_interface_group=0 (from group name 'wheel') BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits) Completing interface initialization Mode: (null) Channel: 6 Frequency: -1 MHz Flushing old station entries Deauthenticate all stations bsd_set_privacy: enabled=0 bsd_set_key: alg=0 addr=0x0 key_idx=0 set_tx=1 seq_len=0 key_len=0 bsd_del_key: key_idx=0 bsd_set_key: alg=0 addr=0x0 key_idx=1 set_tx=0 seq_len=0 key_len=0 bsd_del_key: key_idx=1 bsd_set_key: alg=0 addr=0x0 key_idx=2 set_tx=0 seq_len=0 key_len=0 bsd_del_key: key_idx=2 bsd_set_key: alg=0 addr=0x0 key_idx=3 set_tx=0 seq_len=0 key_len=0 bsd_del_key: key_idx=3 Using interface wlan0 with hwaddr 00:80:48:4f:2a:ee and ssid 'testAP' wlan0: RADIUS Authentication server 146.64.8.25:1812 RADIUS local address: 146.64.5.5:37935 bsd_set_ieee8021x: enabled=1 bsd_configure_wpa: enable WPA= 0x1 WPA: group state machine entering state GTK_INIT (VLAN-ID 0) GMK - hexdump(len=32): [REMOVED] GTK - hexdump(len=32): [REMOVED] WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0) bsd_set_key: alg=2 addr=0x0 key_idx=1 set_tx=1 seq_len=0 key_len=32 bsd_set_privacy: enabled=1 bsd_set_opt_ie: set WPA+RSN ie (len 28) wlan0: Setup of interface done. Discard routing message to if#180 (not for us 7) Discard routing message to if#0 (not for us 7) wlan0: STA 00:15:af:8e:3b:aa IEEE 802.11: associated STA included WPA IE in (Re)AssocReq New STA wlan0: STA 00:15:af:8e:3b:aa WPA: event 1 notification bsd_set_key: alg=0 addr=0x2845a308 key_idx=0 set_tx=1 seq_len=0 key_len=0 bsd_del_key: addr=00:15:af:8e:3b:aa wlan0: STA 00:15:af:8e:3b:aa IEEE 802.1X: start authentication EAP: Server state machine created IEEE 802.1X: 00:15:af:8e:3b:aa BE_AUTH entering state IDLE IEEE 802.1X: 00:15:af:8e:3b:aa CTRL_DIR entering state FORCE_BOTH wlan0: STA 00:15:af:8e:3b:aa WPA: start authentication WPA: 00:15:af:8e:3b:aa WPA_PTK entering state INITIALIZE bsd_set_key: alg=0 addr=0x2845a308 key_idx=0 set_tx=1 seq_len=0 key_len=0 bsd_del_key: addr=00:15:af:8e:3b:aa WPA: 00:15:af:8e:3b:aa WPA_PTK_GROUP entering state IDLE WPA: 00:15:af:8e:3b:aa WPA_PTK entering state AUTHENTICATION WPA: 00:15:af:8e:3b:aa WPA_PTK entering state AUTHENTICATION2 IEEE 802.1X: 00:15:af:8e:3b:aa AUTH_PAE entering state DISCONNECTED wlan0: STA 00:15:af:8e:3b:aa IEEE 802.1X: unauthorizing port IEEE 802.1X: 00:15:af:8e:3b:aa AUTH_PAE entering state RESTART EAP: EAP entering state INITIALIZE CTRL-EVENT-EAP-STARTED 00:15:af:8e:3b:aa EAP: EAP entering state SELECT_ACTION EAP: getDecision: no identity known yet -> CONTINUE EAP: EAP entering state PROPOSE_METHOD EAP: getNextMethod: vendor 0 type 1 CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=1 EAP: EAP entering state METHOD_REQUEST EAP: method not initialized EAP: EAP entering state SEND_REQUEST EAP: SEND_REQUEST - no eapReqData EAP: EAP entering state IDLE EAP: retransmit timeout 3 seconds (from dynamic back off; retransCount=0) IEEE 802.1X: 00:15:af:8e:3b:aa AUTH_PAE entering state CONNECTING IEEE 802.1X: 00:15:af:8e:3b:aa - (EAP) retransWhile --> 0 EAP: EAP entering state RETRANSMIT EAP: EAP entering state IDLE EAP: retransmit timeout 6 seconds (from dynamic back off; retransCount=1) IEEE 802.1X: 4 bytes from 00:15:af:8e:3b:aa IEEE 802.1X: version=1 type=1 length=0 wlan0: STA 00:15:af:8e:3b:aa IEEE 802.1X: received EAPOL-Start from STA wlan0: STA 00:15:af:8e:3b:aa WPA: event 5 notification WPA: 00:15:af:8e:3b:aa WPA_PTK entering state AUTHENTICATION2 IEEE 802.1X: 00:15:af:8e:3b:aa - (EAP) retransWhile --> 0 EAP: EAP entering state RETRANSMIT EAP: EAP entering state IDLE EAP: retransmit timeout 12 seconds (from dynamic back off; retransCount=2) wlan0: STA 00:15:af:8e:3b:aa IEEE 802.11: disassociated AP-STA-DISCONNECTED 00:15:af:8e:3b:aa wlan0: STA 00:15:af:8e:3b:aa WPA: event 2 notification bsd_set_key: alg=0 addr=0x2845a308 key_idx=0 set_tx=1 seq_len=0 key_len=0 bsd_del_key: addr=00:15:af:8e:3b:aa ioctl[SIOCS80211, op=20, val=0, arg_len=7]: No such file or directory WPA: 00:15:af:8e:3b:aa WPA_PTK entering state DISCONNECTED WPA: 00:15:af:8e:3b:aa WPA_PTK entering state INITIALIZE bsd_set_key: alg=0 addr=0x2845a308 key_idx=0 set_tx=1 seq_len=0 key_len=0 bsd_del_key: addr=00:15:af:8e:3b:aa ioctl[SIOCS80211, op=20, val=0, arg_len=7]: No such file or directory EAP: Server state machine removed wlan0: STA 00:15:af:8e:3b:aa IEEE 802.11: associated STA included WPA IE in (Re)AssocReq New STA wlan0: STA 00:15:af:8e:3b:aa WPA: event 1 notification bsd_set_key: alg=0 addr=0x2845a308 key_idx=0 set_tx=1 seq_len=0 key_len=0 bsd_del_key: addr=00:15:af:8e:3b:aa wlan0: STA 00:15:af:8e:3b:aa IEEE 802.1X: start authentication EAP: Server state machine created IEEE 802.1X: 00:15:af:8e:3b:aa BE_AUTH entering state IDLE IEEE 802.1X: 00:15:af:8e:3b:aa CTRL_DIR entering state FORCE_BOTH wlan0: STA 00:15:af:8e:3b:aa WPA: start authentication WPA: 00:15:af:8e:3b:aa WPA_PTK entering state INITIALIZE bsd_set_key: alg=0 addr=0x2845a308 key_idx=0 set_tx=1 seq_len=0 key_len=0 bsd_del_key: addr=00:15:af:8e:3b:aa WPA: 00:15:af:8e:3b:aa WPA_PTK_GROUP entering state IDLE WPA: 00:15:af:8e:3b:aa WPA_PTK entering state AUTHENTICATION WPA: 00:15:af:8e:3b:aa WPA_PTK entering state AUTHENTICATION2 IEEE 802.1X: 00:15:af:8e:3b:aa AUTH_PAE entering state DISCONNECTED wlan0: STA 00:15:af:8e:3b:aa IEEE 802.1X: unauthorizing port IEEE 802.1X: 00:15:af:8e:3b:aa AUTH_PAE entering state RESTART EAP: EAP entering state INITIALIZE CTRL-EVENT-EAP-STARTED 00:15:af:8e:3b:aa EAP: EAP entering state SELECT_ACTION EAP: getDecision: no identity known yet -> CONTINUE EAP: EAP entering state PROPOSE_METHOD EAP: getNextMethod: vendor 0 type 1 CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=1 EAP: EAP entering state METHOD_REQUEST EAP: method not initialized EAP: EAP entering state SEND_REQUEST EAP: SEND_REQUEST - no eapReqData EAP: EAP entering state IDLE EAP: retransmit timeout 3 seconds (from dynamic back off; retransCount=0) IEEE 802.1X: 00:15:af:8e:3b:aa AUTH_PAE entering state CONNECTING IEEE 802.1X: 4 bytes from 00:15:af:8e:3b:aa IEEE 802.1X: version=1 type=1 length=0 wlan0: STA 00:15:af:8e:3b:aa IEEE 802.1X: received EAPOL-Start from STA wlan0: STA 00:15:af:8e:3b:aa WPA: event 5 notification WPA: 00:15:af:8e:3b:aa WPA_PTK entering state AUTHENTICATION2 IEEE 802.1X: 00:15:af:8e:3b:aa - (EAP) retransWhile --> 0 EAP: EAP entering state RETRANSMIT EAP: EAP entering state IDLE EAP: retransmit timeout 6 seconds (from dynamic back off; retransCount=1) wlan0: STA 00:15:af:8e:3b:aa IEEE 802.11: disassociated AP-STA-DISCONNECTED 00:15:af:8e:3b:aa wlan0: STA 00:15:af:8e:3b:aa WPA: event 2 notification bsd_set_key: alg=0 addr=0x2845a308 key_idx=0 set_tx=1 seq_len=0 key_len=0 bsd_del_key: addr=00:15:af:8e:3b:aa ioctl[SIOCS80211, op=20, val=0, arg_len=7]: No such file or directory WPA: 00:15:af:8e:3b:aa WPA_PTK entering state DISCONNECTED WPA: 00:15:af:8e:3b:aa WPA_PTK entering state INITIALIZE bsd_set_key: alg=0 addr=0x2845a308 key_idx=0 set_tx=1 seq_len=0 key_len=0 bsd_del_key: addr=00:15:af:8e:3b:aa ioctl[SIOCS80211, op=20, val=0, arg_len=7]: No such file or directory EAP: Server state machine removed --Boundary-00=_FXuhPtxQ4SdKv90 Content-Type: text/plain; charset="UTF-8"; name="ifconfig.wlan0" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="ifconfig.wlan0" AP-vlan:~ # ifconfig wlan0 wlan0: flags=8843 metric 0 mtu 1500 ether 00:80:48:4f:2a:ee inet 146.64.5.5 netmask 0xffffff00 broadcast 146.64.5.255 inet6 fe80::280:48ff:fe4f:2aee%wlan0 prefixlen 64 scopeid 0x7 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: running ssid testAP channel 6 (2437 MHz 11g) bssid 00:80:48:4f:2a:ee regdomain NONE country ZA ecm authmode WPA privacy MIXED deftxkey 2 TKIP 2:128-bit txpower 30 scanvalid 60 protmode CTS wme burst dtimperiod 1 -dfs --Boundary-00=_FXuhPtxQ4SdKv90-- From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 12 15:52:24 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 28E891065724 for ; Thu, 12 Apr 2012 15:52:24 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id EA3DD8FC08 for ; Thu, 12 Apr 2012 15:52:23 +0000 (UTC) Received: by pbcwz17 with SMTP id wz17so2758409pbc.13 for ; Thu, 12 Apr 2012 08:52:23 -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 :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=5hh+18wQRcIoLhmn147YvbTvQflNB57NpvcVarJC8Is=; b=fV59Vu4VZI1XKS/QXN0gJ0v0+FQ1CzWD2lr1TzLR1L+IY8eYIIF7cqwrEVvSwH1xjq ect4tTbrQUcwW+cVJxoqbPkiKo6CCMQaLjY0DbzV3dCM0BdmogqwXseqPqh6QOQNfqtY eYPA3HxABx9FcHl+r74KrUdcZVS7IeRFDqOqKWeTrpj++S1u6d9JtirHez/1YtXcINbI rq7mKqAj6jZfAoY9otnVi6/+ouURthza1CX0yd/uI3wYROoyjnJiybYvtq/SYirwJQKA jOCyUCqExxwkzpW/+xnYdRAAU99L6CebDx/kb5jB6+vKJZ4uomrfq0hqsWQ+drBXqTAa nj9A== MIME-Version: 1.0 Received: by 10.68.195.162 with SMTP id if2mr3649658pbc.94.1334245943378; Thu, 12 Apr 2012 08:52:23 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.143.9.11 with HTTP; Thu, 12 Apr 2012 08:52:23 -0700 (PDT) In-Reply-To: References: Date: Thu, 12 Apr 2012 08:52:23 -0700 X-Google-Sender-Auth: oPTPWOLDEeXHfXSpzn-kFrelt-M Message-ID: From: Adrian Chadd To: Warren Block Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: ath(4) hardware support list X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 15:52:24 -0000 On 12 April 2012 06:07, Warren Block wrote: > I'd like to add a list of Atheros supported card part numbers to ath(4). > Why? =A0Because it's really hard for a user to tell whether a given card = is > supported or not before buying. =A0Testing before buying is often impossi= ble. > > There are two forms of part numbers, for example, AR5BXB63 and AR5008. > > Is there a practical way to generate this list other than testing? I've started one. It's in the wiki. http://wiki.freebsd.org/dev/ath(4) Adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 12 15:56:10 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 30AB6106566B for ; Thu, 12 Apr 2012 15:56:10 +0000 (UTC) (envelope-from venture37@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 9FDD58FC17 for ; Thu, 12 Apr 2012 15:56:09 +0000 (UTC) Received: by bkcjc3 with SMTP id jc3so2240916bkc.13 for ; Thu, 12 Apr 2012 08:56:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=uCLDSEcejid3D7N3ID4CucUH6ofIj8cD2qG+T5oWS74=; b=vW937QIRUB4W90784f+xtQDnTs2/AYnW1O4e3y9Ksql94V4nnavCG2qg6Z6+1UfDHl tR18G7ug6wj5DTjbVRjERENj1qn9b+/DNp7ZyOL85e4otWgHBHJjVc2n+lVgjENVUeLI DycmKL8ne32HVUXFemV6upG+xAzwARoZ94yxR3fq3+zFlRDyNcm9uuuvEvm/n2eReBr4 jQHoZB96/08kaOkSI1hW2Uz2YNCqmz5P8Nm5r0MXjfKwrgaWgTjYpMJpdppwRo4fiYfT jdbBd4SL8yRnxK0DK1xeJ9OgkHFxgTkG9ATBl7iruotJG0amER+sh4WQe3HCNQ+pCobo MrBQ== Received: by 10.205.136.20 with SMTP id ii20mr867971bkc.97.1334246168617; Thu, 12 Apr 2012 08:56:08 -0700 (PDT) Received: from Sevans-MacBook-Pro.local (cpc2-brig17-2-0-cust527.3-3.cable.virginmedia.com. [81.101.198.16]) by mx.google.com with ESMTPS id cy11sm11780807bkb.7.2012.04.12.08.56.07 (version=SSLv3 cipher=OTHER); Thu, 12 Apr 2012 08:56:07 -0700 (PDT) Message-ID: <4F86FB15.5080500@gmail.com> Date: Thu, 12 Apr 2012 16:56:05 +0100 From: Sevan / Venture37 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: freebsd-wireless@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: ath(4) hardware support list X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 15:56:10 -0000 On 12/04/2012 16:52, Adrian Chadd wrote: > On 12 April 2012 06:07, Warren Block wrote: >> I'd like to add a list of Atheros supported card part numbers to ath(4). >> Why? Because it's really hard for a user to tell whether a given card is >> supported or not before buying. Testing before buying is often impossible. >> >> There are two forms of part numbers, for example, AR5BXB63 and AR5008. >> >> Is there a practical way to generate this list other than testing? > > I've started one. It's in the wiki. > > http://wiki.freebsd.org/dev/ath(4) Are user submitted patches to usbdevs accepted or do changes need to come from upstream? Sevan From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 12 15:58:03 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 52D141065672 for ; Thu, 12 Apr 2012 15:58:02 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by mx1.freebsd.org (Postfix) with ESMTP id 252C38FC19 for ; Thu, 12 Apr 2012 15:58:02 +0000 (UTC) Received: by dadz14 with SMTP id z14so8790266dad.17 for ; Thu, 12 Apr 2012 08:58: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 :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=zl6ubeSA5doY7wq8JcDtBhuiNAYvhEi4yyvHehFmDO4=; b=B5ksEjrMxMMvx/wDgXveZeglth56iLtGaLqt7G4x3c/703YMjC7psEB918o/mawb3e a9qvp8g6xDahE2hKNSl52L7vOAIm/11DMDu6Wyylbd2LWpHdHOhgLAjIeHchpUObMOyp C97nknLNOI4/a1zfqdggEZ25cdG9/HVnvzidnkOY00R3D5UsYiK6/rXPmyavfT9/r4X4 CDAl/vJd3NfZF6c9kMflEfQDhWGdcXnM2m51rB5vnr/EOqUrMMnkOUo5VjNHohYdnGCZ yla0juKW35KWSk+KCsi5TYzA54ixf57ZkkyGidBVAo/aO4XkZGTFKYTr6uK1L9QPJGsM pdiQ== MIME-Version: 1.0 Received: by 10.68.195.162 with SMTP id if2mr3683100pbc.94.1334246281632; Thu, 12 Apr 2012 08:58:01 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.143.9.11 with HTTP; Thu, 12 Apr 2012 08:58:01 -0700 (PDT) In-Reply-To: <4F86FB15.5080500@gmail.com> References: <4F86FB15.5080500@gmail.com> Date: Thu, 12 Apr 2012 08:58:01 -0700 X-Google-Sender-Auth: TB9eGLUEL-5e622hfde18Oyn2ac Message-ID: From: Adrian Chadd To: "Sevan / Venture37" Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: ath(4) hardware support list X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 15:58:03 -0000 .. upstream? What upstream? Adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 12 17:30:00 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 29A5C1065670 for ; Thu, 12 Apr 2012 17:30:00 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 7D7D38FC12 for ; Thu, 12 Apr 2012 17:29:59 +0000 (UTC) Received: by wgbds12 with SMTP id ds12so2243653wgb.31 for ; Thu, 12 Apr 2012 10:29:58 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id :x-gm-message-state; bh=0ycOcC1o9NqKthqHB0302BvUoebldennXa6n8CjL7D4=; b=Gj+Hz18bLNh60S+zDUvWuspnGrxC8TZFq2HvGmrfDs1VFM/A25DMnU1zPu8KvaV8+n emyTOVGXkWdqT7Q67bd9eAzlV97K4yC7PKj8YNwP7qxoPunbBauzJZFv2VPY313jgsIm C/e6g1sqShy54ssr9TcBSImxHQtIeS77zkNJTegFWw0oAA5fcs592x1Z9tkM3mLJ84Mc gEHjBmAeSDIsWzFGvaxlU5c+SzobiwHXRXRKR7IywLgdPe5WjEPBzzwW/4zp2ZPkwCd4 nGSDpQloH5O0lq7bipe7SpTvXwV6v3TEnyR9FDqy+Pc/vmdpysHOVCYhwkH5FLxqOQIb TByA== Received: by 10.180.107.101 with SMTP id hb5mr7921338wib.7.1334251798392; Thu, 12 Apr 2012 10:29:58 -0700 (PDT) Received: from amy.lab.techwires.net (dslb-088-067-211-255.pools.arcor-ip.net. [88.67.211.255]) by mx.google.com with ESMTPS id fn2sm23682123wib.0.2012.04.12.10.29.55 (version=SSLv3 cipher=OTHER); Thu, 12 Apr 2012 10:29:56 -0700 (PDT) Sender: Bernhard Schmidt From: Bernhard Schmidt To: Adrian Chadd Date: Thu, 12 Apr 2012 19:30:16 +0200 User-Agent: KMail/1.13.7 (FreeBSD/9.0-STABLE; KDE/4.7.4; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201204121930.17011.bschmidt@freebsd.org> X-Gm-Message-State: ALoCoQnKF/E6QaYXX6tUulZQ2WLC/xNVTTDijlHgfM9jPW/EKl4gpBTFQDjBVzpXtsXs8CqtC/+E Cc: freebsd-wireless@freebsd.org Subject: Re: [RFC] net80211/ath/iwn: move ni_tx_ampdu to be per-tid, rather than per WME AC X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 17:30:00 -0000 On Wednesday 11 April 2012 04:53:27 Adrian Chadd wrote: > Hi, > > This patch changes ni_tx_ampdu to be per-TID rather than per-AC. > > It includes: > > * changes to net80211 to use the QoS frame TID, rather than > calculating it from the AC (which may have been calculated from the > TID in the first place); > * the one changes to ath(4) to use it; > * a couple of changes to iwn which was using ni_tx_ampdu state. > > I'd like to commit this to -HEAD. Basically fine, but a few nits code be fixed, see below. > Index: sys/net80211/ieee80211_ht.c > =================================================================== > --- sys/net80211/ieee80211_ht.c (revision 234108) > +++ sys/net80211/ieee80211_ht.c (working copy) > @@ -1198,9 +1199,10 @@ > ni->ni_htopmode = 0; /* XXX need protection state */ > ni->ni_htstbc = 0; /* XXX need info */ > > - for (ac = 0; ac < WME_NUM_AC; ac++) { > - tap = &ni->ni_tx_ampdu[ac]; > - tap->txa_ac = ac; > + for (tid = 0; tid < WME_NUM_TID; tid++) { > + tap = &ni->ni_tx_ampdu[tid]; > + tap->txa_ac = TID_TO_WME_AC(tid); > + tap->txa_tid = tid; Do we really need both, txa_ac and txa_tid? > @@ -2099,7 +2101,7 @@ > tap->txa_flags &= ~IEEE80211_AGGR_NAK; > > dialogtoken = (tokens+1) % 63; /* XXX */ > - tid = WME_AC_TO_TID(tap->txa_ac); > + tid = tap->txa_tid; > tap->txa_start = ni->ni_txseqs[tid]; Better use txa_tid directly, no? > @@ -2292,7 +2294,7 @@ > IEEE80211_ADDR_COPY(bar->i_ra, ni->ni_macaddr); > IEEE80211_ADDR_COPY(bar->i_ta, vap->iv_myaddr); > > - tid = WME_AC_TO_TID(tap->txa_ac); > + tid = tap->txa_tid; same here > Index: sys/net80211/ieee80211_ht.h > =================================================================== > --- sys/net80211/ieee80211_ht.h (revision 234108) > +++ sys/net80211/ieee80211_ht.h (working copy) > @@ -45,6 +45,7 @@ > #define IEEE80211_AGGR_NAK 0x0010 /* peer NAK'd ADDBA request */ > #define IEEE80211_AGGR_BARPEND 0x0020 /* BAR response pending */ > uint8_t txa_ac; > + uint8_t txa_tid; Again, do we need both? > uint8_t txa_token; /* dialog token */ > int txa_lastsample; /* ticks @ last traffic sample */ > int txa_pkts; /* packets over last sample interval */ > Index: sys/net80211/ieee80211_output.c > =================================================================== > --- sys/net80211/ieee80211_output.c (revision 234108) > +++ sys/net80211/ieee80211_output.c (working copy) > @@ -324,7 +324,8 @@ > (vap->iv_flags_ht & IEEE80211_FHT_AMPDU_TX) && > (m->m_flags & M_EAPOL) == 0) { > const int ac = M_WME_GETAC(m); > - struct ieee80211_tx_ampdu *tap = &ni->ni_tx_ampdu[ac]; > + const int tid = WME_AC_TO_TID(ac); > + struct ieee80211_tx_ampdu *tap = &ni->ni_tx_ampdu[tid]; Use WME_AC_TO_TID() directly? > ieee80211_txampdu_count_packet(tap); > if (IEEE80211_AMPDU_RUNNING(tap)) { > Index: sys/net80211/ieee80211_superg.c > =================================================================== > --- sys/net80211/ieee80211_superg.c (revision 234108) > +++ sys/net80211/ieee80211_superg.c (working copy) > @@ -562,9 +562,11 @@ > IEEE80211_LOCK(ic); > head = sq->head; > while ((m = sq->head) != NULL && M_AGE_GET(m) < quanta) { > + int ac = M_WME_GETAC(m); > + int tid = WME_AC_TO_TID(ac); No need for those 2 here, use em directly below. > /* clear tap ref to frame */ > ni = (struct ieee80211_node *) m->m_pkthdr.rcvif; > - tap = &ni->ni_tx_ampdu[M_WME_GETAC(m)]; > + tap = &ni->ni_tx_ampdu[tid]; > KASSERT(tap->txa_private == m, ("staging queue empty")); > tap->txa_private = NULL; > > @@ -661,6 +663,7 @@ > struct ieee80211_tx_ampdu *tap; > struct mbuf *mstaged; > uint32_t txtime, limit; > + int tid = WME_AC_TO_TID(pri); > > /* > * Check if the supplied frame can be aggregated. > @@ -670,7 +673,7 @@ > * be aggregated with other types of frames when encryption is on? > */ > IEEE80211_LOCK(ic); > - tap = &ni->ni_tx_ampdu[pri]; > + tap = &ni->ni_tx_ampdu[tid]; Use WME_AC_TO_TID() directly here. Any reason why ac is called pri here? > mstaged = tap->txa_private; /* NB: we reuse AMPDU state */ > ieee80211_txampdu_count_packet(tap); > > @@ -783,12 +786,13 @@ > struct ieee80211_superg *sg = ic->ic_superg; > struct ieee80211_tx_ampdu *tap; > struct mbuf *m, *head; > - int ac; > + int tid; > > IEEE80211_LOCK(ic); > head = NULL; > - for (ac = 0; ac < WME_NUM_AC; ac++) { > - tap = &ni->ni_tx_ampdu[ac]; > + for (tid = 0; tid < WME_NUM_TID; tid++) { > + int ac = TID_TO_WME_AC(tid); > + tap = &ni->ni_tx_ampdu[tid]; I'd prefer to use TID_TO_WME_AC() directly > Index: sys/net80211/ieee80211_ddb.c > =================================================================== > --- sys/net80211/ieee80211_ddb.c (revision 234108) > +++ sys/net80211/ieee80211_ddb.c (working copy) > @@ -293,7 +293,7 @@ > ni->ni_htopmode, ni->ni_htstbc, ni->ni_chw); > > /* XXX ampdu state */ > - for (i = 0; i < WME_NUM_AC; i++) > + for (i = 0; i < WME_NUM_TID; i++) > if (ni->ni_tx_ampdu[i].txa_flags & IEEE80211_AGGR_SETUP) > _db_show_txampdu("\t", i, &ni->ni_tx_ampdu[i]); > for (i = 0; i < WME_NUM_TID; i++) Might want to merge those 2 loops > Index: sys/dev/iwn/if_iwn.c > =================================================================== > --- sys/dev/iwn/if_iwn.c (revision 234108) > +++ sys/dev/iwn/if_iwn.c (working copy) > @@ -3309,9 +3309,12 @@ > } > ac = M_WME_GETAC(m); > > + /* > + * XXX what about the non-QoS TID? > + */ I don't know what that comment is supposed to mean, but it is definitely wrong here. What the code below does is basically updating the seqno, which is already done for !QoS frames in net80211. > if (IEEE80211_QOS_HAS_SEQ(wh) && > - IEEE80211_AMPDU_RUNNING(&ni->ni_tx_ampdu[ac])) { > - struct ieee80211_tx_ampdu *tap = &ni->ni_tx_ampdu[ac]; > + IEEE80211_AMPDU_RUNNING(&ni->ni_tx_ampdu[tid])) { > + struct ieee80211_tx_ampdu *tap = &ni->ni_tx_ampdu[tid]; > > ring = &sc->txq[*(int *)tap->txa_private]; > *(uint16_t *)wh->i_seq = -- Bernhard From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 12 19:25:18 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AA849106564A; Thu, 12 Apr 2012 19:25:18 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 64A488FC0A; Thu, 12 Apr 2012 19:25:18 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id q3CJPChI008911; Thu, 12 Apr 2012 13:25:12 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id q3CJPCiq008908; Thu, 12 Apr 2012 13:25:12 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Thu, 12 Apr 2012 13:25:12 -0600 (MDT) From: Warren Block To: Adrian Chadd In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-902635197-1192756551-1334258712=:8635" X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Thu, 12 Apr 2012 13:25:12 -0600 (MDT) Cc: freebsd-wireless@freebsd.org Subject: Re: ath(4) hardware support list X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 19:25:18 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---902635197-1192756551-1334258712=:8635 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8BIT On Thu, 12 Apr 2012, Adrian Chadd wrote: > On 12 April 2012 06:07, Warren Block wrote: >> I'd like to add a list of Atheros supported card part numbers to ath(4). >> Why?  Because it's really hard for a user to tell whether a given card is >> supported or not before buying.  Testing before buying is often impossible. >> >> There are two forms of part numbers, for example, AR5BXB63 and AR5008. >> >> Is there a practical way to generate this list other than testing? > > I've started one. It's in the wiki. > > http://wiki.freebsd.org/dev/ath(4) Excellent! Is it feasible to add card model numbers of the AR5BXB or AR5BHB form? Those are useful when looking for a replacement card. Another column for branded model numbers ("Linksys XXX123") would be good also. Is there another table for 802.11b/g-only cards? ---902635197-1192756551-1334258712=:8635-- From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 12 19:42:19 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A7141106566B; Thu, 12 Apr 2012 19:42:19 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 059AA8FC12; Thu, 12 Apr 2012 19:42:18 +0000 (UTC) Received: by wgbds12 with SMTP id ds12so2355648wgb.31 for ; Thu, 12 Apr 2012 12:42:18 -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=xidKrX3w+0WdCJ6KmcJ45zhBiP043zhPIwlClA7rPsg=; b=dVWMq/tYiwayHK4UfHRmREkEllQV6RrAdWNxNufQgL3Z8dyhW9JSpyBlkuxAvi4Lrj X46y6gk/H7YQq6vlxLftUoly0A00UzgUZS30lj73xkRuVkEuyAcI4I/ncCZRm0YaTi02 O1X0m++CMQSxppwZ5SNnnhofJSef1sKPwB91RnOPiCaTM7mRR4CSJcAQYRH99Wbyla51 APxXsn2wvOF6sQQZ7FOQ95b2mh++gwbb6C78qS2B+wLloK0z+2I8SEr+tnmTaA8FAkqo oIWRGNOCzzar5VcxyKrey4rGfe+fsMWi0/QNezEE4mMvZO5cBE0cOWW/qQ4gzGmxEOQa wgMA== MIME-Version: 1.0 Received: by 10.180.105.194 with SMTP id go2mr8631173wib.22.1334259737292; Thu, 12 Apr 2012 12:42:17 -0700 (PDT) Received: by 10.223.54.207 with HTTP; Thu, 12 Apr 2012 12:42:17 -0700 (PDT) In-Reply-To: References: Date: Thu, 12 Apr 2012 12:42:17 -0700 Message-ID: From: Kevin Oberman To: Warren Block Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: ath(4) hardware support list X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 19:42:19 -0000 On Thu, Apr 12, 2012 at 12:25 PM, Warren Block wrote: > On Thu, 12 Apr 2012, Adrian Chadd wrote: > >> On 12 April 2012 06:07, Warren Block wrote: >>> >>> I'd like to add a list of Atheros supported card part numbers to ath(4)= . >>> Why? =A0Because it's really hard for a user to tell whether a given car= d is >>> supported or not before buying. =A0Testing before buying is often >>> impossible. >>> >>> There are two forms of part numbers, for example, AR5BXB63 and AR5008. >>> >>> Is there a practical way to generate this list other than testing? >> >> >> I've started one. It's in the wiki. >> >> http://wiki.freebsd.org/dev/ath(4) > > > Excellent! =A0Is it feasible to add card model numbers of the AR5BXB or A= R5BHB > form? =A0Those are useful when looking for a replacement card. > > Another column for branded model numbers ("Linksys XXX123") would be good > also. > > Is there another table for 802.11b/g-only cards? I believe that b/g only is listed in the "Description" column and, by the N/A, the lack of 'n' is in the "802.11n Spatial Streams" column. It's a pretty short list, but it includes my old AR5212 a/b/g card --=20 R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 12 21:16:49 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EE74E106566B; Thu, 12 Apr 2012 21:16:49 +0000 (UTC) (envelope-from uzimac@da3m0n8t3r.com) Received: from z.umatar.com (z.umatar.com [66.135.39.87]) by mx1.freebsd.org (Postfix) with ESMTP id B93B38FC0A; Thu, 12 Apr 2012 21:16:49 +0000 (UTC) Received: from z.umatar.com (localhost [127.0.0.1]) by z.umatar.com (8.14.5/8.14.3) with ESMTP id q3CKs2er057397; Thu, 12 Apr 2012 13:54:02 -0700 (PDT) (envelope-from uzimac@da3m0n8t3r.com) Received: (from uzimac@localhost) by z.umatar.com (8.14.5/8.14.3/Submit) id q3CKs2IA057396; Thu, 12 Apr 2012 13:54:02 -0700 (PDT) (envelope-from uzimac@da3m0n8t3r.com) X-Authentication-Warning: z.umatar.com: uzimac set sender to uzimac@da3m0n8t3r.com using -f From: "Waitman Gobble" To: Warren Block Message-Id: <1334264041.57391@da3m0n8t3r.com> X-Originating-IP: 70.90.171.37 X-Mailer: Usermin 1.500 In-Reply-To: Date: Thu, 12 Apr 2012 13:54:02 -0700 (PDT) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="bound1334264042" Cc: freebsd-wireless@freebsd.org Subject: Re: ath(4) hardware support list X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 21:16:50 -0000 This is a multi-part message in MIME format. --bound1334264042 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Warren Block wrote .. > On Thu, 12 Apr 2012, Adrian Chadd wrote: > > > On 12 April 2012 06:07, Warren Block wrote: > >> I'd like to add a list of Atheros supported card part numbers to ath(4). > >> Why? =A0Because it's really hard for a user to tell whether a given card is > >> supported or not before buying. =A0Testing before buying is often impossible. > >> > >> There are two forms of part numbers, for example, AR5BXB63 and AR5008. > >> > >> Is there a practical way to generate this list other than testing? > > > > I've started one. It's in the wiki. > > > > http://wiki.freebsd.org/dev/ath(4) > > Excellent! Is it feasible to add card model numbers of the AR5BXB or > AR5BHB form? Those are useful when looking for a replacement card. > > Another column for branded model numbers ("Linksys XXX123") would be > good also. > > Is there another table for 802.11b/g-only cards? I've bought every Atheros pci-e model i could find on ebay, so far they have all worked. So maybe not so much of a concern about the luck of getting a card which doesn't work? There are some 'newer-generation'(?) cards listed on qualcomm site but i haven't yet seen these available. -- Waitman Gobble San Jose California USA --bound1334264042-- From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 12 21:33:44 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 227BF106564A for ; Thu, 12 Apr 2012 21:33:44 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by mx1.freebsd.org (Postfix) with ESMTP id E8C7D8FC08 for ; Thu, 12 Apr 2012 21:33:43 +0000 (UTC) Received: by dadz14 with SMTP id z14so9862006dad.17 for ; Thu, 12 Apr 2012 14:33:43 -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 :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=PGDleEQXvuqBiwSo6lCSwlTdIOWpv3WpdCZurvgfePs=; b=ampHtml0lv8cwCSljKvURiVRCLv2Dw6fVOHKveCd2En47lT+A2eJ3/+F5P1AArGgmD ep4YJQ+7uqkg3+seyWXU5G31RgOTfWO2+HPzBWYMrxyjAcuO4C+md8eh6o/8PAeirsTJ 1E3YDWiulCFliOm7GZQiaY4YPt4BvVaayhSp0QW4OM106s6oLoIELK7FpKffnrdfAA5k ERnp7VC8W2SQk3DUFUaVBpaNw2pWFOS2Zfr8YVkTmj/HXr6alf2aL5lwL6WgFQG4PgAW ZsQGdHSz4yMAWGs/pq4biz8iBvotCyl601nXXOh75Md9OkzpmqeSYd7bAaG19bZYGDvf ewjQ== MIME-Version: 1.0 Received: by 10.68.195.162 with SMTP id if2mr267554pbc.94.1334266423461; Thu, 12 Apr 2012 14:33:43 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.143.9.11 with HTTP; Thu, 12 Apr 2012 14:33:43 -0700 (PDT) In-Reply-To: <1334264041.57391@da3m0n8t3r.com> References: <1334264041.57391@da3m0n8t3r.com> Date: Thu, 12 Apr 2012 14:33:43 -0700 X-Google-Sender-Auth: zaqKdB58eUlikz0yNMh4ezVtlxk Message-ID: From: Adrian Chadd To: Waitman Gobble Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: ath(4) hardware support list X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 21:33:44 -0000 On 12 April 2012 13:54, Waitman Gobble wrote: >> Another column for branded model numbers ("Linksys XXX123") would be >> good also. >> >> Is there another table for 802.11b/g-only cards? > > > I've bought every Atheros pci-e model i could find on ebay, so far they have all worked. > So maybe not so much of a concern about the luck of getting a card which doesn't work? > > There are some 'newer-generation'(?) cards listed on qualcomm site but i haven't yet seen these available. Yup. AR9300 and later aren't currently supported. Adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 12 21:35:17 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 78C57106564A for ; Thu, 12 Apr 2012 21:35:17 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by mx1.freebsd.org (Postfix) with ESMTP id 486298FC18 for ; Thu, 12 Apr 2012 21:35:17 +0000 (UTC) Received: by dadz14 with SMTP id z14so9866693dad.17 for ; Thu, 12 Apr 2012 14:35:17 -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 :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=ApgJk7yKVrHHYGenSfvjUWILq2d+uLkIldz9Z7ahLC0=; b=dCwPE3QMmmXz3GEuDgGSC4bWep4TuSRe2fN7OTdob58u3asv/v6N7WXVFB7+3LVBrN QFOld8g4sPxXSJjPc9nBfJ1KxRdfFiuArfR6AzRbwypzKK+cdRz85qDygi/YphVFYHzD yab9Je5XcKACxqkx3uRIZg01tRfjveyXXv0geEGzPFAocdO/bmu40RzhdETRvm434VBk S1zWF3egqNjpVb9uVN7QOQGv0ZYanmxPNMuBS3ZaMKiQMmLoIYhygjAlHnfafHLGZx+W SSHnaNaN56CzYe8Eo4uj1AFzqWqTnWd1rdN+CPxyzq1EEhz+wWzGg3LyFAdJbFe9kPWx c3uQ== MIME-Version: 1.0 Received: by 10.68.197.41 with SMTP id ir9mr299906pbc.83.1334266516944; Thu, 12 Apr 2012 14:35:16 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.143.9.11 with HTTP; Thu, 12 Apr 2012 14:35:16 -0700 (PDT) In-Reply-To: References: Date: Thu, 12 Apr 2012 14:35:16 -0700 X-Google-Sender-Auth: vWd9ZXH_-K6F6Ow0YqTKeZqVEdQ Message-ID: From: Adrian Chadd To: Kevin Oberman Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: ath(4) hardware support list X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2012 21:35:17 -0000 On 12 April 2012 12:42, Kevin Oberman wrote: >> Another column for branded model numbers ("Linksys XXX123") would be good >> also. >> >> Is there another table for 802.11b/g-only cards? > > I believe that b/g only is listed in the "Description" column and, by > the N/A, the lack of 'n' is in the "802.11n Spatial Streams" column. > It's a pretty short list, but it includes my old AR5212 a/b/g card If someone wants to start populating it with NICs that _they've tested_, then I'm happy to accept submissions. I'll add a "tested by" field with your name/email address so I have a record of who has tested what. I have a _big_ bag of assorted atheros NICs which I haven't yet tested and documented. I'm quite sure they work, but I won't add them to the list until it does work. :-) adrian