Return-Path: <linux-bluetooth-owner@vger.kernel.org>
MIME-Version: 1.0
In-Reply-To: <20160419172500.GA16645@t440s.P-661HNU-F1>
References: <CAEZxfGMCA_A1RQVmxr6DWgweD5Qg6e34F-09Ws=stLpV=YU5=w@mail.gmail.com>
 <20160419172500.GA16645@t440s.P-661HNU-F1>
From: =?UTF-8?Q?Fran=C3=A7ois_Beaufort?= <beaufort.francois@gmail.com>
Date: Tue, 19 Apr 2016 20:09:50 +0200
Message-ID: <CAEZxfGNTYECk57B=32V8W-AKHFXQZH+5d916gsn2Ke8QEt8yzQ@mail.gmail.com>
Subject: Re: Add Eddystone GATT Config Service to known UUIDs
To: =?UTF-8?Q?Fran=C3=A7ois_Beaufort?= <beaufort.francois@gmail.com>,
	BlueZ development <linux-bluetooth@vger.kernel.org>
Content-Type: text/plain; charset=UTF-8
Sender: linux-bluetooth-owner@vger.kernel.org
List-ID: <linux-bluetooth.vger.kernel.org>

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 <johan.hedberg@gmail.com> 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