[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <52B4B5B2.70306@zytor.com>
Date: Fri, 20 Dec 2013 13:25:06 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: joeyli <jlee@...e.com>
CC: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Alessandro Zummo <a.zummo@...ertech.it>,
Matt Fleming <matt@...sole-pimps.org>,
Matthew Garrett <matthew.garrett@...ula.com>, Elliott@...com,
samer.el-haj-mahmoud@...com, Oliver Neukum <oneukum@...e.de>,
werner@...e.com, trenn@...e.de, JBeulich@...e.com,
linux-kernel@...r.kernel.org, rtc-linux@...glegroups.com,
x86@...nel.org,
"linux-efi@...r.kernel.org" <linux-efi@...r.kernel.org>,
linux-acpi@...r.kernel.org, Borislav Petkov <bp@...e.de>
Subject: Re: [RFC PATCH 00/14] Support timezone of ACPI TAD and EFI TIME
On 12/20/2013 01:10 PM, H. Peter Anvin wrote:
> On 12/19/2013 09:38 PM, joeyli wrote:
>>
>> If don't use EFI time, then the first priority is using ACPI TAD if it
>> present. Due to ACPI TAD is a generic acpi device that's need OS parsing
>> DSDT table before set system time.
>>
>> Either move DSDT parser from subsystem initial stage to start_kernel or
>> move timekeeping initial to after DSDT be parsed. Which one you think is
>> more possible and risk less? Then I will try that way.
>>
>
> I discussed the DSDT/SSDT parsing issue with Rafael and he claims it
> would require a lot of restructuring. Unfortunately ACPI is at this
> point done rather late, as I understand. All of this is a big problem.
>
The thing is that we probably need this anyway, because that is how one
detects PNP0B0x devices as well. We do need to get away from blindly
poking ports 0x70-73.
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists