From: Jukka Rissanen <jukka.rissanen@linux.intel.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH v8 0/5] Bluetooth LE 6LoWPAN using CoC
Date: Wed, 18 Jun 2014 16:37:06 +0300 [thread overview]
Message-ID: <1403098631-4115-1-git-send-email-jukka.rissanen@linux.intel.com> (raw)
Hi,
v8:
- forgot to commit one change to patch 2 so this version now
contains kvec fixes (using kvec instead of iovec). Sorry for the spam.
v7:
- patch 1 is originally from Marcel but with slight modifications
that avoid the sparse error by using kvec instead of iovec in
kernel's memcpy path. I tested this with 6lowpan and also using
L2CAP user sockets.
- avoid chan_ops forward declaration
- this version did not change the GFP_ATOMIC in alloc_skb cb as it
is needed because the alloc function is called in atomic context
- also no need to ref skb because the caller will wait until we
are finished
- various chan ref issues fixed
v6:
- rebased on top of Marcel's "Bluetooth: Provide L2CAP ops callback
for memcpy_fromiovec" patch
- re-wrote the debugfs psm value handler using DEFINE_SIMPLE_ATTRIBUTE
- renamed and refactored the module init/exit functions, also checked
that debugfs_remove() will gracefully accept NULL values
- added comment to disconnect_devices() why we have two separate
lists
v5:
- memory buffer made const in patch 1
- misc changes and refactoring in patch 2
v4:
- renamed l2cap_from_skbuf() to more logical l2cap_copy_into_skbuff()
in l2cap_core.c (patch 1)
- fixed the module usage count code in patch 4
Usage:
In the slave side do this:
$ modprobe bluetooth_6lowpan
$ echo 62 > /sys/kernel/debug/bluetooth/6lowpan_psm
$ hciconfig hci0 leadv
In the master side do this:
$ modprobe bluetooth_6lowpan
$ echo 62 > /sys/kernel/debug/bluetooth/6lowpan_psm
$ echo 'connect E0:06:E6:B7:2A:73 1' > \
/sys/kernel/debug/bluetooth/6lowpan_control
Cheers,
Jukka
Jukka Rissanen (5):
Bluetooth: Provide L2CAP ops callback for memcpy_fromiovec
Bluetooth: 6LoWPAN: Use connected oriented channel instead of fixed
one
Bluetooth: 6LoWPAN: Create a kernel module
Bluetooth: 6LoWPAN: Count module usage
Bluetooth: 6LoWPAN: Remove network devices when unloading
include/net/bluetooth/hci.h | 1 -
include/net/bluetooth/hci_core.h | 1 -
include/net/bluetooth/l2cap.h | 30 +-
net/bluetooth/6lowpan.c | 857 +++++++++++++++++++++++++++++----------
net/bluetooth/6lowpan.h | 47 ---
net/bluetooth/Kconfig | 6 +-
net/bluetooth/Makefile | 4 +-
net/bluetooth/a2mp.c | 1 +
net/bluetooth/hci_core.c | 45 --
net/bluetooth/hci_event.c | 3 -
net/bluetooth/l2cap_core.c | 26 +-
net/bluetooth/l2cap_sock.c | 34 +-
12 files changed, 718 insertions(+), 337 deletions(-)
delete mode 100644 net/bluetooth/6lowpan.h
--
1.8.3.1
next reply other threads:[~2014-06-18 13:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 13:37 Jukka Rissanen [this message]
2014-06-18 13:37 ` [PATCH v8 1/5] Bluetooth: Provide L2CAP ops callback for memcpy_fromiovec Jukka Rissanen
2014-06-18 13:37 ` [PATCH v8 2/5] Bluetooth: 6LoWPAN: Use connected oriented channel instead of fixed one Jukka Rissanen
2014-06-18 13:37 ` [PATCH v8 3/5] Bluetooth: 6LoWPAN: Create a kernel module Jukka Rissanen
2014-06-18 13:37 ` [PATCH v8 4/5] Bluetooth: 6LoWPAN: Count module usage Jukka Rissanen
2014-06-18 13:37 ` [PATCH v8 5/5] Bluetooth: 6LoWPAN: Remove network devices when unloading Jukka Rissanen
2014-06-23 10:16 ` [PATCH v8 0/5] Bluetooth LE 6LoWPAN using CoC Marcel Holtmann
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=1403098631-4115-1-git-send-email-jukka.rissanen@linux.intel.com \
--to=jukka.rissanen@linux.intel.com \
--cc=linux-bluetooth@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.