3 comments:
Patch Set #2, Line 9: If for some reason a value for fw_config cannot be located
What use case is this change trying to target? Is it the case where fw_config is unprovisioned?
Patch Set #2, Line 12: fw_config_probe_nodefault
Under what circumstances would you use this function instead of fw_config_probe?
When probing devices with fw_config, when the value is undefined or
unable to be located, all devices will be successfully probed, and
fw_config_probe will always return true.
Do we really need a Kconfig for this? I think it should be the default behavior i.e. if FW_CONFIG is not provisioned, keep everything on by default. This should apply to all Chrome OS devices. I think we can add a Kconfig later if any non-Chrome OS devices using FW_CONFIG want to treat the unprovisioned case differently.
To view, visit change 47956. To unsubscribe, or for help writing mail filters, visit settings.