Thread (1 message) 1 message, 1 author, 2003-05-12
  • (off-list ancestor, not in this archive)
  • Re: iasl · Ducrot Bruno <hidden> · 2003-05-12

Re: iasl

From: Ducrot Bruno <hidden>
Date: 2003-05-12 09:48:16

On Fri, May 09, 2003 at 10:37:08PM +0000, sjb wrote:
Moore, Robert wrote:
quoted
In this case, we know that PCI_Config space is always accessed by 32-bit
reads/writes, so change the Op region definition to length 4.
OK .. so I change the 0x01 here
quoted
quoted
quoted
quoted
              OperationRegion (PIUC, PCI_Config, 0x74, 0x01)
to a 0x04 and re-compile and .. *drum roll* ..

Compilation complete. 0 Errors, 0 Warnings, 0 Remarks, 380 Optimizations

Excellent!

The _only way_ to fix *correctly* this error is to know the
definition of all Field like 

Field (PIUC, ...) 
{
...
}

But you didn't give us this info.

For example, if it is
OperationRegion (PIUC, PCI_Config, 0x74, 0x01)
Field (REGS, DWordAcc, NoLock, Preserve)
({
	FOO, 8
})

Then a better fix is to make this:

Field (REGS, DWordAcc, NoLock, Preserve)
changed as:
Field (REGS, ByteAcc, NoLock, Preserve)

-- 
Ducrot Bruno

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.


-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help