linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pazzo Da Legare <pazzodalegare@gmail.com>
To: Luciano Coelho <luciano.coelho@nokia.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Levi, Shahar" <shahar_levi@ti.com>,
	Logan Gunthorpe <logang@deltatee.com>
Subject: Re: wl1271 firmware
Date: Thu, 22 Jul 2010 17:41:24 +0200	[thread overview]
Message-ID: <AANLkTilZhvGg2SUk5btpQQA3qj2k4rob4rTychDu7gXM@mail.gmail.com> (raw)
In-Reply-To: <1279780848.2322.31.camel@powerslave>

Dear Luciano,
Dear All,

I enabled the DEBUG_LEVEL as you advice me but I have no additional
information....

[  186.230000] wl1271_sdio mmc0:0001:2: firmware: requesting
wl1271-fw.bin
[  186.420000] wl1271_sdio mmc0:0001:2: firmware: requesting
wl1271-nvs.bin
[  186.860000] wl1271: firmware booted (Rev 6.1.0.0.310)
[  186.880000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  187.380000] wl1271: ERROR ELP wakeup timeout!
[  187.880000] wl1271: ERROR ELP wakeup timeout!

Pazzo

2010/7/22 Luciano Coelho <luciano.coelho@nokia.com>:
> Hi Pazzo,
>
>
> On Wed, 2010-07-21 at 19:27 +0200, ext Pazzo Da Legare wrote:
>> Dear All again,
>>
>> I've just test with compact-wireless-2010-07-20 but I've the same problem:
>>
>> root@hawkboard:~# ifconfig wlan0 192.168.0.1 up
>> [   68.920000] wl1271_sdio mmc0:0001:2: firmware: requesting wl1271-fw.bin
>> [   69.100000] wl1271_sdio mmc0:0001:2: firmware: requesting wl1271-nvs.bin
>> [   69.510000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
>> root@hawkboard:~# [   70.020000] wl1271: ERROR ELP wakeup timeout!
>> [   70.520000] wl1271: ERROR ELP wakeup timeout!
>>
>>
>> looking at dmesg:
>>
>> [  68.920000] wl1271_sdio mmc0:0001:2: firmware: requesting wl1271-fw.bin
>> [   69.100000] wl1271_sdio mmc0:0001:2: firmware: requesting wl1271-nvs.bin
>> [   69.500000] wl1271: firmware booted (Rev 6.1.0.0.310)
>> [   69.510000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
>> [   70.020000] wl1271: ERROR ELP wakeup timeout!
>> [   70.520000] wl1271: ERROR ELP wakeup timeout!
>>
>> [   68.920000] wl1271_sdio mmc0:0001:2: firmware: requesting wl1271-fw.bin
>> [   69.100000] wl1271_sdio mmc0:0001:2: firmware: requesting wl1271-nvs.bin
>> [   69.500000] wl1271: firmware booted (Rev 6.1.0.0.310)
>> [   70.020000] wl1271: ERROR ELP wakeup timeout!
>> [   70.520000] wl1271: ERROR ELP wakeup timeout!
>>
>> Do you have any clue?
>
> I'm not sure what this is, but usually an ERROR ELP wakeup timeout means
> that the firmware has crashed.
>
> Could you enable the following DEBUG flags in wl1271.h and send the logs
> again? Maybe they provide more clues...
>
> #define DEBUG_LEVEL (DEBUG_BOOT | DEBUG_ACX | DEBUG_CMD | DEBUG_PSM | \
>                     DEBUG_IRQ | DEBUG_EVENT)
>
>
> --
> Cheers,
> Luca.
>
>

  reply	other threads:[~2010-07-22 15:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-10  0:19 wl1271 firmware Logan Gunthorpe
2010-07-11  5:38 ` Levi, Shahar
2010-07-12  5:35   ` Logan Gunthorpe
2010-07-16 21:41   ` Pazzo Da Legare
2010-07-17 12:20     ` Levi, Shahar
     [not found]       ` <AC090B9732AB2B4DB7FF476E907FE6600106966BA5@dnce02.ent.ti.com>
     [not found]         ` <4C45ED36.2090604@deltatee.com>
2010-07-21 17:01           ` Pazzo Da Legare
2010-07-21 17:27             ` Pazzo Da Legare
2010-07-22  6:40               ` Luciano Coelho
2010-07-22 15:41                 ` Pazzo Da Legare [this message]
2010-07-22 16:34                   ` Luciano Coelho
2010-07-23 23:19                     ` Pazzo Da Legare
2010-07-31 13:23                       ` Kalle Valo
  -- strict thread matches above, loose matches on Subject: below --
2010-06-30 11:26 Pazzo Da Legare
2010-06-30 13:42 ` Levi, Shahar
2010-07-01  7:36   ` Pazzo Da Legare
2010-07-02  9:47   ` max
2010-07-02  9:54   ` mastupristi
2010-07-05  7:36   ` Pazzo Da Legare
2010-07-05 16:49     ` Pazzo Da Legare
2010-07-06 12:28       ` Levi, Shahar
2010-07-08  8:42         ` Luciano Coelho
2010-07-06 11:55     ` Levi, Shahar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTilZhvGg2SUk5btpQQA3qj2k4rob4rTychDu7gXM@mail.gmail.com \
    --to=pazzodalegare@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=logang@deltatee.com \
    --cc=luciano.coelho@nokia.com \
    --cc=shahar_levi@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).