No worries. I only tested it on arm7 and amd64. but the patch should not break the code for already supported targets.
It is on my list of things to do, but one thing that needs checking is if the patch introduces old frames (i.e. frame from n-1 shot, where n is the current shot number) being served. If that is the case, we need to also retrieve the frame when calling SVB_EXPOSURE.
Do you know if KStars/Ekos supports showing live video from the SV305?
I tried both the remote version running on my RPi and the Windows version connected to the INDI Web Manager also running on the RPi.
All I got was a black screen.
I confirmed the camera is still working with SharpCap on Windows.
I get some "chess board effects" in B&W, due to the bayer matrix, but if you toggle the "bayer" button, it works well.
(no resize, ROI or binning, just basic streaming)
Do you get a black screen ?
The default exposure time in liveview is very short. Streamed frames are very dark.
I just tried another test and I'm getting some light now. I don't know why I was getting black the other day. This test was outside light hitting the CCD (or CMOS) directly, with my hand partially blocking the chip.
Exposure time is the default, whatever that is.
Uncovered is light grey (2nd attachment) which I guess is normal.
I'm using AstroDMx for the time-being until I've got this figured out.
updated via your comment but was still unable to get driver(s) working.
Then I tried another poster's suggestion of changing names of drivers in various locations and then performing same update you posted, still not working (and now the manually built/installed driver versions are unavailable as a choice in indi).
The error I get when trying to start the "SVBONY" driver (only one avail for profile) is: 2020-09-21T22:21:45: [ERROR] Error: unable to open device. Cannot identify /dev/video0: 2, No such file or directory
Should I consider just a fresh Astroberry install and then start over with adding the indi library and functionality? If so, is there a comprehensive guide for that (current build is base AB then added indi lib then built drivers for svbony sv305)? Thanks
I've already tried the sudo install (i mention this in the post you replied to) , this resulted in the error mentioned in same post.
I also have ADMx installed, still getting the error above. Before that, I'd built the drivers using instructions here, and those were giving errors as well.