On 06/17/2010 04:47 AM, Kevin O'Connor wrote:
BTW, it's been said several times now that ACPI is an interface between OS and firmware. I don't see this at all - ACPI defines how the OS can interact with the hardware. The only place I know of where seabios has involvement is with it's tiny (16 asm statement) SMI stub. Everything else describes the hardware and enables interactions directly with the hardware.
In general, ACPI code can work with memory or device registers that have been initialized by the BIOS and depend on them. It's possible to write ACPI code that depends on preceding BIOS code. I don't know if that's the case with our ACPI implementation.
-- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.
