On Mon, Jun 15, 2015 at 03:01:44PM +0200, Jef Driesen wrote: > > I did already think about this :-) See [1] for some more background info. > > In a nutshell, the serial layer will be changed from a concrete > implementation into an abstract interface. This will allow us to have > multiple implementations: native (using kernel drivers), bluetooth (using > rfcomm sockets), usb-serial (cdc-acm, ftdi, pl2303, cp210x), etc
What about allowing the calling application to handle the creation of a serial communication stream and simply providing a callback to do so? Or am I missing another implementation issue here (it's been too long that I dug deeply into that part of libdivecomputer code) /D _______________________________________________ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
