mjb/altos/libaltos, branch telegps-v0.3AltOS - the operating system for Altus Metrum products
https://git.ethernal.org/mjb/altos/atom?h=telegps-v0.32013-05-17T10:49:42+00:00libaltos: use PurgeComm in Windows altos_close to abort in-progress ops2013-05-17T10:49:42+00:00Keith Packardkeithp@keithp.com2013-05-17T10:34:50+00:00urn:sha1:6735a391c2a1e3be01ac9e68b44ec0974592c11c
Instead of manually signalling the related events, use PurgeComm which
can then abort the operations itself. Also make sure all of the
relevant handles are set to INVALID before closing them to avoid race conditions.
Signed-off-by: Keith Packard <keithp@keithp.com>
libaltos: Build the linux library targets when doing a 'fat' build2013-05-17T10:49:42+00:00Keith Packardkeithp@keithp.com2013-05-17T10:27:20+00:00urn:sha1:bd8d061d0f63158b5b03814d77cb76fdf5a0abad
These are necessary for the fat release, so make sure they're built then.
Signed-off-by: Keith Packard <keithp@keithp.com>
libaltos: Delay after opening bluetooth device on linux2013-04-21T03:22:41+00:00Keith Packardkeithp@keithp.com2013-04-21T03:16:28+00:00urn:sha1:2e28d3541b8da31ebef5a199baf8f544d238298e
Writes immediately after the open disappear sometimes.
Signed-off-by: Keith Packard <keithp@keithp.com>
libaltos: Try Bluetooth open 5 times on EBUSY2013-04-21T03:22:08+00:00Keith Packardkeithp@keithp.com2013-04-21T03:05:01+00:00urn:sha1:02a564bbc3a23b4f90685e8b29083ddb3e4b3563
After closing Bluetooth, it can take a second before the device is up
for another connection. Hang around retrying a few times.
Signed-off-by: Keith Packard <keithp@keithp.com>
libaltos: Retry Windows serial port open five times2013-04-12T23:37:49+00:00Keith Packardkeithp@keithp.com2013-04-12T05:16:03+00:00urn:sha1:25c01719f17be8da73a859867c14df0fc29b5441
Maybe this helps?
Signed-off-by: Keith Packard <keithp@keithp.com>
libaltos: Open FTDI serial devices twice on Windows.2013-03-03T01:46:29+00:00Keith Packardkeithp@keithp.com2013-03-03T01:46:29+00:00urn:sha1:784edcda52d681bbc9302fbc7efb80cb214f71b8
Looks like the Windows FTDI driver has 'issues' and opening it only
once doesn't work correctly. Just close and re-open the device and it
seems to be perfectly happy.
Who knows?
Signed-off-by: Keith Packard <keithp@keithp.com>
libaltos: Need to check for tty/ttyACMx before ttyACMx2013-01-11T05:48:31+00:00Keith Packardkeithp@keithp.com2013-01-11T05:26:20+00:00urn:sha1:12a9bd0479db25cbe45c0385913315cc1e0bc892
Otherwise, we'll find 'tty' when looking for 'ttyACMx' and no good
will come from that
Signed-off-by: Keith Packard <keithp@keithp.com>
micropeak: Create Mac OS X package2013-01-06T20:52:25+00:00Keith Packardkeithp@keithp.com2013-01-06T20:52:25+00:00urn:sha1:0f05b1996122b6c6bce81ca33e85c2a65c3ded18
Includes the FTDI driver and the MicroPeak app
Signed-off-by: Keith Packard <keithp@keithp.com>
Add separate code path for listing FTDI devices2013-01-05T18:35:20+00:00Keith Packardkeithp@keithp.com2013-01-05T18:35:20+00:00urn:sha1:746ae98829a0fc15577ae0f7b506112178f481e3
This lets the library do different things for FTDI devices, as is
required on Windows (for instance)
Signed-off-by: Keith Packard <keithp@keithp.com>
libaltos: Remove a couple of spurious debug printfs2013-01-02T17:06:22+00:00Keith Packardkeithp@keithp.com2013-01-02T17:06:22+00:00urn:sha1:8a5666bcf4949b846589c000e1620afe39593f57
Signed-off-by: Keith Packard <keithp@keithp.com>