acpi_dev_resource_memory(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 acpi_dev_resource_memory(9) 🌸

okay bestie, welcome to the Kernel API Manual page for acpi_dev_resource_memory β€” yes, the ACPI memory resource extraction girlie. she checks resource objects and fills in the generic one. periodt. πŸ’…


πŸ’– NAME πŸ’–

acpi_dev_resource_memory β€” extract ACPI memory resource information. πŸ’–

πŸ¦‹ SYNOPSIS πŸ¦‹

bool acpi_dev_resource_memory (struct acpi_resource *ares , struct
       resource *res );

πŸŽ€ ARGUMENTS πŸŽ€

  • ares β€” input ACPI resource object. like, the thing being checked. πŸ‘€
  • res β€” output generic resource object. this is the one that gets populated. 🫢

πŸ’œ DESCRIPTION πŸ’œ

okay so the function checks if the given ACPI resource object represents a memory resource. if that’s the case, it uses the information in it to populate the generic resource object pointed to by res. that’s the whole vibe. no cap. ✨

πŸ”₯ RETURN πŸ”₯

  1. false with res->flags setting to zero: not the expected resource type. πŸ™ˆ
  2. false with IORESOURCE_DISABLED in res->flags: valid unassigned resource. πŸ’€
  3. true: valid assigned resource. πŸ‘‘

🌈 SEE ALSO 🌈

Kernel file ./drivers/acpi/resource.c β€” bestie, go look at the source if you want the full lore. πŸ“‚


mwah πŸ’‹ this page came from ./drivers/acpi, dated October 2026, and it’s the acpi_dev_resource_memory(9) manual page. bye bestie, go slay some ACPI resources! 🌟

πŸ“¦ where this page comes from