linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Forest Bond <forest@alittletooquiet.net>
To: Mohammed Shafi <shafi.wireless@gmail.com>
Cc: Rajkumar Manoharan <rmanohar@qca.qualcomm.com>,
	"Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>,
	Jouni Malinen <jouni@qca.qualcomm.com>,
	Vasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com>,
	Senthil Balasubramanian <senthilb@qca.qualcomm.com>,
	linux-wireless@vger.kernel.org
Subject: Re: ath9k_htc fails to initialize TL-WN721N with compat-wireless 3.0-rc4-1
Date: Wed, 6 Jul 2011 14:29:38 -0400	[thread overview]
Message-ID: <20110706182937.GE28091@alittletooquiet.net> (raw)
In-Reply-To: <CAD2nsn0HFgm6Puuzuy4gghdDvpb05WaQtETS4=mfQ63mFzo--Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2877 bytes --]

Hi shafi,

On Wed, Jul 06, 2011 at 03:58:13AM -0400, Mohammed Shafi wrote:
> > To avoid multi reg writes please apply the following change
> >
> > diff --git a/drivers/net/wireless/ath/ath9k/wmi.h
> > b/drivers/net/wireless/ath/ath9k/wmi.h
> > index fde6da6..0878add 100644
> > --- a/drivers/net/wireless/ath/ath9k/wmi.h
> > +++ b/drivers/net/wireless/ath/ath9k/wmi.h
> > @@ -124,7 +124,7 @@ enum wmi_event_id {
> >        WMI_TXSTATUS_EVENTID,
> >         };
> >
> >          -#define MAX_CMD_NUMBER 62
> >          +#define MAX_CMD_NUMBER 1
> >
> >            struct register_write {
> >                    __be32 reg;
> > --
> 
> did you try in your system the simple hack Raj had suggested?
> it seems to solve ths issue, but we encountered some soft lock ups due
> to the LED stuff is moved to mac80211 with the recent code base,
> we will take a look at this to fix this, probably requires some backporting.

Yes, the device seems to initialize properly with this patch.  Like you
expected, I am seeing soft lock-ups when I try to bring the interface up.

> in order to recreate the issue, we installed Ubuntu 8.04- the Hardy
> Heron - released in April 2008.
> as expected the issue is perfectly reproducible. thanks to Raj for his
> help and suggestions.

Thanks for taking the time to test.  I really appreciate everyone's help.

> *please obtain the stable compat-wireless-2.6.36-4
> http://linuxwireless.org/en/users/Download/stable/#compat-wireless_2.6.36_stable_releases
> *download the old firmware
> http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git;a=blob_plain;f=ar9271.fw;hb=HEAD
> (history http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git;a=history;f=ar9271.fw;h=d0ee74a1c8dccb7cc21f5be90f1d4048fa9dbf9e;hb=HEAD)
> with this your USB card will be up and running, we did some basic testing.
> *I used  usbmodeswitch-0.9.4

Ultimately we'd like to try the experimental AP mode.  I understand this was
introduced in kernel version 2.6.40, so I don't think compat-wireless-2.6.36-4
will work for us.

Can you point me to the LED-related commits that you mentioned above?  We'll
either need to backport the changes required to fix the soft lock-ups or upgrade
our kernel to include these commits.

> we also recommend you upgrade to latest kernel available for your distribution,
> because we may still face some other issues as ath9k_htc very much new
> compared to ath9k

A kernel upgrade is something I would like to avoid if possible, but of course
it is something we'll consider if we need to.

> please also read
> http://wireless.kernel.org/en/users/Download/compat-wireless-old

I think this kernel is supported by the regular compat-wireless package, right?

Thanks,
Forest
-- 
Forest Bond
http://www.alittletooquiet.net
http://www.rapidrollout.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2011-07-06 18:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-01 13:35 ath9k_htc fails to initialize TL-WN721N with compat-wireless 3.0-rc4-1 Forest Bond
2011-07-01 14:01 ` Mohammed Shafi
     [not found]   ` <BANLkTimUs65_Sw=pwF-J8gPjyrNcs2qnOw@mail.gmail.com>
2011-07-01 17:32     ` Forest Bond
2011-07-04  5:24       ` Rajkumar Manoharan
2011-07-04  9:53         ` Rajkumar Manoharan
2011-07-05 12:49           ` Forest Bond
2011-07-05 13:29             ` Mohammed Shafi
2011-07-05 14:30               ` Forest Bond
2011-07-05 14:47                 ` Mohammed Shafi
2011-07-05 17:20                   ` Forest Bond
2011-07-06  2:39                     ` Rajkumar Manoharan
2011-07-06  7:58                       ` Mohammed Shafi
2011-07-06 18:29                         ` Forest Bond [this message]
2011-07-07  5:12                           ` Mohammed Shafi
2011-07-07  6:19                             ` Mohammed Shafi
2011-07-07  7:23                               ` Mohammed Shafi
2011-07-07 22:53                                 ` Forest Bond
2011-07-08 13:24                                   ` Mohammed Shafi
2011-07-11  5:31                                     ` Mohammed Shafi
2011-07-11 15:04                                       ` Forest Bond
2011-07-11 15:33                                         ` Mohammed Shafi

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=20110706182937.GE28091@alittletooquiet.net \
    --to=forest@alittletooquiet.net \
    --cc=jouni@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rmanohar@qca.qualcomm.com \
    --cc=rodrigue@qca.qualcomm.com \
    --cc=senthilb@qca.qualcomm.com \
    --cc=shafi.wireless@gmail.com \
    --cc=vthiagar@qca.qualcomm.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).