From: Rathgeb Markus <maggu2810-S0/GAf8tV78@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: AE_AML_BUFFER_LIMIT with handmade dsdt file
Date: Thu, 17 Nov 2005 15:18:47 +0100 [thread overview]
Message-ID: <437C9147.9030508@web.de> (raw)
In-Reply-To: <971FCB6690CD0E4898387DBF7552B90E037162E9-sBd4vmA9Se5Qxe9IK+vIArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
can someone send me this new version?
> We made a recent change to ensure that a disassemble/recompile sequence
> works correctly for resource descriptors:
>
> 21 October 2005. Summary of changes for version 20051021:
>
> Relaxed a compiler restriction that disallowed a ResourceIndex byte if
> the corresponding ResourceSource string was not also present in a
> resource descriptor declaration. This restriction caused problems with
> existing AML/ASL code that includes the Index byte without the string.
> When such AML was disassembled, it could not be compiled without
> modification. Further, the modified code created a resource template
> with a different size than the original, breaking code that used fixed
> offsets into the resource template buffer.
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
next prev parent reply other threads:[~2005-11-17 14:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 21:32 AE_AML_BUFFER_LIMIT with handmade dsdt file Moore, Robert
[not found] ` <971FCB6690CD0E4898387DBF7552B90E037162E9-sBd4vmA9Se5Qxe9IK+vIArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2005-11-17 14:18 ` Rathgeb Markus [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-16 22:10 Moore, Robert
2005-11-16 21:56 Thomas Meyer
2005-11-16 21:28 Thomas Meyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=437C9147.9030508@web.de \
--to=maggu2810-s0/gaf8tv78@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.