From: Johannes Berg <johannes@sipsolutions.net>
To: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>,
Marcel Holtmann <marcel@holtmann.org>,
linux-bluetooth@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [RFCv1] mac80211: Adds Software / Virtual AMP 80211
Date: Wed, 18 Apr 2012 07:30:59 -0700 [thread overview]
Message-ID: <4F8ED023.2050605@sipsolutions.net> (raw)
In-Reply-To: <20120418112017.GC19228@aemeltch-MOBL1>
On 4/18/2012 4:20 AM, Andrei Emeltchenko wrote:
> Hi Johannes,
>
> On Tue, Apr 17, 2012 at 07:07:21PM -0700, Johannes Berg wrote:
>>>>>>> I don't get this patch at all. Why am I reviewing some very very basic
>>>>>>> skeleton code when we should be discussing userspace APIs (we have
>>>>>>> already discussed them with a few people years ago), how the AMP is
>>>>>>> going to be managed, how the security handshake is going to work, etc.
>>>
>>> Do we have some outcome from that discussion?
>>
>> This API-defining patch is probably the best we have:
>> http://johannes.sipsolutions.net/patches/kernel/all/2010-10-13-15%
>> 3a24/035-bt3-amp.patch
>
> Thanks for the link. After looking to the patches I think that there are
> some similarities with respect to interface type. As I understood the
> basic idea is the same: create virtual interface. But in your case the
> implementation is really difficult.
>
> Why do we need netlink commands like NL80211_CMD_HCI_AMP_ADD and
> NL80211_CMD_HCI_AMP_DELETE if what we need is to create/delete virtual
> interface which can be done with standard tools with a several lines
> patch to iw:
[...]
That would work, but the plan was to have separate commands because
those commands create a virtual netdev, which we don't want in this case.
And no, given the lack of userspace tools we never tested these patches.
I was more of a "write down API thoughts in code" thing.
johannes
prev parent reply other threads:[~2012-04-18 14:30 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 12:11 [RFCv1] Draft Software/Virtual AMP80211 Andrei Emeltchenko
2012-04-10 12:11 ` [RFCv1] mac80211: Adds Software / Virtual AMP 80211 Andrei Emeltchenko
2012-04-10 12:26 ` Julian Calaby
2012-04-10 12:47 ` Andrei Emeltchenko
2012-04-10 16:39 ` Johannes Berg
2012-04-10 21:17 ` Marcel Holtmann
2012-04-10 21:20 ` Johannes Berg
2012-04-10 21:24 ` Johannes Berg
2012-04-11 7:11 ` Andrei Emeltchenko
2012-04-18 2:03 ` Johannes Berg
2012-04-18 12:15 ` Andrei Emeltchenko
2012-04-18 14:38 ` Johannes Berg
2012-04-18 14:52 ` Andrei Emeltchenko
2012-04-18 15:09 ` Johannes Berg
2012-04-18 15:39 ` Mat Martineau
2012-04-19 6:36 ` Andrei Emeltchenko
2012-04-19 13:28 ` Johannes Berg
2012-04-19 13:39 ` Andrei Emeltchenko
2012-04-19 14:21 ` Johannes Berg
2012-04-10 21:29 ` Marcel Holtmann
2012-04-11 7:05 ` Andrei Emeltchenko
2012-04-18 2:07 ` Johannes Berg
2012-04-18 11:20 ` Andrei Emeltchenko
2012-04-18 11:51 ` Marcel Holtmann
2012-04-18 12:10 ` Andrei Emeltchenko
2012-04-18 12:15 ` Marcel Holtmann
2012-04-18 12:33 ` Andrei Emeltchenko
2012-04-18 13:11 ` Marcel Holtmann
2012-04-18 13:22 ` Andrei Emeltchenko
2012-04-18 14:29 ` Marcel Holtmann
2012-04-18 15:02 ` Andrei Emeltchenko
2012-04-18 14:34 ` Johannes Berg
2012-04-18 14:56 ` Marcel Holtmann
2012-04-18 14:30 ` Johannes Berg [this message]
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=4F8ED023.2050605@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Andrei.Emeltchenko.news@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.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 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).