Return-path: Received: from mail-iy0-f174.google.com ([209.85.210.174]:37587 "EHLO mail-iy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753089Ab2CHTvY convert rfc822-to-8bit (ORCPT ); Thu, 8 Mar 2012 14:51:24 -0500 Received: by iagz16 with SMTP id z16so1121888iag.19 for ; Thu, 08 Mar 2012 11:51:23 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <4B96CD77D9161244899852B5F20DB5B70125BC94@nasanexd02d.na.qualcomm.com> References: <20120307194001.GA2506@ubuntu-macmini> <20120308174101.GB28133@ubuntu-macmini> <4B96CD77D9161244899852B5F20DB5B70125BB72@nasanexd02d.na.qualcomm.com> <4B96CD77D9161244899852B5F20DB5B70125BC94@nasanexd02d.na.qualcomm.com> From: "Luis R. Rodriguez" Date: Thu, 8 Mar 2012 11:51:03 -0800 Message-ID: (sfid-20120308_205128_191502_8BA26166) Subject: Re: Problems with regulatory domain support and BCM43224 To: "Quan, David" Cc: Seth Forshee , "Green, Michael" , "linux-wireless@vger.kernel.org" , Johannes Berg Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Thu, Mar 8, 2012 at 11:45 AM, Quan, David wrote: > I think there is to it more than SW. > Where ever you get this card, is the card tested and regulatory approved for those countries, DFS or not? Seth, what driver are you using? I know you are using a BCM43224 card. > It is possible that this card is only regulatory tested for non DFS channels, but now you enable them for passive. That's a good point. > This means that yes, you are save and not violate DFS rules because you are in passive mode. However, you are in complete violation if the STA finds an AP on that DFS channel and then connects and transmits as this STA is not allow to transmit on that channel since it is not approved. If the driver being used is a supported vendor driver then I'll punt this to the vendor (Broadcom). If this is the reversed engineered driver (b43) that Broadcom to this day seems to blindly ignore even for regulatory, then I'm happy to recommend based on your input to leave the regulatory domain as-is given that we cannot guarantee what the vendor meant as they have not done any work on releasing either documentation or code to help with their regulatory situation. Luis