Re: [PATCH] Preferentially use existing device ID when setting serial number

On Mon, Jun 20, 2016 at 6:47 PM, Steve wrote: > > What if you have multiple deviceids associated with the same serial number (I > seem to get a new entry every firmware update) So that "new device ID due to firmware change" happens only with the DEVINFO model,

RE: [PATCH] Preferentially use existing device ID when setting serial number

We have two different models for setting the deviceid associated with a dive computer: either take the value from the libdivecomputer 'devinfo' field (from the DC_EVENT_DEVINFO event), or generate the device ID by just hashing the serial number string. The one thing we do *not* want to have,

[PATCH] Preferentially use existing device ID when setting serial number

From: Linus Torvalds Date: Mon, 20 Jun 2016 17:59:26 -0700 Subject: [PATCH] Preferentially use existing device ID when setting serial number We have two different models for setting the deviceid associated with a dive computer: either take the value from the

Re: Suunto EON Steel breakages..

On Mon, Jun 20, 2016 at 1:17 PM, Axel Richter wrote: > > Hi Linus, > > I use an EON Steel, too and will update the subsurface sources next week for > compiling. > Should I avoid updating libdivecomputer? So the breakage isn't in the downloaded data itself, it's just

Re: Suunto EON Steel breakages..

> On Jun 20, 2016, at 1:17 PM, Axel Richter wrote: > > Am 20.06.2016 um 21:03 schrieb Linus Torvalds: >> So the fairly recent update of libdivecomputer to merge stuff from >> Jeff is completely broken for the Suunto EON Steel: Jeff added support >> for the "devinfo"

Re: Suunto EON Steel breakages..

Hi Linus, > On Jun 20, 2016, at 12:03 PM, Linus Torvalds > wrote: > > So the fairly recent update of libdivecomputer to merge stuff from > Jeff is completely broken for the Suunto EON Steel: Jeff added support > for the "devinfo" event for the EON Steel, but that

Re: Suunto EON Steel breakages..

Am 20.06.2016 um 21:03 schrieb Linus Torvalds: So the fairly recent update of libdivecomputer to merge stuff from Jeff is completely broken for the Suunto EON Steel: Jeff added support for the "devinfo" event for the EON Steel, but that event is just pointless garbage, and actually breaks things

Re: Cross-compiling Subsurface-mobile from Linux to Android

Am 20.06.2016 um 21:14 schrieb Willem Ferguson: I am downloading build components to cross-compile to Android (i.e. generating an .apk file). I installed Android-ndk, Android-sdk (NOT Android-Studio) and the JDK (version 1.8). None of these components required any compilation or building to

Cross-compiling Subsurface-mobile from Linux to Android

I am downloading build components to cross-compile to Android (i.e. generating an .apk file). I installed Android-ndk, Android-sdk (NOT Android-Studio) and the JDK (version 1.8). None of these components required any compilation or building to be functional. Below a few remarks on the

Suunto EON Steel breakages..

So the fairly recent update of libdivecomputer to merge stuff from Jeff is completely broken for the Suunto EON Steel: Jeff added support for the "devinfo" event for the EON Steel, but that event is just pointless garbage, and actually breaks things by introducing the wrong device IDs. I don't

Issue with Importing all dives from Suunto Vyper

Hello, here the Subsurface version I'm using : ``` subsurface --version Subsurface v4.5.6, built with libdivecomputer v0.5.0-devel-Subsurface-branch (2015546952c06459310e6670c2d3c849af8abfb7) ``` You'll find attached the dumps of the imports as stated in the documentation. I have 136 dives