From: Solomon Peachy <pizza@shaftnet.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Pontus Fuchs <pontus.fuchs@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: RFCv3: ST-E CW1200 WLAN driver
Date: Thu, 31 Jan 2013 20:54:42 -0500 [thread overview]
Message-ID: <20130201015442.GA2174@shaftnet.org> (raw)
In-Reply-To: <20130130223232.GA7307@shaftnet.org>
[-- Attachment #1: Type: text/plain, Size: 1537 bytes --]
On Wed, Jan 30, 2013 at 05:32:32PM -0500, Solomon Peachy wrote:
> This is my current to-do list:
Was unexpectedly able to spend some time on this today!
> * One final Kconfig option to eliminate
Done.
> * A possible crash (reported not three hours ago) that needs confirming
Turns out to not be a crash, but it is a real problem. The driver can
get into an inconsistent internal state if a connection loss event
occurs. Proper fix triggers deadlock due to interdependencies.
Hackish workaround in place now, and I'm working on a proper fix. Or
will be once my head stops throbbing. The code is needlessly complex
and interdependent, and unravelling a bit at a time is difficult.
This state problem actually explains a bunch of other odd quirks I've
seen, so fixing it properly is pretty important.
> * Hot unplug is still iffy (but better!)
More progress here, but more work to be done. (Only a problem now if
device isn't idle when yanked -- if the supplicant is attached, it
deadlocks still)
> * Reworked SPI interrupt delivery completely untested
> * IBSS is still busted (haven't had time to tackle it properly)
> * Rebase against 3.8
> * Investigate adding OF bindings that can be used instead of platform_data
No progress here yet.
I'll post another patch set this weekend.
- 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:[~2013-02-01 1:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 14:06 RFCv3: ST-E CW1200 WLAN driver Solomon Peachy
2013-01-12 14:06 ` [PATCH 01/15] cw1200: v3: low-level hadrware I/O functions Solomon Peachy
2013-01-12 14:06 ` [PATCH 02/15] cw1200: v3: internal tx queue handling and tracking Solomon Peachy
2013-01-12 14:06 ` [PATCH 03/15] cw1200: v3: scanning implementation Solomon Peachy
2013-01-12 14:06 ` [PATCH 04/15] cw1200: v3: power management Solomon Peachy
2013-01-12 14:06 ` [PATCH 05/15] cw1200: v3: firmware loading Solomon Peachy
2013-01-12 14:06 ` [PATCH 06/15] cw1200: v3: mini-ap support code Solomon Peachy
2013-01-12 14:06 ` [PATCH 07/15] cw1200: v3: debugging hooks and test tool support Solomon Peachy
2013-01-12 14:06 ` [PATCH 08/15] cw1200: v3: 802.11 station API Solomon Peachy
2013-01-12 14:06 ` [PATCH 09/15] cw1200: v3: packet transmit and receiving Solomon Peachy
2013-01-12 14:06 ` [PATCH 10/15] cw1200: v3: WSM (host-firmware) interface glue Solomon Peachy
2013-01-12 14:06 ` [PATCH 11/15] cw1200: v3: main processing loop Solomon Peachy
2013-01-12 14:06 ` [PATCH 12/15] cw1200: v3: common state, definitions, and registration handling Solomon Peachy
2013-01-12 14:06 ` [PATCH 13/15] cw1200: v3: SDIO and SPI glue code and platform definitions Solomon Peachy
2013-01-12 14:06 ` [PATCH 14/15] cw1200: v3: Kbuild integration Solomon Peachy
2013-01-12 14:06 ` [PATCH 15/15] cw1200: v3: Add to drivers/staging, and a MAINTAINERS entry Solomon Peachy
2013-01-14 12:17 ` RFCv3: ST-E CW1200 WLAN driver Pontus Fuchs
2013-01-30 19:02 ` John W. Linville
2013-01-30 22:32 ` Solomon Peachy
2013-02-01 1:54 ` Solomon Peachy [this message]
2013-02-07 4:21 ` 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=20130201015442.GA2174@shaftnet.org \
--to=pizza@shaftnet.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=pontus.fuchs@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 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.