mips_machine_is_compatible(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… mips_machine_is_compatible(9) β€” the Kernel API Manual cut πŸ’…

okay bestie, so this one lives in the Kernel API Manual, and it's called mips_machine_is_compatible(9) β€” say that five times fast, i literally dare you. it's a little function that does the "do u two even go here together" vibe check between a machine and a device tree 🌸


✨ NAME ✨

mips_machine_is_compatible β€” check if a machine is compatible with an FDT 🫢

like, genuinely just checking compatibility. no cap.


πŸŽ€ SYNOPSIS πŸŽ€

const struct of_device_id * mips_machine_is_compatible (const struct mips_machine *mach , const void *fdt );

that's the whole signature, she's not long but she IS iconic ✨


πŸ¦‹ ARGUMENTS πŸ¦‹

  • mach β€” the machine struct to check. like, the machine in question πŸ‘€
  • fdt β€” the FDT to check for compatibility with. the other half of the situationship πŸ’€

πŸ’– DESCRIPTION πŸ’–

so what it does is: it checks whether the given machine mach is compatible with the given flattened device tree fdt, and it bases that whole judgement call on the compatibility property of the root node. that's it, that's the bit. lowkey elegant, highkey important 🧚


🌟 RETURN 🌟

it gives you back the device id that matched, if there was any β€” else NULL. so like, NULL is the "it's giving nothing, they're not compatible" answer πŸ™ˆ

fr fr, check for NULL before you go using the result, bestie. that's just self-care πŸ’…

🌈 SEE ALSO 🌈


and that's the tea πŸ“ this page is brought to you by ./arch/mips/include/asm, dated October 2026, and it's literally the mips_machine_is_compatible(9) page β€” go forth and be compatible, queen πŸ‘‘πŸ’œ

πŸ“¦ where this page comes from