/openbmc/openbmc/poky/meta/recipes-core/base-files/base-files/ |
H A D | 0001-add-nss-resolve-to-nsswitch.patch | 9 Upstream-Status: Inappropriate [no upstream, configuration].
|
/openbmc/openbmc/poky/meta/recipes-devtools/log4cplus/ |
H A D | log4cplus_2.1.1.bb | 4 …e, flexible, and arbitrarily granular control over log management and configuration. It is modelle…
|
/openbmc/openbmc/poky/meta/recipes-graphics/virglrenderer/virglrenderer/ |
H A D | 0001-meson.build-use-python3-directly-for-python.patch | 7 its configuration).
|
/openbmc/linux/Documentation/devicetree/bindings/arm/mediatek/ |
H A D | mediatek,mt7622-pcie-mirror.yaml | 14 The mediatek PCIE mirror provides a configuration interface for PCIE
|
H A D | mediatek,mt7986-wed-pcie.yaml | 14 The mediatek WED PCIE provides a configuration interface for PCIE
|
/openbmc/linux/drivers/net/ethernet/fungible/ |
H A D | Kconfig | 3 # Fungible network driver configuration
|
/openbmc/linux/Documentation/devicetree/bindings/nvmem/ |
H A D | microchip,lan9662-otpc.yaml | 14 (e.g. hardware configuration settings, chip identifiers) or
|
/openbmc/linux/Documentation/devicetree/bindings/sound/ |
H A D | option,gtm601.yaml | 13 This device has no configuration interface. The sample rate and channels are
|
/openbmc/linux/drivers/net/ethernet/vertexcom/ |
H A D | Kconfig | 3 # Vertexcom network device configuration
|
/openbmc/linux/Documentation/devicetree/bindings/fpga/ |
H A D | xlnx,zynqmp-pcap-fpga.yaml | 15 configure the Programmable Logic (PL). The configuration uses the
|
/openbmc/openbmc/poky/meta/recipes-core/init-ifupdown/init-ifupdown-1.0/ |
H A D | interfaces | 1 # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
|
/openbmc/linux/drivers/staging/pi433/Documentation/ |
H A D | pi433.txt | 22 Each transmission can take place with a different configuration of the rf 43 reception there is only one configuration set. 45 configuration set is written to the rf module and it gets set into receiving mode. 72 The tx configuration is transferred via struct pi433_tx_cfg, the parameterset for transmission. 164 The rx configuration is transferred via struct pi433_rx_cfg, the parameterset for receiving. It is … 267 This setting must meet the configuration of the transmitting device,
|
/openbmc/linux/Documentation/sound/designs/ |
H A D | oss-emulation.rst | 32 The currently available OSS configuration is shown in 202 You can check the currently defined configuration by reading the proc 204 can save the current configuration 214 Also, for clearing all the current configuration, send ``erase`` command 286 For changing the assignment, you can write the configuration to this 303 current mixer configuration by reading and writing the whole file
|
/openbmc/docs/designs/ |
H A D | bmc-health-monitor.md | 43 hardware discovery process or build-time, hardware-specific configuration for 97 For 1) Configuration, the daemon will have a default in code configuration. 98 Platform may supply a configuration file if it wants to over-ride the specific 99 default attributes. The format for the JSON configuration file is as under - 144 it is optional. Type: This indicates the type of configuration entry. Possible 253 …penbmc.org/xref/openbmc/openbmc/meta-quanta/meta-s6q/recipes-phosphor/configuration/s6q-yaml-confi…
|
/openbmc/linux/Documentation/driver-api/usb/ |
H A D | writing_musb_glue_layer.rst | 36 Devices also provide an overview of the Linux kernel MUSB configuration, 478 kernel configuration to make use of the corresponding transceiver 556 entries in that configuration table. More on that later in 559 Then this configuration is embedded inside ``jz4740_musb_platform_data`` 561 the configuration structure itself, and mode tells the controller driver 609 for USB endpoints configuration. 613 to bypass reading the configuration from silicon, and rely on a 614 hard-coded table that describes the endpoints configuration instead:: 622 Looking at the configuration table above, we see that each endpoints is 635 configuration according to the USB specification. For more examples of [all …]
|
/openbmc/u-boot/doc/device-tree-bindings/net/ |
H A D | snps,dwc-qos-ethernet.txt | 23 configuration, in any order: 90 configuration, in any order: 111 It depends on the SoC configuration. 113 It depends on the SoC configuration.
|
/openbmc/linux/Documentation/devicetree/bindings/net/ |
H A D | snps,dwc-qos-ethernet.txt | 26 configuration, in any order: 91 configuration, in any order: 110 It depends on the SoC configuration. 112 It depends on the SoC configuration.
|
/openbmc/linux/Documentation/gpu/amdgpu/display/ |
H A D | display-manager.rst | 131 (DM) to program the blending configuration of the Multiple Pipe/Plane Combined 140 Therefore, the blending configuration for a single MPCC instance on the MPC 169 Blend configuration flow 182 MPCC blend configuration considering the :c:type:`dc_plane_info
|
/openbmc/linux/Documentation/scsi/ |
H A D | ufs.rst | 21 5. UFS Reference Clock Frequency configuration 77 configuration operations. Device level operations mainly involve 80 requests which are used to modify and retrieve configuration 199 5. UFS Reference Clock Frequency configuration
|
/openbmc/linux/Documentation/virt/kvm/devices/ |
H A D | xive.rst | 75 Resets the interrupt controller configuration for sources and event 146 -ENXIO CPU event queues not configured or configuration of the 238 3. Capture the state of the source targeting, the EQs configuration 243 1. Restore the EQ configuration. As targeting depends on it.
|
/openbmc/linux/Documentation/devicetree/bindings/mtd/ |
H A D | st-fsm.txt | 11 - st,syscfg : Phandle to boot-device system configuration registers
|
/openbmc/linux/drivers/media/common/siano/ |
H A D | Kconfig | 3 # Siano Mobile Silicon Digital TV device configuration
|
/openbmc/linux/drivers/zorro/ |
H A D | Kconfig | 3 # Zorro configuration
|
/openbmc/linux/Documentation/admin-guide/media/ |
H A D | ttusb-dec.rst | 45 /lib/firmware directory (depending on configuration of firmware hotplug).
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/p910nd/p910nd/ |
H A D | fix-var-lock.patch | 3 Upstream-Status: Inappropriate [configuration]
|