Thank you for your prompt response.
You are very welcome.
I believed that U-boot and kernel sources should be available because on related guideline
For our Linux image starting from V2.0 we use OpenEmbedded core. Layers from git.toradex.com are used together with a number of other layers.
oe-core installation and configuration (and the later build) will setup the following directory structure
oe-core/ ±- build ¦ ±- conf ¦ ±- downloads ¦ ±- tmp-glibc ¦ ±- sstate-cache ±- deploy ±- layers ±- meta-angstrom ±- meta-browser (… other layers) ±- openembedded-core
… under the ‘build’ tree is the configuration of what is to be built, the downloaded sources …
No, not really. OE is a build system based on recipes. Each and every one of them downloads stuff, does it’s thing (e.g. configure/compile whatever) and then removes it again unless rm_work is removed from your local.conf.
Moreover as the update.sh utility actually can update u-boot and kernel as well on EVM, I took for granted that u-boot and kernel sources should be available, in order to patch them for our custom board and update them again…
No, update.sh just installs whatever is already available built as binary, no sources involved at all.
Anyway from your argumentation I understand that Qt support on EVM is confined to user space,
No, any Qt support is purely user space and has nothing directly to do with any boot loader and/or kernel.
than to Root File System only…Have I to use the Root File System I find say in Colibri-T20_LXDE-Image_2.8.1/rootfs ?
Sorry, but I really do NOT understand at all what exactly it is that you are trying to achieve but I doubt your current understanding of how things work in OE is quite accurate. What exactly is it that you want to do with those sources and why exactly can’t you just take those from where I already pointed you to before?