Hacker News new | ask | show | jobs
by 1970-01-01 5 days ago
The phrase "standing on the shoulders of giants" comes to mind. So what happened here? Shouldn't there be at minimum a framework for making a camera driver? Nope. They're gluing everything together and hoping it works.. Again. This is not standing on the shoulders of those that came before. It's the same issues year over year over year. It isn't trolling, it is calling out the highly non-optimal, "reinvent the wheel using these bits we have lying around" situation for getting things working.
1 comments

Linux on desktop and Linux on phone hardware are entirely different beasts.

Phones have literally never been open. Historically telecommunications has kept a tight, tight grip on everything, hardware and software included.

Even android, which is open source and based on Linux, cannot boot on any devices on earth without propriety blobs for the hardware. There is not UEFI or ACPI for phones, it doesn’t exist.

The entire history of IBM PCs and phones are just very different. This isn’t a Linux versus the rest thing. We already HAVE Linux on phones, for decades. That’s not the problem. The problem is the hardware manufactures and firmware. They absolutely will not let it go.

We saw this when Qualcomm entered the PC market. They wouldn’t upstream fuck all, and surprise surprise those chips were destined for the trash bin due to low support. That just doesn’t fly on PC, even on Windows. Say what you will about x86, intel and amd. But at least it’s an open and interoperable ecosystem.

What are you talking about? Phones have been open for a very long time. Hundreds of thousands of Linux IoT devices are already on the air. Again, it is the Linux community that has never bothered to organize and put in the work to meet FCC and carrier standards for a consumer-grade phone. Here's v43 of the open guide that nobody from the Linux community wants to even begin working on: https://opendevelopment.verizonwireless.com/open-access/arti...