Lines Matching refs:model

13 Transition to the current hardware model
16 Shortly after Zephyr 3.6.0 was released, a new hardware model was introduced to
17 Zephyr. This new model overhauls the way both SoCs and boards are named and
29 All the documentation in this page refers to the current hardware model. Please
31 previous, now obsolete, hardware model.
34 model can be found in the :github:`original issue <51831>`, the
36 introduced, the `hardware model v2 commit`_.
39 model are still in development. Check the
40 :github:`hardware model v2 enhancements issue <69546>` for a complete list.
42 The transition from the previous hardware model to the current one (commonly
43 referred to as "hardware model v2") requires modifications to all existing board
45 compatibility for the previous model, which leaves users transitioning from a
46 previous version of Zephyr to one including the new model (v3.7.0 and onwards)
49 #. Convert the out-of-tree board to the current hardware model (recommended)
53    defined in the previous hardware model, to continue to work
55 When converting your board from the previous to the current hardware model, we
56 recommend first reading through this page to understand the model in detail. You
60 entirely). Finally, the `hardware model v2 commit`_ contains the full conversion
61 of all existing boards from the old to the current model, so you can use it as a
64 .. _hardware model v2 commit: https://github.com/zephyrproject-rtos/zephyr/commit/8dc3f856229ce083c…  argument
383            model = "A human readable name";
927 The board hardware model in Zephyr allows you to extend an existing board with
974 Board extensions (Old hardware model)
980   format. For boards described in new hardware model format, use the extension