From: "Tobin C. Harding" <me@tobin.cc>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
"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: Tue, 4 Apr 2017 07:39:10 +1000 [thread overview]
Message-ID: <20170403213910.GA7480@eros> (raw)
In-Reply-To: <9bfd1405-fd32-e896-b6f0-09ffedeaac33@broadcom.com>
On Mon, Apr 03, 2017 at 12:15:15PM +0200, Arend Van Spriel wrote:
> seems we are missing out again?
Sorry, I don't understand what this comment means?
> 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.
Thanks for taking a look. If the ks7010 driver has 802.11 stack in
firmware does that mean it is not compatible with using the kernel
mac80211 stack with the current firmware? I do not have my hopes up
about getting any chip information out of Renesas, all I think we have
to go in is the current WEXT driver.
This is an exercise in learning for me, but I do not want to take any
ones time up with a project that is not that useful. Is getting the
ks7010 driver out of staging something that is of use to the kernel
community or are there other wi-fi tasks that our time is better spent
on?
thanks,
Tobin.
next prev parent reply other threads:[~2017-04-03 21:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1490935659-7196-1-git-send-email-me@tobin.cc>
[not found] ` <20170331075851.GB1435@katana>
[not found] ` <20170331102113.GA2930@eros>
2017-04-03 5:19 ` [PATCH RFC] remove custom Michael MIC implementation 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 [this message]
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=20170403213910.GA7480@eros \
--to=me@tobin.cc \
--cc=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=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;
as well as URLs for NNTP newsgroup(s).