Michal Kazior <[email protected]> writes:
> The wmi-tlv firmware contains additional
> versioning info. It may help reporting/debugging.
>
> Signed-off-by: Michal Kazior <[email protected]>
[...]
> void ath10k_print_driver_info(struct ath10k *ar)
> {
> - ath10k_info(ar, "%s (0x%08x, 0x%08x) fw %s api %d htt %d.%d wmi %d cal
> %s max_sta %d\n",
> + ath10k_info(ar, "%s (0x%08x, 0x%08x) fw %s api %d htt %d.%d wmi %d cal
> %s max_sta %d build %u.%u.%u.%u\n",
> ar->hw_params.name,
> ar->target_version,
> ar->chip_id,
> @@ -134,7 +134,11 @@ void ath10k_print_driver_info(struct ath10k *ar)
> ar->htt.target_version_minor,
> ar->wmi.op_version,
> ath10k_cal_mode_str(ar->cal_mode),
> - ar->max_num_stations);
> + ar->max_num_stations,
> + ar->fw_build_major,
> + ar->fw_build_minor,
> + ar->fw_build_si,
> + ar->fw_build_crm);
So now we print two different firmware versions to the user? That's just
confusing. It's ok to print this build id in debug level, but not in
info level. From user's point of view we should have only one firmware
version.
I would rather make sure that ATH10K_FW_IE_FW_VERSION always contains
the correct version string and then developers map whatever they need
from that string.
--
Kalle Valo
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
