I would like to incentivize timely (1-2 months max.) implementation of pmOS camera-support for SDM845 devices by offering a bounty of 6 XMR (Monero, the digital cash). The intent to win the bounty has to be discussed here beforehand.
If supporting the entire list of devices implies significantly more effort than a subset, the minimum should be OnePlus and Shift. Details from comment:
When one opens a camera application (like
millipixels), the screen should show what the camera points at and capturing color photo and video of that content should be possible. It should run in a stable manner (meaning no anticipated crashes) and the required changes should be accepted into the postmarketOSedgebranch.
If bounties happen to be against the ethos of the project, let me know.
On the contrary, I hereby invite others to chip in.
Comment if interested.
You must log in or register to comment.
In favor of supporting our currency as a medium of exchange, any bounties should be quoted in Monero rather than USD, imho.
Agreed. I updated the description accordingly.
@fullmetalScience I like the idea of bounties as a user, and can think of a few things I would be willing to chip in on… But I bet it becomes a nightmare if multiple developers helped towards a goal, and in a way that is always going to be the case. “standing on the shoulders of giants”
There are actually mentions of people having had partial success, but your point makes sense regardless. I updated the description to clarify that interested developers have to express their intent beforehand. This way it should be easier to track who actually made it happen.
Interestingly, I’m already planning to meet with one of the PmOS developers this weekend at FOSDEM to work on this. But I would probably say I’d recommend this bounty goes to either the PMOS or libcamera projects rather than myself if/when we get this completed.
Great. Maybe you can give a little heads-up after the weekend.
Quick updates here.
We managed to get the IMX519 driver probing successfully with the CCS driver (an alternative driver that should be able to run this module), but discovered that the camera is connected over C-PHY instead of D-PHY, which explains our earlier difficulties and inability to capture so far.
The good news is that, knowing that helps a long way to the next steps. The bad news is that as I understand it, C-PHY is not yet supported in the camss driver. So the next development steps are to first determine getting C-PHY support added, and then we can come back to testing and validating the IMX519. With a blocker on the C-PHY, for now I wouldn’t expect this to be achievable in the next two months.
Thank you - are you looking at adding that support to camss yourself?
Kudos on the progress!
Can you clarify - what’s the bounty for - Full hard ISP ?
If all you want is the imx519 with CAMSS/bayer on rb3, that should be easy enough todo
Refer to this and further comments for details.
Did this help? (referenced quote now added to description)
@[email protected] The complexity is that we have a couple of different versions of IMX519 driver already from the Arducam 16MP camera, as well as an expectation that as this sensor should be CCS compatible, it should run with the already upstream CCS driver.
One thing that /would/ help is if someone can find the full register programming manual for the IMX519 which we have not been able to obtain.
On SDM845 (I would guess this might indicate someone is looking at perhaps the OP6 here) there are a couple of small integration issues for the DT and regulators as well. Anyway - My hope is to work through this and get the SoftISP running on OP6 (with the IMX519) during FOSDEM.
I dont have the knowledge to make the camera work and I am also completely fine with the camera not working
