@mudsut4ke: Is there any reason to keep this as a separate sonic_fw package, or would be better to add get_fw_version() and install_firmware() methods to the ChassisBase and ModuleBase classes sonic_platform_base?

@jleveque , Maybe a reason that firmware install tool is installed in sonic platform and cannot be used on pmon docker

@mudsut4ke: Can you elaborate? We would like to consolidate all platform-specific abstraction into the new sonic_platform_base package.

If we were to install the sonic_platform_base package in both the pmon docker and also in the base image, would this suffice?

@jleveque , In my case the CPLD upgrade tool installed in base image (sonic-net/sonic-buildimage#2446)

if you install sonic_platform_base package in both the pmon docker and base image, that will cover my requirement

@jleveque , Any comment?

I think it would be best to add this functionality to the ChassisBase and ModuleBase classes in the new platform API, and we can install the package in the base image as well as the pmon container.

@mudsut4ke , any update on this?

@lguohan , I will move this tool to sonic_platform_base follow Joe suggesttion

@jleveque , In ChassisBase they Identified BIOS/FPGA/CPLD as component
Should I add new ComponentBase ? or Just add the firmware management to ModuleBase is enough ?

@mudsut4ke: I think adding the firmware management functions to ChassisBase and ModuleBase is enough.

Move to #34