[dpdk-dev] [PATCH v4 1/5] ethdev: add firmware version get
qiming.yang at intel.com
Sun Jan 8 04:09:46 CET 2017
From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
Sent: Thursday, January 5, 2017 9:45 PM
To: Yang, Qiming <qiming.yang at intel.com>
Cc: dev at dpdk.org; Yigit, Ferruh <ferruh.yigit at intel.com>; Zhang, Helin <helin.zhang at intel.com>; Horton, Remy <remy.horton at intel.com>
Subject: Re: [dpdk-dev] [PATCH v4 1/5] ethdev: add firmware version get
2017-01-04 20:03, Qiming Yang:
> This patch adds a new API 'rte_eth_dev_fw_version_get' for fetching
> firmware version related information by a given device.
> + * Retrieve the firmware version of a device.
> + *
> + * @param port_id
> + * The port identifier of the device.
> + * @param fw_major
> + * A pointer to store the major firmware version of a device.
> + * @param fw_minor
> + * A pointer to store the minor firmware version of a device.
> + * @param fw_patch
> + * A pointer to store the firmware patch number of a device.
> + * @param etrack_id
> + * A pointer to store the nvm version of a device.
> + */
> +void rte_eth_dev_fw_version_get(uint8_t port_id, uint32_t *fw_major,
> + uint32_t *fw_minor, uint32_t *fw_patch, uint32_t *etrack_id);
After reading few comments, I think it should just fill a string.
There is no way the firmware version can be generalized or standardized.
If the application wants to do some processing like number comparisons, it has to be aware of the specific firmware version string format.
If you want to help the application to parse this string, it should be a PMD specific API.
Qiming: I agree with you.
More information about the dev