ACPICA: Difference between revisions

[unchecked revision]

← Older edit

Content deleted Content added

VisualWikitext

Revision as of 22:59, 30 September 2021 view source Sebastian (talk \| contribs) 73 edits m →‎External links: Fix minor grammar issue ← Older edit		Latest revision as of 17:52, 10 July 2023 view source osdev>Khaledhammouda No edit summary
(2 intermediate revisions by one other user not shown)
Line 1: {{ACPI}} The ACPI Component Architecture '''ACPICA''' provides an operating system (OS)-independent reference implementation of the [[ACPI\|Advanced Configuration and Power Interface]]. It can be adapted to any host OS. The ACPICA code is meant to be directly integrated into the host OS, as a kernel-resident subsystem. Hosting the ACPICA requires no changes to the core ACPICA code. However, it does require a small OS-specific interface layer, which must be written specifically for each host OS. Line 21 ⟶ 23: ACPI_PHYSICAL_ADDRESS AcpiOsGetRootPointer() { ACPI_PHYSICAL_ADDRESS Ret = 0; ~~Ret = 0;~~ AcpiFindRootPointer(&Ret); return Ret; Line 79 ⟶ 80: ==== AcpiOsExecute ==== ACPI_STATUS AcpiOsExecute(ACPI_EXECUTE_TYPE Type, ACPI_OSD_EXEC_CALLBACK Function, void *Context) Create a new ~~Thread~~thread (or process) with entry point at ''Function'' using parameter ''Context''. ''Type'' is not really useful. When the scheduler chooses this thread it has to ~~put~~pass in ''Context'' onto the first argument (RDI for x86-64, stack for x86-32 (using System V ABI) to have something like: Function(Context); ==== AcpiOsSleep ==== void AcpiOsSleep(UINT64 Milliseconds)