Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Mellanox] Update mlnx-fw-upgrade.j2 to support BF3 DPU NIC FW. #31

Closed
wants to merge 1 commit into from

Conversation

oleksandrivantsiv
Copy link
Owner

Why I did it

Extend mlnx-fw-upgrade.j2 to support the upgrade of the DPU NIC FW

Work item tracking
  • Microsoft ADO (number only):

How I did it

Add support for the new device to the script

How to verify it

Compile and install an image

Which release branch to backport (provide reason below if selected)

  • 201811
  • 201911
  • 202006
  • 202012
  • 202106
  • 202111
  • 202205
  • 202211
  • 202305

Tested branch (Please provide the tested image version)

Description for the changelog

Link to config_db schema for YANG module changes

A picture of a cute animal (not mandatory but encouraged)

@oleksandrivantsiv oleksandrivantsiv force-pushed the mlx-fw-upgrade branch 2 times, most recently from e58bc4d to 2240d51 Compare August 7, 2024 01:36
@@ -339,7 +427,13 @@ function UpgradeFW() {
if [[ "${_FW_CURRENT}" == "${_FW_AVAILABLE}" ]]; then
ExitSuccess "firmware is up to date"
else
if [[ "${DRY_RUN}" == "${YES_PARAM}" ]]; then
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we need this? Just for user convenience?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it, used it in bfnet.sh. I think "upgrade_check" or similar name would be better than dry_run

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't agree with this. --dry-run is widely used by Linux commands for purposes like this.


RunCmd "${LIST_CONTENT_CMD} -i ${_FW_FILE} -d ${_MST_DEVICE} -o ${LIST_CONTENT_FILE}"

ERROR_CODE="$?"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@oleksandrivantsiv why do we need it? RunCmd exits script if rc != 0

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

removed, thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants