Hi Bob,
On 2015/11/20 1:41, Bob Copeland wrote:
On Thu, Nov 19, 2015 at 11:20:14AM +0800, yfw wrote:
Hi Bob,
On 2015年11月10日 22:13, Bob Copeland wrote:
On Tue, Nov 10, 2015 at 03:08:53PM +0800, fengwei.yin wrote:
Even on 3620, not all cmds switch to wcn36xx_smd_rsp_status_check_v2.
And I don't think wcn36xx_smd_rsp_status_check_v2 should bind to 3620 (it
may be related with firmware).
In patch v2, the wcn36xx_smd_rsp_status_check_v2 is not bind to 3620. If
you could test on none-3620 platform (I don't have none-3620 plafrom), that
will be great.
Sure, I'll take a look today or tomorrow on my hardware.
Ping...
Oops, sorry. I can confirm my hardware uses this format.
Turns out, in my backports snapshot I was already carrying a patch for it:
https://github.com/KrasnikovEugene/wcn36xx/commit/7d41270b8c3eee0f72713b4553ca047807c0a00e
Actually, this patch was using the v1 and DragonBoard needs v2 for trigger_ba.
And I want to know whether the change from Andy could work on the platform
which is using v1.
Can you try this change on your platform? Thanks.
Regards
Yin, Fengwei
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
