4 ms·
I have never worked at Google, but some of this seems... odd from my perspective. > Upstreaming driver changes was something phone manufacturers just didn't do
by yjftsjthsd-h 4y ago
I have never worked at Google, but some of this seems... odd from my perspective.
> Upstreaming driver changes was something phone manufacturers just didn't do and didn't want to do.
This is absolutely true. However - and this makes no sense to me - Chromebooks apparently do upstream everything, even for ARM models. Any idea what went right there?
> you had duplication of services between the all-but-dead AOSP and Play services.
My understanding from the outside is that Google likes to pretend that AOSP is sufficient for antitrust reasons but really wants to control everything directly; you can't solve that by creating a new product unless the hope is that nobody cares that the "new" ecosystem doesn't get examined by the same standards.
> Remember these are statements of fact.
I'm assuming you meant to type "not" there?
> Google had always had hopes that there would be a healthy ecosystem of phone manufacturers. For awhile there were but now? Now it's really just Samsung.
Samsung is certainly the biggest, but it's hardly the only name in town; https://www.appbrain.com/stats/top-manufacturers https://www.appbrain.com/stats/top-manufacturers puts them at ~34% with the rest in the long tail.
- djbusby 4y agoOne guess is that getting drivers upstream for Chromebook improves the possibility of external vendors making hardware. And Chromebook I seems to be supported for a long time.
- raggi 4y agoThe patches & drivers involved in most Chromebook peripherals are much closer to that of a PC in architecture than for the SoC's that go into phones. In this regard the patches are far less invasive, and thus more easy to match with upstream requirements.
- toast0 4y ago>> Upstreaming driver changes was something phone manufacturers just didn't do and didn't want to do. > This is absolutely true. However - and this makes no sense to me - Chromebooks apparently do upstream everything, even for ARM models. Any idea what went right there? >> you had duplication of services between the all-but-dead AOSP and Play services. > My understanding from the outside is that Google likes to pretend that AOSP is sufficient for antitrust reasons but really wants to control everything directly; you can't solve that by creating a new product unless the hope is that nobody cares that the "new" ecosystem doesn't get examined by the same standards. This might be why Chromebooks upstream and Android doesn't. ChromeOS doesn't have the same market context as Android, so Google doesn't have to play the game of avoiding anti-trust. They can be deeply involved in defining the acceptable hardware and requiring things get pushed upstream or not used. Android hardware on the other hand is more chaotic, and Google doesn't want to get hit with the anti-trust stick, so they're not willing to do very much to disturb the ecosystem. So they're stuck with this patently absurd system where SoC makers deliver an android build with a custom kernel to device manufacturers, and the kernel never gets updated, but Android keeps requiring new kernel features for their userland updates, so nobody can get those anyway; and there's a new project to make updates feasible for longer every two to three years, but it never actually drives the marketplace forward, because it only addresses new phones, but will be abandoned in three years anyway. At least, that's what I can gather as an outsider.
- BoorishBears 4y agoThis is totally overthinking it. Google is making money hand over fist from so many different angles that they can simply afford to. Google Play makes them more profit than some major phone manufacturers do off all their devices sold. So if there are engineers at Google who are willing to own something like getting high quality Chromebook support in the larger Linux ecosystem, the money is there. Compare that to traditional phone manufacturers that are: - reluctant to spend a single dime where they don't have to - actually benefit from obsolete devices - have trouble attracting in-house talent causing them to outsource work in a way that is not conducive to high quality upstream-able code... At the end of the day it's money.
- torginus 4y agoI don’t understand why it’s such a big hurdle to have upstream driver for a SoC - usually Qualcomm makes the chip and probably the drivers for a given chipset. They are the only ones whose responsibility it would be to have an upstream kernel driver. If intel, amd or others can make it so that their very complicated silicon can run on top of open source code, it should be possible for them as well. Granted, the phone manufacturers would probably further customize the kernel, however, the phones could still run on top of code that is 99 percent upstream, and they could both spare a lot of dev resources and stay closer to upstream.
- AdrianB1 4y agoI think the Intel and AMD situation (and Cyrix and VIA in the past) is exactly opposite: open source was build on their public ISA. Qualcomm does not build SoCs for open source, they build SoCs and don't even want to open source the drivers for it, reverse engineering is too complicated or not worth (as SoC changes too often), so third parties cannot write open source drivers.
- lupire 4y agoQualcomm sells more chips when the software fails after 2-3 years and consumers by a new phone. So they don't maintain drivers.
- 4y ago
- sangnoir 4y ago> My understanding from the outside is that Google likes to pretend that AOSP is sufficient for antitrust reasons but really wants to control everything directly; I never worked at Google either - but having an evergreen Google Play service seemed necessary to overcome the greatly exaggerated Fragmentation problem by back-porting what had been OS features to older Android versions. Previously, Android OEMs and their vendors - especially Qualcomm - had no incentive to provide driver updates for already-sold units, so that tended to never happen. Cue the tech press, Apple and developers loudly bemoaning "Fragmentation!!1!"
- fulafel 4y ago> This is absolutely true. However - and this makes no sense to me - Chromebooks apparently do upstream everything, even for ARM models. Any idea what went right there? Isn't the ChromeOS HW platform support built at Google? At least in many cases they seem to first add support for a HW platform (board + SoC) under a codename to the tree and then various vendors ship products based on that HW platform.