rio_local_get_device_id(9)
π rio_local_get_device_id(9) β the Kernel API Manual glow-up β¨
okay so bestie, welcome to the Kernel API Manual page for rio_local_get_device_id(9) and honestly? it's a little cutie. lowkey one job, does it well. let's get into it π«Ά
πΈ NAME πΈ
rio_local_get_device_id β get the base/extended device id for a port, fr fr that's the whole vibe β¨
π SYNOPSIS π
u16 rio_local_get_device_id (struct rio_mport *port );
that's it. one arg, one u16 coming back at you. iconic behavior honestly π
π¦ ARGUMENTS π¦
portβ the RIO master port you're pulling the deviceid from. that's your main character right there π
β¨ DESCRIPTION β¨
so what does it actually do? it reads the base/extended device id from the local device that's implementing the master port. then it hands you back the 8/16-bit device id. that's the whole quest. no cap, no side plots, just the id π
like it's giving "small function, big confidence" and we respect it π
π₯ SEE ALSO π₯
bestie there is a whole rapidio friend group and you're about to meet every single one of them. buckle up π
the kernel file lives at ./drivers/rapidio/rio.c and here's the full clique:
rio_query_mport(9)rio_alloc_net(9)rio_local_set_device_id(9)rio_add_device(9)rio_request_inb_mbox(9)rio_release_inb_mbox(9)rio_request_outb_mbox(9)rio_release_outb_mbox(9)rio_setup_inb_dbell(9)rio_request_inb_dbell(9)rio_release_inb_dbell(9)rio_request_outb_dbell(9)rio_release_outb_dbell(9)rio_add_mport_pw_handler(9)rio_del_mport_pw_handler(9)rio_request_inb_pwrite(9)rio_release_inb_pwrite(9)rio_pw_enable(9)rio_map_inb_region(9)rio_unmap_inb_region(9)rio_map_outb_region(9)rio_unmap_outb_region(9)rio_mport_get_physefb(9)rio_get_comptag(9)rio_set_port_lockout(9)rio_enable_rx_tx_port(9)rio_chk_dev_route(9)rio_mport_chk_dev_access(9)rio_chk_dev_access(9)rio_get_input_status(9)rio_clr_err_stopped(9)rio_inb_pwrite_handler(9)rio_mport_get_efb(9)rio_mport_get_feature(9)rio_std_route_add_entry(9)rio_std_route_get_entry(9)rio_std_route_clr_table(9)rio_lock_device(9)rio_unlock_device(9)rio_route_add_entry(9)rio_route_get_entry(9)rio_route_clr_table(9)rio_request_mport_dma(9)rio_release_dma(9)rio_dma_prep_xfer(9)rio_register_scan(9)rio_mport_scan(9)
and that's the whole page bestie, you ate that π β¨
sign-off time π«Ά this one comes from ./drivers/rapidio and it's dated October 2026 β so yes, she's from the future and she's still just returning a device id. queen behavior ππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms