Added support for motelist and uploading to Z1 motes under Mac OSX
Baudrate now is configured taking into account the MCU frequency, instead of using fixed values for 8MHz freq
removed  tag from z1 Makefile.common
fixed z1 i2c bug where 2 extra bytes were read with every i2c-receive
fixed z1 i2c bug where 2 extra bytes were read with every i2c-receive
add working routines to turn the mc1322x radio on and off
Use the RTC only as the main timer.

This is a major change to how the main tick interrupt is handled on
the mc1322x platforms. Instead of using two timer resources, TMR0 and
RTC, this patch unifies all the timers to use the RTC. This is enabled by
implementing etimers as scheduled rtimers. The main advantage (aside
from freeing TMR0 for general use) is have the Contiki timebase come
from the same source that will be used for sleeping and wakeup.
set the pin defaults properly to reduce current consumption on
sleeping M12s.
Merge pull request #109 from malvira/use-rtc-factor

Improvments to enable low-power mode on mc1322x
Adjusted names.
Fixed Win32 'platform build'.
Use plain ASCII chars for lines on Win32 console CTK.
Merge pull request #121 from oliverschmidt/master

Several minor adjustments.
There's no point in ctk_restore() for standalone GUI builds.
Merge pull request #122 from oliverschmidt/master

There's no point in ctk_restore() for standalone GUI builds.
Fixed severe bug in PSOCK_READTO (?)

Either I found and fixed a severe bug in PSOCK_READTO() or I misunderstood something completely. To me PSOCK_READTO() is supposed to return if either the supplied character was read or if the user supplied buffer is exhausted - sor far so good.

However if the latter occurs up to now PSOCK_READTO() was continuing to process characters already read from the network (aka present in the uIP buffer) in order to check if the supplied character was found there and adjust the return value accordingly. But this means that the character processed this way were lost forever for the caller as the next call to PSOCK_READTO() would continue to read past the characters processed this way.

Therefore I removed that character processing altogether. So now if the user supplied buffer is exhausted before the supplied character is found the next call to PSOCK_READTO() starts exactly where previous call left off.
Fixed severe bug in PSOCK_READTO (?)

Either I found and fixed a severe bug in PSOCK_READTO() or I misunderstood something completely. To me PSOCK_READTO() is supposed to return if either the supplied character was read or if the user supplied buffer is exhausted - sor far so good.

However if the latter occurs up to now PSOCK_READTO() was continuing to process characters already read from the network (aka present in the uIP buffer) in order to check if the supplied character was found there and adjust the return value accordingly. But this means that the character processed this way were lost forever for the caller as the next call to PSOCK_READTO() would continue to read past the characters processed this way.

Therefore I removed that character processing altogether. So now if the user supplied buffer is exhausted before the supplied character is found the next call to PSOCK_READTO() starts exactly where previous call left off.
Merge remote-tracking branch 'refs/remotes/origin/master'
Allow user to read the result of wget.

Several retro targets clear the screen after program termination so allow user to read the result.
Be consistent with tab chars in Makefiles.