On Thu, 29 Mar 2018 12:57:45 +0200, Newdo  declaimed the
following:

>
>Where can information about the complete boot process be found?
>

 Do you mean:

  between application of power and the transfer of control to Linux
kernel

or

  between the start of the kernel and the production of a login
prompt on the system console

or
  between the start of the kernel and the production of a login
prompt on a graphical environment


 For the First, you may have to pay Broadcom -- as I recall, Broadcom
provides a black-box blob to the R-Pi foundation which is loaded by the
graphics processor, and which then sets up the hardware and loads the Linux
kernel image into RAM before allowing the ARM processor to start execution.
{Many other boards use a customized version of U-Boot which runs on the
main processor and gets loaded by code in a small ROM in place of the
initial load going to the graphics processor). Don't know if searching the
ARM site would reveal generic documentation for configuring a processor
boot system (remember: ARM sells processor /designs/, it is up to the chip
designer to wrap the processor core with peripherals to provide booting
capability).

 Second and Third: Study Linux kernel configuration, device tree
definitions, and whatever run-level control scheme is in use. Debian based
OS have transitioned from Sys-V INIT to systemd (sys-V made sense to me; I
glanced at some systemd stuff and was immediately lost -- it was as cryptic
as the device tree). The main difference between 2 & 3 is that 2 stops with
processes waiting for input on text consoles, while 3 has to load an
X-Window environment and start the desktop login process waiting (if it
isn't configured to automatically login as a default user).



--
 Wulfraed                 Dennis Lee Bieber         AF6VN
 wlfraed@ix.netcom.com    HTTP://wlfraed.home.netcom.com/

--- SoupGate-Win32 v1.05