[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3476450.BMEcId2Lgj@vostro.rjw.lan>
Date: Fri, 20 Dec 2013 23:18:56 +0100
From: "Rafael J. Wysocki" <rjw@...ysocki.net>
To: Matt Fleming <matt@...sole-pimps.org>
Cc: "H. Peter Anvin" <hpa@...or.com>, joeyli <jlee@...e.com>,
Alessandro Zummo <a.zummo@...ertech.it>,
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 Friday, December 20, 2013 09:50:56 PM Matt Fleming wrote:
> On Fri, 20 Dec, at 01:43:38PM, H. Peter Anvin wrote:
> >
> > Possibly... will have to investigate. I would also ask if the same
> > applies to the PNP0B0x devices -- all we really need there is the
> > presence/absence indication and the I/O port base.
>
> It's worth noting that efi_late_init() exists solely because the ACPI
> infrastructure to find the BGRT table isn't available any earlier.
>
> If we could setup ACPI earlier that would be awesome.
I'm not sure 100%, but I *think* we need to do that with interrupts enabled.
At least after mm_init(), because it relies on things initialized there if I
remember correctly.
>From what I can tell at the moment, it might be possible to move it before
efi_enter_virtual_mode() if that would help.
Thanks,
Rafael
--
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