Live data from Hacker News

Google Pixel 6 and Pixel 6 Pro

store.google.com

11–20 of 851 posts

Re: Google Pixel 6 and Pixel 6 Pro

#11
post #6

Since this is Google making the SoC, surely we have Linux drivers within a month for it? Already upstreamed? Some register documentation? I didn't check, but I suppose the answer is "no". Can't keep pointing at Qualcomm anymore, I guess.

That's not how open source works in SoC design. In fact it doesn't work at all an here's why: Google hasn't made the SoC and doesn't own the IP, it most likely bought a bunch of IP blocks from established vendors like Cadence, Synopys, Samsung, etc and fused them together to create a SoC.

All those IPs come with their own license terms and NDAs that limit what you can do with it. You can use it in your final product and make money selling it, but most most IP vendors in the semi space will not let you open source anything about their design, including drivers, as that IP is their golden goose.

If you want to blame someone for this sorry state of affairs, you can blame the entire semi industry starting from the EDA and IP vendors all the way to the fabs. It's pretty much a cartel and they all keep their cards close to the vest any way they can.

Re: Google Pixel 6 and Pixel 6 Pro

#14
post #8
post #6

Since this is Google making the SoC, surely we have Linux drivers within a month for it? Already upstreamed? Some register documentation? I didn't check, but I suppose the answer is "no". Can't keep pointing at Qualcomm anymore, I guess.

Why would they release driver for hardware not available to the public?

Getting new drivers into the kernel can be a long process, sometimes taking months. Some companies prefer to engage early to minimise pressure when the device is released.

Re: Google Pixel 6 and Pixel 6 Pro

#16
post #6

Since this is Google making the SoC, surely we have Linux drivers within a month for it? Already upstreamed? Some register documentation? I didn't check, but I suppose the answer is "no". Can't keep pointing at Qualcomm anymore, I guess.

Presumably, they'll show up on https://android.googlesource.com if they haven't already.

Re: Google Pixel 6 and Pixel 6 Pro

#17
post #8
post #6

Since this is Google making the SoC, surely we have Linux drivers within a month for it? Already upstreamed? Some register documentation? I didn't check, but I suppose the answer is "no". Can't keep pointing at Qualcomm anymore, I guess.

Why would they release driver for hardware not available to the public?

That happens all the time:

https://www.phoronix.com/scan.php?page=news_item&px=Intel-Di...

Because working with upstream is not sitting in your chambers for years, then throwing a huge patch over at the end of it.

Re: Google Pixel 6 and Pixel 6 Pro

#19
post #6

Since this is Google making the SoC, surely we have Linux drivers within a month for it? Already upstreamed? Some register documentation? I didn't check, but I suppose the answer is "no". Can't keep pointing at Qualcomm anymore, I guess.

Upstreamed? Why would they want to deal with that kind of crap?

Re: Google Pixel 6 and Pixel 6 Pro

#20
Thanks Google. Think I’ll be buying this.

I want as little to do with Google’s services as possible in my life, but they really deserve credits for making a modern usable smartphone that is reasonably open. There is just one single feature I will be buying this for - the 5 years of software updates. While good image processing is definitely a pro, all of these software you’re presenting features I really don’t give a damn about. Just give me a phone that is meant to last a little while - and allow me to run what I damn please. This looks to be like a continuation of the Pixel 5, which allows you run your own software like /e/OS and CalyxOS aside to just being a lot less of a walled garden on the stock ROM.

The Android market is completely dire, and no vendor can be trusted to provide openness, reasonable taste or security updates. They sell you a phone, and once you’ve clicked buy they’ve already stopped caring. So last year I switched to an iPhone 12. I needed to vote with my wallet to get a phone that lasts. But although I get what’s appealing about iPhones and the walled garden, I started feeling claustrophobic. Feeling claustrophobic about what I can tailor about my browser, how easily I can run Game Boy games, what ads I can block, and Apple’s stated intents to actively incriminate you by scanning your photos on a personal device. I will continue to recommend those phones for most people (pending what they’re going to do with trying to incriminate you), but it’s not for me.

Finally here’s a seemingly good Android phone with 5 years of support - from the only phone vendor outside of Apple who appears to give a damn about that aspect. Don’t get me wrong: 5 years is still too short in my view, and not as long as Apple provides support for on their stuff [1]. But the market needs change, and I’ll put money towards that.

[1]: The iPhone 5S has just hit 8 years of _kernel_ security updates last month with iOS 12.5.5. One can dream on the Android side, but I’ll take 5 years in the current market.

Post reply on HN