Testing ftdi code

[Willem Ferguson]

On 31/10/2016 22:01, Anton Lundin wrote:
> I think you did some snafu there, and didn't capture a log file using 
> the ftdi driver? (or overwrote your log file...) The ftdi log file 
> should start with: INFO: Open: name=ftdi Anyhow. The same "error" 
> shows up in these log files, so I'm confident that this is just a 
> quirk of the oceanic_atom2 protocol. There are quite a bit of retry / 
> error handling in the code so I don't think there is anything to worry 
> about. I would love to see a real ftdi log from that computer 
> anyway... //Anton 
Apologies. I need to keep a few balls in the air, including the 
character device number that changes when I reboot.

Here it is.

Kind regards,
willem

-------------- next part --------------
A non-text attachment was scrubbed...
Name: CustomUSBdriver.log
Type: text/x-log
Size: 139985 bytes
Desc: not available
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20161031/d29d2025/attachment-0001.bin>