fdt_early_m...xtension_isa(9)
πΈ fdt_early_match_extension_isa β NAME β¨
okay so bestie, this is fdt_early_match_extension_isa from the Kernel API Manual, and it's literally just: check if all cpu nodes have an extension π
π SYNOPSIS π
bool fdt_early_match_extension_isa (const void *fdt , const char
*ext_name );
that's the whole vibe check right there π«Ά
π¦ ARGUMENTS π¦
fdtβ pointer to the device tree blob, aka the whole map of your hardware, no cap πext_nameβ the extension to search for, like the specific little feature you're hunting for π
π DESCRIPTION π
Returns true if all the available cpu nodes have the extension, and false otherwise β¨
like, every single available cpu node has to have it. all of them. not most of them, not "the vibes are there" β all. if even one is missing the extension, it's a false and the function said nope π
π§ SEE ALSO π§
- Kernel file
./arch/riscv/kernel/pi/fdt_early.cβ go read the source, it's giving main character energy π fdt_device_is_available(9)isa_string_contains(9)early_cpu_isa_ext_available(9)set_satp_mode_from_fdt(9)
the whole friend group fr fr π
okay that's the whole page bestie, tysm for reading π this one's from ./arch/riscv/kernel/pi and it's dated October 2026 β so like, future iconic β¨π
π
π¦ 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