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: Mon, 18 Feb 2008 18:59:49 -0500	[thread overview]
Message-ID: <20080218235949.GA4305@hash.localnet> (raw)
In-Reply-To: <40f31dec0802112318q281ef27eg2ec0c1df441ed097@mail.gmail.com>

I spent a bunch of reboots on trying to narrow down what needs to stay
and what can go.  Driver is still a little flaky for this card; I'd say
about one third of the time I do an insmod the card gets hung and I need
to reboot.  That makes it harder to rule certain changes in/out.

Also, the calibration stuff will hang more than half the time if we
reset everything but the CTL_PCI.  I've gone back to just resetting _PCU 
and _BASEBAND for now.  Maybe this wants a card-specific flag, or like
Jiri's patch just skip the second reset?

> Have you tried 256 ? Also have you tried only setting lower dma size for rx ?

512 for tx definitely did not work.  Will try 256 and let you know.

> > +       if (ah->ah_mac_srev >= AR5K_SREV_VER_AR2424) {
> > +               ath5k_hw_reg_write(ah, 0x000100aa, 0x8118);
> > +               ath5k_hw_reg_write(ah, 0x00003210, 0x811c);
> > +               ath5k_hw_reg_write(ah, 0x00000052, 0x8108);
> > +               ath5k_hw_reg_write(ah, 0x001e1e1e, AR5K_TXPC);
> 
> Remove TXPC and see what happens...

Yep TXPC can absolutely go.  0x8118 can probably go away too.  Still unsure 
about 811c/8108.

> > +               ath5k_hw_reg_write(ah, 0x00000004, 0x8120);

It never worked without this one.

-- 
Bob Copeland %% www.bobcopeland.com 


      parent reply	other threads:[~2008-02-19  0:00 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
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 [this message]

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=20080218235949.GA4305@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).