in fact, aml is more to be seen as an high level language, and acpica as a framework that come 'on top' of your kernel at some stage
acpica require a kernel that can implement quite a bunch of thing to work, it's just that the interface is low level enougth for that it's easy to implement in any kernel,but it's more like acpica require to take the control of your kernel at some early low level stage, rather than being truly os independant,and it is dependent on a low level kernel
it's why it need to setup the os version to know how the aml is supposed to control the low level part of the kernel, and then it's made in sort higher level part of the kernel depend on the acpica layer initialization, and there is an implicit dependency on private agreement between os makers and asl developpers that is not well defined in the asl spec, or into any spec at all actually
Theoretical: Why the original 386 design was bad
Re: Theoretical: Why the original 386 design was bad
Que?
Fudge - Simplicity, clarity and speed.
http://github.com/Jezze/fudge/
http://github.com/Jezze/fudge/
Re: Theoretical: Why the original 386 design was bad
When someone posts way too many TL;DR posts it doesn't really matter which topic they go into in the end - nobody reads them anyway.Jezze wrote:Que?
Learn to read.