On Wed, Apr 25, 2018 at 04:24:25PM -0700, Linus Torvalds wrote:
> On Wed, Apr 25, 2018 at 4:21 PM, Dirk Hohndel wrote:
> >>
> >> Ok, so it's using the BLE code, it just isn't able to get a service list.
> >> Odd.
> >
> > Indeed - what's the next step to debug this? My guess is
On Wed, Apr 25, 2018 at 4:21 PM, Dirk Hohndel wrote:
>>
>> Ok, so it's using the BLE code, it just isn't able to get a service list.
>> Odd.
>
> Indeed - what's the next step to debug this? My guess is that we should
> somehow dump what we get back?
We do. Normally you'd see
On Wed, Apr 25, 2018 at 04:17:18PM -0700, Linus Torvalds wrote:
> > With a bunch more debugging code added (and a rewritten function to report
> > the supported transports), here are the logs from the attempts with BLE
> > and with BT to connect to my Petrel 2 / dual stack:
> >
> > "10.440:
On Wed, Apr 25, 2018 at 4:08 PM, Dirk Hohndel wrote:
>>
>> And after rebooting everything I finally got it connected.
>> Subsurface sees it both as LE and classic device. I tried downloading
>> via both protocols and in both cases got "Dive computer transport
>> not supported".
On Wed, Apr 25, 2018 at 01:50:46PM -0700, Dirk Hohndel wrote:
>
> > On Apr 25, 2018, at 1:34 PM, Dirk Hohndel wrote:
> >> or similar. But it _would_ be good to test that this actually makes
> >> Petrel 2 work with rfcomm. Because it's certainly possible that there
> >> is
On 25 April, 2018 - Linus Torvalds wrote:
> On Wed, Apr 25, 2018 at 10:38 AM, Anton Lundin wrote:
> >
> > I've tested it now, via the serial layer, libftdi layer, classic bt
> > layer, and with your latest patch BLE and they all work.
>
> Ok, so for you the classic BT case
> On Apr 25, 2018, at 1:34 PM, Dirk Hohndel wrote:
>> or similar. But it _would_ be good to test that this actually makes
>> Petrel 2 work with rfcomm. Because it's certainly possible that there
>> is something else wrong with rfcomm.
>
> Right now I'm testing.
>
> (1)
On Wed, Apr 25, 2018 at 08:40:21PM +, Chirana Gheorghita Eugeniu Theodor
wrote:
> Hello guys,
> Just did a short try dive with a poseidon seven and arrived home, dowloaded
> the dive from Petrel 1 using android app 4.7.8.69 and surprise. When I
> enter the text in notes section it always
Hello guys,
Just did a short try dive with a poseidon seven and arrived home, dowloaded
the dive from Petrel 1 using android app 4.7.8.69 and surprise. When I
enter the text in notes section it always capitalizes . I force small
letters and the next letter I type after a small one is again
On Wed, Apr 25, 2018 at 01:04:36PM -0700, Linus Torvalds wrote:
> On Wed, Apr 25, 2018 at 12:57 PM, Linus Torvalds
> wrote:
> >
> > Odd. It was _supposed_ to apply to current master.
>
> Ok, apparently you worked it out.
Yes
> Anyway, the commit message could be
On Wed, Apr 25, 2018 at 11:51 AM, Dirk Hohndel wrote:
>
> I have a Petrel (single stack BT) and Petrel 2 (dual stack) and will test
> those over lunch today. I'll try to test Mac and Android (embarrassingly,
> I currently don't have a Linux laptop with working BLE...)
Note that
On Wed, Apr 25, 2018 at 12:57 PM, Linus Torvalds
wrote:
>
> Odd. It was _supposed_ to apply to current master.
Ok, apparently you worked it out.
Anyway, the commit message could be something simple along the lines of
Do a better job of picking which transport
On Wed, Apr 25, 2018 at 11:57 AM, Dirk Hohndel wrote:
>
> Which tree should this apply against? Maybe I'm just extra dumb today, but
> it applies neither to current master nor to your tree from yesterday.
> What am I missing (besides a brain, I mean)?
Odd. It was _supposed_ to
On Wed, Apr 25, 2018 at 11:57:13AM -0700, Dirk Hohndel wrote:
> On Wed, Apr 25, 2018 at 09:47:27AM -0700, Linus Torvalds wrote:
> >
> > So attached is a trial patch. It makes sense to me, but I don't have
> > any rfcomm devices to try with.
>
> Which tree should this apply against? Maybe I'm
On 25/04/2018 20:51, Dirk Hohndel wrote:
On Apr 25, 2018, at 11:44 AM, Linus Torvalds
wrote:
On Wed, Apr 25, 2018 at 10:38 AM, Anton Lundin wrote:
I've tested it now, via the serial layer, libftdi layer, classic bt
layer, and with your
On Wed, Apr 25, 2018 at 09:47:27AM -0700, Linus Torvalds wrote:
>
> So attached is a trial patch. It makes sense to me, but I don't have
> any rfcomm devices to try with.
Which tree should this apply against? Maybe I'm just extra dumb today, but
it applies neither to current master nor to your
On Wed, Apr 25, 2018 at 10:38 AM, Anton Lundin wrote:
>
> I've tested it now, via the serial layer, libftdi layer, classic bt
> layer, and with your latest patch BLE and they all work.
Ok, so for you the classic BT case now works too with that patch that
I sent out a couple of
On 18 April, 2018 - Linus Torvalds wrote:
> On Wed, Apr 18, 2018 at 3:37 PM, Robert Helling wrote:
> >
> > Couldn’t get the dive computer configuration to work either with BLE or
> > classic.
>
> Did this work with the previous release (4.7.8 or whatever)?
>
> I had been
On Wed, Apr 25, 2018 at 8:43 AM, Dirk Hohndel wrote:
>
> We should now focus on figuring out the problems with the Shearwater
> downloads.
> For some people these fail on rfcomm, for some they fail on BLE but succeed on
> rfcomm, and it seems that some can't download from their
Ok ... than i can confirm that for perdix does not work either. One of my
friends tested the official release
On Wed, Apr 25, 2018, 11:43 Long, Martin wrote:
>
> On 25 April 2018 at 09:07, Chirana Gheorghita Eugeniu Theodor <
> off...@adaptcom.ro> wrote:
>
>> Hmm very
Dirk,
> On 25. Apr 2018, at 02:02, Dirk Hohndel wrote:
>
> (because for insane reasons you have to have a signing key available in order
> to build for device)
you probably know that Travis suggests using private environment variables to
hold encryption keys for such
Hmm very weird.
I use now latest 4.7.8 and successfully connects to Petrel 1 but will not
connect to mh older tusa zen iq-900 over usb ftdi.
On Wed, Apr 25, 2018, 10:26 Long, Martin wrote:
> The BLE thing has basically made subsurface unusable for me for the last
> month
22 matches
Mail list logo