From: Jouni Malinen <j@w1.fi>
To: Alina Friedrichsen <x-alina@gmx.net>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
johannes@sipsolutions.net, Dan Williams <dcbw@redhat.com>
Subject: Re: [PATCH] ath9k: Set TSF fix
Date: Wed, 28 Jan 2009 20:04:25 +0200 [thread overview]
Message-ID: <20090128180425.GA5069@jm.kir.nu> (raw)
In-Reply-To: <20090124215322.259390@gmx.net>
On Sat, Jan 24, 2009 at 10:53:22PM +0100, Alina Friedrichsen wrote:
> Hallo Dan!
Uhm.. Dan was not on To: or Cc: field.. Anyway..
> The old version I have taken from an several years old madwifi patch. It works only with old ath5k hardware. With my new Atheros-Cards the lower 32 bits of the TSF are only set to zero, not set to the new value. The new code does work with all my ath5k and ath9k cards.
The proposed ath9k change looks fine. The AR_TSF_L32 write does not
actually change TSF and hardware will just store the value temporarily.
The actual change is started by writing the AR_TSF_U32.
It looks like there are some corner cases where the TSF may not actually
change if it is being updated (e.g., a Beacon is received) or we are
waking up from sleep mode etc., but I would hope they do not matter too
much with this debugging need.
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2009-01-28 18:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-24 8:15 [PATCH] ath9k: Set TSF fix Alina Friedrichsen
2009-01-24 14:22 ` Johannes Berg
2009-01-24 14:29 ` Dan Williams
2009-01-24 21:53 ` Alina Friedrichsen
2009-01-28 18:04 ` Jouni Malinen [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-02 22:28 Alina Friedrichsen
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=20090128180425.GA5069@jm.kir.nu \
--to=j@w1.fi \
--cc=dcbw@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=x-alina@gmx.net \
/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).