ISSUE! - Licensed under MCD-ST Liberty SW License Agreement V2
./hw/bsp/stm32f3discovery/src/arch/cortex_m4/startup_stm32f303xc.s
./hw/bsp/stm32f3discovery/src/system_stm32f30x.c
./hw/mcu/stm/stm32f3xx/include/mcu/*
./hw/mcu/stm/stm32f3xx/src/*
./hw/mcu/stm/stm32f4xx/include/mcu/system_stm32f4xx.h
+ a couple of other files
We can raise this with legal, alternatively we could move the MCU &
BSP definitions to github. People would need to config newt to
point at the github URL (newt add-clutch), but it would get around
ASF license issues.
Personally, I'm leaning heavily towards this option: I think code
from the default ASF repository should be pure, as otherwise people
will adopt packages thinking they are Apache licensed and find out
later they are not.
It is not allowed to release a package with such a "gotcha" :-) ... so
yes, a solution where an *optional* feature can be selected by the user,
understanding they are then restricted by the licensing of that optional
feature. ... will Mynewt be useful for other platforms besides STM (eg.
ARM) without that optional github-based feature?
Yup-- and at least for one of the files, they have an alternative file
that doesn't have this license. So we'll likely be able to use our OS
on another processor in the same exact family. These are header files
and startup files that are specifically targeted to the STMicro
processors: it is really silly that they have that proviso in there,
because they are unusable on any other platform except their own.
Sterling
