Graphic design of the ARM Linux kernel

I am exploring the Linux kernel landscape for developing ARM-based SoCs.
This is a very early stage of learning and will certainly take a long time, as the questions seem to be comprehensive.
The goal is to have a good orientation in the ecosystem, therefore, as soon as specific problems in your own project have to be resolved, you can direct the search / investigation to the appropriate routes.

There is a Linus tree, the core of vanilla. As for the ARM platform, there is also an ARI port tee / project / repository. If, however, you look at the MAINTAINER file, there are several support / subsystems, apparently for specific ARM-specific topics.
I wonder why all those topics with a narrow spectrum do not deliver / add to the ARM port ( http://www.arm.linux.org.uk/) instead of directly sending it to the Torvalds tree? It seems that the ARM SUB-ARCHITECTURES subsystem also exists. Some subsystems / accompanying devices with a narrow spectrum, apparently, are intended for transfer to a specific platform, which is based on the name of the found subsystem / maintainer. Why are they centralized in / contribute to the Linus tree directly instead of doing it in the ARM SUB-ARCHITECTURES subsystem or, as mentioned above?

The organization is somehow mysterious, transparent for beginners.

+4
source share

Source: https://habr.com/ru/post/1619509/


All Articles