From: "John W. Linville" <linville@tuxdriver.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
"doug.dahlby" <Doug.Dahlby@atheros.com>,
Atheros Internal ath9k development team <ath9k-devel@atheros.com>,
Cliff Holden <Cliff.Holden@atheros.com>,
Zhifeng Cai <zhifeng.cai@atheros.com>,
Pavel Roskin <proski@gnu.org>
Subject: Re: ath9k initvals-tool - integrity checks | reformat | synchronize
Date: Wed, 21 Apr 2010 09:06:58 -0400 [thread overview]
Message-ID: <20100421130658.GC5072@tuxdriver.com> (raw)
In-Reply-To: <w2v43e72e891004210029g15eaf50fwbca39a73b7c46268@mail.gmail.com>
On Wed, Apr 21, 2010 at 12:29:26AM -0700, Luis R. Rodriguez wrote:
> In the v2 patch cover letter for AR9003 I noted how I had started some
> simple initval userspcae tool to check the integrity of the initvals.
> Since we also had some discussions about the possible format changes
> for it I've gone ahead and extended the same tool to also reformat our
> initvals to any format we like and at the same time allowing us to
> verify the integrity is kept. This same tool can now be used by us at
> Atheros to check for changes quickly between our Atheros HAL and the
> ath9k_hw module. I've written some docs how to do all this here:
>
> http://wireless.kernel.org/en/users/Drivers/ath9k_hw/initvals-tool
Just as an aside, I'd like to thank you for the amount of information
you have added to the Linux Wireless wiki. It is a really great
resource for our community.
Thanks!
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2010-04-21 13:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 7:29 ath9k initvals-tool - integrity checks | reformat | synchronize Luis R. Rodriguez
2010-04-21 13:06 ` John W. Linville [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=20100421130658.GC5072@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=Cliff.Holden@atheros.com \
--cc=Doug.Dahlby@atheros.com \
--cc=ath9k-devel@atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=proski@gnu.org \
--cc=zhifeng.cai@atheros.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.