<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mjb/altos/src/ao_test.c, branch debian/1.7-1</title>
<subtitle>AltOS - the operating system for Altus Metrum products
</subtitle>
<id>https://git.ethernal.org/mjb/altos/atom?h=debian%2F1.7-1</id>
<link rel='self' href='https://git.ethernal.org/mjb/altos/atom?h=debian%2F1.7-1'/>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/'/>
<updated>2011-08-26T03:49:11+00:00</updated>
<entry>
<title>altos: Restructure altos build to prepare for multi-arch support</title>
<updated>2011-08-26T03:49:11+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2011-08-26T03:43:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=9513be7f9d3d0b0ec29f6487fa9dc8f1ac24d0de'/>
<id>urn:sha1:9513be7f9d3d0b0ec29f6487fa9dc8f1ac24d0de</id>
<content type='text'>
Split out sources into separate directories:

	core:		architecture and product independent bits
	cc1111:		cc1111-specific code
	drivers:	architecture independent drivers
	product:	product-specific sources and Makefile fragments
	util:		scripts for building stuff

This should have no effect on the built products, but testing is encouraged

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altos: Ensure flight code gets first crack at new ADC data</title>
<updated>2011-01-17T04:24:34+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2011-01-15T20:12:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=69290588980bb15732a99eca5c911a3b6e9a37b9'/>
<id>urn:sha1:69290588980bb15732a99eca5c911a3b6e9a37b9</id>
<content type='text'>
Instead of having everyone wait on the raw ADC ring, have the flight
code wait on that and have everyone else wait for the flight code to
finish looking at the data and move its pointer forwards.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>Fix clock initialization to not try to use 32kHz xtal on P2_3/P2_4</title>
<updated>2009-06-17T20:55:23+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2009-06-17T20:55:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=e59520e343c2573b1b92c0b3c4aaa93e51bc55d3'/>
<id>urn:sha1:e59520e343c2573b1b92c0b3c4aaa93e51bc55d3</id>
<content type='text'>
None of our boards have a 32kHz xtal oscillator, instead we use those pins
(on Telemetrum) for the deployment firing circuits. The old clock
initialization code was switching from the 32kHz RC oscillator to the 32kHz
crystal and overriding our use of those pins.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>Use autotools, move altos to src subdir</title>
<updated>2009-06-04T17:41:34+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2009-06-04T17:41:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=210dbaa23cdacf3a6f2d6e23493e96ee2ac9bca7'/>
<id>urn:sha1:210dbaa23cdacf3a6f2d6e23493e96ee2ac9bca7</id>
<content type='text'>
Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
</feed>
