title: News
ctime: 2009-12-16
-mtime: 2012-08-15
+mtime: 2014-08-18
+
+### 2014-08-15
+* Port TMI [[tinyos]] enhancements and our [[cp210x]] enhanced driver to
+ Ubuntu 14.04 LTS, Trusty Tahr. Packages for Trusty are available from
+ the [[aptrepo]].
+
+---
### 2012-08-15
Reorganize the website into three categories: [[blog]], [[misc]], and
### 2010-11-04
[[TinyOS]] release 2.1.1-4.4 is available.
-* Revert to how 2.1.0 creates TOSMAKE_PATH. It adds TINYOS_MAKE_PATH to the
- end, allowing local code to override system code. 2.1.1 adds TINYOS_MAKE_PATH
- to the beginning, preventing local overrides.
+* Revert to how 2.1.0 creates TOSMAKE\_PATH. It adds TINYOS\_MAKE\_PATH to the
+ end, allowing local code to override system code. 2.1.1 adds
+ TINYOS\_MAKE\_PATH to the beginning, preventing local overrides.
* Various USCI fixes.
* Provide new system components SharedArbiterC and SharedSplitControlC. We use
- these to activate subsystems only when needed, where the subsystems are usable
- by multiple higher-level components concurrently.
+ these to activate subsystems only when needed, where the subsystems are
+ usable by multiple higher-level components concurrently.
* TinyOS by default presumes that on boot UartStream interface providers have
the receive interrupt active. We had presumed that it was better to allow
the code to specifically activate the interrupt when it was ready to handle
TMI has also updated to nesc-1.3.2. A big thank you to idgay, who fixed bug
[3013497](http://sourceforge.net/tracker/?func=detail&aid=3013497&group_id=56288&atid=480036)
that was preventing us from using nescc with GCC on Ubuntu Linux. Using the
-nx_ types of nescc to define cross platform data structures in header files
+nx\_ types of nescc to define cross platform data structures in header files
shared between TinyOS targets and other systems is much more elegant than
managing a parallel set of definitions defined programmatically by function
calls to the TinyOS C-SDK.
projects / oss-web.git / blobdiff