Linux wireless drivers development
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: wireless <linux-wireless@vger.kernel.org>
Cc: Luciano Coelho <coelho@ti.com>
Subject: wl1271 woes continue
Date: Mon, 30 Apr 2012 07:10:33 -0600	[thread overview]
Message-ID: <4F9E8F49.3080700@mlbassoc.com> (raw)

Luciano,

I'm still having troubles with the WL1271.  I now have a
brand new platform - same basic design as before but with
a DM3730 instead of the DM8148.  I've tried a couple of
off-the-shelf kernels (3.0.0 and 3.3.0) with it, with mixed
results.

With 3.3.0 I could not get the device to associate with the AP.
It would get started and then the wl1271 stopped talking and
the process failed.

With 3.0.0, I can get it to work reasonably well.  However, I
still have to go through the manual steps to get it to associate.
Anything other than the process below causes the wl1271 to reset
and die...  I also cannot shut the device down and restart it.
Attempts at a restart cause the wl1271 to lock up and I have to
reboot to recover.

Only these steps work for the initial association:
   # ifconfig wlan0 hw ether 0:1:2:3:4:5
   # ifconfig wlan0 up
   # iw wlan0 scan
   # ifup wlan0
Note: my AP is using WPA2 so I'm also running wpa_supplicant

I'm going to try using the latest compat-wireless, using the
3.0.0 kernel as overall it is more stable on this platform.
I also plan to experiment a bit with the Panda (OMAP4) as it
has the same peripherals (and I assume that it works?)

What can I do to make this work better?
What data need I provide to help diagnose the failures?

Thanks for your time

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

             reply	other threads:[~2012-04-30 13:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-30 13:10 Gary Thomas [this message]
2012-04-30 17:13 ` wl1271 woes continue Mr Dash Four
2012-05-01 13:42 ` Gary Thomas

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=4F9E8F49.3080700@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=coelho@ti.com \
    --cc=linux-wireless@vger.kernel.org \
    /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