Live data from Hacker News

Fairphone 6 wide camera experimental Linux support

nondescriptpointer.com

21–30 of 90 posts

Re: Fairphone 6 wide camera experimental Linux support

#21

Earlier quoted context omitted.

[flagged]

Different priorities. GrapheneOS prioritizes very strong security (inside a very specific model that includes treating the user as an attack vector to be protected against). Fairphone prioritizes repairable hardware (and actually makes their own hardware). On a finite budget (of both money and time and people), prioritizing either one of these will undermine the other.

and actually makes their own hardware

Fairphone hardware and software is developed/maintained by a Chinese ODM (T2Mobile).

Re: Fairphone 6 wide camera experimental Linux support

#22

Does the article seem AI-written/assisted to anyone else? Some parts that stood out to me: > A phone camera is not a single device. On Qualcomm SoCs, the capture path is a chain: > The bus register base moved from 0xa00 to 0x1800, and encapsulating that offset shift accounted for most of the work. > It gated the AHB register bus used by the whole camera complex, including the CCI. Without it, register accesses silent…

Before AI slop, I rarely saw humans make so many words bold and explicitly mention all affected filenames. On the latter point, humans try to convey the main ideas, while LLMs tend to enumerate the files they changed. Since this post has a lot of terms in bold and enumerates filenames, yes, it seems at least ai-assisted.

I've been doing it all along. Formatted texts just look well from the point of perception — same for em dashes.

Re: Fairphone 6 wide camera experimental Linux support

#24

Earlier quoted context omitted.

[flagged]

I don't have anything to do with GrapheneOS (only using it on a phone), but the security of Fairphone is not great, like many other Android phones it does not have a separate secure enclave to store secrets, but instead relies on a TrustZone-based TEE, which is often vulnerable to side-channel attacks (e.g. see the recent attack where a lot of MediaTek phones could be decrypted in seconds, even in BFU). Note: iPhone…

They're also pretty behind on major OS updates and even bug fixes last I've checked. The software story was very disappointing when I wanted to get one.

Re: Fairphone 6 wide camera experimental Linux support

#25
post #24

Earlier quoted context omitted.

I don't have anything to do with GrapheneOS (only using it on a phone), but the security of Fairphone is not great, like many other Android phones it does not have a separate secure enclave to store secrets, but instead relies on a TrustZone-based TEE, which is often vulnerable to side-channel attacks (e.g. see the recent attack where a lot of MediaTek phones could be decrypted in seconds, even in BFU). Note: iPhone…

They're also pretty behind on major OS updates and even bug fixes last I've checked. The software story was very disappointing when I wanted to get one.

How do they intend to comply with the European CRA act then?

Re: Fairphone 6 wide camera experimental Linux support

#26

Earlier quoted context omitted.

[flagged]

Different priorities. GrapheneOS prioritizes very strong security (inside a very specific model that includes treating the user as an attack vector to be protected against). Fairphone prioritizes repairable hardware (and actually makes their own hardware). On a finite budget (of both money and time and people), prioritizing either one of these will undermine the other.

[flagged]

Re: Fairphone 6 wide camera experimental Linux support

#28

Has anyone had any luck in writing drivers using LLMs? It’s one of those areas of software that is very niche and no one wants to do it. And it’s also relatively testable

Drivers live at a nasty intersection of kernel land code, hardware-coupled code, poorly documented interfaces and undocumented interactions that have to be trialed-and-errored on real HW.

Modern LLMs kick ass, but they aren't magic.

Fully vibe coding a driver for things more complex than, perhaps, a well documented CMOS sensor (that's a small part of what's covered in the article) is still a no-no.

But an LLM does wonders at emitting boilerplate, "vibe checking" your implementations, suggesting how to implement certain things, helping debug some of the things, etc. You can get the LLM to do a lot, but you still need a lot of understanding, and a lot of applied handholding.

Re: Fairphone 6 wide camera experimental Linux support

#29

Has anyone had any luck in writing drivers using LLMs? It’s one of those areas of software that is very niche and no one wants to do it. And it’s also relatively testable

Yes this was done with Opus 4.8 and it was very effective. I ran a local harness on the phone itself so it could probe around and experiment. You do have to reboot into a newly compiled kernel occasionally if a module reload is not sufficient.

Obviously this work was mainly porting downstream code and information so the scope was fairly limited but the diagnostics it could do were very impressive.

Re: Fairphone 6 wide camera experimental Linux support

#30

Earlier quoted context omitted.

Different priorities. GrapheneOS prioritizes very strong security (inside a very specific model that includes treating the user as an attack vector to be protected against). Fairphone prioritizes repairable hardware (and actually makes their own hardware). On a finite budget (of both money and time and people), prioritizing either one of these will undermine the other.

[flagged]

You can't have good privacy without good security
Post reply on HN