From: "Alina Friedrichsen" <x-alina@gmx.net>
To: Bob Copeland <bcopeland@gmail.com>, johannes@sipsolutions.net
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ath5k: Set TSF fix
Date: Mon, 26 Jan 2009 15:01:30 +0100 [thread overview]
Message-ID: <20090126140130.14450@gmx.net> (raw)
In-Reply-To: <b6c5339f0901250847i5f9f98bcl4ebec04027d7c93c@mail.gmail.com>
Hello!
> > Either way, I think the changelog should back up the claim by
> > _something_. Even if it's just "tested on device XXX, old way doesn=
't
> > work, new way does" or "looked at legacy HAL code" or ...
>=20
> Agreed, "tested on..." would be good. I looked at the HAL and it
> doesn't have a set tsf function, only reset.
The old code does not work on:
AR5418+AR2122 (ath9k)
AR5416+AR2133 (ath9k)
The new code is tested on:
AR5418+AR2122 (ath9k)
AR5416+AR2133 (ath9k)
AR5001X+ (ath5k)
AR5007EG (ath5k)
The old code was taken from:
https://dev.openwrt.org/browser/trunk/package/madwifi/patches/383-ibss_=
hostap.patch
(by Sven-Ola Tuecke)
Regards
Alina
--=20
NUR NOCH BIS 31.01.! GMX FreeDSL - Telefonanschluss + DSL=20
f=FCr nur 16,37 EURO/mtl.!* http://dsl.gmx.de/?ac=3DOM.AD.PD003K11308T4=
569a
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-01-26 14:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-24 8:12 [PATCH] ath5k: Set TSF fix Alina Friedrichsen
2009-01-25 16:41 ` Bob Copeland
2009-01-25 16:45 ` Johannes Berg
2009-01-25 16:47 ` Bob Copeland
2009-01-26 14:01 ` Alina Friedrichsen [this message]
2009-01-27 21:25 ` John W. Linville
-- strict thread matches above, loose matches on Subject: below --
2009-03-02 22:29 Alina Friedrichsen
2009-03-02 22:44 ` Bob Copeland
2009-03-02 23:02 ` Alina Friedrichsen
2009-03-02 23:31 ` Bob Copeland
2009-03-03 21:45 ` 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=20090126140130.14450@gmx.net \
--to=x-alina@gmx.net \
--cc=bcopeland@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).