Hi Nino,
Am 07.10.2017 um 08:49 schrieb Nino Bock askarus@openpandora.org:
Hi Nikolaus,
You should see the dts folder like here:
http://git.goldelico.com/?p=gta04-kernel.git;a=tree;f=arch/arm/boot/dts;h=0b...
Yes, I did. I do have the dts folder. Simply when doing the make command the dtb files are not stored in a seperate directory but in the same folder as the dts and dtsi files.
Yes, that is normal. Like .o files are in the same folder as the .c files.
However I can find some dtb files in the /arch/arm/boot/dts folder. Putting them simply into the boot folder and reboot doesn't work. What else do I have to do? Do I need to recompile the whole Kernel?
No, only the dtb files.
All of them or only the omap-whatever-pyra ones?
It should suffice to copy the omap*.dtb but itdoes not harm to copy all of them. U-Boo chooses one of them.
I've tried all of them as well as only the pyra ones and don't get any results.
At least the brightness steps are the same when increasing brightness by 1.
Hm. Then let's do a test: * make a backup of the arch/arm/boot/dts directory * modify the steps * make dtbs * diff the dts directory with the backup directory - then you will know that the compilation does a change (and to which files)
The next thing is to check the boot log from U-Boot. It tells which .dtb file is loaded. Then you can check if it is the one that you have really changed.
Next you can play to modify the "model" entry in the device tree source and check with cat /proc/device-tree/model if it is really modified when the Pyra has booted.
Another idea: install the fdttools package. There is fdtdump to inspect .dtb files.
Hope this helps, Nikolaus