Comment 3 for bug 1933503

Thanks for your information.

Revisit the test, I recalled that the test with value EFI_UNSPECIFIED_TIMEZONE (2047) instead of value 1 in SCT is on purpose. Please refer to https://lists.ubuntu.com/archives/fwts-devel/2017-November/010038.html. Basically it is because we found some HP platforms will use the exact time zone value on earth in the UEFI plugfest, although 1 is allowed by UEFI spec, but not the actual value users will use.

The value EFI_UNSPECIFIED_TIMEZONE(2047) is actually defined in UEFI specification. If firmware not support it, the status code returned value EFI_INVALID_PARAMETER of settime may be expected.

I think the real issue here is that the FW do something instead of returned an error when EFI_UNSPECIFIED_TIMEZONE is not supported. Will it cause the end users setting Local time but get unexpected behaviors?

Currently, I think it is better to keep testing with EFI_UNSPECIFIED_TIMEZONE(2047) instead of changing the value that allow the firmware which not support EFI_UNSPECIFIED_TIMEZONE value to pass the test. Maybe add some advice information for notice on this failure will be a good idea.