Re: Invalid PBLK length

[Jens Haug <haug-X6ztD3ggwzuBAmxm6OvjtTjhTm2NLCe8@public.gmane.org>]

> > Ok, I can see in the code (processor.c) that in the function
> > acpi_processor_get_inf the value of object.processor.pblk_lenght
> > is checked, and in case it's smaller than 6 this error is thrown.
> > If it's 6 or greater, then addresses for C2 and C3 are assigned.
> > But why can't PBLK be 5 and only C2 be used? Couldn't we just 
> > disable C3 and still assign the address for C2 as pblk_address+4?
> > I think it was done that way in prpower.c Revision 32. That gave
> > me a working C2.  
> 
> Well, specs issue?

Yes, I see. I hadn't found that, but Matthew pointed me to the
right chapter of the specs.

> > BTW, how can I make my FADT human readable? It isn't shown by 
> > acpidmp, and I'd like to be able to check some values myself.
> 
> ./acpidmp FACS | ./acpitbl
> 
> Note that it is FACS (the signature of the table), not FADT (I don't know
> why the sig. and the name of this table are not the same).

But this FACS doesn't give me much information (since it's only
the signature, I guess).
It sais:

Signature:		FACS
Length:			64
Hardware Signature:	0x00000000
Firmware Waking Vector: 0x00000000
Global Lock:		0x00000000
Flags:			0x00000000

I'm curious what I'll find in the FADT. I mean, 5 clearly is 
neither 0 nor 6, so there might be some other really heavy bugs.
I'll get me the 


Jens

-- 
Jens Haug
IKFF Universität Stuttgart              Tel. 0711/685-6422
Pfaffenwaldring 9                       Fax  0711/685-6356
70550 Stuttgart	                haug-X6ztD3ggwzuBAmxm6OvjtTjhTm2NLCe8@public.gmane.org



-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/