From: Solomon Peachy <pizza@shaftnet.org>
To: backports@vger.kernel.org
Subject: cw1200 and older kernels (newbie question)
Date: Sat, 20 Jul 2013 08:27:08 -0400 [thread overview]
Message-ID: <20130720122708.GA24056@shaftnet.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1444 bytes --]
As part of the cw1200 mainlining effort, I stripped two chunks out of
the cw1200 driver that only had relevance relevance for older kernels:
1) Workaround for a hardware SDIO bug (needed for < 3.2)
* Formal SDIO-level quirk mainlined in 3.2-rc
* Absence results in device hang with 512-byte SDIO transfers.
2) Support for kernels < 2.6.36
* Driver utilizes the new workqueue API introduced in 2.6.36, taking
advantage of new semantics/features (WQ_HIGHPRI + WQ_CPU_INTENSIVE)
* With older kernels we need a dedicated kthread
Backports has an implementation of the new workqueue API, but it is
expressed in terms of the old API, which is inadequate for the cw1200's
needs.
Perhaps it's a lack of sufficient sleep, but I haven't quite wrapped my
head around how the bakports stuff is put together; it's radically
different that compat-wireless, which had nice orderly patch
directories. :)
Any advice on how I should proceed here? I want to do this the
RightWay, but I don't know what that is yet -- Should I just
add these two patches to the backports tree under patches/unified-drivers?
(The code chunks in question are wrapped with LINUX_VERSION_CODE tests,
so they function fine on newer kernels)
- Solomon
--
Solomon Peachy pizza at shaftnet dot org
Delray Beach, FL ^^ (email/xmpp) ^^
Quidquid latine dictum sit, altum viditur.
[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]
next reply other threads:[~2013-07-20 12:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-20 12:27 Solomon Peachy [this message]
2013-07-20 14:15 ` cw1200 and older kernels (newbie question) Hauke Mehrtens
2013-07-23 22:48 ` Luis R. Rodriguez
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=20130720122708.GA24056@shaftnet.org \
--to=pizza@shaftnet.org \
--cc=backports@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 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.