T
@mcc On a tangent..
Wasn't RISC-V itself conceived as the kind of processor that can be so simple that you could smoosh 128 of them together as an array of GPU shaders?
So a complete system would have RISC-V units of different complexities and scale depending on their role.
@dissident @arstechnica That report missed this issue – Samsung puts un-removeable govt spyware on their phones:
@jamesmarshall @arstechnica Having lived in a house with this model of fridge (pictured with the see-through door), it contains a "sensor" to detect when you knock on the door (knocking illuminates the items in the window). The sensor is a microphone.
@hzulla I see lots of reasons to reject what is being marketed as AI, but there is one reason that stands above them all:
LLMs amplify bias, and the effect seems inescapable.
The issue could be identity politics, but also things like coding styles, system architectures, threat models, etc.
@publicvoit The context in which you made your remarks imply that the user has to stay with the OS / update system supplied by the original vendor to keep receiving proper updates. That is not true. The user's phone can receive updates via the alternative OS.
Its much different to say that the hardware only receives driver updates for as long as the hw vendor publishes them.
Somewhat related topic: The FSF has started a project to reverse engineer hardware (create drivers) for Android phones.
No.
A custom Android firmware like Graphene, Calyx, /e/ etc. will tell you which hardware models are supported and they will update the hardware drivers that allow Android to run on those models. You do not need to receive any updates directly "from the original vendor".