We solved the problem for now by running OpenWRT 18.06 in a virtual machine.
As we had to look for two weeks to find the reason I suggest to add a
human-readable (error) message to dmesg/syslog like
"ath10k: Country code read from ACPI table: XX"
and
"ath10k: Reading country code from ACPI fai
On 2019-04-09 12:18, Adrian Chadd wrote:
What about QCA6174 that uses TLV? Does this change its behaviour?
-a
No, it will not break QCA6174, as earlier also same enum values
(wmi_stats_id) were used for TLV targets,
enum wmi_stats_id {
WMI_STAT_PEER = BIT(0),
WMI_STAT_AP = B
> -Original Message-
> From: David Laight
> Sent: Wednesday, 10 April 2019 6:45 PM
> To: 'Alastair D'Silva' ; alast...@d-silva.org
> Cc: Jani Nikula ; Joonas Lahtinen
> ; Rodrigo Vivi ;
> David Airlie ; Daniel Vetter ; Karsten Keil
> ; Jassi Brar ; Tom Lendacky
> ; David S. Miller ;
> Jose
On (04/10/19 13:17), Alastair D'Silva wrote:
> With the wider display format, it can become hard to identify how many
> bytes into the line you are looking at.
>
> The patch adds new flags to hex_dump_to_buffer() and print_hex_dump() to
> print vertical lines to separate every N groups of bytes.
>
From: Alastair D'Silva
> Sent: 10 April 2019 04:17
> With the wider display format, it can become hard to identify how many
> bytes into the line you are looking at.
>
> The patch adds new flags to hex_dump_to_buffer() and print_hex_dump() to
> print vertical lines to separate every N groups of by