DisplayLink style USB display adapters may work, although if they use the Pi onboard 3D block for composition then your overall desktop is limited to 7680x7680 on Pi4 (2048x2048 on Pi3).
V4L2 decoding for H264 IS supported on the Pi4. (H264, MPEG4, H263, and MPEG2 decoding is supported on earlier Pis via V4L2). DRM and KMS are the default on Pi4, and are optional on Pi0-3. wm4 used to be quite involved in getting things working on the Pi, but now seems to be discarding it as a platf...
As that module is made by Arducam and not Raspberry Pi, please don't expect much support here. Arducam should support their own products. However I suspect that it is just that you haven't installed wiringpi which is used for the GPIO manipulation. "sudo apt install wiringpi" may resolve your issue,...
Do you have a pinout for that connector? Do you have any information on what the sensor actually is? Do you have a datasheet for that sensor, or is there a driver already in the Linux kernel? If the answer to any of those questions is no, then broadly forget about it. There is no standard connector ...
If you want to know what GPIO the LED is connected to, the official source is https://github.com/raspberrypi/firmware/blob/master/extra/dt-blob.dts and look for the CAMERA_0_LED property for your particular board variant. If it is listed as external, then it is on the GPIO expander. Internal is the ...
Thanks for the answer, will the driver be available in updates or OS will it need to be reinstalled? It'll be available via a bump to the raspberrypi-kernel package at some point in the future. It'll be based on the Linux 5.4 release rather than 4.19 though, so there's going to be a fair chunk of t...
If you're not doing anything extra in the callback, then reusing the default one won't do any harm. It only works on local data, no global data. If you want to instance specific stuff, then you can use port->userdata to allow a lookup back to a struct of your choosing which the callback can modify. ...
Provide a link to the Aliexpress page, otherwise we're having to guess. The most common OV5647 with controllable IR cut filter is the Waveshare one - https://www.waveshare.com/rpi-ir-cut-camera.htm Read the wiki for controlling the IR cut filter. You can generally control the camera LED line via sof...
If someone is looking for solutions, there is this: http://patchwork.ozlabs.org/patch/347785/ and this: https://github.com/saschahauer/barebox/blob/master/drivers/net/usb/smsc95xx.c Welcome to the forums, however please be aware that: a) This post was started 7 years ago, and the last post is from ...
If your source is insisting on producing 1080p60, then you are stuck. There is no way of getting the data into a standard Pi at that rate. (The Compute Module can if you use an Auvidea B102). Run "v4l2-ctl --log-status" and it should print out a load of status, including an entry "Lanes needed: X". ...
The first version of the patch set went out to the Linux mailing lists on Monday - https://lists.freedesktop.org/archives/dri-devel/2020-February/256515.html There are a number of rough edges still that need to be resolved, and the expected back and forth on the lists for code review (only the clock...
The main camera stack and the rawcam component use different interrupt handler implementations, and the sync pulse stuff is only in the main camera stack one. rawcam doesn't have need to use check for an LED pin as it is disjoined from the main stack, so making that link would require a bit of thoug...
X chooses display mode independent of the console for reasons best known to itself. The firmware can influence the console via the video= line in the kernel command line, but not to X without rewriting files on the ext4 partition. As andrum99 says, use the Screen Configuration Tool (arandr) to set i...
If you read the I2C spec, addresses 0x00-0x03 and 0x78-0x7f are reserved. https://www.nxp.com/docs/en/user-guide/UM10204.pdf page 70, section 3.1.12 "Reserved addresses".
0x03 is "reserved for future purposes".
I am running archlinux arm 32bit on my rpi4B and trying to launch mpv with hardware decoding in drm mode. However, no matter which settings combination I try in boot/config.txt, all I'm getting is ➜ ~ mpv --drm-mode=highest --hwdec=mmal --vo=rpi /storage/StarTrek.Picard.S01.TeamNotDead.1080p/StarTr...
5.6 is not a LTS release , therefore won't ever become a Raspbian kernel. It exists in our Linux Github tree already as rpi-5.6.y , but won't have that much testing. You can always build your own kernel from there following the provided instructions . 5.4 is an LTS kernel, and is in the process of b...
There is no wide angle official camera. Although I own officials cameras, I have to buy chinese variants because they have a lens mount with a lot of choice. There are third party wide angle variants from Pimoroni/Pi hut also. It is possible to buy an M12 plastic lens housing that can be mounted ov...
I'd be suspicious that you have a version of the sensor with no infra-red filter fitted, what is often termed the NoIR version of the sensor. All 3 colour channels on the sensor are sensitive to IR, which is why one is normally fitted. You may be able to add your own IR filter to the front, but I do...
Have you disabled vc4-fkms-v3d in config.txt? If so, why?
That would do it as then the two framebuffers become totally independent, and nothing is writing to the second one.
when i run ''i2cdetect -y 0" I got a result as this picture. I run "raspi-gpio get" and I see: I2c0 is connected to Pin 28,29 of raspi, it is corrected. I asked you to quote the output of "raspi-gpio get" for good reason. PIns 28 & 29 is INCORRECT for a Pi3. The camera connector is attached to GPIO...