From mboxrd@z Thu Jan  1 00:00:00 1970
From: Peter Stuge <peter@stuge.se>
Date: Fri, 15 Apr 2011 16:53:58 +0200
Subject: [ath9k-devel] Ath9k: changing regulatory domain
In-Reply-To: <BANLkTimq0+6YnR_G-Zr7AsP7xNUvGb==AA@mail.gmail.com>
References: <BANLkTinUJ+wV+FicqpgrKxr0bWeB5WniOw@mail.gmail.com>
	<20110412183140.GF3757@tux> <20110412184226.22356.qmail@stuge.se>
	<BANLkTingzCCPgpeE4eSzULgftEvk+O-6KA@mail.gmail.com>
	<BANLkTimq0+6YnR_G-Zr7AsP7xNUvGb==AA@mail.gmail.com>
Message-ID: <20110415145358.21987.qmail@stuge.se>
List-Id: <ath9k-devel.lists.ath9k.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: ath9k-devel@lists.ath9k.org

Adrien Decostre wrote:
> Would it be more acceptable by regulatory agencies to specify the
> reg_domain to use when loading the driver?

I can just guess. I think this could keep you safe wrt. modifying the
hardware, but as Adrian explained there is still a risk that
calibration data for the channels that you have "unlocked" is so
wrong that the hardware will violate emission regulations.


//Peter