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: Sat, 1 Apr 2017 21:40:48 +1100 [thread overview]
Message-ID: <20170401104048.GB3755@eros> (raw)
In-Reply-To: <20170331104222.GA2873@katana>
[-- Attachment #1: Type: text/plain, Size: 2204 bytes --]
On Fri, Mar 31, 2017 at 12:42:22PM +0200, Wolfram Sang wrote:
> Hi,
>
> > 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.
>
> Sorry, likely not. It is an early SDW-821 and has a MediaTek chipset for
> which no driver is known:
> https://wikidevi.com/wiki/Spectec_SDW-821_%28MediaTek%29
Oh damn.
>
> For SDW-821 (SD size) and KS7010, you'd need a "S2Y-WLAN-11G-K" (but I
> have never seen one yet):
> https://wikidevi.com/wiki/Spectec_SDW-821_%28KeyStream%29
>
> One can find an SDW-823 (microSD) "S2Y-MWLAN-11B-G" once in a while:
> https://wikidevi.com/wiki/Spectec_SDW-823
That's actually the page I was reading, I didn't notice the 'M' in there.
> > > 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.
>
> That should do.
>
> > 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.
>
> Yes, have a look around and check if you like that task. I might have a
> spare SDW-823 lying around if you are up to it. But check first, it is
> not a trivial task. On the pro side, there are tons of interesting
> things about WiFI and kernel development to learn on the way :)
I like the task. You had me at 'this is a huge change...' in your
first email. Whether I have the ability is yet to be seen. Thanks for
the offer of the card, let's wait first to see if I can make any
progress that warrants testing. The new breakout board turned up in
the mail today, super glad to read your email before I spent the day
tomorrow trying to get it working :)
>
> Regards,
>
> Wolfram
>
Cheers Wolfram,
Tobin.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2017-04-01 10:40 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
2017-03-31 10:42 ` Wolfram Sang
2017-04-01 10:40 ` Tobin C. Harding [this message]
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=20170401104048.GB3755@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