On 15.05.2018 14:29, Rafał Miłecki wrote:
I was hoping that maybe looking at fw-reported capabilities will give me
any hint regarding that but I'm afraid I'm out of luck. Below is a list
of firmwares I tested and summary of each of them.
Note: as every firmware reports following capabilities:
On 6/19/2018 10:32 AM, Rafał Miłecki wrote:
On 19.06.2018 09:53, Arend van Spriel wrote:
On 6/19/2018 9:27 AM, Rafał Miłecki wrote:
On Mon, 11 Jun 2018 at 12:48, Arend van Spriel
wrote:
On 5/30/2018 1:52 PM, Rafał Miłecki wrote:
I'm providing extra version info of tested firmware images as
On 19.06.2018 09:53, Arend van Spriel wrote:
On 6/19/2018 9:27 AM, Rafał Miłecki wrote:
On Mon, 11 Jun 2018 at 12:48, Arend van Spriel
wrote:
On 5/30/2018 1:52 PM, Rafał Miłecki wrote:
I'm providing extra version info of tested firmware images as requested
by Arend in another e-mail thread.
On 6/19/2018 9:27 AM, Rafał Miłecki wrote:
On Mon, 11 Jun 2018 at 12:48, Arend van Spriel
wrote:
On 5/30/2018 1:52 PM, Rafał Miłecki wrote:
I'm providing extra version info of tested firmware images as requested
by Arend in another e-mail thread.
Looking into our firmware repo it there are
On Mon, 11 Jun 2018 at 12:48, Arend van Spriel
wrote:
> On 5/30/2018 1:52 PM, Rafał Miłecki wrote:
> > I'm providing extra version info of tested firmware images as requested
> > by Arend in another e-mail thread.
>
> Looking into our firmware repo it there are two flags, ie. WL_MONITOR
> and
On Tue, 19 Jun 2018 at 07:36, Rafał Miłecki wrote:
> On Mon, 18 Jun 2018 at 23:46, Rafał Miłecki wrote:
> > On Mon, 18 Jun 2018 at 21:36, Arend van Spriel
> > wrote:
> > >
> > > On 6/18/2018 1:54 PM, Rafał Miłecki wrote:
> > > > On Mon, 11 Jun 2018 at 12:48, Arend van Spriel
> > > > wrote:
> >
On Mon, 18 Jun 2018 at 23:46, Rafał Miłecki wrote:
> On Mon, 18 Jun 2018 at 21:36, Arend van Spriel
> wrote:
> >
> > On 6/18/2018 1:54 PM, Rafał Miłecki wrote:
> > > On Mon, 11 Jun 2018 at 12:48, Arend van Spriel
> > > wrote:
> > >> On 5/30/2018 1:52 PM, Rafał Miłecki wrote:
> > >>> I'm
On Mon, 18 Jun 2018 at 21:36, Arend van Spriel
wrote:
>
> On 6/18/2018 1:54 PM, Rafał Miłecki wrote:
> > On Mon, 11 Jun 2018 at 12:48, Arend van Spriel
> > wrote:
> >> On 5/30/2018 1:52 PM, Rafał Miłecki wrote:
> >>> I'm providing extra version info of tested firmware images as requested
> >>>
On 6/18/2018 1:54 PM, Rafał Miłecki wrote:
On Mon, 11 Jun 2018 at 12:48, Arend van Spriel
wrote:
On 5/30/2018 1:52 PM, Rafał Miłecki wrote:
I'm providing extra version info of tested firmware images as requested
by Arend in another e-mail thread.
Looking into our firmware repo it there are
On Mon, 11 Jun 2018 at 12:48, Arend van Spriel
wrote:
> On 5/30/2018 1:52 PM, Rafał Miłecki wrote:
> > I'm providing extra version info of tested firmware images as requested
> > by Arend in another e-mail thread.
>
> Looking into our firmware repo it there are two flags, ie. WL_MONITOR
> and
On 16 May 2018 at 10:37, Arend van Spriel wrote:
> On 5/15/2018 2:29 PM, Rafał Miłecki wrote:
>>
>> I'm interested in adding support for monitor mode to the brcmfmac. I did
>> some early research on firmware capabilities & behavior using various
>> firmwares I could
On 5/15/2018 2:29 PM, Rafał Miłecki wrote:
I'm interested in adding support for monitor mode to the brcmfmac. I did
some early research on firmware capabilities & behavior using various
firmwares I could find for my devices: 43602a1, 4366b1, 4366c0 (BCM4366
and BCM4366E).
I am interested too
I'm interested in adding support for monitor mode to the brcmfmac. I did
some early research on firmware capabilities & behavior using various
firmwares I could find for my devices: 43602a1, 4366b1, 4366c0 (BCM4366
and BCM4366E).
I was doing my tests by starting monitor mode with SET_MONITOR
13 matches
Mail list logo