Re: [ACPI] Invalid PBLK length

[Matthew W. <wi...@de...>]

On Thu, Dec 19, 2002 at 12:17:40AM +0900, Adachi, Kenichi wrote:
> I didn't check code, but if that said address space type 127 does mean "Functi
> onal Fixed Hardware (0x7F)", then your processor expects that OS processor dri
> ver knows the specific address to control voltage scaling state transition. Us
> ually it's done by accessing MSRs. This has been true for AMD PowerNow! and Tr
> ansmeta LongRun, and Intel's new Geyserville I/F which will be unveiled on Ban
> ias in the near future. These are mostly under NDA, therefore I can't be speci
> fic, however there're several public documents which explain this stuff a bit 
> more.

you're right.  Andy, could we add something like this?

diff -u -p -r1.6 actypes.h
--- drivers/acpi/include/actypes.h      10 Dec 2002 22:02:09 -0000      1.6
+++ drivers/acpi/include/actypes.h      18 Dec 2002 15:28:47 -0000
@@ -579,6 +579,7 @@ typedef u8                              
 #define ACPI_ADR_SPACE_CMOS             (ACPI_ADR_SPACE_TYPE) 5
 #define ACPI_ADR_SPACE_PCI_BAR_TARGET   (ACPI_ADR_SPACE_TYPE) 6
 #define ACPI_ADR_SPACE_DATA_TABLE       (ACPI_ADR_SPACE_TYPE) 7
+#define ACPI_ADR_SPACE_FIXED_HARDWARE  (ACPI_ADR_SPACE_TYPE) 127
 
 
 /*


-- 
"It's not Hollywood.  War is real, war is primarily not about defeat or
victory, it is about death.  I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk