From owner-freebsd-wireless@FreeBSD.ORG Mon Dec 22 02:44:05 2014 Return-Path: Delivered-To: wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 87A0FC4F for ; Mon, 22 Dec 2014 02:44:05 +0000 (UTC) Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com [IPv6:2a00:1450:400c:c05::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 184B039D0 for ; Mon, 22 Dec 2014 02:44:05 +0000 (UTC) Received: by mail-wi0-f179.google.com with SMTP id ex7so6701680wid.0 for ; Sun, 21 Dec 2014 18:44:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=bHmYbOUPd0m9Ly2D3RDPwMYbYfdx0jWYOdsg+0AelIw=; b=hRxeOCG5TEk7wGoc1f0b69I3LSiAzveUXFRsMUPMadYmIKclKxtJxOv2BeAJFJf+Xs RfueJLR2tAqWRcPnJnI33WwZgNBsCNkvH6+Cgms9oAAWHdhe4FonEVKEFOB3R3M4kcEN x5Yd8cgJmAhSpKBhRoutckK+kMvXtMwFhMVHmmTCLwrG0HcHN8o6IZwenb8tR38IwS2r KvnsiVOjoZpH455f4bQ4nsGiim3s9ww+LuGDEkmjNnHAsPg6xfhLGFOSstiKYBNaNnRC EyNQSlSVQXzsk+VXgvwBud6WfnsSINZzyeJ9tqIkHpWCsjfKyicdSQpJr/0V2hrjxGeA meKA== MIME-Version: 1.0 X-Received: by 10.180.80.133 with SMTP id r5mr26601131wix.20.1419216243486; Sun, 21 Dec 2014 18:44:03 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.106.195 with HTTP; Sun, 21 Dec 2014 18:44:03 -0800 (PST) In-Reply-To: References: <1156584761.958533.1418932395342.JavaMail.yahoo@jws10611.mail.bf1.yahoo.com> Date: Sun, 21 Dec 2014 18:44:03 -0800 X-Google-Sender-Auth: SmnGDlC5pELoS4P9FaBnPMcsWaA Message-ID: Subject: Re: Atheros AR9565 detected, not working From: Adrian Chadd To: Anthony Jenkins Content-Type: text/plain; charset=UTF-8 Cc: "wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 22 Dec 2014 02:44:05 -0000 Oh, and ath_hal_enable_rfkill() maps to setting the capability bit: #define ath_hal_enable_rfkill(_ah, _v) \ ath_hal_setcapability(_ah, HAL_CAP_RFSILENT, 1, _v, AH_NULL) .. so, the AR9300 HAL code is enabling RFKILL in the HAL and then the call to ar9300_enable_rf_kill() is unconditionally turning it on. We likely can't do that for everyone. So, I wonder why this is required for you! -adrian