CHROMEBOOK_PLATFORM(4)

πŸ’» CHROMEBOOK_PLATFORM(4) πŸ’»

Kernel Interfaces Manual ✨ so like, this is the chromebook_platform page, bestie, and it's a whole section 4 moment πŸŽ€


🌸 NAME 🌸

chromebook_platform β€” the support driver for hardware on all the various Chromebook models πŸ¦‹


✨ SYNOPSIS ✨

Okay so if you wanna compile this driver straight into the kernel, you drop these lines into the kernel config file:

device chromebook_platform

OR β€” and this is the lowkey easier route β€” if you wanna load it as a module at boot time instead, you put this single line in loader.conf(5):

chromebook_platform_load="YES"

slay, that's it πŸ’…


πŸ’– DESCRIPTION πŸ’–

So the chromebook_platform driver does the automatic configuration thing for devices that cannot be enumerated or safely probed 🫢. And like, the main character here is I2C peripherals, because bestie, they are different from model to model β€” no cap, every Chromebook's got its own vibe 🌈.

What chromebook_platform brings to the table is model-specific information about:

  • the I2C peripherals themselves πŸ”₯
  • their drivers πŸš—
  • their bus attachments πŸ”Œ
  • their slave addresses πŸ“¬
🚨 okay important heads-up bestie: chromebook_platform does NOT load driver modules for the peripherals. Not its job, not its era. Those have to be compiled into the kernel or loaded separately, fr fr. Don't come for it, it said what it said πŸ’€

🌟 SEE ALSO 🌟


πŸ‘‘ AUTHORS πŸ‘‘

The chromebook_platform driver and this manual page were written by Andriy Gapon <avg@FreeBSD.org> β€” iconic behavior, honestly, we stan πŸŽ€πŸ’œ


Debian Β· October 13, 2016 Β· CHROMEBOOK_PLATFORM(4) β€” and that's the whole page bestie, ty for coming to my TED talk, go configure ur Chromebook πŸ’–βœ¨πŸ¦‹

πŸ“¦ where this page comes from