#devicetree
Live, measured metrics for the hashtag #devicetree from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #devicetree
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-09-16 07:09 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-09-16 07:09 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-09-16 07:09 UTCEverything below is measured over the latest 40 public posts (spanning ~28126 hours).
Posting hours (UTC) — busiest: 17:00
Languages: English (29) · German (5) · French (2) · Russian (2) · Czech (1) · Korean (1)
Avg boosts / post: 1.2
Top of the latest posts
Why am I even making a #DeviceTree visualizer? Modern SoCs are very complex. This tree here from an Allwinner D1 is simple in comparison with just above 100 nodes. Most of those are for peripherals. Some are clocks, power supplies and inter
Now on stage at the Embedded Linux Conference in Prague, @krzk explains How to Get Your DT Schema Bindings Accepted in Less Than 10 Iterations https://eoss2023.sched.com/event/1LcNo/how-to-get-your-dt-schema-bindings-accepted-in-less-than-1
Welp, I posted an RFC for describing display notches, cutouts, rounded corners, and waterfall edges in devicetree. #LinuxMobile #Kernel #Devicetree https://lore.kernel.org/phone-devel/[email protected]
What “devicetree” means
WikipediaIn computing, a devicetree is a data structure describing the hardware components of a particular computer so that the operating system's kernel can use and manage those components, including the CPUs or SoC, the memory, the storage, the buses and the integrated peripherals.
“Devicetree” on Wikipedia (CC BY-SA) →#devicetree across platforms
every network with a public tag surfaceFollow #devicetree straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/devicetree