ubi_get_device_info(9)

📦 version 7.3.1, in nixpkgs unstable

✨ ubi_get_device_info ✨

okay so this is a page from the Kernel API Manual — section 9, kernel API, bestie. it's about ubi_get_device_info, and yeah it's basically the "hey what's up with this UBI device" function. let's get into it 💅

🌸 NAME 🌸

ubi_get_device_info — get information about UBI device.

like, the whole vibe is: you got a UBI device, you wanna know stuff about it, this is the girl for the job 🎀

🦋 SYNOPSIS 🦋

int ubi_get_device_info (int ubi_num , struct ubi_device_info *di );

ok so she takes ubi_num and di, returns an int, and that's literally it. no cap, that's the whole signature 🫶

💖 ARGUMENTS 💖

  • ubi_num — UBI device number. you're like "which one tho" and this is the answer 🦋
  • di — the information is stored here. this is where the tea gets poured, bestie. the info goes in here, so it has to be a struct ubi_device_info *. 💅

👑 DESCRIPTION 👑

so here's the situation: this function returns 0 in case of success — iconic, we love a clean zero 💖 — and it returns -EINVAL if the UBI device number is invalid (like, girl, that number is not it 😭), and -ENODEV if there is no such UBI device (the device said "not me" and vanished 💀).

so basically:

  1. it works? 0. slay. periodt. ⭐
  2. bad device number? -EINVAL. 🚩
  3. no such device? -ENODEV. rip. 🙈
lowkey important: these three return values are the whole story — 0, -EINVAL, -ENODEV. don't go inventing extra ones, i'm not gonna let you set yourself up like that 🫶

🧚 SEE ALSO 🧚

like, go read these next, fr fr — the kernel file ./drivers/mtd/ubi/kapi.c is the main character here 👑 and then we got the whole friend group:

literally a whole squad. iykyk 🦋

and that's the page bestie!! 💜 this one came from ./drivers/mtd/ubi, dated October 2026, and she's living her best life in the Kernel API Manual (section 9). go get that device info, you absolute icon 🌈✨🎀

📦 where this page comes from