linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt <mwtaylor@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Error setting UUIDs discovery filter on big endian systems
Date: Mon, 3 Dec 2018 13:56:23 +0000	[thread overview]
Message-ID: <150d16d9-9149-a463-e285-aaea10bed6e4@gmail.com> (raw)

Hi,

When setting a UUIDs discovery filter I am receiving 
"org.bluez.Error.InProgress" on starting a scan (which isn't in progress 
and will not start unless the discovery filter is cleared).

I am using bluez 5.50 (on openWRT). The problem seems to only appear on 
big endian hardware (tested a couple of recent kernel and bluez 
versions), the same software compiled for and tested on little endian 
hardware works as expected. The issue can be reproduced in the following 
way using bluetoothctl:

# /etc/init.d/bluetoothd restart
# bluetoothctl
[bluetooth]# power on
Changing power on succeeded
[CHG] Controller 00:1A:7D:DA:71:13 Powered: yes
[bluetooth]# menu scan
[bluetooth]# uuids 0000180f-0000-1000-8000-00805f9b34fb
[bluetooth]# back
[bluetooth]# scan on
SetDiscoveryFilter success
Failed to start discovery: org.bluez.Error.InProgress

Setting an rssi filter does work as expected on my big endian hardware, 
it is only the uuids filter that appears to show this problem. The issue 
appears whether set using bluetoothctl or directly using DBus.

Thank you for your help and attention,
Matt

             reply	other threads:[~2018-12-03 13:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-03 13:56 Matt [this message]
2018-12-04 19:53 ` Error setting UUIDs discovery filter on big endian systems Luiz Augusto von Dentz
2018-12-05  0:27   ` Matt
2019-03-05 18:02     ` Matt
2019-03-06 11:10       ` Luiz Augusto von Dentz
2019-03-06 13:48         ` Matt
2019-03-06 14:14           ` Luiz Augusto von Dentz
2019-03-06 15:14             ` Matt

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=150d16d9-9149-a463-e285-aaea10bed6e4@gmail.com \
    --to=mwtaylor@gmail.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 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).