Re: [Madwifi-devel] How to enable HAL_DEBUG

[Aditya B. <ay...@an...>]

Hi,

sorry ill post my queries on the devel list from now on.

When you say make HAL_DEBUG=1, are you saying I should invoke the 'make' 
command in this way or I should set the variable HAL_DEBUG to 1 in the 
code? HAL_DEBUG has been #defined as follows in ah_internal.h, so Im not 
sure how to set it to 1?

#define HALDEBUG(_ah, __m, _fmt, ...)

Is my understanding of the order of function calls correct? 
ath_getchannels() calls ath_hal_init_channels() defined in 
ah_regdomain.c correct? I ask this because my printks in 
ath_hal_init_channels() are not getting printed.

Thanks
regards,
Aditya Bhave






On 06/03/2010 12:17 PM, Pavel Roskin wrote:
> On Thu, 2010-06-03 at 00:02 -0400, Aditya Bhave wrote:
>    
>> Hi,
>>
>> I want to enable HAL_DEBUG and trace the flow of MadWifi code? How can I
>> do that?
>>      
> make HAL_DEBUG=1
>
>    
>> Is there any other tool that can help me do this? Basically I want to
>> see exactly how MadWifi initializes itself by stepping through the code..
>>      
> There are some kernel debuggers, but I have never used them.  I don't
> think stepping through the code would help much.
>
> If you are interested in monitoring hardware registers, consider using
> mmiotrace (see Documentation/trace/mmiotrace.txt in the kernel sources).
>
> Please avoid cross-posting.  You post is clearly a better fit for
> madwifi-devel than for madwifi-users.
>
>