From: Bruno Randolf <br1@einfach.org>
To: Jonathan Guerin <jonathan@guerin.id.au>
Cc: ath5k-devel@lists.ath5k.org,
"linux-wireless" <linux-wireless@vger.kernel.org>,
Nick Kossifidis <mickflemm@gmail.com>
Subject: Re: [ath5k-devel] [ath5k] Incorrect value for ACK_TIMEOUT
Date: Wed, 15 Sep 2010 12:45:53 +0900 [thread overview]
Message-ID: <201009151245.53194.br1@einfach.org> (raw)
In-Reply-To: <AANLkTiniROJatam4yA4sss3qjczT-6=jSP9QxvmDo2dq@mail.gmail.com>
On Wed September 15 2010 12:28:36 Jonathan Guerin wrote:
> >> Should all of the init be changed to use these functions, along with
> >> #define init values?
> >
> > i think it would be best if we could remove the initvals alltoghether and
> > use the function to set the ack timeout. but i'm not sure if we need to
> > have them initialized to some value at the beginning. in this case can
> > we just override them later using the function. or just update the
> > initvals numerically (but no defines).
>
> If there are no initvals, changing the mode won't init them to default
> values, will it? Or are you saying that values should not be
> initialised until the mode is set?
that's what i'm not sure about... but ath5k_hw_set_ack_timeout() could be
called from reset so it applies the changes when the mode is set. i think that
should be fine, but it needs to be tested -- and i think the same applies to a
lot of the initvals.
> I've been a bit scared to post here until I had more information
> rather than a generic "uhh guys, something's not working". It's been
> causing me massive headaches with my work as I'm relying on the spec
> for timing values, but finding that the driver is doing something
> much, much different. I'm more than happy to post these things, but
> I'm not a good enough programmer to just give you patches without
> discussing the fact that I may just not be understanding what's really
> happening.
> Thanks for the help, it's greatly appreciated!
same here :)
the thing is, like bob said, that we don't really know much about what the HW
expects in some of these registers, so unless you can prove your changes to be
correct - e.g. by measurements which fit the theoretical model better, or by
better thruput, it's hard to say if they are correct or not.
so before you worry about how to make a correct patch, just go ahead and
change those initvals to what you believe they should be. if it improves
something, let's talk about how to correctly fix it.
bruno
next prev parent reply other threads:[~2010-09-15 3:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 1:56 [ath5k] Incorrect value for ACK_TIMEOUT Jonathan Guerin
2010-09-15 2:30 ` [ath5k-devel] " Bruno Randolf
2010-09-15 3:01 ` Jonathan Guerin
2010-09-15 3:09 ` Jonathan Guerin
2010-09-15 3:16 ` Bruno Randolf
2010-09-15 3:28 ` Jonathan Guerin
2010-09-15 3:45 ` Bruno Randolf [this message]
2010-09-15 4:11 ` Jonathan Guerin
2010-09-15 7:17 ` Kalle Valo
2010-09-15 7:27 ` Jonathan Guerin
2010-09-15 7:32 ` Bruno Randolf
2010-09-15 7:36 ` Kalle Valo
2010-09-15 10:00 ` Jonathan Guerin
2010-09-15 10:41 ` Kalle Valo
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=201009151245.53194.br1@einfach.org \
--to=br1@einfach.org \
--cc=ath5k-devel@lists.ath5k.org \
--cc=jonathan@guerin.id.au \
--cc=linux-wireless@vger.kernel.org \
--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).