On Tue, Sep 20, 2016 at 1:02 PM Duncan Laurie wrote:
> So far I've been asking people in ACPI patches to not introduce ASL 2.0
> syntax into existing ASL code as it can be confusing if the two are mixed.
> So we should either convert everything or at least only use ASL 2.0
I've even seen this done, or maybe I did it, I forget, but it's a one time
pass through something like cpp:
#define Store(src, dst) dst = src
to produce the final output.
repeat for all ops of interest. Then, if there is a switch to ASL to not
accept pre-asl-2.0 code you do a clean up stage as
So far I've been asking people in ACPI patches to not introduce ASL 2.0
syntax into existing ASL code as it can be confusing if the two are mixed.
So we should either convert everything or at least only use ASL 2.0 syntax
in new files.
The problem with auto-converting sources with the
Hi all,
Just FYI [1], maybe you already know.
There is an alternate syntax available for ACPI ASL sources.
It just converts Polish notation of ASL to something less geeky like C
operators. It says that the tool to convert the sources is in development (to
ratain comments). I think it would make
4 matches
Mail list logo