Comments
Hacker News
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 silently returned zero. > With the wrong numbering, CSIPHY programmed a lane mask with lane 0 missing, and the PHY never locked. > This was the main bug. Frames arrived at the right rate and size, and buf_done fired, but every pixel was zero. [...] The data path delivered frame timing, but not pixel data. > Changing the register value from PLAIN64 (0xa) to 0x0 turned the all-zero frames into real images: the maximum pixel value was 255, the full colour-bar pattern appeared, and the violations stopped.
Sorry if not, but it seems like so much uses AI nowadays.
Good to see this! Love Fairphone!
I wish one day I could do cool stuff like that. Kudos!
by BraveOPotato
Another dev has been hard at work bringing Fairphone 6 Linux support for calls, audio, microphone, NFC, GPS, and IMU: https://blorp.piefed.zip/inbox/u/https%3A%2F%2Fani.social%2F...
It's now probably the most modern well-supported pmOS phone.
by pizzaiolo
have fairphone looked into supporting GrapheneOS? what exactly is missing there other than "it's not Pixel"?
by NooneAtAll3
It's a pity those IMX and ISOCELL sensor chips are unobtainable from Digikey.
Anyone with experience buying them in smaller quantities?
by amelius
Join the discussion
Write your take first — we'll ask for email only when you're ready to publish.
- Hacker News
- 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 silently returned zero. > With the wrong numbering, CSIPHY programmed a lane mask with lane 0 missing, and the PHY never locked. > This was the main bug. Frames arrived at the right rate and size, and buf_done fired, but every pixel was zero. [...] The data path delivered frame timing, but not pixel data. > Changing the register value from PLAIN64 (0xa) to 0x0 turned the all-zero frames into real images: the maximum pixel value was 255, the full colour-bar pattern appeared, and the violations stopped.
Sorry if not, but it seems like so much uses AI nowadays.
- Good to see this! Love Fairphone!
- I wish one day I could do cool stuff like that. Kudos!by BraveOPotato
- Another dev has been hard at work bringing Fairphone 6 Linux support for calls, audio, microphone, NFC, GPS, and IMU: https://blorp.piefed.zip/inbox/u/https%3A%2F%2Fani.social%2F...
It's now probably the most modern well-supported pmOS phone.
by pizzaiolo - have fairphone looked into supporting GrapheneOS? what exactly is missing there other than "it's not Pixel"?by NooneAtAll3
- It's a pity those IMX and ISOCELL sensor chips are unobtainable from Digikey.
Anyone with experience buying them in smaller quantities?
by amelius