On Tue, Jun 21, 2016 at 07:10:28AM -0700, Ben Greear wrote:
>
>
> On 06/20/2016 10:18 PM, Mohammed Shafi Shajakhan wrote:
> >Hi Ben,
> >
> >thanks for reporting ...
> >
> >On Mon, Jun 20, 2016 at 04:06:52PM -0700, Ben Greear wrote:
> >>I'm working on bringing up my hacked up version of 4.7 ath10k
On 06/20/2016 10:18 PM, Mohammed Shafi Shajakhan wrote:
Hi Ben,
thanks for reporting ...
On Mon, Jun 20, 2016 at 04:06:52PM -0700, Ben Greear wrote:
I'm working on bringing up my hacked up version of 4.7 ath10k and 10.4
firmware, and I think
I may have found a regression.
[shafi] let me k
Hi Ben,
thanks for reporting ...
On Mon, Jun 20, 2016 at 04:06:52PM -0700, Ben Greear wrote:
> I'm working on bringing up my hacked up version of 4.7 ath10k and 10.4
> firmware, and I think
> I may have found a regression.
[shafi] let me know what is the issue.. some steps to recreate the issue
I'm working on bringing up my hacked up version of 4.7 ath10k and 10.4
firmware, and I think
I may have found a regression.
My 10.4.3-ish firmware source has a bunch of:
if (stats_id == WMI_REQUEST_PEER_STAT)
logic in it. In other words, it is not using that id as a bitfield.
Now, I can fix t
