rio_basic_attach(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌈 rio_basic_attach(9) β€” Kernel API Manual 🌈

okay bestie, welcome to the Kernel API Manual page for rio_basic_attach(9). This one is short but iconic: it's the attach function for the basic RapidIO enumeration/discovery method. No cap πŸ’–.


✨ NAME ✨

rio_basic_attach β€” the dash after it is followed by literally nothing, so there's no extra one-line description here. Just the function name doing its main-character thing πŸ’….

πŸ¦‹ SYNOPSIS πŸ¦‹

The signature is giving "I return an int and I take zero arguments":

int rio_basic_attach (void );

πŸŽ€ ARGUMENTS πŸŽ€

  • void β€” no arguments. Nothing to pass, nothing to vibe-check, just empty on purpose 🫢.

πŸ’… DESCRIPTION πŸ’…

Okay so when this enumeration/discovery method is loaded as a module, this function registers its specific enumeration and discover routines for all available RapidIO mport devices. That's the whole glow-up ✨.

The "scan" command line parameter controls the ability of the module to start RapidIO enumeration/discovery automatically. So yeah, that parameter is the little switch in charge of the auto-start vibes πŸ‘‘.

It returns 0 for success or -EIO if it's unable to register itself. Very demure, very clear 😌.

Heads up bestie: this enumeration/discovery method cannot be unloaded and therefore does not provide a matching cleanup_module routine. That's not a missing detail β€” it's literally how it is, so don't come for it πŸ’€.

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/rapidio/rio-scan.c β€” and the whole function friend group is:


Mwah πŸ’‹ β€” this page is from the Kernel API Manual, source/version ./drivers/rapidio, dated October 2026. k bye bestie, go register those routines fr fr πŸ’–βœ¨

πŸ“¦ where this page comes from