lwIP | stm32h7: Add Ethernet driver for STM32H743ZI Nucleo (!37)

[Claudio Grasso (@ClaudioGrasso)]

Claudio Grasso commented on a discussion: https://gitlab.rtems.org/rtems/pkg/rtems-lwip/-/merge_requests/37#note_139843


Hi Kinsey,

We are almost done with the driver integration and would like to clarify the intended directory structure to ensure we align with the project's standards.

We have observed two distinct patterns in the repository:

1. **Native/Adapter Code**: Directories inside **`rtemslwip/`**(e.g., **`tms570`**, **`zynq`**) appear to contain code written specifically for RTEMS integration.
2. **Vendor Imports**: Directories at the root (e.g., **`cpsw`**,**`embeddedsw`**) appear to contain third-party vendor code imported with minimal changes.

Since the STM32H7 driver is derived from the **STM32CubeH7 Firmware Package** (an external source, similar to **`cpsw`** and **`embeddedsw`**), we interpreted your previous feedback about using its "own top level directory" to mean it should be placed at the root (i.e., **`/stm32h7/`**) and retain its original filenames (e.g., **`ethernetif.c`**).

Could you please confirm if this root-level placement is the correct approach? Or should the driver ideally be adapted into **`rtemslwip/stm32h7/`** to match the other architecture folders?

Thank you for your guidance.

Claudio

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/pkg/rtems-lwip/-/merge_requests/37#note_139843
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20260123/88f4d20d/attachment-0001.htm>