| /openbmc/webui-vue/src/assets/styles/bmc/custom/ |
| H A D | _forms.scss | 26 .custom-select,
34 .custom-select,
58 .custom-select,
60 .custom-control-label,
70 .custom-select,
90 .custom-checkbox .custom-control-input:checked ~ .custom-control-label::after,
91 .custom-checkbox .custom-control-input:indeterminate ~ .custom-control-label::before,
92 .custom-control-input:checked ~ .custom-control-label::before,
100 .custom-control {
101 .custom-control-input[disabled=disabled] {
[all …]
|
| /openbmc/webui-vue/src/env/assets/styles/ |
| H A D | _intel.scss | 55 .custom-checkbox .custom-control-input:checked ~ .custom-control-label::after,
56 .custom-checkbox .custom-control-input:indeterminate ~ .custom-control-label::before,
57 .custom-control-input:checked ~ .custom-control-label::before {
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/nodejs/nodejs/ |
| H A D | 0001-custom-env.patch | 8 test/fixtures/run-script/node_modules/.bin/custom-env | 2 +-
11 …a/test/fixtures/run-script/node_modules/.bin/custom-env b/test/fixtures/run-script/node_modules/.b…
13 --- a/test/fixtures/run-script/node_modules/.bin/custom-env
14 +++ b/test/fixtures/run-script/node_modules/.bin/custom-env
|
| /openbmc/qemu/target/riscv/ |
| H A D | XVentanaCondOps.decode | 8 # Reference: VTx-family custom instructions
10 … (https://github.com/ventanamicro/ventana-custom-extensions/releases/download/v1.0.0/ventana…
|
| /openbmc/webui-vue/docs/customization/ |
| H A D | readme.md | 21 ├─ custom
24 └─ _obmc-custom.scss
27 ### `custom` Directory
29 The `custom` Directory imports all the styles needed to customize the UI. These
41 ├─ custom
60 └─ _obmc-custom.scss
66 variables that establish the custom theme of the application.
81 └─ _obmc-custom.scss
170 `theme-color-light` and `theme-color-dark` are custom functions used to create
259 overrides, Bootstrap global variable overrides, and custom BMC global variables.
[all …]
|
| /openbmc/webui-vue/docs/guide/components/info-tooltip/ |
| H A D | index.md | 3 The `InfoTooltip` is a custom component that uses a Bootstrap-vue tooltip with
4 an info icon. This custom component requires a title property containing the
|
| /openbmc/openbmc/poky/bitbake/lib/toaster/orm/fixtures/ |
| H A D | README | 18 - custom.xml
20 To add custom initial data/configuration to Toaster place a file called
21 "custom.xml" in this directory. If present it will be loaded into the database.
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | index.rst | 34 custom-distribution
35 custom-template-configuration-directory
|
| H A D | customizing-images.rst | 73 creating a custom class for use with specialized image ``.bb`` files.
106 You can also customize an image by creating a custom recipe that defines
113 Defining the software using a custom recipe gives you total control over
119 The other method for creating a custom image is to base it on an
130 For complex custom images, the best approach for customizing an image is
131 to create a custom package group recipe that is used to build the image
152 hypothetical packagegroup defined in ``packagegroup-custom.bb``, where
154 the full packagegroup name ``packagegroup-custom``::
180 ``packagegroup-custom-apps``, and ``packagegroup-custom-tools``. To
182 ``packagegroup-custom-apps`` and/or ``packagegroup-custom-tools`` to
|
| H A D | custom-template-configuration-directory.rst | 7 use by other users, you might want to provide a custom build configuration
9 ``bblayers.conf`` that are created in a new :term:`Build Directory`) and a custom
12 custom distribution layer.
|
| /openbmc/sdbusplus/docs/ |
| H A D | asio.md | 6 `register_property()`. If you need to provide a custom getter or setter for a
10 custom exception derived from `sdbusplus::exception_t`. For the custom
12 the `name()` or a custom/arbitrary name. The former will be automatically
|
| /openbmc/qemu/docs/devel/testing/ |
| H A D | ci-runners.rst.inc | 14 gitlab-runner, is called a "custom runner".
16 The GitLab CI jobs definition for the custom runners are located under::
18 .gitlab-ci.d/custom-runners.yml
20 Custom runners entail custom machines. To see a list of the machines
105 Because the job definition at ``.gitlab-ci.d/custom-runners.yml``
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-daemons/lldpd/ |
| H A D | lldpd_1.0.19.bb | 43 PACKAGECONFIG[custom] = "--enable-custom,--disable-custom"
|
| /openbmc/webui-vue/src/assets/styles/ |
| H A D | _obmc-custom.scss | 5 @import "./bmc/custom";
|
| /openbmc/phosphor-logging/extensions/openpower-pels/ |
| H A D | user_data_formats.hpp | 13 custom = 4 enumerator
|
| /openbmc/webui-vue/src/assets/styles/bootstrap/ |
| H A D | _index.scss | 4 // Import our custom colors and variables before Bootstrap variables
13 // Import our custom functions that depend on Bootstrap variables
|
| /openbmc/openbmc/poky/documentation/ |
| H A D | transitioning-to-a-custom-environment.rst | 4 Transitioning to a custom environment for systems development
24 Even if you're using custom hardware, it might be easier to start with an
26 architecture as your custom hardware. Knowing the board already has a
56 #. **Add a new layer for any custom recipes and metadata you create**.
72 meta-intel remains in your bblayers.conf). Now you can put your custom BSP
77 Creating your own recipe is especially important for custom application
106 <dev-manual/custom-distribution:creating your own distribution>`.
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-core/init-ifupdown/ |
| H A D | init-ifupdown_1.0.bbappend | 1 # Use custom interface file for Juno
|
| /openbmc/phosphor-bmc-code-mgmt/bmc/ |
| H A D | obmc-flash-host-bios@.service.in | 7 ExecStart=echo Please add custom command for flashing image /tmp/image/%i
|
| /openbmc/openbmc-test-automation/lib/ |
| H A D | gen_plug_in_utils.py | 39 def return_plug_vars(general=True, custom=True, plug_in_package_name=None): argument
81 if not (general or custom):
88 if custom:
222 qprint_plug_vars(headers=0, general=False, custom=True)
|
| /openbmc/openbmc/poky/meta-skeleton/recipes-kernel/linux/ |
| H A D | linux-yocto-custom.bb | 2 # linux-yocto-custom.bb:
7 # To use linux-yocto-custom in your layer, copy this recipe (optionally
60 LINUX_VERSION_EXTENSION:append = "-custom"
|
| /openbmc/x86-power-control/service_files/ |
| H A D | chassis-system-reset.service | 7 ExecStart=echo Please add custom command for system reset chassis
|
| /openbmc/u-boot/include/ |
| H A D | dt_table.h | 46 u32 custom[4]; /* optional, must be zero if unused */ member
|
| /openbmc/webui-vue/docs/guide/quickstart/ |
| H A D | forms.md | 27 - [Form file custom component](/guide/components/file-upload)
34 For custom form validation messages, disable browser native HTML5 validation by
36 validation state and add custom validation messages in the
|
| /openbmc/openbmc/poky/meta/recipes-devtools/python/ |
| H A D | python3-booleanpy_4.0.bb | 1 SUMMARY = "Define boolean algebras, create and parse boolean expressions and create custom boolean …
|