From: Arend Van Spriel <arend.vanspriel@broadcom.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>,
"Tobin C. Harding" <me@tobin.cc>
Cc: Kalle Valo <kvalo@codeaurora.org>,
Tycho Andersen <tycho@tycho.ws>, Wolfram Sang <wsa@the-dreams.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org
Subject: Re: [PATCH RFC] remove custom Michael MIC implementation
Date: Mon, 3 Apr 2017 12:15:15 +0200 [thread overview]
Message-ID: <9bfd1405-fd32-e896-b6f0-09ffedeaac33@broadcom.com> (raw)
In-Reply-To: <87y3vhx1ju.fsf@alrua-karlstad>
seems we are missing out again?
On 3-4-2017 11:50, Toke Høiland-Jørgensen wrote:
> "Tobin C. Harding" <me@tobin.cc> writes:
>
>> Except one: do you know off the top of your head of a canonical
>> implementation of a softmac wi-fi driver.
>
> I'll suggest taking a look at the ath9k driver :)
Looking at ks7010 driver it looks like it has 802.11 stack in firmware
and not sure if Renesas is actively supporting this effort to come up
with mac80211-friendly firmware or provide detailed chip info.
Regards,
Arend
next prev parent reply other threads:[~2017-04-03 10:15 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
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 [this message]
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=9bfd1405-fd32-e896-b6f0-09ffedeaac33@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=me@tobin.cc \
--cc=toke@toke.dk \
--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