linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bob Copeland <me@bobcopeland.com>
To: Nick Kossifidis <mickflemm@gmail.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: ath5k: reset for 5424-based card
Date: Sat, 2 Feb 2008 20:45:59 -0500	[thread overview]
Message-ID: <20080203014559.GA20177@hash.localnet> (raw)
In-Reply-To: <40f31dec0802011748i5a1b8aaftf42f7798762cca3d@mail.gmail.com>

On Sat, Feb 02, 2008 at 03:48:34AM +0200, Nick Kossifidis wrote:
> > Yeah I have an AP but it's broadcom based.  I'll try to do the traces this
> > weekend.
> >
> 
> Thanx ;-)

Ok, so I did -b and -g traces.  That branch is a little out of date, so 
I wound up downgrading to 2.6.22.

I don't have an a-capable AP, so how might I get a/turboa/turbog traces?
Do I use wlanconfig from the madwifi docs like so:

   $ iwpriv ath0 mode 1
   $ wlanconfig ath0 create wlandev wifi0 wlanmode ap

What mode # is used for turbo a/g?

I put the tarballs at http://bobcopeland.com/ath5k/

> Great info ! Your card sends the RXORN interrupt (Rx overrun), at
> least we know what the problem is ;-)
> 
> How about your signal strength ?

Looks fine, I think:
    Quality=89/100  Signal level=-39 dBm  Noise level=-96 dBm

> That's ok since we haven't added initvals/rfbuffer tables for your
> card so phy isn't initialized propertly (this is the first problem we
> should fix so we can be sure that rx overrun is not phy-related).

OK, well I guess that info is in the tarballs.  I poked around in the
code, and it looks like my tables are similar to 5413 with maybe a 
couple of extra registers.  But I'll await your analysis. :)

> 1472         if (ah->ah_version != AR5K_AR5210) {
> 1473                 /*HIU = Host Interface Unit (PCI etc)*/
> 1474                 if (unlikely(data & (AR5K_ISR_HIUERR)))
> 1475                         *interrupt_mask |= AR5K_INT_FATAL;
> 
> 
> Change AR5K_ISR_HIUERR with AR5K_ISR_RXORN

It does get rid of the message, but other than not seeing the printk
any more, it doesn't seem to help things much. 
 
Good luck on the exams! 

-- 
Bob Copeland %% www.bobcopeland.com 


  reply	other threads:[~2008-02-03  1:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31 15:59 ath5k: reset for 5424-based card Bob Copeland
2008-01-31 16:56 ` Nick Kossifidis
2008-02-01  4:03   ` Bob Copeland
2008-02-01 12:09     ` Nick Kossifidis
2008-02-01 22:53       ` Bob Copeland
2008-02-02  1:48         ` Nick Kossifidis
2008-02-03  1:45           ` Bob Copeland [this message]
2008-02-05  9:13             ` Nick Kossifidis
2008-02-10 16:21               ` Bob Copeland
2008-02-10 19:05                 ` Nick Kossifidis
2008-02-11 15:00                   ` Bob Copeland
2008-02-12  7:18                     ` Nick Kossifidis
2008-02-12  7:48                       ` Holger Schurig
2008-02-12  7:55                         ` Nick Kossifidis
2008-02-14  4:20                       ` Bob Copeland
2008-02-18 23:59                       ` Bob Copeland

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=20080203014559.GA20177@hash.localnet \
    --to=me@bobcopeland.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mickflemm@gmail.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).