On 5/26/26 8:00 AM, [email protected] wrote:
From: Daniel Nehrkorn <[email protected]>
We need the EEPROM bus configuration, if we have the env located in EEPROM.
Since there is no eeprom_execute_command() anymore, we have to configure
it implicitly.
This reverts commit e3c2042ae7d188e00e48d984e373a2de505d8b77.
Sorry, not this way. If the env in EEPROM loading does not work with DM,
then it has to be updated to be compatible with DM, that means look up
the EEPROM, get its udevice etc.
Commit e9774afedd20 ("cmd: eeprom: Refactor command execution into
function by action") may provide a hint for the correct fix, possibly
use i2c_get_chip_for_busnum() to get the EEPROM udevice and proceed from
there.
