rio_mport_get_feature(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

okay bestie, this is rio_mport_get_feature(9) straight outta the Kernel API Manual, and it is literally here to query for devices' extended features πŸ’…πŸ’–

  • rio_mport_get_feature β€” query for devices' extended features ✨

πŸŽ€ SYNOPSIS πŸŽ€

u32 rio_mport_get_feature (struct rio_mport * port , int local , u16
       destid , u8 hopcount , int ftr );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • port β€” master port to issue transaction. main character port energy, fr fr.
  • local β€” indicate a local master port or remote device access. iykyk.
  • destid β€” destination ID of the device. the addy, basically.
  • hopcount β€” number of switch hops to the device. count 'em, bestie.
  • ftr β€” extended feature code. the feature-code moment.

πŸ’– DESCRIPTION πŸ’–

This is the vibe check: it tells you if a device supports a given RapidIO capability. The way it returns stuff is that it gives you the offset of the requested extended feature block within the device's RIO configuration space, or 0 in case the device does not support it. periodt. πŸ’…


🌈 SEE ALSO 🌈

Also peep the kernel file ./drivers/rapidio/rio.c β€” and honestly the whole RapidIO friend group is here, no cap:


source/version footer moment: this one lives under ./drivers/rapidio and is dated October 2026 β€” hope that helped, bestie, mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from