ChromeOS/chromebook has been fairly successful at making this happen. Tons of MediaTek and Qualcomm drivers & good support, if you have a chip slightly bigger than a phone chip.<p>Qualcomms slowly turning it around. Their Wi-Fi router situation was reaching a real breaking point, but we are multiple years of folks + them making good progress to getting into grace.<p>The benefit is also higher too, since ChromeOS has a more regular Linux-y environment, and I think even using Wayland now. Where-as on phone, it's like, great, kernel drivers, but the entire upper stack is Android so what the driver needs to prioritize is different.<p>If you read in here, part of the dodge is that rather than a actually upstream, Google maintains their own custom Kernel Module Interface (KMI) in their Android specific "Generic Kernel Image" (GKI) that's different from the actual kernel interface. So instead of vendors targeting upstream, now they're authoring to a Google specific kernel interface - a kernel wrapper - that doesn't exist anywhere else! Google's "Generic Kernel" seems like a fork of upstream that now people develop against. Its hard for me to see this situation as an improvement; it feels like it will insure work doesn't get upstreamed, since work isn't against the kernel but Google's kernel.<p>"Google Kernel Image" (or Android Kernel Image) might have been a better name than Generic Kernel Image.