libertas sd8686 association problem

[kevin chu]

Hi Dan,

Thanks for your reply.
The strange thing is that I didn't find any association request is sent by
firmware before I got the error return code!
But if I issue this command (0x0050) once or twice again (with the
same parameters) and associate to the same AP, it will be OK.
I encountered this problem when I implement "roaming" function.
The sd8686 module has to issue deauthentication command to the firmware
before it try to associate to another AP.
I guess the state machine in firmware maybe is in a unclear state after it
loss the connection with previous AP.
Of course I can try to associate again, but the penalty is stiffer because
the association timeout is so long and this value can't be modified...

Kevin

2012/1/11 Dan Williams <dcbw at redhat.com>

> On Mon, 2011-12-26 at 14:57 +0800, kevin chu wrote:
> > Hi all,
> >
> >
> > Did anybody know the meaning of status code 0x0002 which returned from
> > CMD_802_11_ASSOCIATE (0x0050).
> > I issued associate command to marvell sd8686 firmware, but
> > sometimes Sd8686 can't associate to the AP.
> > The firmware did not send out associate request packet to AP but
> > return 0x0002 to driver after timeout (about 500 ~ 600ms).
> > This association will successful if I retry it again after timeout.
> > So I just wonder what's wrong with the firmware in the first
> > association command.
>
> The information I have says that a "result code" of 0x02 in a command
> response means CMD_STATUS_UNSUPPORTED, which could mean that the command
> request included some parameters that the firmware simply doesn't
> support, or maybe the AP's capabilities don't overlap with the SD8686's
> and thus an association can't be made.
>
> Dan
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/libertas-dev/attachments/20120111/cfe39a4b/attachment.html>