mitch_de Posted November 13, 2009 Author Share Posted November 13, 2009 updated - DL at first post !!! Intel ACPI Component Architecture ASL Optimizing Compiler version 20091112 [Nov 13 2009] Copyright © 2000 - 2009 Intel Corporation Supports ACPI Specification Revision 4.0 Also updated iASLme with that iasl version: -- iASL Me v1.2 2009 by cVad -- - (De)Compiling ASL AML files - - ASL Optimizing Compiler version 20091112 [Nov 13 2009] inside - Link to comment Share on other sites More sharing options...
blackosx Posted November 13, 2009 Share Posted November 13, 2009 updated - DL at first post !!!Intel ACPI Component Architecture ASL Optimizing Compiler version 20091112 [Nov 13 2009] Copyright © 2000 - 2009 Intel Corporation Supports ACPI Specification Revision 4.0 Also updated iASLme with that iasl version: -- iASL Me v1.2 2009 by cVad -- - (De)Compiling ASL <-> AML files - - ASL Optimizing Compiler version 20091112 [Nov 13 2009] inside - Thanks mitch_de. Good to see you keeping this up to date Link to comment Share on other sites More sharing options...
mitch_de Posted November 13, 2009 Author Share Posted November 13, 2009 , Thanks. But i cant garantie that i will be every time sooo fast : Only a few hours after orig. Source update , you got the OS X version too Link to comment Share on other sites More sharing options...
LS8 Posted November 18, 2009 Share Posted November 18, 2009 Can I use the old DSDT patcher version 1.0.1e and just replace the iasl binary in it? Or is therea better / newer / recommender DSDT maker front-end? Thank you! Link to comment Share on other sites More sharing options...
mitch_de Posted November 18, 2009 Author Share Posted November 18, 2009 Can I use the old DSDT patcher version 1.0.1e and just replace the iasl binary in it? Or is therea better / newer / recommender DSDT maker front-end? Thank you! Sure, it should work to use only the IASL commandline in all other GUI Apps. But if possible i would NOT use such old GUIs anymore, because some DSDT patches are "old way" patches. Better to use dsdt hints from DSDT forum or use the great , also user friendly but much, much complete + new DSDTSE: http://www.osx86.es/?p=610 Thats all in one really good: very large+newest dsdt patchtes with explaining text/ tipp database, editor,.... I use that / beside iASLme (quick compile/disass) with IASL 12.11.2009. You can copy (as ti all GUIs) IASL into the DSDTSE ../ressources and overwrite the older IASL version there. I think its an version Juli/August there. HAPPY PATCHING! Link to comment Share on other sites More sharing options...
leslieking Posted December 13, 2009 Share Posted December 13, 2009 How can I create a DSDT? I need to use iasl_Nov_2009.zip? Link to comment Share on other sites More sharing options...
rednous Posted December 13, 2009 Share Posted December 13, 2009 How can I create a DSDT? I need to use iasl_Nov_2009.zip? I'll suggest you this method for creating a DSDT source for your motherboard Link to comment Share on other sites More sharing options...
leslieking Posted December 13, 2009 Share Posted December 13, 2009 I'll suggest you this method for creating a DSDT source for your motherboard I don't need BIOS patching. I would like to create a DSDT file. As far as I know "iaslme" is used to compile/decompile an existing dsdt, but how can I create one? Thanks! Link to comment Share on other sites More sharing options...
rednous Posted December 13, 2009 Share Posted December 13, 2009 I don't need BIOS patching. I would like to create a DSDT file. As far as I know "iaslme" is used to compile/decompile an existing dsdt, but how can I create one? Thanks! Then use the PDF guide as a general reference for building your own DSDT Link to comment Share on other sites More sharing options...
leslieking Posted December 13, 2009 Share Posted December 13, 2009 Is there any difference between Koalala's ACPIpatcher and Fassl dsdt patcher? Link to comment Share on other sites More sharing options...
Master Chief Posted December 15, 2009 Share Posted December 15, 2009 Get the latest release now! 14 December 2009. Summary of changes for version 20091214 (only the important/relevant bits): iASL Compiler/Disassembler and Tools: iASL: Fixed a regression introduced in 20091112 where intermediate .SRC files were no longer automatically removed at the termination of the compile. Link to comment Share on other sites More sharing options...
mitch_de Posted December 16, 2009 Author Share Posted December 16, 2009 Same procdure as every "year" - NEW IASL SOURCE = NEW OS X version compiled Link to comment Share on other sites More sharing options...
blackosx Posted December 16, 2009 Share Posted December 16, 2009 Same procdure as every "year" - NEW IASL SOURCE = NEW OS X version compiled Thanks mitch_de iASL: Fixed a regression introduced in 20091112 where intermediate .SRC files were no longer automatically removed at the termination of the compile. and Thanks MasterChief Link to comment Share on other sites More sharing options...
rednous Posted December 16, 2009 Share Posted December 16, 2009 Thanx Link to comment Share on other sites More sharing options...
Smith@@™ Posted December 16, 2009 Share Posted December 16, 2009 Thanks men Link to comment Share on other sites More sharing options...
Master Chief Posted December 16, 2009 Share Posted December 16, 2009 @mitch_de, You may want to add a link, or explain people here what you've done to compile it on OS X Also. I have changed my link and now point people to this thread. I'll keep you posted about new updates. Edit: I meant to ask for a diff file, but apparently was in too much of a hurry. As usual. Link to comment Share on other sites More sharing options...
mitch_de Posted December 16, 2009 Author Share Posted December 16, 2009 HOW to get + compile - DEV Tools installed (XCODE) needed. Look POST #8 and #15 (Post 15 has an better source code fix than in Post #8) - its easy. Link to comment Share on other sites More sharing options...
Õun Posted December 29, 2009 Share Posted December 29, 2009 DL link to newest iasl at end of this post. LASTEST NOW: V2009_12_14 : Dezember 2009 Version Could you compile acpiexec for me as well? I don't have any xcode installed right now. Well I checked it out and seems that its more complicated than I expected. Not sure if its even possible as there are symbols missing. Oh well, Need to remote debug my system then Link to comment Share on other sites More sharing options...
mitch_de Posted January 25, 2010 Author Share Posted January 25, 2010 As always: updated iASL to 2010/01/21. Updated the iaslME only (iasl is within that app!) Link to comment Share on other sites More sharing options...
Master Chief Posted January 26, 2010 Share Posted January 26, 2010 As always: updated iASL to 2010/01/21.Updated the iaslME only (iasl is within that app!) Just to let you know: The iASL Compiler/Disassembler is still the same. Is basically unchanged (except for the date/copyright notice). Here's the official announcement: 21 January 2010. Summary of changes for version 20100121: This release is available at www.acpica.org/downloads 1) ACPI CA Core Subsystem: Added the 2010 copyright to all module headers and signons. This affects virtually every file in the ACPICA core subsystem, the iASL compiler, the tools/utilities, and the test suites. Implemented a change to the AcpiGetDevices interface to eliminate unnecessary invocations of the _STA method. In the case where a specific _HID is requested, do not run _STA until a _HID match is found. This eliminates potentially dozens of _STA calls during a search for a particular device/HID, which in turn can improve boot times. ACPICA BZ 828. Lin Ming. Implemented an additional repair for predefined method return values. Attempt to repair unexpected NULL elements within returned Package objects. Create an Integer of value zero, a NULL String, or a zero-length Buffer as appropriate. ACPICA BZ 818. Lin Ming, Bob Moore. Removed the obsolete ACPI_INTEGER data type. This type was introduced as the code was migrated from ACPI 1.0 (with 32-bit AML integers) to ACPI 2.0 (with 64-bit AML integers). It is now obsolete and this change removes it from the ACPICA code base, replaced by UINT64. The original typedef has been retained for now for compatibility with existing device driver code. ACPICA BZ 824. Removed the unused UINT32_STRUCT type, and the obsolete Integer64 field in the parse tree object. Added additional warning options for the gcc-4 generation. Updated the source accordingly. This includes some code restructuring to eliminate unreachable code, elimination of some gotos, elimination of unused return values, some additional casting, and removal of redundant declarations. Example Code and Data Size: These are the sizes for the OS-independent acpica.lib produced by the Microsoft Visual C++ 6.0 32-bit compiler. The debug version of the code includes the debug output trace mechanism and has a much larger code and data size. Previous Release: Non-Debug Version: 87.0K Code, 18.0K Data, 105.0K Total Debug Version: 163.4K Code, 50.8K Data, 214.2K Total Current Release: Non-Debug Version: 87.1K Code, 18.0K Data, 105.1K Total Debug Version: 163.5K Code, 50.9K Data, 214.4K Total 2) iASL Compiler/Disassembler and Tools: No functional changes for this release. Link to comment Share on other sites More sharing options...
mitch_de Posted January 26, 2010 Author Share Posted January 26, 2010 Hmmmm, but size of the compiled is differerent (bigger) to dec version ?! Q: What does that with the _STA means ? We all use/have that _STA in use. Link to comment Share on other sites More sharing options...
rednous Posted January 26, 2010 Share Posted January 26, 2010 mitch_de & Master Chief Link to comment Share on other sites More sharing options...
Master Chief Posted January 26, 2010 Share Posted January 26, 2010 Hmmmm, but size of the compiled is differerent (bigger) to dec version ?! Yes, the code size changed, but without any functional changes. Q: What does that with the _STA means ? We all use/have that _STA in use. _STA returns the status of a device. And while a number of these can be found in your DSDT you are not affected by this change. The reason is simple; Apple is still using an older version of ACPI CA. Which is unfortunate for us, but that's the way things are right now. I hope this helps. Link to comment Share on other sites More sharing options...
rednous Posted March 6, 2010 Share Posted March 6, 2010 mitch_de, just want to inform you there's a new version of ACPICA (March 04 2010) available on the ACPICA site ---------------------------------------- 04 March 2010. Summary of changes for version 20100304: 1) ACPI CA Core Subsystem: Fixed a possible problem with the AML Mutex handling function AcpiExReleaseMutex where the function could fault under the very rare condition when the interpreter has blocked, the interpreter lock is released, the interpreter is then reentered via the same thread, and attempts to acquire an AML mutex that was previously acquired. FreeBSD report 140979. Lin Ming. Implemented additional configuration support for the AML "Debug Object". Output from the debug object can now be enabled via a global variable, AcpiGbl_EnableAmlDebugObject. This will assist with remote machine debugging. This debug output is now available in the release version of ACPICA instead of just the debug version. Also, the entire debug output module can now be configured out of the ACPICA build if desired. One new file added, executer/exdebug.c. Lin Ming, Bob Moore. Added header support for the ACPI MCHI table (Management Controller Host Interface Table). This table was added in ACPI 4.0, but the defining document has only recently become available. Standardized output of integer values for ACPICA warnings/errors. Always use 0x prefix for hex output, always use %u for unsigned integer decimal output. Affects ACPI_INFO, ACPI_ERROR, ACPI_EXCEPTION, and ACPI_WARNING (about 400 invocations.) These invocations were converted from the original ACPI_DEBUG_PRINT invocations and were not consistent. ACPICA BZ 835. Example Code and Data Size: These are the sizes for the OS-independent acpica.lib produced by the Microsoft Visual C++ 6.0 32-bit compiler. The debug version of the code includes the debug output trace mechanism and has a much larger code and data size. Previous Release: Non-Debug Version: 87.1K Code, 18.0K Data, 105.1K Total Debug Version: 163.5K Code, 50.9K Data, 214.4K Total Current Release: Non-Debug Version: 87.5K Code, 18.4K Data, 105.9K Total Debug Version: 163.4K Code, 51.1K Data, 214.5K Total 2) iASL Compiler/Disassembler and Tools: iASL: Implemented typechecking support for static (non-control method) predefined named objects that are declared with the Name() operator. For example, the type of this object is now validated to be of type Integer: Name(_BBN, 1). This change migrates the compiler to using the core predefined name table instead of maintaining a local version. Added a new file, aslpredef.c. ACPICA BZ 832. Disassembler: Added support for the ACPI 4.0 MCHI table. Link to comment Share on other sites More sharing options...
mitch_de Posted March 7, 2010 Author Share Posted March 7, 2010 Updated to newest version Link to comment Share on other sites More sharing options...
Recommended Posts