From: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
To: linux-bluetooth@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: [RFCv2 0/6] Draft Software/Virtual AMP80211
Date: Tue, 24 Apr 2012 16:17:34 +0300 [thread overview]
Message-ID: <1335273460-12682-1-git-send-email-Andrei.Emeltchenko.news@gmail.com> (raw)
From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
RFC for Software / Virtual _DRAFT_ implementation of Bluetooth High Speed
by using wireless driver. Currently it can be used for testing Bluetooth
A2MP protocol.
Changes:
RFCv2: Process basic HCI commands and basic data traffic; added skeleton
for Netlink comms, took comments from reviewers.
RFCv1: Initial release.
TODO:
Change names from vamp to <softamp|bt_softamp|etc>
Main ideas:
- Use existing wireless infrastructure nl80211, mac80211.
- Use virtual interface of type NL80211_IFTYPE_BLUETOOTH_AMP. Then all
drivers supporting virtual interface should work.
After modifying iw it will be enabled by adding new virtual interface.
# iw phy <physical device> interface add vamp type vamp
# iw dev
phy#0
Interface vamp
ifindex 6
type Virtual AMP
...
# hciconfig
hci1: Type: AMP Bus: VIRTUAL
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:0 acl:0 sco:0 commands:0 errors:0
...
Andrei Emeltchenko (6):
mac80211: softamp: Adds Bluetooth Software AMP
mac80211: softamp: Adds build config option
hwsim: Adds support for BT SOFTAMP for testing
mac80211: softamp: Handle assoc request
mac80211: softamp: Netlink interface to softamp
mac80211: softamp: Handle data traffic
drivers/net/wireless/mac80211_hwsim.c | 3 +-
include/linux/ieee80211.h | 13 +
include/linux/nl80211.h | 1 +
net/mac80211/Kconfig | 9 +
net/mac80211/Makefile | 2 +
net/mac80211/ieee80211_i.h | 5 +
net/mac80211/iface.c | 9 +
net/mac80211/rx.c | 4 +
net/mac80211/sta_info.h | 4 +
net/mac80211/util.c | 1 +
net/mac80211/virtual_amp.c | 675 +++++++++++++++++++++++++++++++++
net/mac80211/virtual_amp.h | 96 +++++
12 files changed, 821 insertions(+), 1 deletion(-)
create mode 100644 net/mac80211/virtual_amp.c
create mode 100644 net/mac80211/virtual_amp.h
--
1.7.9.5
next reply other threads:[~2012-04-24 13:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 13:17 Andrei Emeltchenko [this message]
2012-04-24 13:17 ` [RFCv2 1/6] mac80211: softamp: Adds Bluetooth Software AMP Andrei Emeltchenko
2012-05-07 11:41 ` Johannes Berg
2012-05-07 11:56 ` Andrei Emeltchenko
2012-05-07 11:59 ` Johannes Berg
2012-04-24 13:17 ` [RFCv2 2/6] mac80211: softamp: Adds build config option Andrei Emeltchenko
2012-04-24 13:17 ` [RFCv2 3/6] hwsim: Adds support for BT SOFTAMP for testing Andrei Emeltchenko
2012-04-24 13:17 ` [RFCv2 4/6] mac80211: softamp: Handle assoc request Andrei Emeltchenko
2012-05-07 11:42 ` Johannes Berg
2012-04-24 13:17 ` [RFCv2 5/6] mac80211: softamp: Netlink interface to softamp Andrei Emeltchenko
2012-05-07 11:42 ` Johannes Berg
2012-04-24 13:17 ` [RFCv2 6/6] mac80211: softamp: Handle data traffic Andrei Emeltchenko
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=1335273460-12682-1-git-send-email-Andrei.Emeltchenko.news@gmail.com \
--to=andrei.emeltchenko.news@gmail.com \
--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).