Conversation
ciopor@fosstodon.org

ciopor

Is anybody still working on getting camera to work on ?

1
0
0
cas@social.treehouse.systems

caleb 🌈

Reply to @ciopor@fosstodon.org

@ciopor I'll have another go at it eventually. more or less ran out of things to try

0
0
0
fell@ma.fellr.net

Felix Urbasik

Reply to

@ciopor @cas I think the drivers for these cameras are hundreds of thousands of lines of code that need to be ported to mainline linux to get anything out of them. And the stack of programs outside of the kernel (libcamera, pipewire) is also pretty incomplete which makes it even harder.

2
0
0
cas@social.treehouse.systems

caleb 🌈

Reply to @fell@ma.fellr.net

@fell @ciopor the camss driver is complicated sure, but not that bad :P

There's two issues

The first: for the op6 is that the communication between the main sensor and the soc happens using the C-PHY protocol on the wire. This is a much more complicated tri-state logic, rather than the relatively simple inverted pairs of the more typical (but lower bandwidth) D-PHY.

It requires a bunch of changes to the CSIPHY and CSID which aren't supported in upstream.

The SHIFT6mq has the same soc, the same sensors, but uses D-PHY mode. Everything seeems fine, it looks like data is coming in, but we never get the interrupt telling us that the buffer is full, sooo it just hangs

anyways, it's been weeks since i looked into this. just don't have the energy. The pocophone f1 and pixel 3a are looking great

0
1
1
pavel

Pavel Machek

Reply to @fell@ma.fellr.net
@fell @ciopor @cas Drivers for cameras are normally not _that_ huge. Camera chip is simple device connected over i2c... and we don't have real drivers for most of them, we have just lists "write this to this register". Yes, then there are SoC pieces and ISP chips and ... but parts can be bypassed and done in software. If you are experimenting with this, take a look at megapixels, first. It is simpler than libcamera.
0
0
0
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: