From owner-freebsd-wireless@FreeBSD.ORG Sat Nov 26 06:28:11 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0DACC1065670 for ; Sat, 26 Nov 2011 06:28:11 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id BA5F18FC12 for ; Sat, 26 Nov 2011 06:28:10 +0000 (UTC) Received: by vbbfa15 with SMTP id fa15so5220988vbb.13 for ; Fri, 25 Nov 2011 22:28:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=FEdwQi/RX0H47HLlsd9dFmL6QiDIUxCgjCjubU874xA=; b=IRHsQbIG6A3Et9BZUVbSB/mU8usSp3eKKvkMrYDduuBdt8+DIqdh0zYQRTq8SuUX6T uj9aXZNfTpHUzujhYoOmHdinbQKGSr5H3cDdp+BCtujcZdFc4BsdxjtR9yCahVqrs8kA tbDRzWTOU3OFSaYZ08sA74TNCmE0dTY9S0IKQ= MIME-Version: 1.0 Received: by 10.52.33.69 with SMTP id p5mr35624353vdi.78.1322288889829; Fri, 25 Nov 2011 22:28:09 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.186.74 with HTTP; Fri, 25 Nov 2011 22:28:09 -0800 (PST) In-Reply-To: <4ECFFB3C.16808.D76FB2F@andres.beek.mail.ee> References: <4ECFFB3C.16808.D76FB2F@andres.beek.mail.ee> Date: Sat, 26 Nov 2011 14:28:09 +0800 X-Google-Sender-Auth: hn5IaErA86Oqi6XxpPE5IKCIvmc Message-ID: From: Adrian Chadd To: Andres Beek Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: Uanble to enable 802.11g chanels above 11 despite of the REGDOMAIN set X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Nov 2011 06:28:11 -0000 Just for you (and others) reference, just because you're overriding the regulatory domain with a specific value doesn't mean the NIC has all the calibration data you need for operation on those channels. For example, just because you can configure a NIC to be in the japan country code, doesn't instantly give you access to the two 4.9ghz channels. :-) There's more involved then just overriding the regulatory domain. Hence, if it's an AR5416 or later, we can easily inspect the EEPROM calibration/channel edge values and see what the NIC is configured for. It's possible your NIC has channel edges which exclude > channel 11. At which point you won't be able to use those frequencies without (further) breaking all kinds of potential legal issues. Thanks, Adrian