RESOURCE_INT_VALUE(9)

💖 RESOURCE_INT_VALUE — the kernel dev manual, bestie edition 💖

okay so you're poking around section 9 of the Kernel Developer's Manual and you found resource_int_value, resource_long_value, and resource_string_value?? slay, you're literally in the kernel right now. let's get into it 🫶

---

✨ NAME ✨

resource_int_value, resource_long_value, resource_string_value — get a value from the hints mechanism

no cap, that's the whole job. they fetch. you receive. 💅

---

🌸 SYNOPSIS 🌸

#include <sys/param.h>
#include <sys/bus.h>

int
resource_int_value(const char *name, int unit, const char *resname,
    int *result);

int
resource_long_value(const char *name, int unit, const char *resname,
    long *result);

int
resource_string_value(const char *name, int unit, const char *resname,
    const char **result);

three little functions, three little vibes: one does int, one does long, one does string. pick your fighter. ⭐

---

🎀 DESCRIPTION 🎀

so the way that these functions work is they fetch a value from the "hints" mechanism. that's it, that's the plot. 🦋

and here's the cast of arguments, one by one:

• name — the name of the device you're getting the resource value from. the main character, honestly. 👑
• unit — the unit number of the device. and listen, -1 is special: it's the wildcard entry. so -1 isn't a normal number here, it's a whole mood. 🌈
• resname — the resource name. the thing you're asking about. 🍓
• result — a pointer to memory where the resource value gets stored. yes bestie, you have to hand it somewhere to live. 🏠

---

💫 RETURN VALUES 💫

if it worked? 0. iconic. ✨

if it did not work? a non-zero error code comes back at you. not iconic, but informative. 😭

---

💀 ERRORS 💀

these functions will fail if:

• [ENOENT] — the resource could not be found. it's giving lost in the sauce. 🙈
• [EFTYPE] — inappropriate resource type. wrong vibe, wrong type, hard no. 💅

---

🔥 SEE ALSO 🔥

• device(9)
• driver(9)

go read those too, iykyk. 🧚

---

👑 AUTHORS 👑

this manual page was written by Warner Losh <imp@FreeBSD.org>. legend behaviour, honestly. 💜

---

and that's the whole page, bestie!! it's from the Debian flavour of things, dated March 1, 2001 — so yes, this lore is vintage, and it still ate. periodt. 🎀💖🌸