Added missing include of contiki-conf.h
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
Load Makefile.target for slip-radio

This loads Makefile.target into Makefile so we can check for TARGET==sky
when building this. Compilation for sky fails without it.

Signed-off-by: Johannes Gilger <heipei@hackvalue.de>
Makes RPL Initial Link Metric configurable
stm32f1x_cl: Add initial support for STM32F1x connectivity line

This currently supports the stm32f107, but support will be added for
the F105 shortly (missing a linker script and I can't properly test
without a devkit).
stm32f107_basic: Add support for a simple stm32f107 platform

This platform is a basic waveshare stm32f107 devkit which contains a
USART, USB device port, some buttons and some LEDs.  Unfortunately not
enough to bring up networking, but enough to test building and a
simple contiki shell
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.
stm32f1x_cl: Fix stm32f107 linker script

This is a critical fix which adds inclusion of the entire data/bss
section to the output ELF file.  Without it, the BSS section will not
be zeroed out
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.
Bug fix: changed the macro RPL_LOLLIPOP_INCREMENT to update the counter instead of returning the new value since this is how the macro is used today.
add_timer() does not set owning process
Moved from last cc65 release (2.13.3) to recent cc65 snapshot (2.13.9).

Relevant cc65 changes...

General:
- The compiler generates "extended" dependency info (like gcc) so there's no need for postprocessing whatsoever :-)
- The linker is very pernickety regarding the ordering of cmdline options so a custom linker rule is necessary :-(

Apple2:
- The various memory usage scenarios aren't specified anymore via separate linker configs but via defines overriding default values in the builtin linker config.

Atari:
- The builtin linker config allows to override the start addr so there no more need for a custom linker config.
- The C library comes with POSIX directory access. So there's no more need for for a custom coding.

CBM:
- The C library comes with POSIX directory access. So there's no more need for for a custom coding.
The recent cc65 snapshot yields somewhat small programs so we can move back to the MTU size used before.