All of lore.kernel.org
 help / color / mirror / Atom feed
From: jacopo mondi <j.mondi@voltaelectronics.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k_htc: deauthenticated Reason: 16
Date: Sun, 28 Nov 2010 18:03:34 +0100	[thread overview]
Message-ID: <20101128180334.36b8ce0c@BlackBox> (raw)
In-Reply-To: <AANLkTi=8cH8wfC29e=ZhmW-6vRmzYPM6zjF2kNe-xaf6@mail.gmail.com>

Thank you all for your responses...

I'm using latest firmware from linux-firmware git repo (size corresponds
to the one mentioned in the post you were referring to).
I've also applied that 1 line patch suggested by Rajkumar Manoharan.

I've done different tries, and registered logs, in order to provide
more debug informations I can.

ath9k_htc (no debug, nohwcrypt=0)
http://pastebin.com/QVJkHMzy
As you can see CRDA thinks I'm in China, which is not true. I think
that information is taken from some kind of chip memory (log talks
about EEPROM), and I've no idea if it's important to change that
information and how to do that.
Connection is unstable and disconnection happens about every 30 seconds.

ath9k_htc (debug=601, nohwcrypt=0)
http://pastebin.com/Z045ZDFQ
Same situation as before but with huge debugging infos

When enabling nohwcrypt connection seems to be stable, but I've to
guess that doing encryption entirely in software decreases overall
performances.
Since hw encryption seems to introduce problems, could it be a firmware
related issue?

Thanks a lot 
	j

  reply	other threads:[~2010-11-28 17:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-26 16:59 [ath9k-devel] ath9k_htc: deauthenticated Reason: 16 jacopo mondi
2010-11-26 18:01 ` Rajkumar Manoharan
2010-11-26 18:23   ` Senthilkumar Balasubramanian
2010-11-28 17:03     ` jacopo mondi [this message]
2010-11-28 17:31       ` Rajkumar Manoharan
2010-11-28 18:07         ` jacopo mondi

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=20101128180334.36b8ce0c@BlackBox \
    --to=j.mondi@voltaelectronics.com \
    --cc=ath9k-devel@lists.ath9k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.