rio_get_comptag(9)
π rio_get_comptag(9) β the Kernel API Manual page, bestie edition π
okay so this is a page from the Kernel API Manual and it's literally all about rio_get_comptag β yes that's the whole name, it's giving "begin or continue searching for a RIO device by component tag" and honestly? iconic. β¨
π¦ NAME π¦
rio_get_comptag β start a search for a RIO device by component tag, or keep the hunt going from where you left off. no cap, that's it. π
πΈ SYNOPSIS πΈ
struct rio_dev * rio_get_comptag (u32 comp_tag , struct rio_dev *from );
look at her. so structured. so composed. π«Ά
β¨ ARGUMENTS β¨
comp_tagβ the RIO component tag you're matching against. this is the thing you're looking for, bestie πfromβ the previous RIO device you already found in the search, orNULLif you're starting fresh.NULL= new search energy π«
π DESCRIPTION π
so what it does is, it iterates through the list of known RIO devices. that's the whole main character move. π
if a RIO device gets found with a matching comp_tag, you get a pointer to its device structure returned. slay. otherwise? NULL comes back and that's just how it is. π
and here's the lowkey important bit β a new search is initiated by passing NULL to the from argument. but if from is not NULL, the search continues from the next device on the global list. so you're basically picking up right where you left off, no restarting, no drama. β¨
ngl thefromparameter is the whole vibe βNULLin, brand-new search out; anything else in, and you're continuing the journey. keep track of it or your loop will have a bad time π
β SEE ALSO β
all her friends, fr fr π
β the kernel file ./drivers/rapidio/rio.c and:
rio_local_get_device_id(9)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_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 page!! π this little beauty lives in ./drivers/rapidio, it's dated October 2026, and it's rio_get_comptag(9) through and through. go find your device, bestie β you've got this πβ¨π¦
π¦ 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