On 18/05/2015 15:31, Dirk Hohndel wrote:
On Mon, May 18, 2015 at 01:35:01PM +0200, Willem Ferguson wrote:
The gas changes from my galileo dive computer are not automatically read
into Subsurface. As far as I can see, gas changes are logged and
interpreted by libdivecomputer. For instance, there
On 18 May, 2015 - Linus Torvalds wrote:
On Mon, May 18, 2015 at 10:39 AM, Anton Lundin gla...@acc.umu.se wrote:
That might be a good thing to implement as a memory dump function in
libdivecomputer. That way users with future potential problems already
have a tool to produce the debug
On 17 May, 2015 - Rick Walsh wrote:
Try bt-device yada connect something and re-pair the computer with your
dongle.
Link keys are kept by the os so if you paired that device with that dongle
under a different os you need to re-pair the devices.
I don't have (on Fedora 22
On 19-05-15 22:10, Robert Helling wrote:
On 19 May 2015, at 20:15, Linus Torvalds torva...@linux-foundation.org
wrote:
Hmm. In fact, I guess you can already get it. There's left-over debugging
code in there, and you just have to enable logging (ENABLE_LOGGING during
the build) and make sure to
Thank you for your help and patience Anton,
On 19 May 2015 at 19:50, Anton Lundin gla...@acc.umu.se wrote:
bt-device and bt-adapter are quite nice tools from a old Gsoc project:
https://code.google.com/p/bluez-tools/
I don't know if they are packaged for Fedora.
If they are, it isn't obvious
On Tue, May 19, 2015 at 11:36 AM, Robert C. Helling hell...@atdotde.de wrote:
On 19 May 2015, at 18:22, Miika Turkia miika.tur...@gmail.com wrote:
Miika,
This is actually relevant information when someone surfaces
accidentally, thus we should not ignore it.
maybe this event should also
Hi Willem.
2015-05-19 10:50 GMT+02:00 Willem Ferguson willemfergu...@zoology.up.ac.za
:
Dirk you are absolutely correct. I ran universal after your last mail,
above, and the events are not shown in the xml, even though I see them
clearly in the binary dump. So the problem is on the
This is actually relevant information when someone surfaces
accidentally, thus we should not ignore it.
Signed-off-by: Miika Turkia miika.tur...@gmail.com
---
parse-xml.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/parse-xml.c b/parse-xml.c
index 6894ec0..c5ed21a
On 19 May 2015, at 20:15, Linus Torvalds torva...@linux-foundation.org wrote:
Hi,
Hmm. In fact, I guess you can already get it. There's left-over
debugging code in there, and you just have to enable logging
(ENABLE_LOGGING during the build) and make sure to set the log level
to enable debug
On 20 May, 2015 - Rick Walsh wrote:
Thank you for your help and patience Anton,
Then try to connect via rfcomm:
sudo rfcomm -i 00:15:83:3D:0A:57 connect /dev/rfcomm0 00:13:43:0E:6B:D0
Connecting is the bit that doesn't work, either from within
bluetoothctl or with rfcomm.
sudo
On Tue, May 19, 2015 at 9:43 PM, Linus Torvalds
torva...@linux-foundation.org wrote:
On Tue, May 19, 2015 at 11:36 AM, Robert C. Helling hell...@atdotde.de
wrote:
On 19 May 2015, at 18:22, Miika Turkia miika.tur...@gmail.com wrote:
Miika,
This is actually relevant information when someone
11 matches
Mail list logo
