From: "Tobin C. Harding" <me@tobin.cc>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@linuxdriverproject.org, Tycho Andersen <tycho@tycho.ws>
Subject: Re: [PATCH RFC] remove custom Michael MIC implementation
Date: Fri, 31 Mar 2017 21:21:13 +1100 [thread overview]
Message-ID: <20170331102113.GA2930@eros> (raw)
In-Reply-To: <20170331075851.GB1435@katana>
[-- Attachment #1: Type: text/plain, Size: 1812 bytes --]
On Fri, Mar 31, 2017 at 09:58:51AM +0200, Wolfram Sang wrote:
>
> > The code is untested, I have hardware in the mail.
>
> Cool!
The card I have is a Spectec FCC ID: S2Y-WLAN-11B-G which I believe is
a SDW-823 and should use the ks7010 driver. I am going to attempt to
get it running on a Raspberry Pi B+. I ordered the wrong size break
out board originally so waiting on the new one now.
>
> > If any one is interested and has any comments I would really like to
> > hear them. I am open to all suggestions (even down to trivial coding
> > style issues).
>
> I'll just repeat that the key move to get this driver out of staging is
> to get away from the WEXT interface to CFG80211. Otherwise no chance
> that wireless maintainers will even look at it. This is a huge change
> but once it is done, features like Michael MIC come with it for free
> (from what I recall, I am not a wireless expert myself).
That would explain why I could not find more than the Orinoco driver
using the Michael MIC module directly.
> Without the CFG80211 conversion, replacing the Michael custom
> implementation with the in-kernel one makes the driver a tad better and
> is good exercise. However, it will sadly not help to get the driver out
> of staging.
I'll drop it then. Could you please tell me, is there any thing else
more I need to do to let LKML know that this RFC is dropped? Or is
this reply enough. I don't want to use any ones time unnecessarily.
>
> But if you want a clean WEXT driver first, this is a step in the right
> direction.
>
Let's go for a CFG80211 driver and get out of staging :) So next step
is I guess study the ath6kl driver, learn how CFG80211 is done and
implement that interface in ks7010? Oh, and test that it works.
thanks,
Tobin.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2017-03-31 10:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 4:47 [PATCH RFC] remove custom Michael MIC implementation Tobin C. Harding
2017-03-31 4:47 ` [PATCH RFC] staging: ks7010: " Tobin C. Harding
2017-03-31 5:16 ` Joe Perches
2017-03-31 9:37 ` Tobin C. Harding
2017-03-31 7:58 ` [PATCH RFC] " Wolfram Sang
2017-03-31 10:21 ` Tobin C. Harding [this message]
2017-03-31 10:42 ` Wolfram Sang
2017-04-01 10:40 ` Tobin C. Harding
2017-04-26 23:23 ` Tobin C. Harding
2017-04-28 6:09 ` Wolfram Sang
2017-04-03 5:19 ` Kalle Valo
2017-04-03 9:03 ` Tobin C. Harding
2017-04-03 9:50 ` Toke Høiland-Jørgensen
2017-04-03 10:15 ` Arend Van Spriel
2017-04-03 21:39 ` Tobin C. Harding
2017-04-04 21:31 ` Arend Van Spriel
2017-04-05 1:18 ` Tobin C. Harding
2017-04-03 9:55 ` Kalle Valo
2017-04-03 12:13 ` Greg Kroah-Hartman
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=20170331102113.GA2930@eros \
--to=me@tobin.cc \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tycho@tycho.ws \
--cc=wsa@the-dreams.de \
/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