[En-Nut-Discussion] MCD_ST_LIBERTY and ST_GUIDANCE_ONLY question

Harald Kipp harald.kipp at egnite.de
Sun May 19 12:57:09 CEST 2013

Hi Uwe,

On 10.05.2013 13:47, Uwe Bonnes wrote:

> In the meantime, a lot changed and files with MCD_ST_LIBERTY and
> ST_GUIDANCE_ONLY are used for
> 1. for the basic headers, defining the device
> 2. for system initialization
> 3. for some F1 devices
> 4. for the ST CDC USB implemenations.
> To keep in sync with the vendor, I think (1.) will not change

This is bad.

> (2.) could be rewritten.


> (3.) will go away with some more work on the devices

Same view here.

> (4.) I like to pull from the tree, as libopencm3 has much easier to use USB
> implementaion and a free license

All this lawyer stuff requires precise statements. The STM licenses are
"free licenses" as well. From a first short look I see, that libopencm3
is published under LGPLv3.

Note: You can link against LGPL libraries, because it is up to the
vendor of the final product to check, whether all licenses fit. Basic
Nut/OS is BSDL. If any source code is included into Nut/OS, which isn't
BSDL, the user needs to, in general, explicitly confirm the use of
another license. This, however, does not apply to similar or more
permissive licenses like "Public Domain".

> So I would like to remove the MCD_ST_LIBERTY and ST_GUIDANCE_ONLY from many
> configuration places. I would only keep it where we list a ST licended
> C-File in the configuration item, e,g, arch/cm3/stm32f4.nut STM32F4 PLL
> Configuration. On items where we compile our code I would
> like to remove the requirement, e.g. at following configuration item:

What I understood so far: You want to use header files published under
STM license into BSDL code and declare the result BSDL'ed code. Is that
what you meant?



More information about the En-Nut-Discussion mailing list