-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IPU3 pipeline handler supports only 2 cameras #21
Comments
To see this limitation in the code base, see lines: |
I tried your quick-fix at linux-surface/linux-surface#91 (comment). I can see all three cameras in the selection menu now, but I unfortunately get a segfault as soon as I select one of the cams at index 1 or 2. Index 0 works as before. Here's the relevant section in the kernel log, if it's of any help:
|
Can you run the test under gdb to get a backtrace perhaps please? It's most likely simply that the imgu object doesn't like being shared yet. Unfortunately we won't be able to look at this anytime soon at the moment. Our goals on surface are focused on getting the algorithms working to fix the colours, but we will only focus that attention on a single camera for now. |
Sure, I'll try to find some time for that this evening.
No worries, I agree that getting a single camera to work has precedence. |
Alright, here's a backtrace: gdb.log |
The IPU3 Pipeline handler only supports 2 cameras.
This is due to the only being 2 imgu (ISP) units, even though there are 4 CIO2 receivers.
The current implementation solves this simply by assigning a single cio2 to a single imgu and ignoring any further sensors found.
To support more than 2 cameras an implementation to share the imgu will be needed.
The text was updated successfully, but these errors were encountered: