From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from wolverine02.qualcomm.com ([199.106.114.251]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1WlIsl-00064T-4Y for ath10k@lists.infradead.org; Fri, 16 May 2014 14:13:07 +0000 From: Kalle Valo Subject: Re: RE : RE : RE : RE : ath10k: set channel by command "iw" not from hostapd and DFS support of firmware-2.bin_10.1.467.2-1 References: <5373382C.1030709@elisanet.fi> <87oayx6fp7.fsf@kamboji.qca.qualcomm.com> Date: Fri, 16 May 2014 17:12:40 +0300 In-Reply-To: (Janusz Dziedzic's message of "Fri, 16 May 2014 16:03:53 +0200") Message-ID: <877g5l4xt3.fsf@kamboji.qca.qualcomm.com> MIME-Version: 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "ath10k" Errors-To: ath10k-bounces+kvalo=adurom.com@lists.infradead.org To: Janusz Dziedzic Cc: Vu Hai NGUYEN , Patrick CARNEIRO RODRIGUEZ , "ath10k@lists.infradead.org" , Matti Laakso Janusz Dziedzic writes: > On 16 May 2014 15:00, Kalle Valo wrote: >> Janusz Dziedzic writes: >> >>> Seems CONFIG_ATH10K_DFS_CERTIFIED is not set. >>> You can simply check this during compilation adding eg. to mac.c >>> #ifndef CONFIG_ATH10K_DFS_CERTIFIED >>> #error DFS_NOT_SET >>> #endif >> >> This reminds me of a feature I have been thinking. We really should have >> an info print of what ath10k kconfig options are enabled in the build. >> For example something like this: >> >> ath10k: debug off debugfs on tracing off dfs on >> >> Patches welcome :) > > I can add this, but question here is what *.c file should I use - > mac.c looks fine I think having it after the info message below in core.c is a good place. if (!test_bit(ATH10K_FLAG_FIRST_BOOT_DONE, &ar->dev_flags)) ath10k_info("%s (0x%08x, 0x%08x) fw %s api %d htt %d.%d\n", > but still someone can set flags only for some files and for some files > not. We cannot make this 100% bullet proof. If someone messes around with the build system and breaks it in the process, then it his/her problem and there's nothing we can do. We can only assume that the build system works as specified. -- Kalle Valo _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k