Edited by ChrisP at Fri Oct 16, 2015 13:04 |
Ok, I'll try to rephrase my understanding of the basis, just to be sure not to misunderstand and it could be useful for other people too ^^
I still have to read deeply the provided documentation, had only a first quick reading.
U-boot isthe boot-loader, his job is to initialize everything that is needed in order to properly launch the kernel.
DeviceTree is a way to have hardware settings outside of uboot and kernel, giving abstraction layer. If you need to address hardware variation of the same board,editing the dts file and compiling it to the binary dtb should be sufficient,as soon as no additional driver is needed. Right ?
U-boot have his own set of driver and should have as minimum what is needed to launch the kernel (typically storage drivers, network, text interface to be able to have external interaction , like serial console for example).
Kernel have every driver of hardware components of the device, which can be included inside the kernel itself or loaded as external modules, and optionally additional system services. Kernel have his own dts, which can be different ofthe u-boot dts.
I presume kernel and uboot dts does not necessary have exactly same content, but that's a good practice to avoid additionnal issue. Am I right here again ?
However,what I don't get yet, is how I make the put together the device config definedin dts file and the driver files that are supposed to use it ?
The hdmi settings isdefined by:
How to identify thedriver source that must use these settings ?
Interesting discussion ^^