The default license we use is LGPLv2.1. I think you should use a header similar to the one in dist/tools/ethos/ethos.c for example.
(adapt your name and email of course ;)

No license means that you grant no rights to use your code to anyone as far as I know.

@OlegHahm @haukepetersen ping :-)

@yogo1212, did you change anything else than the copyright notice? Usually, a PR should not be squashed until the reviewer says so. (See rule 9 of the development procedures).

@OlegHahm damn. sry. i didn't know about those :-(
no, i didn't change anything grave.
i've added more defines to prcm and fixed a duplicate value - as far as i can remember

@haukepetersen rebase on current master, commits unchanged
..
and i have a question regarding these:

        Building application: bindist (2/14) .......
                failed .. retrying .. retrying: cc2650stk
                success: arduino-due, cc2538dk, fox, iotlab-m3, mbed_lpc1768, nucleo-f103

BUILDTEST_MCU_GROUP=cortex_m3_1 dist/tools/travis-scripts/build_and_test.sh has cc2650stk fail almost everywhere..

cd examples/bindist ; BOARD=cc2650stk make clean all
works though.

do you have an explanation? i'm trying to figure it out atm

found it using make buildtest
this is the error:
/home/leon/git/RIOT/boards/cc2650stk/Makefile.include:13: *** Please point the environment var UNIFLASH_PATH to your uniflash path. Stop.

@haukepetersen ping again :-)
should now build successfully

just tell me when to squash :-p

lalalalalalalilalalilala

murdock helps saving the planet :-)
stops building old states when new stuff is pushed - nice

Could you just squash the 2 cpuid fixed into the cpu: add CC26x0-family commit and the boardfix default UNIFLASH_PATH to prevent buildtest from failing into the boards: add cc2650stk, then I will be happy to press the merge button :-)

@haukepetersen happy merging! :-p

CI is happy -> and go

but no need to backport to the current RC1

@emmanuelsearch :-)
@haukepetersen shiver i might be allergic to the word 'backport'..

So, main open issues for this board are currently a missing radio driver and problems with the timer, right?

@yogo1212 great. On to the next steps!
Is there an issue open for the timer problem?
Is there a PR WIP for the radio? @yogo1212 you are currently working on the 802.15.4 mode, correct?

Is there an issue open for the timer problem?

now there is.

@emmanuelsearch I could open a PR with the WIP - if you like.
If you just want to look, here it is: https://github.com/yogo1212/RIOT/tree/cc26x0_rfc

Right now, nothing has been done specific to either BLE or 802.15.4. Communication with the RF module is unstable. Do you prefer one?
There are arguments to start with either: I can use my notebook to test BLE or use existing support for 802.15.4 in RIOT (have no hardware, though)

@yogo1212 would love BLE, but for not the stack we have in RIOT has support for 802.15.4 so start with that mode. We can lend some SAMR21 to interop with it, no problem. BLE will be second phase. @haukepetersen you are of the same opinion?

yes

@yogo1212 could you open a wiki page for this board with instructions how to flash it etc.?
(e.g. https://github.com/RIOT-OS/RIOT/wiki/Board%3A-Mulle)

@emmanuelsearch my firefox crashed and the github-magic for saving the content failed as well..
had to start again and now it's too late -.-
https://github.com/RIOT-OS/RIOT/wiki/Board%3A-CC2650STK

gn8 ;-)

thanks @yogo1212