Native DSDT/AML IDE & Compiler: MaciASL Open Beta

[khe91]

1. The latest binary on sourceforge.net is from 2013-08-01. I got the source and compiled it.

There is a warning:
Fix.m:16:13: 161 enumeration values not handled in switch: 'ASL_MSG_RESERVED', 'ASL_MSG_ALIGNMENT', 'ASL_MSG_ALPHANUMERIC_STRING'...

I don't have expirience with OSX programming yet.
Can I ignore this warning and use version 1.3 build 251 ?

2. How to create a .acpi file for all tables, so I don't get errors from external definitions in DSDT ?

Thanks

 

[SJ_UnderWater]

All that warning says is I haven't finished the fix-it feature. Choose "Export Tableset" to save a .acpi (tableset) file

 

[khe91]

The Device Properties window is very usefull.
But I can't make a screenshoot of it with Grab, since the window hides if another program gets active.
Also the text inside the Device Properties window can't be marked and copied.

Can you please make the window stay visible even if MaciASL is not the active application or enable copy of the text inside the window or both ?

Thanks

 

[SJ_UnderWater]

I will consider adding more delegate methods for copying, but you shouldn't be using Grab for screenshots.
http://www.tonymacx86.com/basics/105527-how-take-screenshots-os-x.html

 

[misterfrista]

Hey SJ_UnderWater!

I have recently expired a problem with your patching engine!

RehabMan confirmed to me that it somehow has to do with maciasl!

All files and the problem with patching are underhttp://www.tonymacx86.com/mavericks-laptop-support/125911-dell-inspiron-3x37-5x37-7x37-clover-install-guide-24.html

Please help me

 

[SJ_UnderWater]

First, you should _never_, _ever_, _ever_ use a DSL file. While it's technically an acceptable iASL file format, it serves no useful purpose when you have access to an IDE like MaciASL. IDEs like MaciASL automatically decompile AML files and display the text for editing, then compile back to AML; there is no need to save in that format. Considering all of the possible encoding, line-ending, and content-transfer issues inherent to text files, there's no point. If you're working on your system's tables, they're already in AML format in memory. If you're working on the tables of another system, use the ACPI (tableset) format, which packages all tables and can perform name resolution when a table references others; just choose File > Export Tableset. We even support ACPI files directly here, so there's no need to ZIP.

For this specific issue, the DSL has a comment "/* HID Protocol Device (I2C bus) */" which fools the parser into thinking "Device (I2C bus)" is a device in the tree. This Device has no content, so the patcher can't find the region to check for matches. The parser could be better no doubt, but considering this would never appear in an AML file, it hasn't been an issue up until now. If users mark up their AMLs and save as DSL to preserve the comments, they don't then try to compile that file.

I have pushed a commit which makes the parser stricter, and to use this version you will have to compile MaciASL. With Xcode installed, clone http://git.code.sf.net/p/maciasl/code, open the Xcode project, and Build.

 

[RehabMan]

First, you should _never_, _ever_, _ever_ use a DSL file.

Tablesets are not as universal as disassembly via 'iasl -da' because you cannot disassemble SSDTs properly using MaciASL since it does not pass the other SSDTs/DSDT as context to the iasl disassembler when loading an SSDT from a tableset.

In addition, tablesets cannot be saved once one or more patches are applied. Because the (patched) SSDT cannot be disassembled standalone, further edits using the resulting AML are not possible.

The best strategy is to disassemble with 'iasl -da' all tables, and then work with the resulting *.dsl files from that point on.

For this specific issue, the DSL has a comment "/* HID Protocol Device (I2C bus) */" which fools the parser into thinking "Device (I2C bus)" is a device in the tree. This Device has no content, so the patcher can't find the region to check for matches. The parser could be better no doubt, but considering this would never appear in an AML file, it hasn't been an issue up until now. If users mark up their AMLs and save as DSL to preserve the comments, they don't then try to compile that file.

The newer versions of the iasl disassembler are more liberal with comments. This comment was generated by iasl, not the user.

I have pushed a commit which makes the parser stricter, and to use this version you will have to compile MaciASL. With Xcode installed, clone http://git.code.sf.net/p/maciasl/code, open the Xcode project, and Build.

Thanks. This should help users dealing with complex SSDTs and newer versions of iasl.

 

[toleda]

With Xcode installed, clone http://git.code.sf.net/p/maciasl/code, open the Xcode project, and Build.

white page with url?

 

[RehabMan]

white page with url?

Not for web browsers... just git:

# in Terminal
mkdir ~/proj
cd ~/proj
git clone http://git.code.sf.net/p/maciasl/code maciasl.git
cd maciasl.git
open MaciASL.xcodeproj

 

[toleda]

Not for web browsers..

Thanks.