> On Sep 30, 2019, at 11:55 AM, Anton Lundin wrote:
>>> Yea, its a quite complex call chain, but I thin it can be simplified to
>>> filling out struct libusb_device and calling usbi_connect_device on
>>> those.
>>>
>>> UsbManager.getDeviceList() gives us enough to fill in the libusb_device
>>>
On 30 September, 2019 - Dirk Hohndel wrote:
>
> > On Sep 30, 2019, at 12:05 AM, Anton Lundin wrote:
> >>
> >> I honestly think that this is the right approach. I started staring at the
> >> code and
> >> as expected the more I look the more I worry that I will get started and
> >> never
> >>
Apparently my OSTC was just as tired as I was (I sent that last email at
3:30am).
Replacing the (new) AA Alkaline with an (old) Saft battery was enough to give
it the
boost to start up again.
So for now I'm back in business with a "working" FTDI dive computer (the DC has
been broken for a long
> On Sep 30, 2019, at 12:05 AM, Anton Lundin wrote:
>>
>> I honestly think that this is the right approach. I started staring at the
>> code and
>> as expected the more I look the more I worry that I will get started and
>> never
>> get finished. My challenge is that I don't understand the
On 29 September, 2019 - Dirk Hohndel wrote:
> As I try to catch up with my large backlog of email...
>
>
> > On Sep 23, 2019, at 7:45 AM, Anton Lundin wrote:
> >
> > First of all, I'd just try to run our current code on a libusb
> > containing:
> >
