On 30/1/22 7:19 am, Joel Sherrill wrote:
> Hi
> https://lists.rtems.org/pipermail/build/2022-January/031425.html
>
> bsp-builder is reporting this. Help appreciated. Looks like it could
> be a tooling issue
>
> Failures Report
> ===
>1 posix-debug riscv/frdme310arty build:
>
On 27/1/22 6:09 pm, Sebastian Huber wrote:
> On 27/01/2022 03:24, Chris Johns wrote:
>> On 25/1/22 5:37 pm, Sebastian Huber wrote:
>>> On 25/01/2022 01:09, Chris Johns wrote:
On 25/1/22 1:39 am, Sebastian Huber wrote:
> how do we want to proceed with the integration of the new validation
On 29/1/22 2:36 am, Sebastian Huber wrote:
> On 28/01/2022 15:28, Christian MAUDERER wrote:
>> So I think at the moment, the engineering manual is wrong. The release branch
>> will always have the number N.0.0 as long as we don't change the release
>> process.
>
> I think the manual is right and
Hello Sebastian,
I guess you will be in charge of reviewing this patch. Please allow me
to explain motivation behind it plus add some questions.
You know I'd like to update STM32H7 HAL to the latest code provided by
STMicro to be able to use it on my stm32h735g-dk board. Before doing
that I'd
---
bsps/arm/stm32h7/console/console-usart1-cfg.c | 8 +--
bsps/arm/stm32h7/start/bspstarthooks.c| 2 +-
bsps/arm/stm32h7/start/stm32h7-config-clk.c | 4 ++
bsps/arm/stm32h7/start/stm32h7-config-fls.c | 8 ++-
bsps/arm/stm32h7/start/stm32h7-config-osc.c | 17 +++
