I'd love to see the new Eddystone Configuration GATT Service
(https://github.com/google/eddystone/tree/master/configuration-service)
being recognized by BlueZ.
Could you guys make this happen?
Something like:
[bluetooth]# info F1:6F:DE:EC:F1:D6
Device F1:6F:DE:EC:F1:D6
Name: ES G-SLOTS-X
Alias: ES G-SLOTS-X
Appearance: 0x0200
Paired: no
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Eddystone Configuration GATT Service
(a3c87500-8ed3-4bdf-8a39-a01bebede295)
instead of
[bluetooth]# info F1:6F:DE:EC:F1:D6
Device F1:6F:DE:EC:F1:D6
Name: ES G-SLOTS-X
Alias: ES G-SLOTS-X
Appearance: 0x0200
Paired: no
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (a3c87500-8ed3-4bdf-8a39-a01bebede295)
Thank you!
I've just sent http://permalink.gmane.org/gmane.linux.bluez.kernel/67370
for review.
On Wed, Apr 20, 2016 at 10:00 AM, Luiz Augusto von Dentz
<[email protected]> wrote:
> Hi François,
>
> On Wed, Apr 20, 2016 at 9:49 AM, François Beaufort
> <[email protected]> wrote:
>> Regarding my initial request, can someone point to me where to start
>> if I wanted to code that?
>
> https://git.kernel.org/cgit/bluetooth/bluez.git/tree/monitor/uuid.c
> you might need to add a table for known UUID 128 bits so
> uuidstr_to_str don't return "Vendor specific" instead it lookup by
> string.
>
>> On Tue, Apr 19, 2016 at 8:09 PM, François Beaufort
>> <[email protected]> wrote:
>>> For info, I've asked this question at
>>> https://github.com/google/eddystone/issues/138
>>> Let's see what they say.
>>>
>>> On Tue, Apr 19, 2016 at 7:25 PM, Johan Hedberg <[email protected]> wrote:
>>>> Hi François,
>>>>
>>>> On Tue, Apr 19, 2016, François Beaufort wrote:
>>>>> I'd love to see the new Eddystone Configuration GATT Service
>>>>> (https://github.com/google/eddystone/tree/master/configuration-service)
>>>>> being recognized by BlueZ.
>>>>> Could you guys make this happen?
>>>>
>>>> That'd indeed be nice! I'm not volunteering, but I do have a question
>>>> about this part:
>>>>
>>>> "Where not explicitly stated, data written and read is defined in terms
>>>> of big-endian arrays of signed bytes."
>>>>
>>>> Why on earth big-endian? GATT, like most other Bluetooth protocols, is
>>>> little-endian. Can this still be fixed?
>>>>
>>>> Johan
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
>> the body of a message to [email protected]
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
> --
> Luiz Augusto von Dentz
Hi François,
On Wed, Apr 20, 2016 at 9:49 AM, François Beaufort
<[email protected]> wrote:
> Regarding my initial request, can someone point to me where to start
> if I wanted to code that?
https://git.kernel.org/cgit/bluetooth/bluez.git/tree/monitor/uuid.c
you might need to add a table for known UUID 128 bits so
uuidstr_to_str don't return "Vendor specific" instead it lookup by
string.
> On Tue, Apr 19, 2016 at 8:09 PM, François Beaufort
> <[email protected]> wrote:
>> For info, I've asked this question at
>> https://github.com/google/eddystone/issues/138
>> Let's see what they say.
>>
>> On Tue, Apr 19, 2016 at 7:25 PM, Johan Hedberg <[email protected]> wrote:
>>> Hi François,
>>>
>>> On Tue, Apr 19, 2016, François Beaufort wrote:
>>>> I'd love to see the new Eddystone Configuration GATT Service
>>>> (https://github.com/google/eddystone/tree/master/configuration-service)
>>>> being recognized by BlueZ.
>>>> Could you guys make this happen?
>>>
>>> That'd indeed be nice! I'm not volunteering, but I do have a question
>>> about this part:
>>>
>>> "Where not explicitly stated, data written and read is defined in terms
>>> of big-endian arrays of signed bytes."
>>>
>>> Why on earth big-endian? GATT, like most other Bluetooth protocols, is
>>> little-endian. Can this still be fixed?
>>>
>>> Johan
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Luiz Augusto von Dentz
Regarding my initial request, can someone point to me where to start
if I wanted to code that?
On Tue, Apr 19, 2016 at 8:09 PM, François Beaufort
<[email protected]> wrote:
> For info, I've asked this question at
> https://github.com/google/eddystone/issues/138
> Let's see what they say.
>
> On Tue, Apr 19, 2016 at 7:25 PM, Johan Hedberg <[email protected]> wrote:
>> Hi François,
>>
>> On Tue, Apr 19, 2016, François Beaufort wrote:
>>> I'd love to see the new Eddystone Configuration GATT Service
>>> (https://github.com/google/eddystone/tree/master/configuration-service)
>>> being recognized by BlueZ.
>>> Could you guys make this happen?
>>
>> That'd indeed be nice! I'm not volunteering, but I do have a question
>> about this part:
>>
>> "Where not explicitly stated, data written and read is defined in terms
>> of big-endian arrays of signed bytes."
>>
>> Why on earth big-endian? GATT, like most other Bluetooth protocols, is
>> little-endian. Can this still be fixed?
>>
>> Johan
For info, I've asked this question at
https://github.com/google/eddystone/issues/138
Let's see what they say.
On Tue, Apr 19, 2016 at 7:25 PM, Johan Hedberg <[email protected]> wrote:
> Hi François,
>
> On Tue, Apr 19, 2016, François Beaufort wrote:
>> I'd love to see the new Eddystone Configuration GATT Service
>> (https://github.com/google/eddystone/tree/master/configuration-service)
>> being recognized by BlueZ.
>> Could you guys make this happen?
>
> That'd indeed be nice! I'm not volunteering, but I do have a question
> about this part:
>
> "Where not explicitly stated, data written and read is defined in terms
> of big-endian arrays of signed bytes."
>
> Why on earth big-endian? GATT, like most other Bluetooth protocols, is
> little-endian. Can this still be fixed?
>
> Johan
Hi Fran?ois,
On Tue, Apr 19, 2016, Fran?ois Beaufort wrote:
> I'd love to see the new Eddystone Configuration GATT Service
> (https://github.com/google/eddystone/tree/master/configuration-service)
> being recognized by BlueZ.
> Could you guys make this happen?
That'd indeed be nice! I'm not volunteering, but I do have a question
about this part:
"Where not explicitly stated, data written and read is defined in terms
of big-endian arrays of signed bytes."
Why on earth big-endian? GATT, like most other Bluetooth protocols, is
little-endian. Can this still be fixed?
Johan