Progress on OLPC's board wireless device

[Ronak Chokshi]

Hi Marcelo,
Regarding the USB firmware download hang issue, I don't think we have
seen that issue on our test beds. 

Regarding the issue with the Association command here are some points,
	I don't think we have seen that one also here in our side.
	Can you send me a sniffer capture on this?
	What is the AP that you are trying to associate?
	I hope that you are using the correct firmware (standalone
client firmware and not the firmware that works with Roofnet) by any
chance.

But I am confirming both of them with our teams.

Here is an updated document "WLAN Subsystem Host Driver, Firmware, and
Interface IEEE 802.11a/g/b Firmware Specification v5.1".

Are you testing these things on the OLPC board? If yes, then we should
be able to help you guys out better from next week when we get some
boards for us?

Thanks
Ronak


-----Original Message-----
From: Marcelo Tosatti [mailto:marcelo at kvack.org] 
Sent: Wednesday, June 14, 2006 12:31 PM
To: Ronak Chokshi; libertas-dev at lists.infradead.org
Subject: Progress on OLPC's board wireless device

Hi Ronak,

I have been testing the Libertas driver on the OLPC board and got a few
questions for you.

Good news first: The device is detected by the USB subsystem and the
Libertas driver, and its able to scan for AP's correctly (with "iwlist
eth0 scan").

And the bad news:

One issue is that the firmware download is not reliable, it fails at
times (my first attempt to load the driver was not successful).

What happens is that no response is received from the device, even
though the URB write request containing the firmware data is ACKed (ie.
there is a successful URB write callback notification).

>From there on the device seems completly dead. Attempting to reload the
firmware results in no ACKs referring to the URB fw write.

To fix the situation I have to power off the board, reboot, and,
occassionaly, the firmware boots successfully. Obviously this situation
is not acceptable for production.

Any clues on what might be going on? Should a HostCmd_CMD_802_11_RESET
help?
Is this a known issue?

Another issue is failure to associate to an AP.
HostCmd_CMD_802_11_ASSOCIATE _always_ returns status code "4", which
results in:

/**
 *  @brief This function handles the command response of associate
 *
 *  @param priv    A pointer to wlan_private structure
 *  @param resp    A pointer to HostCmd_DS_COMMAND
 *  @return        WLAN_STATUS_SUCCESS or WLAN_STATUS_FAILURE
 */
int wlan_ret_802_11_associate(wlan_private* priv,
                              struct HostCmd_DS_COMMAND* resp)
{
    wlan_adapter*           Adapter = priv->adapter;
    int                     ret     = WLAN_STATUS_SUCCESS;
    union iwreq_data        wrqu;
    IEEEtypes_AssocRsp_t*   pAssocRsp;
    BSSDescriptor_t*        pBSSDesc;

    ENTER();

    pAssocRsp = (IEEEtypes_AssocRsp_t*)&resp->params;

    if (pAssocRsp->StatusCode) {

        if (Adapter->MediaConnectStatus == WlanMediaStateConnected) {
            MacEventDisconnected(priv);
        }

        PRINTM(INFO, "ASSOC_RESP: Association Failed, status code =
%d\n",
               pAssocRsp->StatusCode);


Where can I find more information about this status codes? I've
searched for the IEEE IE 802.11 types but no success. The documentation
Marvell provided is not very extensive. Is there anything more complete
other than "WLAN Subsystem Host Driver, Firmware, and Interface IEEE
802.11a/g/b Firmware Specification v5.0" ?

Thank you


-------------- next part --------------
A non-text attachment was scrubbed...
Name: WLAN Firmware Spec v5.1 - MV-S103752-00.zip
Type: application/x-zip-compressed
Size: 889243 bytes
Desc: WLAN Firmware Spec v5.1 - MV-S103752-00.zip
Url : http://lists.infradead.org/pipermail/libertas-dev/attachments/20060614/bb59070f/attachment-0001.bin