<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mjb/altos, branch branch-1.5</title>
<subtitle>AltOS - the operating system for Altus Metrum products
</subtitle>
<id>https://git.ethernal.org/mjb/altos/atom?h=branch-1.5</id>
<link rel='self' href='https://git.ethernal.org/mjb/altos/atom?h=branch-1.5'/>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/'/>
<updated>2014-09-27T06:00:37+00:00</updated>
<entry>
<title>altos: Make sure we drop the SPI mutex when aborting cc1120 recv</title>
<updated>2014-09-27T06:00:37+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2014-09-27T05:53:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=1b19c9b0c622b79a0fa251fd369eb6834256b4f7'/>
<id>urn:sha1:1b19c9b0c622b79a0fa251fd369eb6834256b4f7</id>
<content type='text'>
The cc1120 receive code is 'twisty', in that it acquires the SPI mutex
in the middle of an interrupt handler so that it can quickly start the
radio when the signal comes in. This means we have to be careful to
drop that mutex in all paths which leave the receive code, including
when the packet receive is aborted mid-way through the process.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'branch-1.5' of ssh://git.gag.com/scm/git/fw/altos into branch-1.5</title>
<updated>2014-09-13T23:57:11+00:00</updated>
<author>
<name>Bdale Garbee</name>
<email>bdale@gag.com</email>
</author>
<published>2014-09-13T23:57:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=453abb62172324989b38629772f32eddf0c46ea7'/>
<id>urn:sha1:453abb62172324989b38629772f32eddf0c46ea7</id>
<content type='text'>
</content>
</entry>
<entry>
<title>store cal value correctly even when we didn't need to change it</title>
<updated>2014-09-13T23:56:51+00:00</updated>
<author>
<name>Bdale Garbee</name>
<email>bdale@gag.com</email>
</author>
<published>2014-09-13T23:56:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=af61b0d46cb183cdc46e045b21de1bb6ac9b3cb3'/>
<id>urn:sha1:af61b0d46cb183cdc46e045b21de1bb6ac9b3cb3</id>
<content type='text'>
</content>
</entry>
<entry>
<title>altosui: Fix --replay to run in realtime after boost</title>
<updated>2014-09-13T23:01:06+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2014-09-13T22:51:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=76d597ba069d953010609c44b5030091dc2c3024'/>
<id>urn:sha1:76d597ba069d953010609c44b5030091dc2c3024</id>
<content type='text'>
I added the ability to rapidly replay files for AltosDroid to recover
from a crash, but didn't change AltosUI to use realtime mode again.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altosdroid: Update version code and name for 1.5</title>
<updated>2014-09-13T20:38:31+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2014-09-13T20:38:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=97dc44381b6d99ace326afae0aa606765e6dcddc'/>
<id>urn:sha1:97dc44381b6d99ace326afae0aa606765e6dcddc</id>
<content type='text'>
Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>updated ChangeLog for release</title>
<updated>2014-09-13T17:30:36+00:00</updated>
<author>
<name>Bdale Garbee</name>
<email>bdale@gag.com</email>
</author>
<published>2014-09-13T17:30:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=07336fe0cde8900d30858957164b09f05a6cf23e'/>
<id>urn:sha1:07336fe0cde8900d30858957164b09f05a6cf23e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>ignore cal_values file in bringup directory</title>
<updated>2014-09-13T17:29:19+00:00</updated>
<author>
<name>Bdale Garbee</name>
<email>bdale@gag.com</email>
</author>
<published>2014-09-13T17:29:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=d16e60858427bf7dbe83a858728ebf097a09207a'/>
<id>urn:sha1:d16e60858427bf7dbe83a858728ebf097a09207a</id>
<content type='text'>
</content>
</entry>
<entry>
<title>need multi-arch in fat build</title>
<updated>2014-09-13T17:28:19+00:00</updated>
<author>
<name>Bdale Garbee</name>
<email>bdale@gag.com</email>
</author>
<published>2014-09-13T17:28:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=40885ae5e6be66faf08cdb9b481d1d998856ca4b'/>
<id>urn:sha1:40885ae5e6be66faf08cdb9b481d1d998856ca4b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>altos: Make sure we don't beep out continuity twice in idle mode</title>
<updated>2014-09-13T17:26:21+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2014-09-12T02:56:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=e969172a81e24f70c349b10f429e69817900c307'/>
<id>urn:sha1:e969172a81e24f70c349b10f429e69817900c307</id>
<content type='text'>
If the battery voltage report takes longer than the initialiation
sequence, we could get to the state reporting after the state had
switched from startup to idle. This would result in continuity being
reported the first time through the loop. Then, as the state had
already changed, we'd pass through the while test and go back to
report continuity a second time.

Fixed by using the state remembered before beeping out the voltage to
decide whether to report the continuity.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altos: Fix ability to disable telemetry by setting interval to 0</title>
<updated>2014-09-13T17:26:13+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2014-09-11T22:00:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=800f3377b1a374ad5cf826aa897efdcb08059040'/>
<id>urn:sha1:800f3377b1a374ad5cf826aa897efdcb08059040</id>
<content type='text'>
For non-zero telemetry intervals, the radio code limits the value
based on the data rate. However, a zero interval means that telemetry
should be entirely disabled, so that value should be left alone when
checking.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
</feed>
