Peter Oh writes:
> Split Mesh service to 11s Mesh and non-11s Mesh according to
> firmware service bit to help users distinguish 11s Mesh from
> non 11s Mesh.
> And add abstraction layer for vdev subtype to solve subtype mismatch
> and to give flexible compatibility among different firmware revis
On 01/27/2016 06:04 PM, Yeoh Chun-Yeow wrote:
On Thu, Jan 28, 2016 at 5:53 AM, Peter Oh wrote:
On 01/27/2016 11:39 AM, Bob Copeland wrote:
On Wed, Jan 27, 2016 at 10:55:53AM -0800, Peter Oh wrote:
Split Mesh service to 11s Mesh and non-11s Mesh according to
firmware service bit to help users
On Thu, Jan 28, 2016 at 5:53 AM, Peter Oh wrote:
>
> On 01/27/2016 11:39 AM, Bob Copeland wrote:
>>
>> On Wed, Jan 27, 2016 at 10:55:53AM -0800, Peter Oh wrote:
>>>
>>> Split Mesh service to 11s Mesh and non-11s Mesh according to
>>> firmware service bit to help users distinguish 11s Mesh from
>>>
On 01/27/2016 11:39 AM, Bob Copeland wrote:
On Wed, Jan 27, 2016 at 10:55:53AM -0800, Peter Oh wrote:
Split Mesh service to 11s Mesh and non-11s Mesh according to
firmware service bit to help users distinguish 11s Mesh from
non 11s Mesh.
And add abstraction layer for vdev subtype to solve subty
On Wed, Jan 27, 2016 at 10:55:53AM -0800, Peter Oh wrote:
> Split Mesh service to 11s Mesh and non-11s Mesh according to
> firmware service bit to help users distinguish 11s Mesh from
> non 11s Mesh.
> And add abstraction layer for vdev subtype to solve subtype mismatch
> and to give flexible compa
Split Mesh service to 11s Mesh and non-11s Mesh according to
firmware service bit to help users distinguish 11s Mesh from
non 11s Mesh.
And add abstraction layer for vdev subtype to solve subtype mismatch
and to give flexible compatibility among different firmware revisions.
Peter Oh (4):
ath10k