2 ms·
That's often not that simple. For example, SAMSUNG might build your device, and get all of their own code openly. But now for the US model, due to CDMA, they
by kuschku 9y ago
That's often not that simple.
For example, SAMSUNG might build your device, and get all of their own code openly.
But now for the US model, due to CDMA, they need to use a Qualcomm processor.
That needs a blob, and Qualcomm won't release that under an open license, nor update it.
So the OEM can either just not have CDMA support, or accept foreign blobs.
It works like this all way down the stack, down to even camera chips.
And then these devices all have custom hardware. Often hundreds of customly designed parts, with custom drivers, only ever for a single device.
Think of the Moto Z Play, withthe replacable components. Samsung phones with facial scanners. LG phones with 3D display.
One-off features that'd never get mainlined.
- mjevans 9y agoMy understanding about the US side of this is that the software defined radios and FCC compliance are a major portion of the problem. STILL, that stuff should be equivalent to a firmware blob that should have been baked in to a ROM or EEPROM. The actual driver controlling it should be able to be open, and for regulatory compliance should use 'magic numbers' as specified for the configuration; which as a fact of how to use that device must be configured already /not/ be covered by copyright (in the US at least).
- matt_wulfeck 9y agoApple has the same issues, yet they keep their devices updated and secure for 5+ years.
- pcwalton 9y agoWell, Apple completely controls the XNU kernel and its I/O Kit framework. By contrast, Google--and especially phone manufacturers--don't control development of the Linux kernel.