Buildroot update / Raspberry Pi 2 Support #197
Conversation
dgsiegel
force-pushed
the
buildroot-update
branch
2 times, most recently
from
8700d0d
to
76860bb
Compare
|
Not fully sure what's going on with the version issue on the libcamera patch, but if that works that's enough for now. The version probably only affects the 'string' that reports the version compiled. A nice to have but not essential. What effect does all of this update have on the /boot/config.txt ? Does it automatically enable the libcamera stack? or is the legacy enabled by default in this buildroot? |
|
I also see updates to the kernel configs. Are there any changes there that could affect how ConfigFS is configured or enabled? |
dgsiegel
force-pushed
the
buildroot-update
branch
from
ee285a9
to
3bbc246
Compare
Only enable uncompressed or mjpeg headers if they are defined. Signed-off-by: Kieran Bingham <kieran.bingham@ideasonboard.com>
Ensure that udev has settled before we query if /dev/video0 exists. Signed-off-by: Kieran Bingham <kieran.bingham@ideasonboard.com>
From what I could figure out was that the GnuTLS signature path is broken and you need both GnuTLS and libcrypto/openssl to allow libcamera to check and validate IPA signatures.
|
So contrary to what I thought last time - there is access to the hardware jpeg encoder, through the V4L2 M2M device node. (/dev/video31 by default by the looks of it - but we shouldn't rely on that number). Support for this should be added to either libcamera or uvc-gadget ... and then I hope/expect we'll get back to the existing performance capabilities!. If anyone has the ability to help work on this let me know - otherwise I'll see if we can look at it when we have some downtime. |
|
Will this also support the new camera module 3? |
No description provided.