Re: [RFC PATCH 04/14] ACPI: Add ACPI 5.0 Time and Alarm Device driver

2014-01-09 Thread Rafael J. Wysocki
On Thursday, January 09, 2014 11:47:39 AM joeyli wrote: > 於 三,2014-01-08 於 09:56 -0800,H. Peter Anvin 提到: > [...] > > > Document of Windows XP: > > > > > http://www.freelists.org/post/windows_errors/what-error-messages-really-mean-WinXP-IO-Ports-Blocked-from-Bios-AML-on-Windows-XP > > > > > > If j

Re: [RFC PATCH 04/14] ACPI: Add ACPI 5.0 Time and Alarm Device driver

2014-01-08 Thread H. Peter Anvin
On 01/08/2014 07:47 PM, joeyli wrote: > > Unfortunately current acpica leaks the SystemCMOS handler: > > ACPI Error: Region SystemCMOS (ID=5) has no handler (20131115/exfldio-299) > I'm sorry, I can't parse either your statement or the error message... sounds like there is a bug here, too.

Re: [RFC PATCH 04/14] ACPI: Add ACPI 5.0 Time and Alarm Device driver

2014-01-08 Thread joeyli
於 三,2014-01-08 於 09:56 -0800,H. Peter Anvin 提到: [...] > > Document of Windows XP: > > > http://www.freelists.org/post/windows_errors/what-error-messages-really-mean-WinXP-IO-Ports-Blocked-from-Bios-AML-on-Windows-XP > > > > If just for ACPI TAD testing, we can remove the port protection > check of

Re: [RFC PATCH 04/14] ACPI: Add ACPI 5.0 Time and Alarm Device driver

2014-01-08 Thread H. Peter Anvin
On 01/08/2014 06:59 AM, joeyli wrote: > > ACPICA denied AML access RTC ports. > > I tried to access 0x70, 0x71 ports in ASL on a real machine, ACPICA > denied AML access to those ports. I got the following dmesg: > > hwvalid-0188 hw_validate_io_request: Denied AML access to port > 0x

Re: [RFC PATCH 04/14] ACPI: Add ACPI 5.0 Time and Alarm Device driver

2014-01-08 Thread joeyli
於 二,2014-01-07 於 08:35 -0800,H. Peter Anvin 提到: > On 01/07/2014 02:40 AM, joeyli wrote: > > > > Due to accessing CMOS through ASL need enable SMM support in OVMF, > > Why? The CMOS is its own ASL address space, and you need that anyway to > be able to access the RTC proper. If you don't want to

Re: [RFC PATCH 04/14] ACPI: Add ACPI 5.0 Time and Alarm Device driver

2014-01-07 Thread H. Peter Anvin
On 01/07/2014 02:40 AM, joeyli wrote: > > Due to accessing CMOS through ASL need enable SMM support in OVMF, Why? The CMOS is its own ASL address space, and you need that anyway to be able to access the RTC proper. If you don't want to use it because you don't want to export any indication of a

Re: [RFC PATCH 04/14] ACPI: Add ACPI 5.0 Time and Alarm Device driver

2014-01-07 Thread joeyli
於 一,2014-01-06 於 21:37 -0800,H. Peter Anvin 提到: > On 01/06/2014 12:58 AM, joeyli wrote: > > 於 二,2013-12-31 於 16:42 -0800,H. Peter Anvin 提到: > >> On 12/19/2013 09:41 PM, joeyli wrote: > > What platform do you have that has TAD support? I am wondering how this > was tested. > > >

Re: [RFC PATCH 04/14] ACPI: Add ACPI 5.0 Time and Alarm Device driver

2014-01-06 Thread H. Peter Anvin
On 01/06/2014 12:58 AM, joeyli wrote: > 於 二,2013-12-31 於 16:42 -0800,H. Peter Anvin 提到: >> On 12/19/2013 09:41 PM, joeyli wrote: What platform do you have that has TAD support? I am wondering how this was tested. >>> >>> It's a testing platform that's only support get/set time

Re: [RFC PATCH 04/14] ACPI: Add ACPI 5.0 Time and Alarm Device driver

2014-01-06 Thread joeyli
於 四,2014-01-02 於 16:09 +0800,Lan Tianyu 提到: > > diff --git a/drivers/acpi/bus.c b/drivers/acpi/bus.c > > index bba9b72..3f7a075 100644 > > --- a/drivers/acpi/bus.c > > +++ b/drivers/acpi/bus.c > > @@ -689,6 +689,9 @@ static int __init acpi_init(void) > > pci_mmcfg_late_init(); > > a

Re: [RFC PATCH 04/14] ACPI: Add ACPI 5.0 Time and Alarm Device driver

2014-01-06 Thread joeyli
於 二,2013-12-31 於 16:42 -0800,H. Peter Anvin 提到: > On 12/19/2013 09:41 PM, joeyli wrote: > >> > >> What platform do you have that has TAD support? I am wondering how this > >> was tested. > >> > > > > It's a testing platform that's only support get/set time functions of > > ACPI TAD. > > > > It

Re: [RFC PATCH 04/14] ACPI: Add ACPI 5.0 Time and Alarm Device driver

2014-01-02 Thread Lan Tianyu
2013/12/19 Lee, Chun-Yi : > This patch add the driver of Time and Alarm Device in ACPI 5.0. > Currently it only implemented get/set time functions and grab > the capabilities of device when driver initial. > > This driver also register rtc-acpitad platform device for RTC ACPITAD > stub driver using

Re: [RFC PATCH 04/14] ACPI: Add ACPI 5.0 Time and Alarm Device driver

2013-12-31 Thread H. Peter Anvin
On 12/19/2013 09:41 PM, joeyli wrote: >> >> What platform do you have that has TAD support? I am wondering how this >> was tested. >> > > It's a testing platform that's only support get/set time functions of > ACPI TAD. > It would be really, really good to get this into Qemu (either SeaBIOS or

Re: [RFC PATCH 04/14] ACPI: Add ACPI 5.0 Time and Alarm Device driver

2013-12-19 Thread joeyli
於 四,2013-12-19 於 07:22 -0800,H. Peter Anvin 提到: > On 12/18/2013 11:51 PM, Lee, Chun-Yi wrote: > > This patch add the driver of Time and Alarm Device in ACPI 5.0. > > Currently it only implemented get/set time functions and grab > > the capabilities of device when driver initial. > > > > This drive

Re: [RFC PATCH 04/14] ACPI: Add ACPI 5.0 Time and Alarm Device driver

2013-12-19 Thread H. Peter Anvin
On 12/18/2013 11:51 PM, Lee, Chun-Yi wrote: > This patch add the driver of Time and Alarm Device in ACPI 5.0. > Currently it only implemented get/set time functions and grab > the capabilities of device when driver initial. > > This driver also register rtc-acpitad platform device for RTC ACPITAD