Amar Takhar created a merge request: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/582
Project:Branches: amar/rtems:contrib2 to rtems/rtos/rtems:main Author: Amar Takhar Assignee: Amar Takhar ## Summary I've tested the `arm/stm32h7` and ` arm/stm32u5-grisp-nano` BSPs with this I will do further testing later today but both build fine with tests. Some things to note: * I have removed RTEMS doxygen markers * Line endings had to be converted as they were accidentally imported with Windows line endings for \``` tm32u5xx` `` * I've noted the original commits that were re-applied over top of the pure imports * The entire upstream repositories were imported this makes updating far easier * The old build copied the headers to the `include/` directory to the BSP I have pointed them to the include directories in the contrib repos. In the future we should build 3rd party code as its own library so the includes are limited to the contrib files not not globally available. This is how it works now I have not changed it. I will also import these repositories to the https://gitlab.rtems.org/contrib as mirrors so we can keep track of changes. We can't rely on upstream repos existing forever. This also creates 3 tags please see the `README.md` in the change for instructions on how we should keep things updated. * contrib/bsps/arm/stm32h7/cmsis-device-h7/1.10.4 * contrib/bsps/arm/stm32h7/stm32h7xx_hal_driver/1.11.3 * contrib/bsps/arm/stm32u5/stm32u5xx-hal-driver/1.5.0 Tags will always point to the pure import with our local changes in between this way we can diff between upstream versions and our own changes easily it also exposes the load we carry on modifying upstream code and if we should try to avoid the changes or upstream them. Updates #5294 <!--Default settings, if it is a dropdown it will set after submission--> -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/582 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list bugs@rtems.org http://lists.rtems.org/mailman/listinfo/bugs
