Linux bluetooth development
 help / color / mirror / Atom feed
From: Antonio Ospite <ospite@studenti.unina.it>
To: linux-bluetooth@vger.kernel.org
Subject: Re: bluez: lowercase hex digits in BDADDRs
Date: Thu, 20 May 2010 11:57:27 +0200	[thread overview]
Message-ID: <20100520115727.32df80c3.ospite@studenti.unina.it> (raw)
In-Reply-To: <20100505151220.137a0b37.ospite@studenti.unina.it>

[-- Attachment #1: Type: text/plain, Size: 1196 bytes --]

On Wed, 5 May 2010 15:12:20 +0200
Antonio Ospite <ospite@studenti.unina.it> wrote:

> Hi,
> 
> when working on Sixaxis pairing plugin I found out a weird behavior, if
> I use a BDADDR with lowercase hex digits the association can fail.
>

Ping. Anyone ever experienced that?

> The interesting bits in bluetoothd logs are reported in the attached
> diff, maybe adapter_create_device() is not robust enough?
> 
> You can reproduce this behavior using a lowercase _device_ bdaddr
> into these files:
>     /var/lib/bluetooth/00:03:C9:XX:XX:XX/did
>     /var/lib/bluetooth/00:03:C9:XX:XX:XX/lastused
>     /var/lib/bluetooth/00:03:C9:XX:XX:XX/sdp
>     /var/lib/bluetooth/00:03:C9:XX:XX:XX/trusts
> where 00:03:C9:XX:XX:XX is the _adapter_ bdaddr.
> 
> Can anyone else confirm that? bluez-4.64
> 
> Not a big deal, but worth reporting IMHO.
> 
> Thanks,
>    Antonio
> 

-- 
Antonio Ospite
http://ao2.it

PGP public key ID: 0x4553B001

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2010-05-20  9:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-05 13:12 bluez: lowercase hex digits in BDADDRs Antonio Ospite
2010-05-20  9:57 ` Antonio Ospite [this message]

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=20100520115727.32df80c3.ospite@studenti.unina.it \
    --to=ospite@studenti.unina.it \
    --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