rio_destid_next(9)
π rio_destid_next(9) β from the Kernel API Manual, bestie π
okay so picture this: you're deep in the RIO network code and you need to know which destID is, like, actually being used right now. This little function is your girl. She's from the <pink>Kernel API Manual</pink> and she's here to hand you the next one in line. β¨
β¨ NAME β¨
rio_destid_next β return next destID in use πΈ
β¨ SYNOPSIS β¨
u16 rio_destid_next (struct rio_net *net , u16 from );
β¨ ARGUMENTS β¨
netβ the RIO network, aka the whole vibe-y playground we're searching in π¦fromβ the destination ID from which search shall continue. like, you start looking right after this one, bestie π
β¨ SEE ALSO β¨
the kernel file ./drivers/rapidio/rio-scan.c (go look, it's giving main character energy), plus this whole squad of RIO besties:
rio_destid_alloc(9)rio_destid_reserve(9)rio_destid_free(9)rio_destid_first(9)rio_get_device_id(9)rio_set_device_id(9)rio_clear_locks(9)rio_enum_host(9)rio_device_has_destid(9)rio_release_dev(9)rio_is_switch(9)rio_setup_device(9)rio_sport_is_active(9)rio_get_host_deviceid_lock(9)rio_enum_peer(9)rio_enum_complete(9)rio_disc_peer(9)rio_mport_is_active(9)rio_update_route_tables(9)rio_init_em(9)rio_enum_mport(9)rio_build_route_tables(9)rio_disc_mport(9)rio_basic_attach(9)
ngl the whole crew above is iconique and you should absolutely go read all of them, no cap π
k bye ily, this page lives in ./drivers/rapidio and it's dated October 2026 β she's a documented queen and we stan π«Άπ
π¦ 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