* Re: [PATCH 6/9] android/bluetooth: Add support for remote device RSSI
From: Szymon Janc @ 2013-12-12 8:58 UTC (permalink / raw)
To: Anderson Lizardo; +Cc: BlueZ development
In-Reply-To: <CAJdJm_N2aABBteKtWyRXh_-a8Oy722BMbZSrH_koNYbY8F5hpA@mail.gmail.com>
Hi Anderson,
> Hi Szymon,
>
> On Wed, Dec 11, 2013 at 7:31 AM, Szymon Janc <szymon.janc@tieto.com> wrote:
> \> @@ -2306,11 +2309,13 @@ static uint8_t
> get_device_friendly_name(struct device *dev)
> >
> > static uint8_t get_device_rssi(struct device *dev)
> > {
> > - DBG("Not implemented");
> > + if (!dev->rssi)
> > + return HAL_STATUS_FAILED;
>
> 0 dBm is a valid RSSI value, so I suppose this code needs some other
> way to identify an uninitialized value (e.g. a second boolean field.)
Kernel sends rssi==0 if rssi info was not present on inquiry so I used this
value, but maybe it should use 127 for that.. ? (yet, this might cause trouble
as linux bluetoothd is checking 0 as well)
--
BR
Szymon Janc
^ permalink raw reply
* Re: [PATCH v2 1/8] android/pts: Remove PIXIT info from PICS files
From: Johan Hedberg @ 2013-12-12 8:29 UTC (permalink / raw)
To: Szymon Janc; +Cc: linux-bluetooth
In-Reply-To: <1386775638-24941-1-git-send-email-szymon.janc@tieto.com>
Hi Szymon,
On Wed, Dec 11, 2013, Szymon Janc wrote:
> Full PIXIT configuration will be provided in separate files.
> ---
> android/pics-did.txt | 11 -----------
> android/pics-gap.txt | 5 -----
> android/pics-hid.txt | 5 -----
> android/pics-opp.txt | 5 -----
> android/pics-pan.txt | 5 -----
> android/pics-pbap.txt | 5 -----
> 6 files changed, 36 deletions(-)
All patches have been applied. Thanks.
Johan
^ permalink raw reply
* Re: [PATCH 2/2] Bluetooth: Fix test for lookup_dev return value
From: Marcel Holtmann @ 2013-12-12 8:01 UTC (permalink / raw)
To: Johan Hedberg; +Cc: linux-bluetooth@vger.kernel.org development
In-Reply-To: <1386834801-1635-2-git-send-email-johan.hedberg@gmail.com>
Hi Johan,
> The condition wouldn't have previously caused -ENOENT to be returned if
> dev was NULL. The proper condition should be if (!dev || !dev->netdev).
>
> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
> ---
> net/bluetooth/6lowpan.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
patch has been applied to bluetooth-next tree.
Regards
Marcel
^ permalink raw reply
* Re: [PATCH 1/2] Bluetooth: Add missing 6lowpan.h include
From: Marcel Holtmann @ 2013-12-12 8:00 UTC (permalink / raw)
To: Johan Hedberg; +Cc: linux-bluetooth@vger.kernel.org development
In-Reply-To: <1386834801-1635-1-git-send-email-johan.hedberg@gmail.com>
Hi Johan,
> The 6lowpan.c file was missing an #include statement for 6lowpan.h.
> Without it we get the following type of warnings:
>
> net/bluetooth/6lowpan.c:320:5: warning: symbol 'bt_6lowpan_recv' was not declared. Should it be static?
> net/bluetooth/6lowpan.c:737:5: warning: symbol 'bt_6lowpan_add_conn' was not declared. Should it be static?
> net/bluetooth/6lowpan.c:805:5: warning: symbol 'bt_6lowpan_del_conn' was not declared. Should it be static?
> net/bluetooth/6lowpan.c:878:5: warning: symbol 'bt_6lowpan_init' was not declared. Should it be static?
> net/bluetooth/6lowpan.c:883:6: warning: symbol 'bt_6lowpan_cleanup' was not declared. Should it be static?
>
> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
> ---
> net/bluetooth/6lowpan.c | 2 ++
> 1 file changed, 2 insertions(+)
patch has been applied to bluetooth-next tree.
Regards
Marcel
^ permalink raw reply
* Re: [PATCH] l2cap-tester: Close sk in error path
From: Johan Hedberg @ 2013-12-12 7:57 UTC (permalink / raw)
To: Andrei Emeltchenko; +Cc: linux-bluetooth
In-Reply-To: <1386834508-9929-1-git-send-email-Andrei.Emeltchenko.news@gmail.com>
Hi Andrei,
On Thu, Dec 12, 2013, Andrei Emeltchenko wrote:
> This fixes resource leak warnings.
> ---
> tools/l2cap-tester.c | 2 ++
> 1 file changed, 2 insertions(+)
Applied. Thanks.
Johan
^ permalink raw reply
* [PATCH 2/2] Bluetooth: Fix test for lookup_dev return value
From: johan.hedberg @ 2013-12-12 7:53 UTC (permalink / raw)
To: linux-bluetooth
In-Reply-To: <1386834801-1635-1-git-send-email-johan.hedberg@gmail.com>
From: Johan Hedberg <johan.hedberg@intel.com>
The condition wouldn't have previously caused -ENOENT to be returned if
dev was NULL. The proper condition should be if (!dev || !dev->netdev).
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
---
net/bluetooth/6lowpan.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/bluetooth/6lowpan.c b/net/bluetooth/6lowpan.c
index 3cbb1d14c304..5ad8b483efa3 100644
--- a/net/bluetooth/6lowpan.c
+++ b/net/bluetooth/6lowpan.c
@@ -330,7 +330,7 @@ int bt_6lowpan_recv(struct l2cap_conn *conn, struct sk_buff *skb)
return -ENOENT;
dev = lookup_dev(conn);
- if (dev && !dev->netdev)
+ if (!dev || !dev->netdev)
return -ENOENT;
err = recv_pkt(skb, dev->netdev, conn);
--
1.8.4.2
^ permalink raw reply related
* [PATCH 1/2] Bluetooth: Add missing 6lowpan.h include
From: johan.hedberg @ 2013-12-12 7:53 UTC (permalink / raw)
To: linux-bluetooth
From: Johan Hedberg <johan.hedberg@intel.com>
The 6lowpan.c file was missing an #include statement for 6lowpan.h.
Without it we get the following type of warnings:
net/bluetooth/6lowpan.c:320:5: warning: symbol 'bt_6lowpan_recv' was not declared. Should it be static?
net/bluetooth/6lowpan.c:737:5: warning: symbol 'bt_6lowpan_add_conn' was not declared. Should it be static?
net/bluetooth/6lowpan.c:805:5: warning: symbol 'bt_6lowpan_del_conn' was not declared. Should it be static?
net/bluetooth/6lowpan.c:878:5: warning: symbol 'bt_6lowpan_init' was not declared. Should it be static?
net/bluetooth/6lowpan.c:883:6: warning: symbol 'bt_6lowpan_cleanup' was not declared. Should it be static?
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
---
net/bluetooth/6lowpan.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/net/bluetooth/6lowpan.c b/net/bluetooth/6lowpan.c
index ba840fe2c555..3cbb1d14c304 100644
--- a/net/bluetooth/6lowpan.c
+++ b/net/bluetooth/6lowpan.c
@@ -26,6 +26,8 @@
#include <net/bluetooth/hci_core.h>
#include <net/bluetooth/l2cap.h>
+#include "6lowpan.h"
+
#include "../ieee802154/6lowpan.h" /* for the compression support */
#define IFACE_NAME_TEMPLATE "bt%d"
--
1.8.4.2
^ permalink raw reply related
* [PATCH] l2cap-tester: Close sk in error path
From: Andrei Emeltchenko @ 2013-12-12 7:48 UTC (permalink / raw)
To: linux-bluetooth
From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
This fixes resource leak warnings.
---
tools/l2cap-tester.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tools/l2cap-tester.c b/tools/l2cap-tester.c
index 505ac79..e4dade2 100644
--- a/tools/l2cap-tester.c
+++ b/tools/l2cap-tester.c
@@ -503,6 +503,7 @@ static int create_l2cap_sock(struct test_data *data, uint16_t psm)
master_bdaddr = hciemu_get_master_bdaddr(data->hciemu);
if (!master_bdaddr) {
tester_warn("No master bdaddr");
+ close(sk);
return -ENODEV;
}
@@ -701,6 +702,7 @@ static void test_server(const void *test_data)
tester_warn("listening on socket failed: %s (%u)",
strerror(errno), errno);
tester_test_failed();
+ close(sk);
return;
}
--
1.8.3.2
^ permalink raw reply related
* Re: openSUSE 13.1: bt headsets lose connection
From: Bastien Nocera @ 2013-12-12 0:31 UTC (permalink / raw)
To: colbec; +Cc: linux-bluetooth@vger.kernel.org
In-Reply-To: <1385236029.2236.7.camel@linux-3kti>
On Sat, 2013-11-23 at 14:47 -0500, Colin Beckingham wrote:
> In openSUSE 12.3 bluetooth operations were mostly ok. In the last few
> days I have upgraded from 12.3 to 13.1 and now none of my bt headsets
> can remain connected. Pairing is not a problem, but then they
> immediately disconnect.
>
> I have posted a bug at gnome-bluetooth, but it seems that a previous
> similar bug has been tested and found that gnome-bluetooth may be
> excluded. Here is the bug report:
>
> https://bugzilla.gnome.org/show_bug.cgi?id=712379
>
> I have run a test connection using bluetoothd (5.11) in debug mode, and
> have attached the output in file bluedump.txt.
>
> Also I have tried running bluetoothd with the -E option and no change.
>
> I understand that it is possible this may already be known, and that
> pulseaudio may be involved. But since I have the debug output I thought
> I would check with the linux-bluetooth community first.
If your headset only has support for HFP/Hansfree, it likely won't work
with PulseAudio yet/anymore. PulseAudio is currently adding support for
this.
Cheers
^ permalink raw reply
* Re: [PATCH 6/9] android/bluetooth: Add support for remote device RSSI
From: Anderson Lizardo @ 2013-12-12 0:04 UTC (permalink / raw)
To: Szymon Janc; +Cc: BlueZ development
In-Reply-To: <1386757887-29018-6-git-send-email-szymon.janc@tieto.com>
Hi Szymon,
On Wed, Dec 11, 2013 at 7:31 AM, Szymon Janc <szymon.janc@tieto.com> wrote:
\> @@ -2306,11 +2309,13 @@ static uint8_t
get_device_friendly_name(struct device *dev)
>
> static uint8_t get_device_rssi(struct device *dev)
> {
> - DBG("Not implemented");
> + if (!dev->rssi)
> + return HAL_STATUS_FAILED;
0 dBm is a valid RSSI value, so I suppose this code needs some other
way to identify an uninitialized value (e.g. a second boolean field.)
>
> - /* TODO */
> + send_device_property(&dev->bdaddr, HAL_PROP_DEVICE_RSSI,
> + sizeof(dev->rssi), &dev->rssi);
>
> - return HAL_STATUS_FAILED;
> + return HAL_STATUS_SUCCESS;
> }
Best Regards,
--
Anderson Lizardo
Instituto Nokia de Tecnologia - INdT
Manaus - Brazil
^ permalink raw reply
* Re: [PATCH BlueZ] build: Add coverage support
From: Anderson Lizardo @ 2013-12-11 22:31 UTC (permalink / raw)
To: Luiz Augusto von Dentz; +Cc: BlueZ development
In-Reply-To: <1386759341-14346-1-git-send-email-luiz.dentz@gmail.com>
Hi Luiz,
On Wed, Dec 11, 2013 at 7:55 AM, Luiz Augusto von Dentz
<luiz.dentz@gmail.com> wrote:
> --- a/acinclude.m4
> +++ b/acinclude.m4
> @@ -51,6 +51,15 @@ AC_DEFUN([MISC_FLAGS], [
> misc_ldflags="$misc_ldflags -pie"
> fi
> ])
> + AC_ARG_ENABLE(coverage, AC_HELP_STRING([--enable-coverage],
> + [enable coverage flags]), [
> + AC_PATH_PROG([LCOV], [lcov])
> + if (test "$LCOV" && test "${enableval}" = "yes"); then
> + misc_cflags="$misc_cflags -ftest-coverage"
> + misc_cflags="$misc_cflags -fprofile-arcs"
> + misc_ldflags="$misc_ldflags -gcov"
> + fi
> + ])
I believe the current recommended (or at least simpler) way to enable
coverage is to use "--coverage" option (both as CFLAGS and LDFLAGS),
instead of separate -ftest-coverage/-fprofile-arcs/-gcov options.
Check "man gcc" for details.
> AC_SUBST([MISC_CFLAGS], $misc_cflags)
> AC_SUBST([MISC_LDFLAGS], $misc_ldflags)
> ])
Best Regards,
--
Anderson Lizardo
Instituto Nokia de Tecnologia - INdT
Manaus - Brazil
^ permalink raw reply
* Re: mouse not found with bluez5 but was fine with bluez4
From: Bastien Nocera @ 2013-12-11 21:49 UTC (permalink / raw)
To: Brian J. Murrell; +Cc: Johan Hedberg, linux-bluetooth
In-Reply-To: <1386792806.3586.6.camel@bmurrell-mobl.amr.corp.intel.com>
On Wed, 2013-12-11 at 15:13 -0500, Brian J. Murrell wrote:
> On Wed, 2013-12-11 at 21:25 +0200, Johan Hedberg wrote:
> > Hi Brian,
>
> Hi Johan,
>
> > I'm not sure if I'm interpreting this right, but it seems the device is
> > in HID mode and not HCI (normal Bluetooth) mode?
>
> I dunno. I'm just the user. :-)
>
> > Have you tried running
> > the hid2hci tool (part of BlueZ)?
>
> Not yet. It wasn't installed by default on F20. When I did though,
> things went much better:
>
> $ bluetoothctl
> [NEW] Controller 00:02:72:1E:E0:12 pc.interlinx.bc.ca-0 [default]
> [NEW] Device 00:0D:E6:68:B4:6F Samsung WEP850
> [NEW] Device 70:F3:95:3E:92:34 brian-laptop
> [NEW] Device 7C:1E:52:6E:59:D2 Microsoft Sculpt Touch Mouse
<snip>
> So it looks like it's a gnome bluetooth-wizard problem. I will raise
> some tickets.
I don't see why it would be a problem in the wizard. You basically
didn't have a Bluetooth adapter before you installed bluez-hid2hci.
> > Maybe that was somehow auto-run with
> > your previous installation?
>
> I don't really know. It was F19. And that means bluez4. So I guess
> this is going to be a transition issue/bug I need to raise on F20.
bluez-hid2hci was already an optional package in F19.
^ permalink raw reply
* Re: [PATCH v10 0/5] Bluetooth LE 6LoWPAN
From: Marcel Holtmann @ 2013-12-11 20:59 UTC (permalink / raw)
To: Jukka Rissanen; +Cc: linux-bluetooth@vger.kernel.org development
In-Reply-To: <1386774338-2093-1-git-send-email-jukka.rissanen@linux.intel.com>
Hi Jukka,
> this is 6LoWPAN code for BT LE as described in
> http://tools.ietf.org/html/draft-ietf-6lo-btle-00
all 5 patches have been applied to bluetooth-next tree.
Regards
Marcel
^ permalink raw reply
* Doc for Qualcomm AR3001 HCI
From: Frank Zhao @ 2013-12-11 20:36 UTC (permalink / raw)
To: linux-bluetooth
I am doing some hacking on a PlayStation 4's DualShock 4 controller,
inside is a Qualcomm Atheros AR3002 connected to a microcontroller
using UART HCI. I have a logic analyzer connected to the UART signals
and I have captured a lot of data. But a lot of the HCI commands have
OGF of 0xFC which means that the commands are "vendor defined", and
thus they are not in the HCI functional specifications documentation.
I can't find any helpful technical documentation at all from
Qualcomm's website and they probably won't help some hobbyist anyways.
I've searched Google and found your website. You guys have written a
driver for this chip already, so you must have some documentation on
Qualcomm's own HCI commands. Can you please share this documentation
with me?
Thank you
Frank Zhao
PS: I originally wrote this email to linux-wireless but they told me
to try linux-bluetooth instead
^ permalink raw reply
* Re: mouse not found with bluez5 but was fine with bluez4
From: Brian J. Murrell @ 2013-12-11 20:13 UTC (permalink / raw)
To: Johan Hedberg; +Cc: linux-bluetooth
In-Reply-To: <20131211192523.GA17953@x220.p-661hnu-f1>
On Wed, 2013-12-11 at 21:25 +0200, Johan Hedberg wrote:
> Hi Brian,
Hi Johan,
> I'm not sure if I'm interpreting this right, but it seems the device is
> in HID mode and not HCI (normal Bluetooth) mode?
I dunno. I'm just the user. :-)
> Have you tried running
> the hid2hci tool (part of BlueZ)?
Not yet. It wasn't installed by default on F20. When I did though,
things went much better:
$ bluetoothctl
[NEW] Controller 00:02:72:1E:E0:12 pc.interlinx.bc.ca-0 [default]
[NEW] Device 00:0D:E6:68:B4:6F Samsung WEP850
[NEW] Device 70:F3:95:3E:92:34 brian-laptop
[NEW] Device 7C:1E:52:6E:59:D2 Microsoft Sculpt Touch Mouse
[bluetooth]# agent on
Agent registered
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# scan on
Discovery started
[CHG] Controller 00:02:72:1E:E0:12 Discovering: yes
[CHG] Device 7C:1E:52:6E:59:D2 RSSI: -59
[bluetooth]# scan off
[CHG] Device 7C:1E:52:6E:59:D2 RSSI is nil
Discovery stopped
[CHG] Controller 00:02:72:1E:E0:12 Discovering: no
[bluetooth]# pair 7C:1E:52:6E:59:D2
Attempting to pair with 7C:1E:52:6E:59:D2
[CHG] Device 7C:1E:52:6E:59:D2 Connected: yes
[CHG] Device 7C:1E:52:6E:59:D2 Paired: yes
Pairing successful
[CHG] Device 7C:1E:52:6E:59:D2 Connected: no
[bluetooth]# connect 7C:1E:52:6E:59:D2
Attempting to connect to 7C:1E:52:6E:59:D2
[CHG] Device 7C:1E:52:6E:59:D2 Connected: yes
Connection successful
[CHG] Device 7C:1E:52:6E:59:D2 Modalias: usb:v045Ep077Cd011E
[CHG] Device 7C:1E:52:6E:59:D2 Modalias: usb:v045Ep077Cd011E
[bluetooth]# trust 7C:1E:52:6E:59:D2
Changing 7C:1E:52:6E:59:D2 trust succeeded
[bluetooth]# quit
[DEL] Controller 00:02:72:1E:E0:12 pc.interlinx.bc.ca-0 [default]
So it looks like it's a gnome bluetooth-wizard problem. I will raise
some tickets.
> Maybe that was somehow auto-run with
> your previous installation?
I don't really know. It was F19. And that means bluez4. So I guess
this is going to be a transition issue/bug I need to raise on F20.
Cheers and thanks so much!
b.
^ permalink raw reply
* Re: mouse not found with bluez5 but was fine with bluez4
From: Johan Hedberg @ 2013-12-11 19:25 UTC (permalink / raw)
To: Brian J. Murrell; +Cc: linux-bluetooth
In-Reply-To: <1386776083.31076.60.camel@bmurrell-mobl.amr.corp.intel.com>
Hi Brian,
On Wed, Dec 11, 2013, Brian J. Murrell wrote:
> [ 1472.102375] usb 2-1: USB disconnect, device number 2
> [ 1472.102386] usb 2-1.1: USB disconnect, device number 9
> [ 1472.127401] usb 2-1.2: USB disconnect, device number 10
> [ 1472.141932] usb 2-1.3: USB disconnect, device number 11
> [ 1479.644058] usb 2-1: new full-speed USB device number 12 using ohci-pci
> [ 1479.844081] usb 2-1: New USB device found, idVendor=0a5c, idProduct=4500
> [ 1479.844093] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> [ 1479.844099] usb 2-1: Product: BCM2046B1
> [ 1479.844104] usb 2-1: Manufacturer: Broadcom
> [ 1479.847670] hub 2-1:1.0: USB hub found
> [ 1479.850082] hub 2-1:1.0: 3 ports detected
> [ 1480.151074] usb 2-1.1: new full-speed USB device number 13 using ohci-pci
> [ 1480.250070] usb 2-1.1: New USB device found, idVendor=0a5c, idProduct=4502
> [ 1480.250077] usb 2-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber
> [ 1480.260236] input: HID 0a5c:4502 as /devices/pci0000:00/0000:00:02.0/usb2/2-1
> [ 1480.261860] hid-generic 0003:0A5C:4502.0004: input,hidraw1: USB HID v1.11 Key
> [ 1480.330068] usb 2-1.2: new full-speed USB device number 14 using ohci-pci
> [ 1480.430070] usb 2-1.2: New USB device found, idVendor=0a5c, idProduct=4503
> [ 1480.430079] usb 2-1.2: New USB device strings: Mfr=0, Product=0, SerialNumber
> [ 1480.441241] input: HID 0a5c:4503 as /devices/pci0000:00/0000:00:02.0/usb2/2-1
> [ 1480.442349] hid-generic 0003:0A5C:4503.0005: input,hidraw2: USB HID v1.11 Mou
> [ 1480.513076] usb 2-1.3: new full-speed USB device number 15 using ohci-pci
> [ 1480.626069] usb 2-1.3: New USB device found, idVendor=0a5c, idProduct=2148
> [ 1480.626081] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber
> [ 1480.626088] usb 2-1.3: Product: BCM92046DG-CL1ROM
> [ 1480.626093] usb 2-1.3: Manufacturer: Broadcom Corp
> [ 1480.626098] usb 2-1.3: SerialNumber: XXXXXXXXXXXXXXX
I'm not sure if I'm interpreting this right, but it seems the device is
in HID mode and not HCI (normal Bluetooth) mode? Have you tried running
the hid2hci tool (part of BlueZ)? Maybe that was somehow auto-run with
your previous installation?
Johan
^ permalink raw reply
* Re: pull request: bluetooth-next 2013-12-10
From: John W. Linville @ 2013-12-11 15:55 UTC (permalink / raw)
To: Gustavo Padovan, linux-wireless, linux-bluetooth, linux-kernel
In-Reply-To: <20131210153830.GA1542@joana>
On Tue, Dec 10, 2013 at 01:38:30PM -0200, Gustavo Padovan wrote:
> Hi John,
>
> More patches to 3.14. Here we have the support for Low Energy Connection
> Oriented Channels (LE CoC). Basically, as the name says, this adds supports
> for connection oriented channels in the same way we already have them for
> BR/EDR connections so profiles/protocols that work on top of BR/EDR can now
> work on LE plus a plenty of new possibilities for LE.
>
> Please pull. Thanks!!
>
> Gustavo
>
> ---
> The following changes since commit 201a5929c8c788f9ef53b010065c9ce70c9c06f0:
>
> Bluetooth: Remove dead code from SMP encryption function (2013-12-04 11:09:05 -0200)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git for-upstream
>
> for you to fetch changes up to 71fb419724fadab4efdf98210aa3fe053bd81d29:
>
> Bluetooth: Fix handling of L2CAP Command Reject over LE (2013-12-10 01:15:44 -0800)
Pulling now...
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
^ permalink raw reply
* Re: mouse not found with bluez5 but was fine with bluez4
From: Brian J. Murrell @ 2013-12-11 15:34 UTC (permalink / raw)
To: Johan Hedberg; +Cc: linux-bluetooth
In-Reply-To: <20131211092135.GA16525@x220.p-661hnu-f1>
On Wed, 2013-12-11 at 11:21 +0200, Johan Hedberg wrote:
> Hi Brian,
Hi Johan,
> For one thing, it'd be good to determine whether this is a GUI thing (I
> assume you're using the GNOME UI?)
Yeah.
> or something in BlueZ. The way to do
> that would be to use the bluetoothctl tool that's part of BlueZ 5. The
> commands you'd give it would go something like:
>
> agent on
> power on
> scan on
> <wait for mouse to show up>
> scan off
> pair <mouse addr> (optional if the mouse doesn't support pairing)
> connect <mouse addr>
> trust <mouse addr>
Here is what I get:
$ bluetoothctl
[bluetooth]# agent on
Agent registration enabled
[bluetooth]# power on
No default controller available
[bluetooth]# scan on
No default controller available
[bluetooth]#
$ lsb
...
Bus 002 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Unplugging the BT dongle and plugging it back in yields:
[ 1472.102375] usb 2-1: USB disconnect, device number 2
[ 1472.102386] usb 2-1.1: USB disconnect, device number 9
[ 1472.127401] usb 2-1.2: USB disconnect, device number 10
[ 1472.141932] usb 2-1.3: USB disconnect, device number 11
[ 1479.644058] usb 2-1: new full-speed USB device number 12 using ohci-pci
[ 1479.844081] usb 2-1: New USB device found, idVendor=0a5c, idProduct=4500
[ 1479.844093] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1479.844099] usb 2-1: Product: BCM2046B1
[ 1479.844104] usb 2-1: Manufacturer: Broadcom
[ 1479.847670] hub 2-1:1.0: USB hub found
[ 1479.850082] hub 2-1:1.0: 3 ports detected
[ 1480.151074] usb 2-1.1: new full-speed USB device number 13 using ohci-pci
[ 1480.250070] usb 2-1.1: New USB device found, idVendor=0a5c, idProduct=4502
[ 1480.250077] usb 2-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber
[ 1480.260236] input: HID 0a5c:4502 as /devices/pci0000:00/0000:00:02.0/usb2/2-1
[ 1480.261860] hid-generic 0003:0A5C:4502.0004: input,hidraw1: USB HID v1.11 Key
[ 1480.330068] usb 2-1.2: new full-speed USB device number 14 using ohci-pci
[ 1480.430070] usb 2-1.2: New USB device found, idVendor=0a5c, idProduct=4503
[ 1480.430079] usb 2-1.2: New USB device strings: Mfr=0, Product=0, SerialNumber
[ 1480.441241] input: HID 0a5c:4503 as /devices/pci0000:00/0000:00:02.0/usb2/2-1
[ 1480.442349] hid-generic 0003:0A5C:4503.0005: input,hidraw2: USB HID v1.11 Mou
[ 1480.513076] usb 2-1.3: new full-speed USB device number 15 using ohci-pci
[ 1480.626069] usb 2-1.3: New USB device found, idVendor=0a5c, idProduct=2148
[ 1480.626081] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber
[ 1480.626088] usb 2-1.3: Product: BCM92046DG-CL1ROM
[ 1480.626093] usb 2-1.3: Manufacturer: Broadcom Corp
[ 1480.626098] usb 2-1.3: SerialNumber: XXXXXXXXXXXXXXX
Cheers,
b.
^ permalink raw reply
* [PATCH v2 8/8] android/pts: Add PTS PIXIT for PBAP
From: Szymon Janc @ 2013-12-11 15:27 UTC (permalink / raw)
To: linux-bluetooth; +Cc: Szymon Janc
In-Reply-To: <1386775638-24941-1-git-send-email-szymon.janc@tieto.com>
This complements PTS PICS configuration.
---
android/Makefile.am | 3 ++-
android/pixit-pbap.txt | 33 +++++++++++++++++++++++++++++++++
2 files changed, 35 insertions(+), 1 deletion(-)
create mode 100644 android/pixit-pbap.txt
diff --git a/android/Makefile.am b/android/Makefile.am
index a9b09da..0bcab2f 100644
--- a/android/Makefile.am
+++ b/android/Makefile.am
@@ -109,4 +109,5 @@ EXTRA_DIST += android/Android.mk android/hal-ipc-api.txt android/README \
android/pics-opp.txt android/pics-pbap.txt \
android/pixit-did.txt android/pts-did.txt \
android/pixit-gap.txt android/pixit-hid.txt \
- android/pixit-opp.txt android/pixit-pan.txt
+ android/pixit-opp.txt android/pixit-pan.txt \
+ android/pixit-pbap.txt
diff --git a/android/pixit-pbap.txt b/android/pixit-pbap.txt
new file mode 100644
index 0000000..272cbc3
--- /dev/null
+++ b/android/pixit-pbap.txt
@@ -0,0 +1,33 @@
+PBAP PIXIT for the PTS tool.
+
+* - different than PTS defaults
+& - should be set to IUT Bluetooth address
+
+ Required PIXIT settings
+-------------------------------------------------------------------------------
+Parameter Name Value
+-------------------------------------------------------------------------------
+TSPX_auth_password 0000
+TSPX_auth_user_id PTS
+TSPX_security_enabled True
+TSPX_bd_addr_iut 112233445566 (*&)
+TSPX_pin_code 0000
+TSPX_time_guard 100000
+TSPX_use_implicit_send True
+TSPX_client_class_of_device 100204
+TSPX_server_class_of_device 100204
+TSPX_PSE_vCardSelector 0000000000000001
+TSPX_delete_link_key False
+TSPX_PBAP_profile_version 1
+TSPX_PBAP_supported_repositories 1
+TSPX_PBAP_rfcomm_channel 1
+TSPX_telecom_folder_path telecom
+TSPX_secure_simple_pairing_pass_key_confirmation False
+TSPX_check_downloaded_contents_after_disconnect False
+TSPX_SPP_rfcomm_channel 03
+TSPX_l2cap_psm 1005
+TSPX_rfcomm_channel 2
+TSPX_obex_auth_password 0000
+TSPX_no_confirmations False
+TSPX_PSE_vCardSelector 0000000000000001
+-------------------------------------------------------------------------------
--
1.8.3.2
^ permalink raw reply related
* [PATCH v2 7/8] android/pts: Add PTS PIXIT for PAN
From: Szymon Janc @ 2013-12-11 15:27 UTC (permalink / raw)
To: linux-bluetooth; +Cc: Szymon Janc
In-Reply-To: <1386775638-24941-1-git-send-email-szymon.janc@tieto.com>
This complements PTS PICS configuration.
---
android/Makefile.am | 2 +-
android/pixit-pan.txt | 28 ++++++++++++++++++++++++++++
2 files changed, 29 insertions(+), 1 deletion(-)
create mode 100644 android/pixit-pan.txt
diff --git a/android/Makefile.am b/android/Makefile.am
index 1bba128..a9b09da 100644
--- a/android/Makefile.am
+++ b/android/Makefile.am
@@ -109,4 +109,4 @@ EXTRA_DIST += android/Android.mk android/hal-ipc-api.txt android/README \
android/pics-opp.txt android/pics-pbap.txt \
android/pixit-did.txt android/pts-did.txt \
android/pixit-gap.txt android/pixit-hid.txt \
- android/pixit-opp.txt
+ android/pixit-opp.txt android/pixit-pan.txt
diff --git a/android/pixit-pan.txt b/android/pixit-pan.txt
new file mode 100644
index 0000000..2d180da
--- /dev/null
+++ b/android/pixit-pan.txt
@@ -0,0 +1,28 @@
+PAN PIXIT for the PTS tool.
+
+* - different than PTS defaults
+& - should be set to IUT Bluetooth address
+
+ Required PIXIT settings
+-------------------------------------------------------------------------------
+Parameter Name Value
+-------------------------------------------------------------------------------
+TSPX_GN_class_of_device 020104
+TSPX_NAP_class_of_device 020300
+TSPX_PANU_class_of_device 020104
+TSPX_time_guard 300000
+TSPX_bd_addr_iut 112233445566 (*&)
+TSPX_security_enabled False
+TSPX_pin_code 0000
+TSPX_delete_link_key False
+TSPX_use_implicit_send True
+TSPX_iut_ip_address 192.168.167.152
+TSPX_iut_port_number 4242
+TSPX_PTS_ip_address 192.168.168.100
+TSPX_PTS_port_number 4242
+TSPX_bd_addr_PTS 000000000000
+TSPX_checksum E851
+TSPX_secure_simple_pairing_pass_key_confirmation False
+TSPX_iut_friendly_bt_name gprs-pc
+TSPX_PTS_role_when_iut_is_PANU default
+-------------------------------------------------------------------------------
--
1.8.3.2
^ permalink raw reply related
* [PATCH v2 6/8] android/pts: Add PTS PIXIT for OPP
From: Szymon Janc @ 2013-12-11 15:27 UTC (permalink / raw)
To: linux-bluetooth; +Cc: Szymon Janc
In-Reply-To: <1386775638-24941-1-git-send-email-szymon.janc@tieto.com>
This complements PTS PICS configuration.
---
android/Makefile.am | 3 ++-
android/pixit-opp.txt | 25 +++++++++++++++++++++++++
2 files changed, 27 insertions(+), 1 deletion(-)
create mode 100644 android/pixit-opp.txt
diff --git a/android/Makefile.am b/android/Makefile.am
index 60d46b5..1bba128 100644
--- a/android/Makefile.am
+++ b/android/Makefile.am
@@ -108,4 +108,5 @@ EXTRA_DIST += android/Android.mk android/hal-ipc-api.txt android/README \
android/pics-pan.txt android/pics-did.txt \
android/pics-opp.txt android/pics-pbap.txt \
android/pixit-did.txt android/pts-did.txt \
- android/pixit-gap.txt android/pixit-hid.txt
+ android/pixit-gap.txt android/pixit-hid.txt \
+ android/pixit-opp.txt
diff --git a/android/pixit-opp.txt b/android/pixit-opp.txt
new file mode 100644
index 0000000..1b1e834
--- /dev/null
+++ b/android/pixit-opp.txt
@@ -0,0 +1,25 @@
+OPP PIXIT for the PTS tool.
+
+* - different than PTS defaults
+& - should be set to IUT Bluetooth address
+
+ Required PIXIT settings
+-------------------------------------------------------------------------------
+Parameter Name Value
+-------------------------------------------------------------------------------
+TSPX_unsupported_extension dat
+TSPX_supported_extension jpg
+TSPX_security_enabled False
+TSPX_bd_addr_iut 112233445566 (*&)
+TSPX_client_class_of_device 100104
+TSPX_server_class_of_device 100104
+TSPX_rfcomm_channel 8
+TSPX_pin_code 0000
+TSPX_reply_reject_push True
+TSPX_delete_link_key False
+TSPX_time_guard 180000
+TSPX_use_implicit_send True
+TSPX_secure_simple_pairing_pass_key_confirmation False
+TSPX_PTS_sends_real_jpg_data True
+TSPX_confirm_received_objects True
+-------------------------------------------------------------------------------
--
1.8.3.2
^ permalink raw reply related
* [PATCH v2 5/8] android/pts: Add PTS PIXIT for HID
From: Szymon Janc @ 2013-12-11 15:27 UTC (permalink / raw)
To: linux-bluetooth; +Cc: Szymon Janc
In-Reply-To: <1386775638-24941-1-git-send-email-szymon.janc@tieto.com>
This complements PTS PICS configuration.
---
android/Makefile.am | 2 +-
android/pixit-hid.txt | 28 ++++++++++++++++++++++++++++
2 files changed, 29 insertions(+), 1 deletion(-)
create mode 100644 android/pixit-hid.txt
diff --git a/android/Makefile.am b/android/Makefile.am
index 66c3dba..60d46b5 100644
--- a/android/Makefile.am
+++ b/android/Makefile.am
@@ -108,4 +108,4 @@ EXTRA_DIST += android/Android.mk android/hal-ipc-api.txt android/README \
android/pics-pan.txt android/pics-did.txt \
android/pics-opp.txt android/pics-pbap.txt \
android/pixit-did.txt android/pts-did.txt \
- android/pixit-gap.txt
+ android/pixit-gap.txt android/pixit-hid.txt
diff --git a/android/pixit-hid.txt b/android/pixit-hid.txt
new file mode 100644
index 0000000..f306615
--- /dev/null
+++ b/android/pixit-hid.txt
@@ -0,0 +1,28 @@
+HID PIXIT for the PTS tool.
+
+* - different than PTS defaults
+& - should be set to IUT Bluetooth address
+
+ Required PIXIT settings
+-------------------------------------------------------------------------------
+Parameter Name Value
+-------------------------------------------------------------------------------
+TSPX_security_enabled True
+TSPX_delete_link_key True
+TSPX_query_iut_sdp True
+TSPX_bd_addr_iut 112233445566 (*&)
+TSPX_pointing_device_class_of_device 002580
+TSPX_keyboard_device_class_of_device 002540
+TSPX_host_class_of_device 100108
+TSPX_pts_device_role MOUSE
+TSPX_pin_code 0000
+TSPX_use_dynamic_pin_code False
+TSPX_time_guard 6000000
+TSPX_hid_data_interval 1000
+TSPX_use_implicit_send True
+TSPX_verbose_implicit_send False
+TSPX_no_fail_verdicts False
+TSPX_time_reconnect 30000
+TSPX_secure_simple_pairing_pass_key_confirmation False
+TSPX_hid_report_id 1
+-------------------------------------------------------------------------------
--
1.8.3.2
^ permalink raw reply related
* [PATCH v2 4/8] android/pts: Add PTS PIXIT for GAP
From: Szymon Janc @ 2013-12-11 15:27 UTC (permalink / raw)
To: linux-bluetooth; +Cc: Szymon Janc
In-Reply-To: <1386775638-24941-1-git-send-email-szymon.janc@tieto.com>
This complements PTS PICS configuration.
---
android/Makefile.am | 3 ++-
android/pixit-gap.txt | 55 +++++++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 57 insertions(+), 1 deletion(-)
create mode 100644 android/pixit-gap.txt
diff --git a/android/Makefile.am b/android/Makefile.am
index b505c33..66c3dba 100644
--- a/android/Makefile.am
+++ b/android/Makefile.am
@@ -107,4 +107,5 @@ EXTRA_DIST += android/Android.mk android/hal-ipc-api.txt android/README \
android/pics-gap.txt android/pics-hid.txt \
android/pics-pan.txt android/pics-did.txt \
android/pics-opp.txt android/pics-pbap.txt \
- android/pixit-did.txt android/pts-did.txt
+ android/pixit-did.txt android/pts-did.txt \
+ android/pixit-gap.txt
diff --git a/android/pixit-gap.txt b/android/pixit-gap.txt
new file mode 100644
index 0000000..786c55e
--- /dev/null
+++ b/android/pixit-gap.txt
@@ -0,0 +1,55 @@
+GAP PIXIT for the PTS tool.
+
+* - different than PTS defaults
+& - should be set to IUT Bluetooth address
+
+ Required PIXIT settings
+-------------------------------------------------------------------------------
+Parameter Name Value
+-------------------------------------------------------------------------------
+TSPX_bd_addr_iut 112233445566 (*&)
+TSPX_bd_addr_PTS 000000000000
+TSPX_broadcaster_class_of_device 100104
+TSPX_observer_class_of_device 100104
+TSPX_peripheral_class_of_device 100104
+TSPX_central_class_of_device 100104
+TSPX_security_enabled True
+TSPX_delete_link_key True
+TSPX_pin_code 0000
+TSPX_time_guard 300000
+TSPX_use_implicit_send True
+TSPX_use_dynamic_pin False
+TSPX_secure_simple_pairing_pass_key_confirmation False
+TSPX_using_public_device_address True
+TSPX_using_random_device_address False
+TSPX_lim_adv_timeout 30720
+TSPX_gen_disc_adv_min 30720
+TSPX_lim_disc_scan_min 10240
+TSPX_gen_disc_scan_min 10240
+TSPX_database_file Database-GAP.sig
+TSPX_iut_rx_mtu 23
+TSPX_iut_private_address_interval 10000
+TSPX_iut_privacy_enabled False
+TSPX_psm 1001
+TSPX_iut_valid_connection_interval_min 00C8
+TSPX_iut_valid_conneciton_interval_max 0960
+TSPX_iut_valid_connection_latency 0007
+TSPX_iut_valid_timeout_multiplier 0960
+TSPX_iut_connection_parameter_timeout 30000
+TSPX_iut_invalid_connection_interval_min 0000
+TSPX_iut_invalid_conneciton_interval_max 0000
+TSPX_iut_invalid_connection_latency 0000
+TSPX_iut_invalid_timeout_multiplier 0000
+TSPX_LE_scan_interval 0010
+TSPX_LE_scan_window 0010
+TSPX_con_interval_min 0032
+TSPX_con_interval_max 0046
+TSPX_con_latency 0000
+TSPX_supervision_timeout 07D0
+TSPX_minimum_ce_length 0000
+TSPX_maximum_ce_length 0000
+TSPX_pairing_before_service_request False
+TSPX_iut_mandates_mitm False
+TSPX_encryption_before_service_request False
+TSPX_tester_appearance 0000
+-------------------------------------------------------------------------------
--
1.8.3.2
^ permalink raw reply related
* [PATCH v2 3/8] android/pts: Add PTS test results for DID
From: Szymon Janc @ 2013-12-11 15:27 UTC (permalink / raw)
To: linux-bluetooth; +Cc: Szymon Janc
In-Reply-To: <1386775638-24941-1-git-send-email-szymon.janc@tieto.com>
This will allow for better tracking of current state of implementation.
---
android/Makefile.am | 2 +-
android/pts-did.txt | 19 +++++++++++++++++++
2 files changed, 20 insertions(+), 1 deletion(-)
create mode 100644 android/pts-did.txt
diff --git a/android/Makefile.am b/android/Makefile.am
index 0ffbdb0..b505c33 100644
--- a/android/Makefile.am
+++ b/android/Makefile.am
@@ -107,4 +107,4 @@ EXTRA_DIST += android/Android.mk android/hal-ipc-api.txt android/README \
android/pics-gap.txt android/pics-hid.txt \
android/pics-pan.txt android/pics-did.txt \
android/pics-opp.txt android/pics-pbap.txt \
- android/pixit-did.txt
+ android/pixit-did.txt android/pts-did.txt
diff --git a/android/pts-did.txt b/android/pts-did.txt
new file mode 100644
index 0000000..c44f56c
--- /dev/null
+++ b/android/pts-did.txt
@@ -0,0 +1,19 @@
+PTS test results for DID
+
+PTS version: 5.0
+Tested: 11.12.2013
+
+Results:
+PASS test passed
+FAIL test failed
+INC test is inconclusive
+N/A test is disabled due to PICS setup
+
+-------------------------------------------------------------------------------
+Test Name Result Notes
+-------------------------------------------------------------------------------
+TC_SDI_BV_1_I PASS IUT must be discoverable
+TC_SDI_BV_2_I PASS IUT must be discoverable
+TC_SDI_BV_3_I PASS IUT must be discoverable
+TC_SDI_BV_4_I PASS IUT must be discoverable
+-------------------------------------------------------------------------------
--
1.8.3.2
^ permalink raw reply related
* [PATCH v2 2/8] android/pts: Add PTS PIXIT for DID
From: Szymon Janc @ 2013-12-11 15:27 UTC (permalink / raw)
To: linux-bluetooth; +Cc: Szymon Janc
In-Reply-To: <1386775638-24941-1-git-send-email-szymon.janc@tieto.com>
This complements PTS PICS configuration.
---
android/Makefile.am | 3 ++-
android/pixit-did.txt | 22 ++++++++++++++++++++++
2 files changed, 24 insertions(+), 1 deletion(-)
create mode 100644 android/pixit-did.txt
diff --git a/android/Makefile.am b/android/Makefile.am
index f3e77c3..0ffbdb0 100644
--- a/android/Makefile.am
+++ b/android/Makefile.am
@@ -106,4 +106,5 @@ endif
EXTRA_DIST += android/Android.mk android/hal-ipc-api.txt android/README \
android/pics-gap.txt android/pics-hid.txt \
android/pics-pan.txt android/pics-did.txt \
- android/pics-opp.txt android/pics-pbap.txt
+ android/pics-opp.txt android/pics-pbap.txt \
+ android/pixit-did.txt
diff --git a/android/pixit-did.txt b/android/pixit-did.txt
new file mode 100644
index 0000000..2527845
--- /dev/null
+++ b/android/pixit-did.txt
@@ -0,0 +1,22 @@
+DID PIXIT for the PTS tool.
+
+* - different than PTS defaults
+& - should be set to IUT Bluetooth address
+
+ Required PIXIT settings
+-------------------------------------------------------------------------------
+Parameter Name Value
+-------------------------------------------------------------------------------
+TSPX_security_enabled False
+TSPX_ClientExecutableURL False (*)
+TSPX_ServiceDescription False (*)
+TSPX_DocumentationURL False (*)
+TSPX_bd_addr_iut 112233445566 (*&)
+TSPX_class_of_device_pts 200404
+TSPX_device_search_time 30
+TSPX_delete_link_key False
+TSPX_pin_code 0000
+TSPX_time_guard 200000
+TSPX_use_implicit_send True
+TSPX_secure_simple_pairing_pass_key_confirmation False
+-------------------------------------------------------------------------------
--
1.8.3.2
^ permalink raw reply related
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox