On 13:40-20231128, Vishal Mahaveer wrote:
This patch series brings in the latest board configurations for am62 and am62a device.
Patch "board: ti: am62x/am62ax: Update virtual interrupt allocations in board config" is needed for booting with the latest TIFS and DM firmware [1].
[1] https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/log/?h=ti -linux-firmware SHA: e891ddc65c55bfa7111e4f45834b7c26444dff72
U-boot boot log - https://gist.github.com/vishalmti/6b38fb80d557478131d5aaed5aeb3596
Vishal Mahaveer (4): board: ti: am62x/am62ax: Formatting updates to board config files board: ti: am62ax: Add C7x resource allocation entries to board config board: ti: am62x/am62ax: Update MCU GPIO interrupt allocation in board config board: ti: am62x/am62ax: Update virtual interrupt allocations in board config
board/ti/am62ax/rm-cfg.yaml | 522 +++++++++++++++--------------------- board/ti/am62x/rm-cfg.yaml | 481 +++++++++++++-------------------- 2 files changed, 396 insertions(+), 607 deletions(-)
Sorry, but this is completely confusing. There is no documentation to indicate there is backward compatibility break in firmware. do all users need to upgrade firmware along with board config updates?? what is the minimum firmware version that is supported? is there an ABI version check that should be enforced?
Is there absolutely no way for people to use the new firmware and keep their old u-boot? Rather disappointing to see backward compatible breakage occurring this stage of the device. This is not appreciated.
Please see if you can fix your firmware to maintain compatibility (as has been the case for year+ now)
Understood the concern. Sorry about that.
Will send a V2 with the virtual interrupt patch dropped. The firmware will be updated to have the change reverted that causes backward compatibility issue.
-- Regards, Nishanth Menon Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D