Moved Ieee154Address and LqiRead to radio folders.

As mentioned in the todo of
http://docs.tinyos.net/tinywiki/index.php/BLIP_2.0_Platform_Support_Guide
I moved some radio specific code to the specific radio folders.
ReadLqi now in radio chips folder.

Rather than use a bunch of #defines that defeat the purpose of the
modularity of TinyOS I moved the appropriate Lqi code to the relevant
radio folder.
Created a simple interface for Blip.

Rather than wiring directly to the CC2420 driver, this interface layer
allows Blip to wire to something more generic.
changes for the rpi
Split Ieee154BareC into two files

The metadata interfaces that BLIP needs are now their own configuration
file, in case a radio driver wants to provide Ieee154BareC without
providing any of the metadata features (such as LPL or a PacketLink
layer). These should be logically separated anyway.

Added better Ieee154BareC header comment to describe why that component
exists.
Cleaned up the DS2411 code for Epic

- Changed variable and macro names. Removed anything refering to Dallas
as that doesn't make much sense anymore.
- Moved onewire to the system folder and made a more intuitive Hpl file
in epic/chips
- Moved LocalIeeeEui64 code to its own folder in platforms/epic. This
should be separated from the ds2411 chip.
- Made the filenames and file functions easier to understand. It is
still 7 files to get the Eui64, but that is better than 11 and they make
more sense and are located in intuitive folders.
Created DS24X1

Many changes to merge the ds2411 and ds2401 to ds24x1.

- Moved OneWire to tos/lib
- Updated epic, telosb, iris, and mica platforms to use ds24x1
- Changed all variables to be *ds24x1*
- Moved the LocalIeeeEui64C/P to tos/chips/ds24x1. I'm not in love with
this, but I'm not sure where a better place would be. LocalIeeeEui64C is
tied to ds24x1, so it does make sense to put them in the same folder,
but it wouldn't be intuitive to someone looking for LocalIeeeEui64*.
- Tested with epic, and verified that iris and telosb compile.
- Ignored shimmer. Shimmer has yet another copy of the ds24x1 code
(really? THREE copies?) but it has its own constants (which are only
slightly off from what is in OneWireMaster, but maybe it matters) and I
don't want to change it without being able to test it.
Changed the TestEui app to compile on Epic

This app didn't follow the Printf rules, and I'm not sure how it
compilied for anyone.
Converting shimmer to ds24x1 driver

Updated the relevant platform files and tested that all 3 shimmer
platforms can compile TestEui.
Corrected paths concerning micaz/LocalIeeeEui64C

Moved platforms/micaz/LocalIeeeEui64C.nc to platforms/micaz/eui64 so
that the iris platform will not use it instead of the ds24x1 version of
LocalIeeeEui64.

Also fixed compile bug with mica2/chips/ds2401/HplDs24x1C.nc.
Removed all old .cvsignore files
Updated .gitignore

Added all of the various make output
Removed assumed environment variables

Many places in /tools (and in READMEs) code or documentation assumes
that there are environment variables set. In order to remove the
requirement that environment variables need be set, this commit changes
structure to work without the environment variables. Generally, this
means adding an argument so that callers of scripts can pass in the
information the environment variable used to provide.

A major consequence of this is that ncc --print-tosdir no longer works.
Any instance of this is now removed.
Set TINYOS_ROOT_DIR in Makefile, change var names

This removes the non-desireable requirement that a user must set
environment variables in order to build TinyOS. The $TOSROOT variable
then trickles through the makefiles and in makerules $TOSDIR is set.

The overhead to do this is small (1 line in each application makefile)
but it should really help make tinyos more user friendly.

TOSROOT is set with "?=" meaning that it won't override TOSROOT if it is
already set by an environment variable.

Makefile.include in the root sets TOSDIR and MAKERULES before including
$(MAKERULES). This allows the current env variables to override the
derived settings.

Changing TinyOS Make system variable names:

| Old Variable        | Proposed Variable Name      | Default Value                    | Purpose                                                             |
|---------------------|-----------------------------|----------------------------------|---------------------------------------------------------------------|
| TOSROOT             | TINYOS_ROOT_DIR             | relative to application Makefile | Base for all other variable defaults                                |
| TOSDIR              | TINYOS_OS_DIR               | $TINYOS_ROOT_DIR/tos             | Path to `/tos` folder containing main system source to compile with |
| TINYOS_MAKE_PATH    | TINYOS_MAKE_DIR             | $TINYOS_ROOT_DIR/support/make    | Path to `/make` that contains the targets, extras, and rules        |
| MAKERULES           | TINYOS_MAKERULES            | $TINYOS_MAKE_DIR/Makerules       | Path to main makefile                                               |
| TINYOS_MAKELOCAL    | TINYOS_MAKELOCAL            | $TINYOS_MAKE_DIR/Makelocal       | Path to optional Makelocal file                                     |
| TINYOS_MAKEDEFAULTS | TINYOS_MAKEDEFAULTS         | $TINYOS_MAKE_DIR/Makedefaults    | Path to Makedefaults                                                |
| TOSMAKE_PATH        | TINYOS_MAKE_DIR_ADDITIONAL  | unset                            | Space separated paths of additional `support/make` directories      |
Moved python code to tools/, now gets installed

In order to remove more environment variable usage, the tinyos python
code must be installed on the user's system instead of in the tinyos
tree. This commit moves all the python to tools so automake will install
it. Doing this requires one subtle change: "import tos" will no longer
work. It needs to be "from tinyos import tos" now.

I think I updated all of the relevant files.

One note: python3 is handled a bit weirdly, and therefore tos-serlook.py
may not be able to find tinyos.misc.hexdump. It seems that
/usr/local/lib/python3/dist-packages is not in the search path by
default. I fixed this by adding "tinyos.pth" containing the correct
directory to /usr/local/lib/python3.2/dist-packages.
Moved CoAP to /tools dir

The CoAP support code will now be built and installed with tinyos-tools.

I updated coap.extra to reflect the moved .c files.

Conflicts:
	tools/.gitignore
Moved blip support to /tools directory

Will not compile the blip sdk code on cygwin as it only supports linux and mac.

Conflicts:
	tools/.gitignore
Moved sf and serial_tun to /tools

I have no idea if anyone still uses this code. The configure script for
sf is out of date and does not work with newer automake (I updated it).

I also renamed some binaries so they can be installed. If the user is
installing TinyOS, they may as well _install_ tinyos. Why make them hunt
around for different binaries? If something shouldn't be installed, then
the question is why is it distributed with the main TinyOS source? It
should be some sort of optional extra somewhere, not part of the main
source. Hard drives are big, just give me all of the TinyOS tools.
Moved cpp version of sf to /tools

Because there are 2 sf applications, the cpp version is named sf2.
Moved java to /tools; Removed env vars

Java is now compiled and installed with tinyos-tools