On Mon, Apr 24, 2017 at 10:26 AM, Linus Torvalds
wrote:
> On Mon, Apr 24, 2017 at 12:44 AM, Rick Walsh wrote:
>>
>> Summary of brief testing, it appears:
>> - download works with a BLE controller
>> - this breaks pairing (at least for me)
>> - this breaks bluetooth support for at least one non-BL
On Mon, Apr 24, 2017 at 12:44 AM, Rick Walsh wrote:
>
> Summary of brief testing, it appears:
> - download works with a BLE controller
> - this breaks pairing (at least for me)
> - this breaks bluetooth support for at least one non-BLE controller
Hmm. The ble-prep branch really should change abso
Hi Linus (et al)
On 20 April 2017 at 06:49, Rick Walsh wrote:
>
>
> On 20 Apr. 2017 5:49 am, "Linus Torvalds"
> wrote:
>
> On Wed, Apr 19, 2017 at 12:33 PM, Dirk Hohndel wrote:
> >
> >> It's really just three commits:
> >>
> >> custom serial: pass device_data_t to bluetooth operation fun
Am 24.04.2017 um 01:47 schrieb Linus Torvalds:
> On Sun, Apr 23, 2017 at 1:49 PM, Anton Lundin wrote:
>>
>> As far as I've understood things, even the scan for devices are
>> completely different, so is the reason that Qt merges the two scan
>> results?
>
> So as far as Qt seems to be concerned,
On Sun, Apr 23, 2017 at 1:49 PM, Anton Lundin wrote:
>
> As far as I've understood things, even the scan for devices are
> completely different, so is the reason that Qt merges the two scan
> results?
So as far as Qt seems to be concerned, "scan for devices" is all
exactly the same. Only after th
On 19 April, 2017 - Linus Torvalds wrote:
> Dirk, Anton, (and possibly others who currently use RFCOMM),
>
> would you mind taking a look at my "ble-prep" branch in
>
> https://github.com/torvalds/subsurface-for-dirk.git ble-prep
>
> that I have *not* made into a pull request yet, because
Am Donnerstag, 20. April 2017, 01:06:31 CEST schrieb Linus Torvalds:
> On Wed, Apr 19, 2017 at 3:45 PM, Linus Torvalds
>
> wrote:
> > Because as part of reading the Qt Bluetooth docs (I'm resigned to
> > having to look at this myself), I noticed that the docs clearly say
> > that the "QBluetoothD
It used to work, but when I tried last week I couldn't get it to work on Mac...
--
>From my phone
Original Message
From: Linus Torvalds
Sent: Wed Apr 19 15:45:09 PDT 2017
To: Dirk Hohndel , Anton Lundin ,
Subsurface Mailing List
Subject: Re: Very timid beginning f
On Wed, Apr 19, 2017 at 3:45 PM, Linus Torvalds
wrote:
>
> Because as part of reading the Qt Bluetooth docs (I'm resigned to
> having to look at this myself), I noticed that the docs clearly say
> that the "QBluetoothDeviceInfo::address()" data is invalid on MacOS
> and iOS, and that you should us
On Wed, Apr 19, 2017 at 12:17 PM, Linus Torvalds
wrote:
> Dirk, Anton, (and possibly others who currently use RFCOMM),
Side note: does the bluetooth code actually work on MacOS at all?
Because as part of reading the Qt Bluetooth docs (I'm resigned to
having to look at this myself), I noticed tha
On 20 Apr. 2017 5:49 am, "Linus Torvalds"
wrote:
On Wed, Apr 19, 2017 at 12:33 PM, Dirk Hohndel wrote:
>
>> It's really just three commits:
>>
>> custom serial: pass device_data_t to bluetooth operation function
>> Expand 'bluetooth_mode' from a boolean to an emun
>> Prepare to
On Wed, Apr 19, 2017 at 12:33 PM, Dirk Hohndel wrote:
>
>> It's really just three commits:
>>
>> custom serial: pass device_data_t to bluetooth operation function
>> Expand 'bluetooth_mode' from a boolean to an emun
>> Prepare to split the custom serial operations up by RFCOMM-vs
On Wed, Apr 19, 2017 at 12:17:41PM -0700, Linus Torvalds wrote:
> Dirk, Anton, (and possibly others who currently use RFCOMM),
>
> would you mind taking a look at my "ble-prep" branch in
>
> https://github.com/torvalds/subsurface-for-dirk.git ble-prep
>
> that I have *not* made into a pull
13 matches
Mail list logo