gree...@candelatech.com writes:
> From: Ben Greear
>
> They may be dumped through the firmware dump debugfs
> file.
>
> Signed-off-by: Ben Greear
> ---
>
> v3: Re-worked byte-order related stuff again,
>thanks to Michael's comments on IRC.
>Fix problem reported by smatch, possible NPE.
From: Ben Greear
They may be dumped through the firmware dump debugfs
file.
Signed-off-by: Ben Greear
---
v3: Re-worked byte-order related stuff again,
thanks to Michael's comments on IRC.
Fix problem reported by smatch, possible NPE.
v2: Remove some #ifdefs
rebase: Fix logging
From: Ben Greear
They may be dumped through the firmware dump debugfs
file.
Signed-off-by: Ben Greear
---
v2: Remove some #ifdefs
rebase: Fix logging, deal with byte-order differences
when reading firmware memory.
Tested on x86-64.
drivers/net/wireless/ath/ath10k/core.h |
Recent changes done to start/restart sequences
broke hw recovery in some hw configurations. The
pci transport was stopped twice however due to a
workaround in the pci disabling code the
disable/enable for first msi interrupt was not
balanced. This ended up with irqs not being
properly re-enabled an
Hi John,
here's a new pull request containing latest ath10k and ath6kl patches
accumulated during the merge window, changelog below. Please let me know
if there are any problems.
Please note that commit 7aa7a72a2367 ("ath10k: improve logging to
include dev id") is huge but still a simple patch ad
Michal Kazior writes:
> This removes implicit endianess in some places.
> I'd love to get rid of it from
> ath10k_pci_diag_access* as well but let's fix
> ath10k_pci_diag_mem_* first.
>
> Note: This is based on my logging patch and fw
> crash dump fix.
>
> v2:
> * rebased
> * some fixes in patc
On 27 August 2014 09:28, Kalle Valo wrote:
> Michal Kazior writes:
>
>> Some copy engine structures are target specific
>> and are uploaded to the device during
>> init/configuration.
>>
>> This also cleans up a bit diag_mem_read/write
>> implicit byteswap mess leaving only
>> diag_access_read/wr
On 27 August 2014 09:26, Kalle Valo wrote:
> Michal Kazior writes:
>
>> Some copy engine structures are target specific
>> and are uploaded to the device during
>> init/configuration.
>>
>> This also cleans up a bit diag_mem_read/write
>> implicit byteswap mess leaving only
>> diag_access_read/wr
On Wed, Aug 27, 2014 at 2:55 AM, Michal Kazior wrote:
> Avery wrote:
>> Any guesses about why the offchannel time would be too short on ath10k?
>
> Try setting up a larger beacon interval, e.g. 300ms.
wireshark confirmed that the beacon interval was changed, but
offchannel time was weirdly still
Michal Kazior writes:
> Some copy engine structures are target specific
> and are uploaded to the device during
> init/configuration.
>
> This also cleans up a bit diag_mem_read/write
> implicit byteswap mess leaving only
> diag_access_read/write with an implicit endianess
> byteswap.
>
> Signed-
Michal Kazior writes:
> Some copy engine structures are target specific
> and are uploaded to the device during
> init/configuration.
>
> This also cleans up a bit diag_mem_read/write
> implicit byteswap mess leaving only
> diag_access_read/write with an implicit endianess
> byteswap.
>
> Signed-
11 matches
Mail list logo
