pdc_pat_io_pci_cfg_write(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

okay so this is pdc_pat_io_pci_cfg_write(9), straight out of the Kernel API Manual, and we're gonna get you caught up bestie 🫢

The official one-liner is literally: Retrieve information about memory address ranges.

yes, that's the exact description on the page β€” we keep the facts exactly as they are, periodt πŸ’…


✨ SYNOPSIS ✨

Here's the signature, copied exactly:

       int pdc_pat_io_pci_cfg_write (unsigned long pci_addr , int pci_size ,
       u32 val );

πŸŽ€ ARGUMENTS πŸŽ€

  • pci_addr β€” the PCI configuration space address for which the write request is being made. That's where the write is headed, iykyk.
  • pci_size β€” size of the write in bytes. Valid values are 1, 2, and 4 β€” literally just those three, no cap.
  • val β€” pointer to the 1, 2, or 4 byte value in the low order end of the argument that's going to be written to PCI Config space. low order end, bestie β€” keep that detail πŸ“

🌈 SEE ALSO 🌈

The page points at the kernel file ./arch/parisc/kernel/firmware.c, and then it name-drops this entire squad of references β€” all of them, no skipping πŸ’–


byeee πŸ’œ source/version is ./arch/parisc/kernel, date is October 2026, and the page is pdc_pat_io_pci_cfg_write(9) β€” that's the whole footer, bestie πŸ¦‹

πŸ“¦ where this page comes from