ChangeSet 1.1938.505.21, 2005/03/03 19:55:50-05:00, [EMAIL PROTECTED]

        [ACPI] ACPICA 20050303 from Bob Moore for AE_AML_BUFFER_LIMIT issue.
        
        It turns out that tightening up the interpreter to truncate buffers
        per the ACPI spec was a bad idea -- BIOS' in the field depended
        on old behaviour.  Instead, we'll endeavor to update the ACPI spec
        to reflect industry practice in this area.
        
        http://bugme.osdl.org/show_bug.cgi?id=4263
        
        Signed-off-by: Len Brown <[EMAIL PROTECTED]>



 drivers/acpi/executer/exstorob.c |    2 ++
 include/acpi/acconfig.h          |    2 +-
 2 files changed, 3 insertions(+), 1 deletion(-)


diff -Nru a/drivers/acpi/executer/exstorob.c b/drivers/acpi/executer/exstorob.c
--- a/drivers/acpi/executer/exstorob.c  2005-04-01 08:11:54 -08:00
+++ b/drivers/acpi/executer/exstorob.c  2005-04-01 08:11:54 -08:00
@@ -105,6 +105,7 @@
                ACPI_MEMSET (target_desc->buffer.pointer, 0, 
target_desc->buffer.length);
                ACPI_MEMCPY (target_desc->buffer.pointer, buffer, length);
 
+#if ACPI_STRICT_CONFORMANCE
                /*
                 * If the original source was a string, we must truncate the 
buffer,
                 * according to the ACPI spec.  Integer-to-Buffer and 
Buffer-to-Buffer
@@ -115,6 +116,7 @@
 
                        target_desc->buffer.length = length;
                }
+#endif
        }
        else {
                /* Truncate the source, copy only what will fit */
diff -Nru a/include/acpi/acconfig.h b/include/acpi/acconfig.h
--- a/include/acpi/acconfig.h   2005-04-01 08:11:54 -08:00
+++ b/include/acpi/acconfig.h   2005-04-01 08:11:54 -08:00
@@ -64,7 +64,7 @@
 
 /* Version string */
 
-#define ACPI_CA_VERSION                 0x20050228
+#define ACPI_CA_VERSION                 0x20050303
 
 /*
  * OS name, used for the _OS object.  The _OS object is essentially obsolete,
-
To unsubscribe from this list: send the line "unsubscribe bk-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to