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 <beaufort.francois@xxxxxxxxx> 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 <johan.hedberg@xxxxxxxxx> 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 majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
