On 12/10/2013 04:20 PM, joeyli wrote: > > Actually, I am working on the timezone support of ACPI TIME and EFI > TIME. My current implementation is using EFI time services to deal with > clock in RTC. > > The ACPI TAD is a generic device that need parse DSDT for access it. The > DSDT parser is in subsystem initial stage. But in start_kernel, the > timekeeping_init() call wallclock functions to deal system clock with > RTC, it's too early for access ACPI TAD, so it still access CMOS > interface unless switch it to EFI services. > > If we adapt to ACPI TAD, then how does system clock deal with RTC > through it when system boot? > I don't really have a good answer for that. We could call the EFI services from the boot stub, of course, and pass in an approximate time (and perhaps the TSC value to go with it), but I'm not sure if that will be adequate. The other alternative would be to either parse ACPI earlier or initialize wall time later. -hpa -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
