Lines Matching refs:mapping
90 [mapping:my_component]
105 [mapping:my_component]
126 [mapping:my_component]
135 [mapping:my_component]
147 [mapping:my_component]
159 [mapping:my_component]
178 [mapping:my_component]
219 …ctions-fragment>`, :ref:`scheme<ldgen-scheme-fragment>` and :ref:`mapping<ldgen-mapping-fragment>`.
236 - type: Corresponds to the fragment type, can either be ``sections``, ``scheme`` or ``mapping``.
313 - mapping fragments now requires a name like other fragment types
315 …v3.x version of this document). Backward compatibility with the previous mapping fragment grammar …
396 .. _ldgen-mapping-fragment :
404 [mapping:name]
449 [mapping:map]
464 … or both are specified) the input section description generated from the mapping fragment entry. I…
502 Putting it all together, the following mapping fragment, for example,
506 [mapping:name]
521 …n the flag descriptions, are order sensitive. Therefore, if for the same mapping fragment these tw…
540 …ame}``, ``.rodata.{var_name}`` or ``.bss.{var_name}``; and so ``Type I`` mapping entry works for t…
554 mapping[target]
568 mapping[iram0_text]
593 [mapping:freertos]
616 …Rule generated from the entry ``* (noflash)`` of the ``freertos`` mapping fragment. All ``text`` s…