Conversation

Holy hell, they’re really using PCIe in the mobile devices pcisig.com/sites/default/

Quote Tweet

battery failure. battery failure would cause the cursed device to fail DDR training and lose the PCIe link with the camera. replacing the battery immediately fixed all of the issues. sigh

Show this thread

Replying to

they've been using PCIe to connect to the baseband for a while, it's better than USB! PCIe for -cameras- is new, though not surprising

Muzaffer Kal @

Replying to

and

Where do you see that?

Replying to

and

Pixel 3. it calls the camera "Easel" and the binary runs code paths that log strings with "easel_comm_pcie.cc" in the filename

Replying to

and

It's an Intel ARM SoC with an ASIC for very parallelized HDR+ image processing. Runs Linux uploaded to it on boot and will accept anything: twitter.com/kdrag0n/status Was replaced by a Samsung chip including generic AOSP Neural Networks API on Pixel 4. 4a and beyond dropped it.

Quote Tweet

Danny Lin

@kdrag0n

Jul 9, 2020

Mainline Linux v5.8-rc4 kernel running on a Pixel Visual Core image coprocessor, built with Clang 11 + LTO + CFI + SCS for kicks. It runs Linux, so why not put it to good use? github.com/kdrag0n/mainli

Show this thread

Replying to

PVC on Pixel 2 / 3 and PNC on Pixel 4 were primarily used to implement HDR+ for apps other than Google Camera. Google Camera mostly continued using Snapdragon DSP and software. They ended up simply using Snapdragon capabilities with no loss for the Pixel 4a and 5th gen devices.

Replying to

PVC had high latency and CameraX disables HDR+ on the Pixel 2 and 3 in the default latency mode. It might have been better for the OS to use the DSP like Google Camera... PNC was far better but quickly obsoleted by the SoC. Possible they used what they learned from it for Tensor.

5:45 AM · Apr 4, 2022Twitter Web App