From: Marcel Holtmann <marcel@holtmann.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>,
linux-bluetooth@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [RFCv1] mac80211: Adds Software / Virtual AMP 80211
Date: Tue, 10 Apr 2012 23:29:38 +0200 [thread overview]
Message-ID: <1334093378.16897.62.camel@aeonflux> (raw)
In-Reply-To: <4F84A422.3030900@sipsolutions.net>
Hi Johannes,
> >> 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.
> >
> > adding AMP (meaning Bluetooth Alternate MAC/PHY in case anybody cares)
> > for SoftMac WiFi cards should be done solely in kernel space between
> > Bluetooth core and mac80211. All the FullMac cards will expose the HCI
> > AMP directly via the Bluetooth core. See Marvell solution for example.
> >
> > If we require a userspace interaction, I think we are doing something
> > wrong here. And as far as I can tell, the only tricky part is the WPA2
> > PSK 4-way handshake. We would need a kernel implementation for that.
>
> You already know I disagree, I don't want this code re-implemented in
> kernel space when adding a few tightly controlled APIs is all it needs
> to use an existing implementation of the relevant mechanisms.
I know that, but I still think it is the right approach here. It might
take me a bit longer to convince you ;)
The whole AMP control goes via A2MP and L2CAP and both are fully
implemented inside the kernel. In theory we do not even need to expose
HCI AMP interfaces to userspace. We just do it for convince right now so
we can sniff the transfers, but even that is no longer needed with the
addition of the Bluetooth monitor socket.
Anyway, my real point is that we should not need any extra userspace API
to add support for Bluetooth HS in mac80211.
Regards
Marcel
next prev parent reply other threads:[~2012-04-10 21:29 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 [this message]
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
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=1334093378.16897.62.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=Andrei.Emeltchenko.news@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-wireless@vger.kernel.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).