| /openbmc/openbmc/poky/documentation/ref-manual/ |
| H A D | varlocality.rst | 28 - :term:`DISTRO`
30 - :term:`DISTRO_NAME`
32 - :term:`DISTRO_VERSION`
34 - :term:`MAINTAINER`
36 - :term:`PACKAGE_CLASSES`
38 - :term:`TARGET_OS`
40 - :term:`TARGET_FPU`
42 - :term:`TCMODE`
44 - :term:`TCLIBC`
53 - :term:`TARGET_ARCH`
[all …]
|
| H A D | variables.rst | 10 :term:`A <ABIEXTENSION>` :term:`B` :term:`C <CACHE>`
11 :term:`D` :term:`E <EFI_PROVIDER>` :term:`F <FAKEROOT>`
12 :term:`G <GCCPIE>` :term:`H <HGDIR>` :term:`I <ICECC_CLASS_DISABLE>`
13 :term:`K <KARCH>` :term:`L <LABELS>` :term:`M <MACHINE>`
14 :term:`N <NATIVELSBSTRING>` :term:`O <OBJCOPY>` :term:`P`
15 :term:`Q <QA_EMPTY_DIRS>` :term:`R <RANLIB>` :term:`S` :term:`T`
16 :term:`U <UBOOT_BINARY>` :term:`V <VIRTUAL-RUNTIME>`
17 :term:`W <WARN_QA>` :term:`X <XSERVER>` :term:`Z <ZSTD_THREADS>`
22 :term:`ABIEXTENSION`
32 :term:`ALLOW_EMPTY`
[all …]
|
| H A D | terms.rst | 13 :term:`Append Files`
52 :term:`BitBake`
57 :term:`Board Support Package (BSP)`
62 :term:`Build Directory`
63 This term refers to the area used by the OpenEmbedded build system for
67 :term:`TOPDIR` variable points to the :term:`Build Directory`.
69 You have a lot of flexibility when creating the :term:`Build Directory`.
71 examples assume your :term:`Source Directory` is named ``poky``:
73 - Create the :term:`Build Directory` inside your Source Directory and let
74 the name of the :term:`Build Directory` default to ``build``:
[all …]
|
| H A D | classes.rst | 14 Any :term:`Metadata` usually found in a recipe can also be
17 beneath the ``meta*/`` directory found in the :term:`Source Directory`:
25 :term:`BUILDDIR` (e.g. ``build/``) in the same way as
27 in :term:`BBPATH` using the same method by which ``.conf``
50 :term:`RDEPENDS` and
51 :term:`TUNE_PKGARCH` variables, should never be
59 different :term:`MACHINE` is built even when the recipe never changes.
79 the :term:`ARCHIVER_MODE` variable for information
105 the same as the :ref:`ref-classes-autotools` class but builds with :term:`B`
106 == :term:`S`. This method is useful when out-of-tree build
[all …]
|
| /openbmc/phosphor-webui/app/common/directives/ |
| H A D | vt100plus.js | 51 function customVT100PlusKey(ev, term) { argument
62 term.handler(EscapeSequences.C0.BS); // Backspace
64 term.handler(EscapeSequences.C0.DEL); // Delete
68 term.handler(EscapeSequences.C0.ESC + '?');
71 term.handler(EscapeSequences.C0.ESC + '/');
74 term.handler(EscapeSequences.C0.ESC + 'k');
77 term.handler(EscapeSequences.C0.ESC + 'h');
80 term.handler(EscapeSequences.C0.ESC + '+');
83 term.handler(EscapeSequences.C0.ESC + '-');
86 term.handler(EscapeSequences.C0.ESC + '1');
[all …]
|
| H A D | serial-console.js | 17 function measureChar(term) { argument
25 fontFamily = term.getOption('fontFamily');
26 fontSize = term.getOption('fontSize');
143 var term = new Terminal();
150 term.open(terminal);
151 term.fit();
153 term.attachCustomKeyEventHandler(customKeyHandlers); field in AnonymousFunctiond2c7d9910300.AnonymousClassd2c7d9910501
160 term.setOption('theme', SOL_THEME);
166 term.attach(ws);
183 term.fit();
[all …]
|
| /openbmc/linux/tools/perf/util/ |
| H A D | parse-events.c | 158 struct parse_events_term *term; in get_config_str() local
163 list_for_each_entry(term, head_terms, list) in get_config_str()
164 if (term->type_term == type_term) in get_config_str()
165 return term->val.str; in get_config_str()
193 struct parse_events_term *term; in fix_raw() local
195 list_for_each_entry(term, config_terms, list) { in fix_raw()
198 if (term->type_term != PARSE_EVENTS__TERM_TYPE_RAW) in fix_raw()
201 if (perf_pmu__have_event(pmu, term->val.str)) { in fix_raw()
202 zfree(&term->config); in fix_raw()
203 term->config = term->val.str; in fix_raw()
[all …]
|
| H A D | parse-events.y | 84 %type <term> event_term
85 %destructor { parse_events_term__delete ($$); } <term>
117 struct parse_events_term *term; member
659 struct parse_events_term *term = $3; variable
662 parse_events_term__delete(term);
665 list_add_tail(&term->list, head);
672 struct parse_events_term *term = $1; variable
677 list_add_tail(&term->list, head);
686 struct parse_events_term *term; variable
687 int err = parse_events_term__str(&term, PARSE_EVENTS__TERM_TYPE_RAW,
[all …]
|
| H A D | parse-events.l | 119 static int term(yyscan_t scanner, enum parse_events__term_type type) in term() function
228 config { return term(yyscanner, PARSE_EVENTS__TERM_TYPE_CONFIG); }
229 config1 { return term(yyscanner, PARSE_EVENTS__TERM_TYPE_CONFIG1); }
230 config2 { return term(yyscanner, PARSE_EVENTS__TERM_TYPE_CONFIG2); }
231 config3 { return term(yyscanner, PARSE_EVENTS__TERM_TYPE_CONFIG3); }
232 name { return term(yyscanner, PARSE_EVENTS__TERM_TYPE_NAME); }
233 period { return term(yyscanner, PARSE_EVENTS__TERM_TYPE_SAMPLE_PERIOD); }
234 freq { return term(yyscanner, PARSE_EVENTS__TERM_TYPE_SAMPLE_FREQ); }
235 branch_type { return term(yyscanner, PARSE_EVENTS__TERM_TYPE_BRANCH_SAMPLE_TYPE); }
236 time { return term(yyscanner, PARSE_EVENTS__TERM_TYPE_TIME); }
[all …]
|
| /openbmc/openbmc/poky/bitbake/doc/bitbake-user-manual/ |
| H A D | bitbake-user-manual-ref-variables-context.rst | 22 - System resources, like disk space to be used (:term:`BB_DISKMON_DIRS`),
23 or the number of tasks to be run in parallel by BitBake (:term:`BB_NUMBER_THREADS`).
25 - How the fetchers shall behave, e.g., :term:`BB_FETCH_PREMIRRORONLY` is used
27 :term:`PREMIRRORS` for files.
36 - Like :term:`B` or :term:`T`, that are used to specify directories used by
38 specified in ``bitbake.conf``. Some, like :term:`B`, are quite often
46 data reuse between build runs like :term:`CACHE`, :term:`DL_DIR` or
47 :term:`PERSISTENT_DIR`. Those are usually global.
57 - :term:`LAYERDEPENDS` is used to configure on which layers a given layer
60 - The configured layers are contained in :term:`BBLAYERS` and files in
[all …]
|
| H A D | bitbake-user-manual-ref-variables.rst | 29 :term:`ASSUME_PROVIDED`
30 Lists recipe names (:term:`PN` values) BitBake does not
34 In OpenEmbedded-Core, :term:`ASSUME_PROVIDED` mostly specifies native
39 :term:`AZ_SAS`
51 :term:`B`
55 :term:`BB_ALLOWED_NETWORKS`
61 :term:`BB_NO_NETWORK` is either not set or
86 Using :term:`BB_ALLOWED_NETWORKS` in conjunction with
87 :term:`PREMIRRORS` is very useful. Adding the
88 host you want to use to :term:`PREMIRRORS` results in the source code
[all …]
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | temporary-source-code.rst | 11 :term:`Build Directory`, and then you can force a re-compile and quickly
16 build packages is available in the :term:`Build Directory` as defined by the
17 :term:`S` variable. Below is the default value for the :term:`S` variable as
19 :term:`Source Directory`::
24 :term:`S` variable. For example, recipes that fetch their source from Git
25 usually set :term:`S` to ``${WORKDIR}/git``.
29 The :term:`BP` represents the base recipe name, which consists of the name
36 (:term:`WORKDIR`) is defined as
43 - :term:`TMPDIR`: The top-level build
46 - :term:`MULTIMACH_TARGET_SYS`:
[all …]
|
| H A D | sbom.rst | 16 (:term:`SBOM`), using the :term:`SPDX` standard.
20 :term:`SBOM` tooling is often used to ensure open source license compliance by
24 :term:`SBOM` information is also critical to performing vulnerability exposure
35 - :term:`SPDX` output in JSON format as an ``IMAGE-MACHINE.spdx.json`` file in
36 ``tmp/deploy/images/MACHINE/`` inside the :term:`Build Directory`.
39 containing an index of JSON :term:`SPDX` files for individual recipes.
45 more information in the output :term:`SPDX` data:
47 - Make the json files more human readable by setting (:term:`SPDX_PRETTY`).
50 setting (:term:`SPDX_ARCHIVE_PACKAGED`).
53 packages (:term:`SPDX_INCLUDE_SOURCES`)
[all …]
|
| /openbmc/openbmc/poky/documentation/migration-guides/ |
| H A D | migration-5.1.rst | 14 :term:`WORKDIR` changes
20 If a recipe has :term:`S` set to be :term:`WORKDIR`, this is no longer
26 Any :term:`WORKDIR` references where files from :term:`SRC_URI` are referenced
27 should be changed to :term:`S`. These are commonly in :ref:`ref-tasks-compile`,
28 :ref:`ref-tasks-compile`, :ref:`ref-tasks-install` and :term:`LIC_FILES_CHKSUM`.
30 :term:`WORKDIR` references in recipes
33 :term:`WORKDIR` references in other recipes need auditing. If they reference
34 files from :term:`SRC_URI`, they likely need changing to :term:`UNPACKDIR`.
39 References to ``../`` in :term:`LIC_FILES_CHKSUM` or elsewhere may need changing
40 to :term:`UNPACKDIR`. References to :term:`WORKDIR` in ``sed`` commands are
[all …]
|
| H A D | migration-1.4.rst | 23 :term:`RDEPENDS`,
24 :term:`RRECOMMENDS`,
25 :term:`RSUGGESTS`,
26 :term:`RPROVIDES`,
27 :term:`RCONFLICTS`,
28 :term:`RREPLACES`, :term:`FILES`,
29 :term:`ALLOW_EMPTY`, and the pre, post, install,
33 instead of :term:`RDEPENDS`. BitBake uses more strict checks when it
55 :term:`SRC_URI`, the build system now uses
56 :term:`FILESOVERRIDES` instead of
[all …]
|
| H A D | migration-4.0.rst | 28 - ``BB_ENV_WHITELIST`` became :term:`BB_ENV_PASSTHROUGH`
29 - ``BB_ENV_EXTRAWHITE`` became :term:`BB_ENV_PASSTHROUGH_ADDITIONS`
30 - ``BB_HASHBASE_WHITELIST`` became :term:`BB_BASEHASH_IGNORE_VARS`
31 - ``BB_HASHCONFIG_WHITELIST`` became :term:`BB_HASHCONFIG_IGNORE_VARS`
34 - ``CVE_CHECK_PN_WHITELIST`` became :term:`CVE_CHECK_SKIP_RECIPE`
35 - ``CVE_CHECK_WHITELIST`` became :term:`CVE_CHECK_IGNORE`
36 - ``ICECC_USER_CLASS_BL`` became :term:`ICECC_CLASS_DISABLE`
37 - ``ICECC_SYSTEM_CLASS_BL`` became :term:`ICECC_CLASS_DISABLE`
38 - ``ICECC_USER_PACKAGE_WL`` became :term:`ICECC_RECIPE_ENABLE`
39 - ``ICECC_USER_PACKAGE_BL`` became :term:`ICECC_RECIPE_DISABLE`
[all …]
|
| H A D | migration-4.1.rst | 19 be installed on the build host. A new :term:`buildtools-make` tarball has been
22 :term:`buildtools` tarball. For more information see
32 building an SDK, or if you have added ``dev-deps`` to :term:`IMAGE_FEATURES`),
33 recommends (as defined by :term:`RRECOMMENDS`) are no longer installed.
37 you can explicitly install items by adding them to :term:`IMAGE_INSTALL` in
38 image recipes or :term:`TOOLCHAIN_TARGET_TASK` for the SDK.
46 The default for ``${PN}-dev`` package is now to use :term:`RRECOMMENDS` instead
47 of :term:`RDEPENDS` to pull in the main package. This takes advantage of a
48 change to complimentary package installation to not follow :term:`RRECOMMENDS`
68 A. Use ``dropbear`` in :term:`IMAGE_INSTALL` instead of
[all …]
|
| H A D | migration-4.3.rst | 17 The :term:`OLDEST_KERNEL` setting has been changed to "5.15" in this release, meaning that
35 :term:`FILE_LAYERNAME` variable and the ``layer-<layername> override``. This is being used
114 - :term:`CVE_CHECK_IGNORE`: use :term:`CVE_STATUS` instead.
128 consoles listed in :term:`SERIAL_CONSOLES` are checked for their existence
138 - ``apmd``: obsolete (``apm`` in :term:`MACHINE_FEATURES` also removed).
165 - :term:`IMAGE_NAME` and :term:`IMAGE_LINK_NAME` now include the
166 :term:`IMAGE_NAME_SUFFIX` value directly. In practical terms, this means
169 :term:`IMAGE_NAME_SUFFIX` to "" and this will now be consistently respected
176 - :term:`SDK_NAME` now includes the values of :term:`IMAGE_BASENAME` and
177 :term:`MACHINE` so that they are unique when building SDKs for different
[all …]
|
| H A D | migration-1.5.rst | 69 - ``${``\ :term:`P`\ ``}`` and
70 ``${``\ :term:`PF`\ ``}`` are no longer added to
71 :term:`PROVIDES` by default in ``bitbake.conf``.
72 These version-specific :term:`PROVIDES` items were seldom used.
84 - If you have customized :term:`ERROR_QA` or
85 :term:`WARN_QA` values in your configuration, check
88 item not mentioned in :term:`ERROR_QA` or :term:`WARN_QA` would be treated as
90 the default value of :term:`WARN_QA`. All of the possible QA checks are
100 Thus, if you have customized your :term:`ERROR_QA` or :term:`WARN_QA` values
114 and tuning architecture through the :term:`SDK_NAME`
[all …]
|
| /openbmc/u-boot/tools/buildman/ |
| H A D | board.py | 217 for term in word.split('&'):
218 if term:
219 sym_build.append(term)
223 term = None
229 term.AddExpr(sym)
232 if term:
233 terms.append(term)
234 term = Term()
235 term.AddExpr(sym)
236 if term:
[all …]
|
| /openbmc/linux/Documentation/userspace-api/media/ |
| H A D | glossary.rst | 17 A :term:`Device Driver` that implements the main logic to talk with
39 An API designed to control a subset of the :term:`Media Hardware`
47 A specialized :term:`Microprocessor`, with its architecture
53 An :term:`IC` circuit designed to be configured by a customer or
59 A subset of the :term:`Media Hardware`. For example an :term:`I²C` or
60 :term:`SPI` device, or an :term:`IP Block` inside an
61 :term:`SoC` or :term:`FPGA`.
64 A group of :term:`hardware components <Hardware Component>` that
66 instance, the :term:`SoC` :term:`ISP` :term:`IP Block`
70 Also known as :term:`Peripheral`.
[all …]
|
| /openbmc/openbmc/poky/documentation/contributor-guide/ |
| H A D | recipe-style-guide.rst | 16 and the recipe would set :term:`PV`.
22 or in BitBake variable terms ${:term:`PE`}:${:term:`PV`}-${:term:`PR`}. We
26 In most cases the version :term:`PV` will be set automatically from the recipe
38 may be found where :term:`PV` is set as a combination of the prior version
49 version of software (e.g. is not a tagged version), the :term:`PV` variable
50 should include the sign ``+``, so :term:`bitbake` automatically includes package
58 also useful when using :term:`AUTOREV` to set the recipe to increment source
64 The :term:`PR` variable is used to indicate different revisions of a recipe
70 When :term:`PV` increases, any existing :term:`PR` value can and should be
73 If :term:`PV` changes in such a way that it does not increase with respect to
[all …]
|
| /openbmc/linux/lib/ |
| H A D | polynomial.c | 81 const struct polynomial_term *term = poly->terms; in polynomial_calc() local
97 tmp = term->coef; in polynomial_calc()
98 for (deg = 0; deg < term->deg; ++deg) in polynomial_calc()
99 tmp = mult_frac(tmp, data, term->divider); in polynomial_calc()
100 ret += tmp / term->divider_leftover; in polynomial_calc()
101 } while ((term++)->deg); in polynomial_calc()
|
| /openbmc/linux/drivers/infiniband/sw/siw/ |
| H A D | iwarp.h | 216 static inline u8 __rdmap_term_layer(struct iwarp_terminate *term) in __rdmap_term_layer() argument
218 return term->layer; in __rdmap_term_layer()
221 static inline void __rdmap_term_set_layer(struct iwarp_terminate *term, in __rdmap_term_set_layer() argument
224 term->layer = layer & 0xf; in __rdmap_term_set_layer()
227 static inline u8 __rdmap_term_etype(struct iwarp_terminate *term) in __rdmap_term_etype() argument
229 return term->etype; in __rdmap_term_etype()
232 static inline void __rdmap_term_set_etype(struct iwarp_terminate *term, in __rdmap_term_set_etype() argument
235 term->etype = etype & 0xf; in __rdmap_term_set_etype()
238 static inline u8 __rdmap_term_ecode(struct iwarp_terminate *term) in __rdmap_term_ecode() argument
240 return term->ecode; in __rdmap_term_ecode()
[all …]
|
| /openbmc/openbmc/poky/documentation/sdk-manual/ |
| H A D | appendix-customizing.rst | 27 specific to the :term:`Build Host`.
30 :term:`ESDK_LOCALCONF_REMOVE`
38 :term:`ESDK_LOCALCONF_REMOVE`
42 :term:`ESDK_LOCALCONF_ALLOW`
44 :term:`ESDK_LOCALCONF_ALLOW` overrides either of the previous two
47 - Classes inherited globally with :term:`INHERIT` that are listed in
48 :term:`ESDK_CLASS_INHERIT_DISABLE` are disabled. Using
49 :term:`ESDK_CLASS_INHERIT_DISABLE` to disable these classes is the typical
63 In most cases, the extensible SDK defaults should work with your :term:`Build
68 :term:`INHERIT` variable and you
[all …]
|