Su Kang Yin writes:
> On 11 May 2017 at 11:55, Kalle Valo wrote:
>> Su Kang Yin writes:
>>
>>> Without this patch QCA9888 is not working. Also I have to update
>>> board2.bin from Kalle's git repo.
>>
>> More details would be good to know, as the behaviour seems to vary quite
>> a lot. What platf
On 11 May 2017 at 11:55, Kalle Valo wrote:
> Su Kang Yin writes:
>
>> Without this patch QCA9888 is not working. Also I have to update
>> board2.bin from Kalle's git repo.
>
> More details would be good to know, as the behaviour seems to vary quite
> a lot. What platform are you using, x86, some AR
Su Kang Yin writes:
> Without this patch QCA9888 is not working. Also I have to update
> board2.bin from Kalle's git repo.
More details would be good to know, as the behaviour seems to vary quite
a lot. What platform are you using, x86, some ARM board or what? And
what kernel exactly?
--
Kalle
This adds a few configurable debugging options:
* driver debugging and tracing is now configurable per device
* driver debugging and tracing is now configurable at runtime
* the debugging / tracing is not run at all (besides a mask check)
unless the specific debugging bitmap field is configured.
grr, no. lemme go re-add that and resubmit.
thanks!
-a
On 10 May 2017 at 09:44, Steve deRosier wrote:
> Hi Adrian,
>
> On Wed, May 10, 2017 at 9:25 AM, Adrian Chadd wrote:
>
>> diff --git a/drivers/net/wireless/ath/ath10k/debug.h
>> b/drivers/net/wireless/ath/ath10k/debug.h
>> index 257d109
Hi Adrian,
On Wed, May 10, 2017 at 9:25 AM, Adrian Chadd wrote:
> diff --git a/drivers/net/wireless/ath/ath10k/debug.h
> b/drivers/net/wireless/ath/ath10k/debug.h
> index 257d10985c6e..7bd461927029 100644
> --- a/drivers/net/wireless/ath/ath10k/debug.h
> +++ b/drivers/net/wireless/ath/ath10k/de
This adds a few configurable debugging options:
* driver debugging and tracing is now configurable per device
* driver debugging and tracing is now configurable at runtime
* the debugging / tracing is not run at all (besides a mask check)
unless the specific debugging bitmap field is configured.
On 05/10/2017 03:30 AM, Tom Psyborg wrote:
On 9 May 2017 at 19:50, Adrian Chadd mailto:adr...@freebsd.org>> wrote:
(Note note: some of those channels have non-megahertz boundaries,
which means ... yeah, hello inter-operability boundaries. Hilarious.)
-adrian
From what I can
