Lines Matching refs:was
44 was added to each of these macros, and the original name has been
46 names. Support for the new macros was added to iASL, disassembler,
53 ACPI 6.0: Added support for a new integer field that was appended to the
136 lengths of 8/16/32/64 were supported. This was sufficient for many years,
164 control method if a non-data object was encountered.
231 this support. Therefore, the change was reverted to the original ACPICA
300 descriptors. The _PIN field name was incorrectly defined to be an array
363 not handled correctly when the invocation was itself a SuperName argument
364 to another ASL operator. In these cases, the method was not invoked.
412 was incorrectly defined in the iASL parser rules, causing a new scope to
468 was hardwired to a specific ID. Lv Zheng.
514 Support for this type of file was also added to the various tools that
620 This completes the ACPI 6.0 ASL+ support as it was the only operator not
645 The max-number-of-AML-loops is now runtime configurable (previously was
675 - AcpiNames: Fix a regression where some output was missing and no longer
788 template generator. (The client table was already previously supported)
893 contained extra data that was not expected. The compiler was using this
920 buffer/string/package was emitted.
990 returns 2 (was 5). This matches other ACPI implementations. _REV will be
1029 Implemented the -Pn option for the iASL Table Compiler (was only
1067 A raw gpe handling mechanism was created to allow better handling of GPE
1317 that could cause the compiler to crash. This was introduced inadvertently
1350 library. This divide is not actually necessary, so the code was
1374 state was not always properly restored upon exit. Seen when using the -v
1378 Memory24 resource descriptor. There was a boundary condition when the
1379 range was equal to the (length -1) caused by the fact that these values
1393 specification. Remove a similar requirement that was incorrectly in place
1552 Originally, a fixed buffer length was used. This change allows for
1556 Fixed a problem where an object detached from a namespace node was not
1612 number of system GPEs (> 124). This was the "32-bit FADT register is too
1707 Reverted the use of #pragma push/pop which was introduced in the 20140214
1780 AE_ALREADY_EXISTS exception if the method was actually entered by more
1823 first reserved field was incorrectly forced to have a value of zero. This
1906 new values to each data object, and ensuring that the write was
1917 Global note: The ACPI 5.0A specification was released this month. There
2106 field object was inadvertently changed to match the type of the source
2296 circumstances: 1) Interpreter slack mode was not enabled, and 2) the _WAK
2393 max. The original purpose of this constraint was to limit the amount of
2418 longer executed properly because of a memory block that was not
2678 was probably intended to do something, but for whatever reason, the value
2679 was not stored. Therefore, this issue has been upgraded from a warning to
2715 lone end tag descriptor in the following cases: A Return(0) was executed,
2716 a null buffer was returned, or no object at all was returned (non-slack
2930 code was using a relative-time timeout, but sem_timedwait requires the
2964 flags (was incorrectly 2 bits, should be 3).
2995 This command was out-of-date and did not properly disassemble control
3036 compiler/disassembler into an ACPI 2.0 mode, this was never implemented
3046 introduced by late changes to the table as it was added to the ACPI 5.0
3192 line was longer than the buffer.
3197 Type3 opcode was used.
3223 Linux has removed all use of the methods also. It was discovered that
3299 expressions. The constant-folding code was not being invoked for constant
3318 AE_BAD_PARAMETER was always returned.
3412 AcpiUnloadParentTable external interface. This command was disable
3545 This keyword was added late in the ACPI 5.0 release cycle and was not
3609 count was calculated incorrectly. Regression was introduced in the commit
3649 the allowable range was 0x80-0xFF (user-defined spaces), now the range is
3691 Fixed a problem where the length of the local/common FADT was set too
3892 descriptors (I2C, SPI, UART) where the resource produce/consumer bit was
4125 Support for this language was implemented and released as a subsystem of
4146 Fixed an issue with the FFixedHW space ID where the ID was not always
4177 operator where AML listing was disabled until the entire Switch block was
4222 Fixed a problem where the maximum sleep time for the Sleep() operator was
4223 intended to be limited to two seconds, but was inadvertently limited to
4607 root object was passed to the AcpiSetupGpeForWake interface. Lin Ming.
4647 "Wrong checksum", etc., into the dump file. This was causing problems for
4695 generation cases. The _AcpiModuleName was left undefined in these cases,
4771 possibly cause a fault. The problem was apparently introduced in version
4856 Completed the major overhaul of the GPE support code that was begun in
4952 Device. This was found to be confusing to the host software that
5006 _MULTI_THREADED option was replaced by the (reverse) ACPI_SINGLE_THREADED
5061 The UINT64_OVERLAY was moved to utmath.c, which is the only module where
5119 Controller (EC) operation regions. A reported problem was found to be a
5123 size passed to the EC operation region handler was a single byte. There
5201 no longer disabled during this process, as it was found to cause problems
5206 Controller multi-byte transfers. This change was found to cause problems
5213 reference to an Alias within the definition of a Package was not always
5268 Note: The ACPI 4.0a specification was released on April 5, 2010 and is
5281 operation region handler was a single byte. There are often EC Fields
5315 entire namespace was traversed on each control method exit. This change
5395 where initial table loading could fail. This was introduced in the fix
5404 where the object to be copied was a namespace node. Lin Ming. ACPICA BZ
5438 iASL: Added support for the _Wxx predefined names. This support was
5475 removed. One new external interface was added. Most of the GPE external
5493 was
5517 When copying the root table to the new allocation, the length used was
5518 incorrect. The new size was used instead of the current table size,
5520 too much data was copied. Also, the count of available slots for ACPI
5522 was not set correctly. Alexey Starikovskiy, Bob Moore.
5569 acquire an AML mutex that was previously acquired. FreeBSD report 140979.
5585 Interface Table). This table was added in ACPI 4.0, but the defining
5649 Removed the obsolete ACPI_INTEGER data type. This type was introduced as
5651 code was migrated from ACPI 1.0 (with 32-bit AML integers) to ACPI 2.0
5703 module was completely restructured. Lin Ming, Bob Moore.
5750 was considered too wordy. Now, messages are only unconditionally emitted
5830 the object was successfully repaired, a warning is too severe. Reduced to
5867 of errors was reached (200).
5889 operand object was leaked. Lin Ming.
6009 iASL: Fixed a problem where the full pathname for include files was not
6046 31 new names in ACPI 4.0. The predefined validation module was split into
6077 The _HID/_CID matching was broken and no longer matched IDs correctly.
6082 register was one of the protected I/O ports. AcpiReset now bypasses the
6121 The ACPI 4.0 Specification was released on June 16 and is available at
6161 Fixed several problems with AcpiAttachData. The handler was not invoked
6163 the host node was deleted. The data sub-object was not automatically
6165 when the host node was deleted. The interface to the handler had an
6167 parameter, this was removed. ACPICA BZ 778.
6180 warnings on subsequent calls was interfering with the repair mechanism.
6419 versions were valid, but not equal, the 64-bit version was used. This was
6435 made obsolete by the port protection mechanism above. It was previously
6536 was writing an optional PM1B status register twice. The existing call to
6553 for the truncation value was incorrect.
6662 AcpiRead - Low-level read ACPI register (was HwLowLevelRead.)
6663 AcpiWrite - Low-level write ACPI register (was HwLowLevelWrite.)
6674 time option was added to fall back to the default hardcoded lengths if
6681 Fixed a reference count issue in NsRepairObject. This problem was
6745 was found instead. This can happen when reading string battery data from
6780 object was allocated and freed for each execution of the loop. The
6910 was useful under SourceSafe and CVS, but has no meaning under git. It is
7002 errors where a full 16-bit table type field was not extracted from the
7024 at dispatch time. This code was introduced in version 20060831 as a
7125 (get ACPI tables on Windows). This was apparently broken in version
7131 completion message. Previously, no message was displayed in this case.
7168 Fixed a problem where the wrong descriptor length was calculated for the
7236 to allow creation of an OpRegion with a real address that was passed to
7263 was a regression introduced in 20080514. The new method argument count
7270 Fixed a problem where the _SST execution status was incorrectly returned
7272 the caller of AcpiEnterSleepStatePrep. This was a regression introduced
7279 parser. This was a regression introduced in version 20080123 as a fix for
7300 loop termination value was used. Loop terminated on iteration early,
7340 method to just before setting sleep enable bit. The execution was moved
7396 longer needed, especially with the removal of 16-bit support. It was
7442 AcpiEvaluateObject interface correctly. The element was simply ignored
7480 Fixed a problem where an extraneous debug message was produced for
7518 variables and if/else pairs. The solution chosen was to mark any method
7566 was
7624 Fixed a problem with the Load operator where an exception was not
7727 Fixed a problem with Index Fields where the Index register was
7779 control was passed to the called method). The references are now
7785 The reference was incorrectly dereferenced before the copy. The reference
7845 Reverted a change to Notify handling that was introduced in version
7849 ASL operator). It was found that this change caused more problems than it
7850 solved and was removed by most users.
7858 location within the namespace was ignored. Instead, the table was always
7862 object. The input buffer was prematurely zeroed and/or deleted. (BZ 577)
7894 Fixed a problem where if a single file was specified and the file did not
7895 exist, no error message was emitted. (Introduced with wildcard support in
7975 Fixed a problem where the Global Lock handle was not properly updated if
7984 could be corrupted if the interrupt being removed was at the head of the
8051 of a reference (Reference.Opcode). This code was no longer necessary. BZ
8055 was
8082 during a table load. A bad pointer was passed in the case where the DSDT
8227 AcpiWalkNamespace and the AML interpreter. This condition was removed by
8273 obtained before it is actually obtained. The global lock semaphore was
8310 operator. An incorrect output filename was produced when this parameter
8311 was
8333 Fixed a regression where an error was no longer emitted if a control
8374 temporary variable was declared too close to the actual Switch, instead
8718 feature was requested. The base code now uses mutexes (and the new mutex
8719 interfaces) wherever a binary semaphore was used previously. However, for
8839 was
8978 the _STA method was not run unless an _INI was also present for the same
9093 machines, this change was made to enable ACPI support for them. Also,
9101 was
9112 region where a cached memory mapping was not deleted. This became a
9174 was deemed unnecessary. This reduces the size of each namespace node by
9297 Register() macro. This parameter was inadvertently left out of the ACPI
9326 VendorLong, and Interrupt. This was noticed on IA64 machines, but could
9358 descriptor was incorrectly emitted as a descriptor of length one.
9377 Fixed a problem where the AE_BUFFER_LIMIT exception was returned instead
9487 Fixed an internal error that was generated for any forward references to
9520 Fixed a memory leak within the AML Debugger "Set" command. One object was
9544 The compiler now officially supports the ACPI 3.0a specification that was
9618 method call was made from within a Return statement.
9697 table load. Related to the problem above, this was causing unwind issues
9906 corresponding ResourceSource string was not also present in a resource
9910 was disassembled, it could not be compiled without modification. Further,
9947 single location for clarity and ease of maintenance. One new file was
9997 buffer is zero. Previously, this was a warning.
10005 Register descriptor was not fully implemented. This descriptor is now
10048 string (within a large resource descriptor) was not surrounded by quotes
10050 not followed by a comma, causing errors when the resulting ASL module was
10231 where an error message was inadvertently emitted for invocations of the
10241 considerably reduced. Previously, a debug structure was declared in every
10269 the namespace node descriptor was reduced by 2 bytes as a result (Alexey
10322 change was made for performance reasons, since this is the purpose of the
10336 change was required because the global initialization now calls OSL
10410 Fixed a problem in the ACPI table handling where a valid XSDT was assumed
10411 present if the revision of the RSDP was 2 or greater. According to the
10430 object is now correctly overwritten. Previously, an error was returned.
10468 output incorrectly. This problem was introduced in the previous release
10491 exactly once at the time the table is loaded. This type of code was legal
10498 that was previously generated upon detection of such code.
10545 executed once at the time the table is loaded. This type of code was
10556 Previously, the revision ID value was only emitted in the AML table
10594 conversion was improperly performed while storing the result to the
10654 function was still (internally) 32 bits instead of the required 64 bits.
10655 This was the Index argument to the Index, Mid, and Match operators.
10796 The "implicit return" support was rewritten to a new algorithm that
10822 non-hex character terminates the conversion and this is the code that was
10831 properly popping the result stack during execution. There was no memory
10877 Added "ProcessorObj" to the ObjectTypeKeyword list. This object type was
10883 was made because some vendors place non-ascii characters within comments.
10887 Fixed a problem with the CondRefOf operator where the compiler was
10907 Fixed and enhanced the "list namespace" option (-ln). This option was
11005 errata change to the ACPI specification as this support was intended for
11006 ACPI 3.0, but was inadvertently omitted.
11015 spec.) The problem was introduced when code was added to truncate the
11023 stack was not being popped after the execution of these operators,
11028 reference object returned from Index was inadvertently resolved to an
11030 value. This problem was introduced in version 20050114 when the behavior
11032 Store() was modified to restrict the object types that can be used as the
11063 where incorrect code was generated if a constant was reduced to a buffer
11075 underlying semaphore was not created. This problem was introduced in
11087 optional "implicit return" support where an error was returned if no
11089 object was expected, but one was implicitly returned. AE_OK is now
11159 36 temps available per-method, not 36 temps per-module as was the case
11172 null terminator was not included in the buffer after conversion, but
11176 the root of the ACPI_AML_BUFFER_LIMIT regression. This problem was
11177 introduced in the previous version when the code was updated to correctly
11251 length was incorrectly calculated. The length is now calculated exactly,
11260 routine where the length of the resulting buffer was not truncated to the
11292 Fixed a problem where the _HE resource name for the Interrupt macro was
11298 incorrect AML code was generated if the offset within the resource buffer
11299 was 0 or 1. The optimizer shortened the AML code to a single byte opcode
11325 conversion was necessary (e.g., if the input to ToInteger was an Integer
11330 exception code was returned if the resulting string would be > 200 chars.
11333 Fixed a problem with the Concatenate operator where AE_OK was always
11360 Fixed typechecking for the ObjectType and SizeOf operators. Problem was
11365 byte was inadvertently set to zero.
11384 (via the Index() operator). The previous behavior was to invoke the
11386 conversion rules if an object was already present at the index. The new
11427 Implemented support for FADT revision 2. This was an interim table
11445 where the operand was resolved to a value too early, causing incorrect
11479 emitted properly if the target of the scope was in another table.
11517 string could be set incorrectly too long if the input operand was a
11554 Fixed a problem where the compiler would fault if there was a syntax
11599 Fixed two problems in the ToString operator. If the length parameter was
11600 zero, an incorrect string object was created and the value of the input
11601 length parameter was inadvertently changed from zero to Ones.
11605 resource macro was ignored.
11634 Fixed a problem where the Default() operator was inadvertently ignored in
11636 Switch/Case block. This was a problem in the translation of the Switch
11644 translated Else...If parse tree was improperly constructed leading to the
11654 was not returned for the TRUE case. Changed the code to return Ones
11656 of (!Arg) which was usually 1. This change affects iASL constant folding
11660 Fixed a problem in AcpiUtInitializeBuffer where an existing buffer was
11700 Fixed a problem with constant folding and the LNot operator. LNot was
11759 was
11805 support was not used internally, and would not work correctly anyway
11835 generation. This problem was introduced in the 20040715 release.
11968 Fixed a fault when using the -g or -d<nofilename> options if the FADT was
11980 the Scope() operator could not be optimized if the namepath was a subpath
12001 arguments. Obsolete code that was causing the problem was removed.
12051 ACPI_OS_NAME was removed from the OS-specific headers. The default name
12136 Fixed a problem where the physical address was incorrectly calculated
12138 the Load() operator was used to directly load from an Operation Region
12231 parameter was incorrectly applying the "implicit conversion rules" during
12303 properly. The proper scope within the namespace was not initialized
12312 being extracted instead of just _MEM. (i.e. bitmask was incorrectly too
12377 S4Bios_f field was incorrectly defined as UINT32 instead of UINT32_BIT.
12553 Implemented a fix for the iASL disassembler where a bad index was
12554 generated. This was most noticeable on 64-bit platforms
12564 _Lxx control method was incorrectly cleared twice.
12597 relinquishing the processor, as would happen if AcpiOsSleep() was
12605 Fixed a reported error where and incorrect GPE number was passed
12640 Fixed a problem with Index Fields where the index was not
12646 beyond the end-of-field if the field was larger than the access
12653 was larger than the specified field access width.
12707 of the opcode failed. The solution to this problem was to
12713 Fixed a call to AcpiHwRegisterWrite in hwregs.c that was causing a
12862 after it was already working, thus disabling all ACPI and the IRQs
12876 in incorrect warnings and incorrect AML code. This was a problem
12897 ACPI mode was enabled.
12913 tables (SSDTs) was not being propagated into the namespace objects
12927 was incorrectly handling the case where a namespace node was the
12975 AcpiHwClearGpeBlock() where an incorrect offset was passed to the
12976 low level hardware write routine. The offset parameter was
12980 Fixed a problem where a handler object was deleted twice during
12986 A fix for SMP systems with link devices was contributed by
13059 could cause the premature deletion of the object. This was seen
13187 implementations (although the behavior was not defined in the ACPI
13191 terminated. This problem was seen during the generation of _BIF
13274 ACPI CA interfaces) could be overwritten if the buffer was too
13278 string of length one was always returned, regardless of the size
13307 cause corruption of the DSDT if the object type being stored was
13309 being stored was equal to or smaller than the original (existing)
13310 target object. This was seen to cause corruption of battery _BIF
13313 Fixed a problem where an internal error was generated if a control
13314 method invocation was used in an OperationRegion, Buffer, or
13315 Package declaration. This was caused by the deferred parsing of
13317 method object. The solution to this problem was to create the
13326 and caused memory corruption. This problem was seen to cause
13386 or Arg was not copied to a new object during the store - the
13387 object pointer was simply copied to the Local/Arg. This caused
13392 was not completed properly if the Local/Arg contained a reference
13398 a protection fault if the object being copied was a Package and
13457 Fixed a problem where the target of the Index() operator was not
13458 correctly constructed if the source object was a package. This
13462 Fixed a problem with the Index() operator where an attempt was
13465 Fixed a problem where an attempt was made to delete an operand
13480 premature deletion of a buffer object if a buffer was used as an
13483 the 10/02 release was attempting to fix a memory leak (albeit
13543 Fixed a problem where the semaphore WAIT_FOREVER constant was
13599 (name reference) of the object that was not found is displayed in
13630 /proc. This was related to the scope type change described above.
13706 was optimizing the wrong path (of the two namepaths.) This caused
13715 the NamePath was examined instead of the last NameSeg.
13730 behavior was identical to the ToHexString operator instead of just
13738 where the original object was not deleted if it was converted to a
13747 where a new object was assigned to one of the two names due to the
13808 conversion" was not performed. In other words, if the existing
13809 object (package element) was to be replaced completely, the code
13868 same scope. This previously was allowed if both objects were of
13869 the same type. (i.e., a lookup was the same as entering a new
13904 Fixed a problem where the listing file was not generated if the
13905 compiler aborted if the maximum error count was exceeded (200).
13907 Fixed a problem where the typechecking of method return values was
13922 This problem was created during the conversion to the new
13924 code was not updated to reflect the new model.
13933 more carats precede a single nameseg, the nameseg was treated as
13934 standalone and the search rule (to root) was inadvertently
13940 load. This was a relatively minor tweak to the table loading code
14053 dma channels during the GetCurrentResources call. This was
14095 descriptors where an invalid AML sequence was created.
14097 Implemented a fix for BufferData term in the ASL parser. It was
14102 value of zero if "Ones" was used where a byte, word or dword value
14103 was expected. The 64-bit value is now truncated to the correct
14126 method.) The return buffer length was set to zero instead of the
14162 limited testing was performed of the added functionality.)
14195 interpreter where a buffer result object was incorrectly marked as
14239 Fixed a problem where the "_DDN" reserved name was defined to be a
14250 names within error messages were wrong. This was caused by a
14279 new table pointer was incorrectly treated as a physical address
14285 Fixed a problem where an exception would occur if an ASL Field was
14339 Previously, this check was only performed for control methods.
14358 the indentation of closing parentheses and brackets was not
14378 AcpiSetRegister. This was simply an externalization of the
14486 was stored only with control method nodes, causing a fault when
14487 non-control method code was executed during table loading. The
14502 where memory was always accessed byte-wise even if the AML-
14503 specified access width was larger than a byte. This caused
14512 of the 4-byte Irq field was extracted.
14515 function was out of date and required a rewrite.
14544 itself was checked.
14561 1.0, if the field was larger than 32 bits, it was returned as a
14562 buffer - otherwise it was returned as an integer. In ACPI 2.0,
14618 idle handler was modified to more aggressively use C2, and PIIX4
14653 This field was 8 bits when it should be 64.
14675 an attempt was made to map memory beyond the end of the region.
14676 This was the root cause of the "AE_ERROR" and "AE_NO_MEMORY"
14680 algorithm was not functioning for some object types. Relaxed the
14718 Re-add some /proc/acpi/event functionality that was lost during
14763 fault. This was a side effect of the deployment of the new memory
14767 in the last major build. The "common" (1.0/2.0) internal FACS was
14769 Global Lock pointer. Also, the actual firmware FACS was being
14854 Obsoleted the AcpiOsCallocate OSL interface. This interface was
14861 Reorganized the GPE information and shrunk a large array that was
14880 prefix (^) was not handled correctly in the interpreter and
14898 was confusing during single stepping.
14953 Fixed a problem where incorrect AML was generated for the case
14988 was lost if the caller had to actually wait for the mutex.
15047 tha actual value before the size is evaluated. This behavior was
15056 integers when the internal Package was converted to an external
15063 to track objects was broken.
15069 length required for the _PRT structure was not being returned
15129 operator was not recorded correctly into the field object.
15167 arch/i386/kernel/acpitables.c, which was introduced in an earlier
15205 parent operation region) was calculated incorrectly if the
15257 disassembly for IndexFields was not supported correctly.
15267 Fields: Fixed a problem where the AML interpreter was incorrectly
15268 attempting to write beyond the end of a Field/OpRegion. This was
15269 a boundary case that occurred when a DWORD field was written to a
15274 starting bit address of a field was incorrectly calculated if the
15275 current access type was wider than a byte (WordAcc, DwordAcc, or
15352 Fixed a problem where the AML debugger was causing some internal
15435 root table pointer was not mapped into a logical address properly.
15437 Fixed a problem where a NULL pointer was being dereferenced in the
15447 by the called method. The object reference count mechanism was
15461 The module exxface.c was eliminated as it was an unnecessary extra
15495 was found and fixed. The implicit function return value (not the
15496 explicit store operands) was returning the remainder instead of
15497 the quotient. This was a longstanding bug and it fixes several
15639 DeviceFunction field into two 16-bit fields. This was
15752 The source code directory tree was restructured to reflect the
15856 thread was waking up with an error from receiving a SIGCHLD
15892 This reserved value was changed from 0 since Unix systems allow a
15906 address space was set to 0, not 0x7f as it should be.
15992 Added a new OSL Interface, AcpiOsGetThreadId. This was required
16029 element was not always set in a package returned from
16032 Fixed a problem where the length of a String package element was
16069 Core ACPI CA Subsystem: Fixed a problem where an error was
16070 incorrectly returned if the return resource buffer was larger than
16201 properly. The symptom was an AE_AML_OPERAND_TYPE during
16203 related internally) to the problem that was fixed in the last
16217 properly. The symptom was an AE_AML_OPERAND_TYPE during
16226 AE_AML_OPERAND_TYPE errors. This was actually a rather serious
16232 previous build (The prefix part of a relative path was handled
16236 the operation region name was a "namepath" instead of a simple
16237 "nameseg". Symptom was an AE_NO_OPERAND error.
16284 Fix for Processor object length field, was always zero
16345 Fixed problem where the call to AcpiEvFindPciRootBuses was
16368 Fixed problem where TerminateControlMethod was being called
16409 manifested itself when a Field was created with WordAccess or
16410 DwordAccess, but the field unit defined within the Field was less
16420 context was getting confused between accesses. This required a
16443 was done to prevent collisions with existing files in the host
16524 OsdUnMapMemory was renamed to OsdUnmapMemory and then
16556 The Store operator was modified to mimic Microsoft's