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: Wed, 13 Feb 2008 23:20:07 -0500	[thread overview]
Message-ID: <20080214042007.GA24186@hash.localnet> (raw)
In-Reply-To: <40f31dec0802112318q281ef27eg2ec0c1df441ed097@mail.gmail.com>

On Tue, Feb 12, 2008 at 09:18:05AM +0200, Nick Kossifidis wrote:
> > Not sure, I'll try them again.  Are the other traces for other cards
> > online somewhere?
> 
> Nope i have them all gathered on my laptop, you 'll sure find some
> posted on ath5k-devel list. I'll send you a b-only trace from one of
> my cards (a 5413) to check it out ;-)
> 
> We are working on a way to have all dumps uploaded somewhere...

Okay that would be good.  I was basically searching for differences by
hooking ath_hw_reg_write with a printk, sorting that, and diffing it
with a sorted file of "reg_address:value" extracted from the traces.
Would be useful to run the same scripts over other cards' dumps...

> 
> > -                               AR5K_DMASIZE_512B);
> > +                               AR5K_DMASIZE_128B);
> >         }
> 
> Have you tried 256 ? Also have you tried only setting lower dma size for rx ?

I did a few times, but not enough to definitively say which works and 
which doesn't.  I'll try to get it repeatedly starting up correctly when
I get some free time, and from there I should be able to figure out 
what's actually needed and what is noise.

> > +               ath5k_hw_reg_write(ah, 0x001e1e1e, AR5K_TXPC);
> 
> Remove TXPC and see what happens...

Sure, I'll give that a go as well.

-- 
Bob Copeland %% www.bobcopeland.com 


  parent reply	other threads:[~2008-02-14  4:21 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 [this message]
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=20080214042007.GA24186@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).