Because buying BCM2836 in the very small quantities required for Pi2 is more expensive than slightly increasing the quantity of BCM2837 and using that.Edmor wrote:I'm wondering about why Pi2 Model B V1.2 have the same CPU as Pi3 model B V1.2.
Sure. Add "arm_freq=900" to config.txt and your Pi will run cooler and slower.i486 wrote:Can I slow down the clock of Pi3 to 900Mhz and avoid overheat problem?
That won't make any difference for video playback in chromium.cjan wrote:in my case Rpi2, kodi need gpu_mem=160 to play hd-dvb youtube 720p-video and better mouse moving...etc.
hello_video_simple is a working version of what you are describing. Might be worth a look.sbakke wrote: Tried creating a pipeline with just decoder and render (removed scheduler and clock) but nothing is ever displayed. Is there more we need to do?
Yes, the config.txt overscan settings are not compatible with arm side vc4 driver and should be disabled.hanzelpeter wrote:So I looks like I need to remove overscan. Is it the culprit of a problem?
Yes, works for me on Pi3.mcduman wrote:anybody tried this with the rpi3? I cannot get it to work.
Code: Select all
tar xf llctl.tgz make sudo ./llctl f0 l0 d0
Increasing GPU memory (e.g. through raspi-config) does help fullscreen video decode in Chromium a little. 80M should be enough.treeHouse wrote:I have 2 rp3's, one on a 720p tv and the other on a 1080p.
The latest chromium does full screen youtube very well on the 720, but choppily on the 1080.
Did you you read the linked post? It describes the differences.ric96 wrote:So needed some clearance with the difference between the kms and fkms dtoverlay, and is it related to full kms and fake kms option recently introduced in the raspi-config?