On Wed, 2017-03-15 at 22:08 -0300, Mauro Carvalho Chehab wrote: > No, I didn't. Thanks! Applied it but, unfortunately, didn't work. > Perhaps I'm missing some other patch. I'm compiling it from > the Greg's staging tree (branch staging-next): > https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging. > git/log/?h=staging-next > > Btw, as I'm running Raspbian, and didn't want to use compat32 bits, > I'm compiling the Kernel as an arm32 bits Kernel. > > I did a small trick to build the DTB on arm32: > > ln -sf ../../../arm64/boot/dts/broadcom/bcm2837-rpi-3-b.dts > arch/arm/boot/dts/bcm2837-rpi-3-b.dts > ln -sf ../../../arm64/boot/dts/broadcom/bcm2837.dtsi > arch/arm/boot/dts/bcm2837.dtsi > git checkout arch/arm/boot/dts/Makefile > sed "s,bcm2835-rpi-zero.dtb,bcm2835-rpi-zero.dtb bcm2837-rpi-3- > b.dtb," a && mv a arch/arm/boot/dts/Makefile > Two other hacks are currently needed to get the camera to work: 1. Add this to config.txt(This required to get the firmware to detect the camera) start_x=1 gpu_mem=128 2. VC4 is incompatible with the firmware at this time, so you need to presently munge the build configuration. What you do is leave simplefb in the build config(I'm assuming you already have that), but you will need to remove VC4 from the config. The firmware currently adds a node for a simplefb for debugging purposes to show the boot log. Surprisingly, this is still good enough for basic usage and testing. The only remaining issue is that since simplefb is intented for debugging, you wan't be able to use many of the RPI specific applications. I've been using cheese and ffmpeg to test the camera which are not RPI specific. _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
