MITHILESH MATTAPALLI created a merge request: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1104

Project:Branches: mithileshm/rtems:refactor-dev-drivers to rtems/rtos/rtems:main
Author:   MITHILESH MATTAPALLI



## Summary

This merge request resolves an architectural violation by moving 
hardware-specific CAN and I2C drivers out of the core OS API layer (`cpukit/`) 
and into the Board Support Package layer (`bsps/shared/`).

Changes included:

* Relocated `ctucanfd` and `can-virtual` drivers from `cpukit/dev/can/` to 
`bsps/shared/dev/can/`.
* Relocated associated CAN hardware headers to `bsps/include/dev/can/`.
* Relocated hardware-specific I2C drivers from `cpukit/dev/i2c/` to 
`bsps/shared/dev/i2c/` (leaving `i2c-bus.c` and `i2c-dev.c` in the core 
framework).
* Relocated hardware-specific I2C headers to `bsps/include/dev/i2c/`.
* Updated `spec/build/cpukit/librtemscpu.yml` and `spec/build/bsps/obj.yml` to 
enforce the new architectural paths.

Closes #5196

## Generative AI

* **Prompt used:** Various prompts regarding `waf` build system syntax and bulk 
terminal operations, such as: _"What is the correct YAML array formatting to 
relocate cpukit/dev/can to bsps/shared/dev/can within the RTEMS obj.yml build 
specification?"_
* **Which AI model was used:** Google Gemini 3.1 Pro
* **How AI was used for the contribution:** Formatting and build system 
mechanics. The AI was used exclusively as a command-line and formatting utility 
to generate the bulk `git mv` commands and to correctly alphabetize the YAML 
file arrays within `spec/build/bsps/obj.yml` and 
`spec/build/cpukit/librtemscpu.yml`. All changes were manually audited and 
verified via local `./waf` compilation.
* **Copyright Statement:** I have not used a product that claims copyright over 
its output, and I have legitimate access to this tool.

milestone %7.1

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1104
You're receiving this email because of your account on gitlab.rtems.org.


_______________________________________________
bugs mailing list
[email protected]
http://lists.rtems.org/mailman/listinfo/bugs

Reply via email to