| /openbmc/phosphor-psu-code-mgmt/src/ |
| H A D | meson.build | 2 configuration: cdata,
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | smsc47b397.rst | 107 To program the configuration registers, the following sequence must be followed:
121 In configuration mode, the INDEX PORT is located at the CONFIG PORT address and
124 The desired configuration registers are accessed in two steps:
130 b. Write the address of the desired configuration register within the
|
| /openbmc/linux/Documentation/devicetree/bindings/powerpc/fsl/ |
| H A D | srio-rmu.txt | 22 length of the SRIO configuration registers for message units
53 length of the SRIO configuration registers for message units
83 length of the SRIO configuration registers for message units
113 length of the SRIO configuration registers for message units
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | configfs-most | 60 configuration, the creation is post-poned until
115 configuration, the creation is post-poned until
170 configuration, the creation is post-poned until
236 configuration, the creation is post-poned until
|
| H A D | sysfs-driver-altera-cvp | 6 Contains either 1 or 0 and controls if configuration
|
| /openbmc/linux/Documentation/devicetree/bindings/clock/ |
| H A D | nvidia,tegra124-dfll.txt | 67 - pinctrl-0: I/O pad configuration when PWM control is enabled.
68 - pinctrl-1: I/O pad configuration when PWM control is disabled.
70 - dvfs_pwm_enable: I/O pad configuration when PWM control is enabled.
71 - dvfs_pwm_disable: I/O pad configuration when PWM control is disabled.
|
| /openbmc/linux/drivers/rapidio/devices/ |
| H A D | Kconfig | 3 # RapidIO master port configuration
|
| /openbmc/qemu/configs/devices/ppc-softmmu/ |
| H A D | default.mak | 1 # Default configuration for ppc-softmmu
|
| /openbmc/openbmc/meta-ibm/meta-fsp2/conf/machine/include/ |
| H A D | fsp2.inc | 3 #@DESCRIPTION: evaluation machine board configuration for the fsp2 ppc476
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | layers.rst | 56 layer name begins with "meta-". A notable example is in configuration
59 configuration.
63 an existing layer configuration file and copy that to your layer's
85 Here is an explanation of the layer configuration file:
95 configuration filenames in your custom layer.
148 distro policy, add the distro configuration in a ``conf/distro/``
568 SUMMARY = "X.Org X server configuration file"
684 - ``flatten:`` Flattens the layer configuration into a separate
685 output directory. Flattening your layer configuration builds a
737 …":ref:`dev-manual/custom-template-configuration-directory:creating a custom template configuration…
[all …]
|
| /openbmc/qemu/docs/system/arm/ |
| H A D | orangepi.rst | 16 * Generic Interrupt Controller configuration
83 simply configure the kernel using the sunxi_defconfig configuration:
91 configuration item. Start the kconfig configuration tool:
97 Navigate to the following item, enable it and save your configuration:
187 for development/testing to select the following configuration setting in U-Boot:
219 the orangepi_pc_defconfig configuration as described in the previous section.
|
| /openbmc/openbmc-test-automation/gui/gui_test/security_and_access_menu/ |
| H A D | test_ldap_sub_menu.robot | 90 [Documentation] Verify created LDAP configuration.
162 [Documentation] Read network configuration via different user roles and verify.
216 [Documentation] Create LDAP configuration.
228 # Clearing existing LDAP configuration by disabling it.
279 [Documentation] Update LDAP configuration update with LDAP user role and group.
320 [Documentation] Disable LDAP configuration on BMC.
351 [Documentation] Update LDAP user role and read network configuration via GUI.
|
| /openbmc/linux/scripts/kconfig/lxdialog/ |
| H A D | BIG.FAT.WARNING | 3 kernel configuration script. Please do not bother Savio Lam with
|
| /openbmc/u-boot/scripts/kconfig/lxdialog/ |
| H A D | BIG.FAT.WARNING | 3 kernel configuration script. Please do not bother Savio Lam with
|
| /openbmc/openbmc/meta-facebook/meta-harma/recipes-phosphor/leds/ |
| H A D | phosphor-led-manager_%.bbappend | 1 # phosphor led configuration
|
| /openbmc/u-boot/arch/arm/dts/ |
| H A D | fsl-ls1088a.dtsi | 111 0x20 0x00000000 0x0 0x20000>; /* configuration space */
127 0x28 0x00000000 0x0 0x20000>; /* configuration space */
143 0x30 0x00000000 0x0 0x20000>; /* configuration space */
|
| /openbmc/u-boot/drivers/usb/gadget/ |
| H A D | ep0.c | 487 serial_printf("get config %d\n", device->configuration); in ep0_recv_setup()
489 device->configuration); in ep0_recv_setup()
571 device->configuration = le16_to_cpu(request->wValue) & 0xff; in ep0_recv_setup()
|
| /openbmc/linux/drivers/amba/ |
| H A D | Kconfig | 11 Adds AHB configuration functionality for NVIDIA Tegra SoCs,
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-connectivity/krb5/krb5/etc/default/ |
| H A D | krb5-kdc | 3 # dpkg-reconfigure krb5-kdc and disable managing the KDC configuration with
|
| /openbmc/linux/Documentation/networking/ |
| H A D | bonding.rst | 663 Most switches will require some type of configuration
1171 off or The device configuration is ignored.
1210 change the bonding configuration.
1243 the system ``/etc/modules.d/*.conf`` configuration files.
1333 options for your configuration.
1392 values for your configuration.
1849 4.2 Network configuration
1894 require any specific configuration of the switch.
2056 This routing configuration will likely still update the
2268 In this configuration, there is a link between the two
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/arm/ |
| H A D | spear-misc.txt | 1 SPEAr Misc configuration
|
| /openbmc/linux/drivers/net/ethernet/aeroflex/ |
| H A D | Kconfig | 3 # Aeroflex Gaisler network device configuration
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | selection-api.rst | 14 selection-api-configuration.rst
|
| /openbmc/openbmc/poky/meta/recipes-graphics/xorg-app/ |
| H A D | xinput_1.6.4.bb | 3 SUMMARY = "Runtime configuration and test of XInput devices"
|
| /openbmc/linux/Documentation/admin-guide/pm/ |
| H A D | suspend-flows.rst | 137 2. Resuming devices and restoring the working-state configuration of IRQs.
146 The working-state configuration of IRQs is restored after the *noirq* resume
198 configuration of system wakeup sources usually starts when system wakeup
205 configuration of the system (in particular, the hardware cannot be accessed
243 control is passed back to the kernel (the working configuration of the
249 The suspend-time configuration of the core system components is restored and
255 back online and their suspend-time configuration is restored.
257 4. Resuming devices and restoring the working-state configuration of IRQs.
|