Problem with STM32 HAL license

[Joel Sherrill]

On Mon, Jun 13, 2022 at 11:19 AM Duc Doan <dtbpkmte at gmail.com> wrote:

> Dear all,
>
> I am working on my GSoC project about adding features to the STM32F4 BSP.
> I am planning to include STM32 HAL from STMicroelectronics (which can be
> found here:
> https://github.com/STMicroelectronics/STM32CubeF4/tree/master/Drivers/STM32F4xx_HAL_Driver)
> into RTEMS. However, the license text in each code file might be unclear:
> "This software is licensed under terms that can be found in the LICENSE
> file in the root directory of this software component. If no LICENSE file
> comes with this software, it is provided AS-IS", especially the part about
> a LICENSE file "in the root directory". The root directory is likely the
> STM32F4xx_HAL_Driver folder that I have included the direct link above. I
> would like to ask if I need to modify (adding text clarification in the
> license text for each file) the files, or should I do something else to be
> safe?
>

Is this the text found in each source file?

https://github.com/STMicroelectronics/STM32CubeF4/blob/master/Drivers/STM32F4xx_HAL_Driver/Src/stm32f4xx_hal.c#L9

I don't think this is a direct copy of the 3 paragraph BSD license which we
have at the top of the RTEMS source tree (
https://git.rtems.org/rtems/tree/LICENSE.BSD-3-Clause). I'm prone to
suggest putting a LICENSE.STM-3-Clause at the top of the RTEMS tree and
adding a comment in ifdef __rtems__ at the top of each file saying the
LICENSE file is there.

This impacts other imports from STM so I am curious what Karel, Sebastian,
and Andrei are seeing for the license in the code they are importing and
what they plan to do.

I don't think we can have a generically named file "LICENSE" way down in
the tree. We have the pattern of having licenses at the top of the RTEMS
source tree.

--joel


>
> Best,
>
> Duc Doan
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20220613/5637236a/attachment.htm>