STRUCT TPCI200_INFOS(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨ β€” struct tpci200_infos(9), from the Kernel API Manual πŸ’–

okay bestie, listen: this page is all about struct tpci200_infos, and the official NAME line is struct tpci200_infos β€” "informations specific of the TPCI200 tpci200." yes, that's the exact wording, grammar and all, and we are not fixing it because the rule is keep every detail. periodt. πŸ’…

the NAME block also lists these little @-tagged goodies:

  • @pci_dev β€” PCI device
  • @interface_regs β€” Pointer to IP interface space (Bar 2)
  • @ioidint_space β€” Pointer to IP ID, IO and INT space (Bar 3)
  • @mem8_space β€” Pointer to MEM space (Bar 4)

no cap, that's the whole NAME situation. 🫢

πŸ¦‹ SYNOPSIS πŸ¦‹

here's the struct in all its glory, copied exactly because we do not play with code around here:

       struct tpci200_infos {
           struct pci_dev                  *pdev;
           struct tpci200_regs __iomem     *interface_regs;
           void __iomem                    *cfg_regs;
           struct ipack_bus_device         *ipack_bus;
        };

πŸŽ€ Members πŸŽ€

bestie, this heading is literally here β€” and there are no entries listed under it on the page. it's giving "I have arrived and I have nothing to say." πŸ’€ keep it moving, we still love her.

🌈 SEE ALSO 🌈

the SEE ALSO squad is:

  • Kernel file ./drivers/ipack/carriers/tpci200.h
  • struct slot_irq(9)
  • struct tpci200_slot(9)

iykyk β€” those are the cross-references, and yes, that exact kernel file path matters. 🧚


🌟 cute little sign-off: this page comes from the source path ./drivers/ipack/carriers, dated October 2026, and it's the manual entry for struct tpci200_infos(9). mwah, slay, bye bestie πŸ’‹πŸ‘‘

πŸ“¦ where this page comes from