From: Solomon Peachy <pizza@shaftnet.org>
To: linux-wireless@vger.kernel.org
Subject: Re: RFCv2: ST-E cw1200 driver
Date: Mon, 24 Dec 2012 14:00:25 -0500 [thread overview]
Message-ID: <20121224190024.GB9739@shaftnet.org> (raw)
In-Reply-To: <1356218312-13616-1-git-send-email-pizza@shaftnet.org>
[-- Attachment #1: Type: text/plain, Size: 1210 bytes --]
On Sat, Dec 22, 2012 at 06:18:15PM -0500, Solomon Peachy wrote:
> Okay, here's the second pass. Changes from v1:
I just finised going through a code drop that Sony provided
(v6.1.1.B.1.10 for the Xperia go/advance/sola/U) and merged a bunch of
changes they made. I've also fixed a few more checkpatch warnings.
The most notable change is that the "bh_thread" abombination is gone,
but in its place is a single high-priority workqueue.
This code is undergoing testing on my desk now. Needless to say, any
help with testing this out would be greatly appreciated.
To that effect, if anyone's interested in tracking my tree I created a
git tree of my work-in-progress, built on top of compat-wireless 3.6.
Its initial commit was the RFCv2 code.
git://git.shaftnet.org/compat-wireless-cw1200.git
(I don't have an SDIO-capable target capable of running anything newer
than Linux 3.2 at the moment, so I need to stick with compat-wireless
for now)
Anyway, back to the bit mines.
- Solomon
--
Solomon Peachy pizza at shaftnet dot org
Melbourne, FL ^^ (mail/jabber/gtalk) ^^
Quidquid latine dictum sit, altum viditur.
[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2012-12-24 19:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-22 23:18 RFCv2: ST-E cw1200 driver Solomon Peachy
2012-12-22 23:18 ` [PATCH 01/17] cw1200: v2: low-level hardware I/O functions Solomon Peachy
2012-12-22 23:18 ` [PATCH 02/17] cw1200: v2: internal tx queue tracking and handling Solomon Peachy
2012-12-22 23:18 ` [PATCH 03/17] cw1200: v2: Scan implementation Solomon Peachy
2012-12-22 23:18 ` [PATCH 04/17] cw1200: v2: power management Solomon Peachy
2012-12-22 23:18 ` [PATCH 05/17] cw1200: v2: firmware loading Solomon Peachy
2012-12-22 23:18 ` [PATCH 06/17] cw1200: v2: mini-ap support code Solomon Peachy
2012-12-22 23:18 ` [PATCH 07/17] cw1200: v2: debuging hooks Solomon Peachy
2012-12-22 23:18 ` [PATCH 08/17] cw1200: v2: test tool support Solomon Peachy
2012-12-22 23:18 ` [PATCH 09/17] cw1200: v2: 802.11 station api Solomon Peachy
2012-12-22 23:18 ` [PATCH 10/17] cw1200: v2: packet transmit/receive handling Solomon Peachy
2012-12-22 23:18 ` [PATCH 11/17] cw1200: v2: WSM (ie host-firmware) host interface Solomon Peachy
2013-01-02 14:37 ` Bob Copeland
2013-01-02 15:07 ` Solomon Peachy
2012-12-22 23:18 ` [PATCH 12/17] cw1200: v2: main processing loop Solomon Peachy
2012-12-22 23:18 ` [PATCH 13/17] cw1200: v2: common registration/setup code Solomon Peachy
2012-12-22 23:18 ` [PATCH 14/17] cw1200: v2: driver state and definitions Solomon Peachy
2012-12-22 23:18 ` [PATCH 15/17] cw1200: v2: SDIO and SPI glue code, and platform definitions Solomon Peachy
2012-12-22 23:18 ` [PATCH 16/17] cw1200: v2: kbuild integration Solomon Peachy
2012-12-22 23:18 ` [PATCH 17/17] cw1200: v2: add to drivers/staging Solomon Peachy
2012-12-24 19:00 ` Solomon Peachy [this message]
2013-01-11 15:58 ` RFCv2: ST-E cw1200 driver Solomon Peachy
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=20121224190024.GB9739@shaftnet.org \
--to=pizza@shaftnet.org \
--cc=linux-wireless@vger.kernel.org \
/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).