roon83 Posted June 13, 2013 Share Posted June 13, 2013 Why do people use Linux or OS X to extract, edit and compile the DSDT when all of this is possible on Windows by using just the iASL and a good text editor?Are the ACPI Tables different on Windows? Link to comment Share on other sites More sharing options...
Funkoyote Posted June 13, 2013 Share Posted June 13, 2013 Maybe because this people (like me) don't use windows, and don't want to install it. Link to comment Share on other sites More sharing options...
roon83 Posted June 13, 2013 Author Share Posted June 13, 2013 I saw a lot of posts on forums and blogs giving instructions to extract and compile DSDT from Linux Live CD's as if it is too hard or impossible on Windows. Some people even giving links to their custom Linux Live Distros to do that. Taking advantage of ignorance? Some people mention DSDTE for Windows. I know it's a lot easier to do the editing and compiling using the AIO tool but recommending it as if it is the only tool for Windows is not right. Some people recommend using Aida64 a commercial product to do that.as if everybody can afford to buy one (people can use the pirated version but why encourage piracy when all that can be done for free). Link to comment Share on other sites More sharing options...
DAXGr Posted June 13, 2013 Share Posted June 13, 2013 Hmm I don't know, maybe the BIOS loads presents different ACPI code or something like that. I agree with you, I dual boot Win8 and 10.8.3 and this would make life so much easier for those BIOS and OSX updates Link to comment Share on other sites More sharing options...
3.14r2 Posted June 13, 2013 Share Posted June 13, 2013 Linux, OS X and Windows although are designed to understand/work the ACPI specification, developers of all the above OSs, do interprent/implemnt the specification differently. Windows can work with DSDT containing many bugs (there are many examples on web, when people using Linux have to fix DSDT in order to make PC work as it should, while the same PC may and usually is perfectly working in Windows). Linux developers (Apple developers as well), as I see it, are playing by the rules and expect that each x86 compatible PC/Mac uses ACPI tables made to the letter according to the official ACPI specification. It obviously not always true. Therefore Linux or OS X may read the ACPI tables more precisely or honestly (if you will), then Windows would do. Windows is well known for containing and using various non trivial fixes and workarounds. I use Linux for the task. It had never failed me. Link to comment Share on other sites More sharing options...
Recommended Posts