Skip to content

Conversation

@mrjimenez
Copy link
Contributor

@mrjimenez mrjimenez commented Nov 14, 2025

The default configuration for all STM32 microcontrollers in HAL is
to replace the ehternet MAC address with the address configured in
replace address zero. In "modules/hal", Grep for:

macDefaultConf.SourceAddrControl = ETH_SOURCEADDRESS_REPLACE_ADDR0;

But this is a bad thing for bridging. Since Zephyr ethernet LL code
always writes the source address, this patch has no impact on normal
operation. And has the benefit of maintaining the source MAC address of
bridged packets.

This patch just formats the files eth_stm32_hal_v1 and the file
stm32_hal_v2.c file before the real patch, otherwise the changes
would be hard to read.

Signed-off-by: Marcelo Roberto Jimenez <marcelo.jimenez@gmail.com>
The default configuration for all STM32 microcontrollers in HAL is
to replace the ehternet MAC address with the address configured in
replace address zero. In "modules/hal", Grep for:

macDefaultConf.SourceAddrControl = ETH_SOURCEADDRESS_REPLACE_ADDR0;

But this is a bad thing for bridging. Since Zephyr ethernet LL code
always writes the source address, this patch has no impact on normal
operation. And has the benefit of maintaining the source MAC address
of bridged packets.

Signed-off-by: Marcelo Roberto Jimenez <marcelo.jimenez@gmail.com>
@sonarqubecloud
Copy link

@mrjimenez mrjimenez closed this Nov 15, 2025
@mrjimenez mrjimenez deleted the stm32_fix_checksum branch November 15, 2025 01:48
@erwango
Copy link
Member

erwango commented Nov 17, 2025

@mrjimenez Sorry we didn't had time to look at this point. Any reason to close that early ?

@mrjimenez
Copy link
Contributor Author

Hi Erwan,

I have already resubmitted it. There were too many compliance errors, I wanted to look carefully at what happened, because I had not seen them before submitting. I think I got my editor fixed now.

The new pull request is this one: #99429

Regards,
Marcelo.

@erwango
Copy link
Member

erwango commented Nov 17, 2025

@mrjimenez Ok, but next time, please keep the same PR. What you need to do is clean up your branch locally and force push once you're done. Otherwise there are too much PR created and it becomes confusing for reviewers.

@mrjimenez
Copy link
Contributor Author

Ok, got it, sorry for that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants