Basically mlnx-fw-upgrade.sh is used in two places: 1. https://github.com/Azure/sonic-buildimage/blob/201811/files/scripts/syncd.sh#L109 ```bash /usr/bin/mst start /usr/bin/mlnx-fw-upgrade.sh /etc/init.d/sxdkernel start /sbin/modprobe i2c-dev ``` 2. https://github.com/Azure/sonic-buildimage/blob/201811/device/mellanox/x86_64-mlnx_msn2700-r0/platform_reboot#L32 ```bash ParseArguments "$@" ${FW_UPGRADE_SCRIPT} --upgrade --verbose EXIT_CODE="$?" ``` In first case the `stdout` is redirected to `syslog` directly by `systemd`. Thus, the `syslog` logger is only required in second case. #### Why I did it * To improve ASIC/CPLD FW upgrade logging * To improve CPLD upgrade time #### How I did it * Added `syslog` logger support * Replaced `_pciconf0` -> `_pci_cr0` to reduce CPLD upgrade time #### How to verify it 1. mlnx-fw-upgrade.sh --upgrade |
||
---|---|---|
.. | ||
cpld | ||
docker-saiserver-mlnx | ||
docker-syncd-mlnx | ||
docker-syncd-mlnx-rpc | ||
hw-management | ||
issu-version | ||
mft | ||
mlnx-platform-api | ||
mlnx-sai | ||
mlnx-sfpd | ||
sdk-src | ||
.gitignore | ||
cpld.mk | ||
docker-orchagent-mlnx.mk | ||
docker-ptf-mlnx.mk | ||
docker-saiserver-mlnx.mk | ||
docker-syncd-mlnx-rpc.mk | ||
docker-syncd-mlnx.mk | ||
fw.mk | ||
hw-management-wd.mk | ||
hw-management-wd.sh | ||
hw-management.mk | ||
issu-version.mk | ||
libsaithrift-dev.mk | ||
mft.mk | ||
mlnx-ffb.mk | ||
mlnx-ffb.sh | ||
mlnx-fw-upgrade.j2 | ||
mlnx-platform-api.mk | ||
mlnx-sai.mk | ||
mlnx-sfpd.mk | ||
mlnx-ssd-fw-update.mk | ||
mlnx-ssd-fw-update.sh | ||
one-image.mk | ||
platform.conf | ||
rules.mk | ||
sdk.mk |