more documentation needed
Dear Zephyr community,
I very like the zephyr project but I need more documentation in order to get productive with it.
1) Concepts: For me it looks like Zephyr uses some of the Linux concepts. Several good books exists for Linux discussing the kernel, device drivers etc. Which concepts are borrowed form Linux and why? Generally, what concepts does zephyr implement? How an non Linux expert may use those concepts for building high quality embedded software?
2) Porting to custom boards: The provided documentation  is very unclear to me. In the next version of the documentation pages it will be very helpful for me to have a step-by-step tutorial where the migration to a new board is shown, new drivers are included etc.
More specific example: Currently I want to use the Ethernet peripheral of an esp32 chip (board ESP32-POE ). Should I write an network interface or device driver? How to add support for that?
3) West, Kconfig and Cmake: I want to understand how west uses the Kconfig and Cmake files to build an executable image.
On Tue, 2019-10-15 at 01:26 -0700, email@example.com
Dear Zephyr community,You need to create a device driver for this chip. By doing that, the
network interface is instantiated automatically when the device runs.
I recommend that you look how other Ethernet device drivers in
drivers/ethernet directory are implemented.
"stefan.hristozov via Lists.Zephyrproject.Org"
If you want to see what 'west build' is doing, just run it in verbose
mode with -v, like this:
$ west -v build -b reel_board samples/hello_world
This prints every cmake command line before it is run (search for
"Running CMake:" in the command output), and also enables verbose
compiler command lines.
You can also run 'west -v flash', 'west -v debug', etc. to see the
commands they run.
That should be all you want to know and more :). Please let me know if
those commands' output doesn't contain what you're looking for.