Most of those 'high MP' cameras are also not really useful anymore without an ISP and those aren't available open-source (except perhaps with camera emulation and a fake CSI interface to the application processor cores).
But to clarify: it's not really as much about "any ISP" as it is about a good ISP that can do multi-camera composition. The ISP in the RockChip SoC can't even do one, it mostly just does basic cropping/rotation/resizing and controls the PHY. While technically an ISP, it's more like an interface driver at this stage. The driver is open source, but the hardware isn't. That's not always a bad thing, as in this case the hardware doesn't run on any RT blob, it's mostly just a bunch of registers for (image) stream processing.
I think in the android rom hacking world, most ISPs are used with their binary blobs (both firmware and kernel modules) but without the configuration and user land blobs, resulting in working cameras (at high pixel counts) but really bad image quality.
It's still a bit basic, I'd like more, but there much more color and image correction controls than you're acknowledging https://www.kernel.org/doc/html/latest/userspace-api/media/v...
There's also no firmware. It can be used as is without one.
Lack of documentation is also not a huge issue, since rockchip manuals for all/most parameters of the ISP are findable on the net.
What's missing are calibration tools. But those can be re-created from scratch. It's not terribly difficult.
Just saying that there are FOSS supported ISPs available. RKISP10 is fully supported in mainline Linux. You can just use it via v4l2.
It does indeed not need firmware, but higher end IPS blocks often do, especially when you get much higher bandwidth sensors per CSI channel.
What I am wondering now about those calibration tools is if however they are built or reverse-engineered, they could read the pre-existing calibration payload.
Preexisting calibration data are just XML files with params to load to the ISP and params to use to determine which set of params to load based on statistics collected from ISP (like after detecting what kind of light the scene has, you have to load params calibrated for that light type).
(I do rotation via RGA, so maybe you mean that? That's a separate HW block, not part of ISP.)
Pine64 doesn't make any of those components. High end components are also generally from manufacturers that don't share documentation, so entirely useless for Pine64's goals.
edit: wow, did not realise how far phone cameras had come!
The upcoming Moto X30 Pro has a 200 MP camera in it.
edit: these are all rear cameras
[1]: https://www.smartprix.com/bytes/best-108mp-camera-phones/
Motorola Moto X30 Pro is 200 mp.
Could you explain to me why I'm unhinged? I didn't feel like I had posted anything controversial or whatever.
I believe I understand why you feel I am unhinged.
I said, "Sure sounds like iphone will get there first, pine could beat them to it."
Obviously I said iphone will win, I optimistically or enthusiastically said pine could put in the work and get there first.
You feel I am unhinged because of optimism?
For me. My love for webOS is so great it’s all I want
I feel like I wasn't being unrealistic at all.
solid state batteries exist today and can be bought. Obviously early in the commercialization but they do exist. Still unclear how safe they are.
88mp camera is less than what I can go buy from costco right now.
3d scanners totally fit in your pocket. I don't mean photogrammetry neither. The newer iphones have lidar that can scan. Newer androids have depth sensors or TOF sensors.
13MP camera is nice. Specs are certainly much improved. Probably enough for daily driver.
My next phone though:
Next battery tech, solid state?
88mp front cam as this is the threshold for beating film.
depth cam that can 3d scan things for me.
Sure sounds like iphone will get there first, pine could beat them to it.