- Add a more sophisticated acpi loading mechanism to enable loading custom acpi tables when dsdtdrop=y␊ |
Here's a specification to think about:␊ |
First we must care about if a forced DSDT full path has been specified (was the pb smith had in␊ |
his first tries) and take it for the DSDT path as is.␊ |
his first tries) and take it for the DSDT path as is.␊ |
Then we have the case where no DSDT path was set where we run our usual DSDT search algorithm to find this file.␊ |
In the latter case, the file has to be named DSDT.aml and be in one of the / /Extra or bt(0,0)/Extra directory.␊ |
␊ |
|
Whatever the path was hardcoded in the DSDT option or was automatically found, we extract the path part of ␊ |
the DSDT file that has been successfully found and we run a loop to enumerate all other acpi files in the same directory.␊ |
Now for each acpi file found, we should compare the name with an existing acpi table found in the system that␊ |
we would normally load and replace this usual injection by the content of the file.␊ |
we would normally load and replace this usual injection by the content of the file.␊ |
␊ |
Once DropDSDT=y is set, no other acpi table than dsdt is loaded, then it is the responsibility of user␊ |
to provide any other acpi table.␊ |
|
␊ |
The preferred internal behavior of the log info ioreg buffer␊ |
would be to store the messages in a consolidated buffer then only write once,␊ |
this buffer (i.e just before call the kernel) with flushLogToIOREG();␊ |
this buffer (i.e just before call the kernel) with flushLogToIOREG();␊ |
The other public function for writing chameleon boot info data would be:␊ |
␊ |
verbose() should incorporate a call to logMessageToIOREG() ␊ |