mjb/altos, branch 1.2.1

update Changelog for 1.2.1 release, again

2013-05-21T15:32:22+00:00

Merge branch 'branch-1.2' of ssh://git.gag.com/scm/git/fw/altos into branch-1.2

2013-05-21T15:31:48+00:00

update changelog for 1.2.1 release

2013-05-21T15:29:30+00:00

update configure.ac to reflect version 1.2.1

2013-05-21T15:28:53+00:00

doc: Update description of graph window to note new tabs (config and map)

2013-05-21T04:41:01+00:00

Signed-off-by: Keith Packard

Create release notes for 1.2.1

2013-05-21T04:37:20+00:00

Move most of the 1.2 content to the 1.2.1 block Signed-off-by: Keith Packard

altos/telemega: The last two igniters are apogee and main

2013-05-21T04:16:25+00:00

Not the first two. TeleMega v0.3 has these marked on the silk Signed-off-by: Keith Packard

libaltos: Build the linux library targets when doing a 'fat' build

2013-05-17T10:51:16+00:00

These are necessary for the fat release, so make sure they're built then. Signed-off-by: Keith Packard

libaltos: use PurgeComm in Windows altos_close to abort in-progress ops

2013-05-17T10:51:16+00:00

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

altos/cc1111: Hack on USB driver to make Windows happy

2013-05-17T10:51:16+00:00

The Windows modem driver is quite chatty at startup time, getting and setting the comm parameters each time the device is opened. Sometimes, when setting the parameters, the cc1111 would STALL EP0. Most of the time, Windows would happily pass this as an error back to AltosUI which would then re-try the open (and succeed, most of the time). Sometimes, Windows would stall for 30 seconds before passing the error back. This made the whole UI freeze, and I suspect most people assumed our app had died. A bit of analysis with the beagle USB sniffer and I discovered the STALL settings, but there wasn't any correlation between the data on the wire and when the STALL would be generated. So, I found a couple of other cc1111 USB stacks on the net and just looked to see how our driver differed. There wasn't anything clearly related, but there were a list of small differences: 1) Other drivers didn't bother waiting for the hardware to ack the USBADDR setting; doing it this way means we can set the address *before* acking the setup packet. It'll get set eventually, at which point the device will start responding to packets again. Easy to fix, and saves a bit of code space too. 2) The other drivers set the STALL bit for setup packets which aren't understood. This shouldn't have any effect on 'good' systems as those shouldn't ever be generating bogus setup packets anyways. The driver already handled the STALL state in the interrupt handler, the only requirement was to figure out when to explicitly set the STALL bit. That required moving the state updating code from the start of the ep0 setup handling to the end, after the setup packet had been examined and data queued in or out as appropriate. 3) Our driver explicitly queued an IN packet for any setup request that wasn't waiting for an OUT pack. This appears to tie in with the USBADDR change above as before I made that change, this change caused the driver to fail to respond to most setup packets. This was simple once the above change was made, just move the generation of the IN packet inside the code that switched to the IN state. Signed-off-by: Keith Packard