| /openbmc/linux/Documentation/networking/ |
| H A D | tcp-thin.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Thin-streams and TCP
7 A wide range of Internet-based services that use reliable transport
8 protocols display what we call thin-stream properties. This means
9 that the application sends data with such a low rate that the
11 effective. In time-dependent scenarios (like online games, control
15 dependency on the arrival of new data from the application to trigger
19 After analysing a large number of time-dependent interactive
22 lifespan. The combination of time-dependency and the fact that the
25 In order to reduce application-layer latency when packets are lost,
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/pci/ |
| H A D | snps,dw-pcie-common.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pci/snps,dw-pcie-common.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jingoo Han <jingoohan1@gmail.com>
11 - Gustavo Pimentel <gustavo.pimentel@synopsys.com>
23 Interface - DBI. In accordance with the reference manual the register
24 configuration space belongs to the Configuration-Dependent Module (CDM)
25 and is split up into several sub-parts Standard PCIe configuration
26 space, Port Logic Registers (PL), Shadow Config-space Registers,
[all …]
|
| H A D | snps,dw-pcie-ep.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/pci/snps,dw-pcie-ep.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jingoo Han <jingoohan1@gmail.com>
11 - Gustavo Pimentel <gustavo.pimentel@synopsys.com>
16 # Please create a separate DT-schema for your DWC PCIe Endpoint controller
17 # and make sure it's assigned with the vendor-specific compatible string.
21 const: snps,dw-pcie-ep
23 - compatible
[all …]
|
| /openbmc/libpldm/ |
| H A D | README.md | 7 - keeping it light weight
8 - implementation in C
9 - minimal dynamic memory allocations
10 - endian-safe
11 - no OpenBMC specific dependencies
20 encode_foo_req() - encode a foo request
21 decode_foo_resp() - decode a response to foo
27 decode_foo_req() - decode a foo request
28 encode_foo_resp() - encode a response to foo
47 meson setup build && meson compile -C build
[all …]
|
| /openbmc/linux/Documentation/crypto/ |
| H A D | async-tx-api.rst | 1 .. SPDX-License-Identifier: GPL-2.0
24 4.2 "My application needs exclusive control of hardware channels"
32 bulk memory transfers/transforms with support for inter-transactional
43 xor-parity-calculations of the md-raid5 driver using the offload engines
53 2. cross channel dependency chains: the API allows a chain of dependent
54 operations to be submitted, like xor->copy->xor in the raid5 case. The
64 -----------------------------
72 ------------------------
92 -------------------------
94 The return value is non-NULL and points to a 'descriptor' when the operation
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/nodejs/nodejs-oe-cache-22.13/ |
| H A D | oe-npm-cache | 3 /// Usage: oe-npm-cache <cache-dir> <type> <key> <file-name>
4 /// <type> ... meta - metainformation about package
5 /// tgz - tarball
22 // metadata content is highly nodejs dependent; when cache entries are not
23 // found, place debug statements in 'make-fetch-happen/lib/cache/policy.js'
27 'key_prefix': 'make-fetch-happen:request-cache:',
33 'accept': 'application/json',
36 "content-type": "application/json",
47 'key_prefix': 'make-fetch-happen:request-cache:',
56 "content-type": "application/octet-stream",
|
| /openbmc/linux/Documentation/admin-guide/media/ |
| H A D | ci.rst | 1 .. SPDX-License-Identifier: GPL-2.0
25 A userspace application, like ``ca_zap`` is required to handle encrypted
26 MPEG-TS streams.
28 The ``ca_zap`` userland application is in charge of sending the
31 This application requires the following to function properly as of now.
35 eg: $ szap -c channels.conf -r "TMC" -x
68 The CI module support is largely dependent upon the firmware on the cards
|
| /openbmc/u-boot/doc/ |
| H A D | README.standalone | 1 Design Notes on Exporting U-Boot Functions to Standalone Applications:
4 1. The functions are exported by U-Boot via a jump table. The jump
15 gd->jt->malloc = my_malloc;
16 gd->jt->free = my_free;
21 2. The pointer to the jump table is passed to the application in a
22 machine-dependent way. PowerPC, ARM, MIPS, Blackfin and Nios II
27 structure is passed as 'argv[-1]' pointer.
29 The application can access the 'global_data' structure in the same
30 way as U-Boot does:
34 printf("U-Boot relocation offset: %x\n", gd->reloc_off);
[all …]
|
| H A D | README.u-boot_on_efi | 1 # SPDX-License-Identifier: GPL-2.0+
5 U-Boot on EFI
7 This document provides information about U-Boot running on top of EFI, either
8 as an application or just as a means of getting U-Boot onto a new platform.
18 EFI Application
22 32/64-bit
28 ----------
29 Running U-Boot on EFI is useful in several situations:
31 - You have EFI running on a board but U-Boot does not natively support it
32 fully yet. You can boot into U-Boot from EFI and use that until U-Boot is
[all …]
|
| H A D | README.console | 1 SPDX-License-Identifier: GPL-2.0+
4 * Paolo Scaffardi, AIRVENT SAM s.p.a - RIMINI(ITALY), arsenio@tin.it
7 U-Boot console handling
11 ----------------------
13 At system startup U-Boot initializes a serial console. When U-Boot
27 setenv stdin serial <- To use the serial input
28 setenv stdout video <- To use the video console
34 ---------------------------------------------
59 Remember that all FILE-related functions CANNOT be used before
60 U-Boot relocation (done in 'board_init_r' in arch/*/lib/board.c).
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | Application.v1_0_1.json | 2 "$id": "http://redfish.dmtf.org/schemas/v1/Application.v1_0_1.json",
3 "$ref": "#/definitions/Application",
4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
26 "#Application.Reset": {
31 "description": "The available OEM-specific actions for this resource.",
32 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
37 "Application": { object
39 …"description": "The `Application` schema represents an application or service running on a compute…
[all …]
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | selection-api-configuration.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
18 parameters and return the actual values selected. An application can
20 :ref:`constraint flags <v4l2-selection-flags>`.
26 See figure :ref:`sel-targets-capture` for examples of the selection
61 adjustments according to hardware limitations. The application can
63 :ref:`constraint flags <v4l2-selection-flags>`.
74 padded area but outside active area is undefined. The application can
123 However, such a padded area is driver-dependent feature not covered by
133 An application can detect if scaling is performed by comparing the width
136 scaling is applied. The application can compute the scaling ratios using
|
| H A D | open.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
22 the hardware, which may also expose device nodes, called V4L2 sub-devices.
24 When such V4L2 sub-devices are exposed, they allow controlling those
25 other hardware components - usually connected via a serial bus (like
26 I²C, SMBus or SPI). Depending on the bridge driver, those sub-devices
29 :ref:`V4L2 sub-devices <subdev>`.
32 :ref:`Media Controller <media_controller>` are called **MC-centric**
34 are called **video-node-centric**.
36 Userspace can check if a V4L2 hardware peripheral is MC-centric by
38 :ref:`device_caps field <device-capabilities>`.
[all …]
|
| /openbmc/webui-vue/docs/customization/ |
| H A D | theme.md | 3 Customization of the application requires knowledge of Sass and CSS. It also
4 will require becoming familiar with the Bootstrap and Bootstrap-Vue component
12 application navigation, and theming.
25 these built-in variables is `enabled-*`.
27 ### $enable-rounded
29 This option enables or disables the border-radius styles on various components.
31 - Set to `false` to remove rounded corners on all container elements and buttons
33 ### $enable-validation-icons
35 This option enables or disables background-image icons within textual inputs and
38 - Set to `false` due to inability to style icons using CSS
[all …]
|
| /openbmc/docs/designs/ |
| H A D | voltage-regulator-configuration.md | 8 Created: 2019-07-13
13 voltage, over-current limit, and pgood thresholds. The configuration is often
14 dependent on the system type and rail type. Regulators have a hardware default
17 new application is needed to configure regulators. It should be data-driven to
18 support a variety of regulator types and to avoid hard-coded logic.
24 Hardware engineers must specify many low-level configuration values for a
25 regulator. Some simple examples include output voltage, over-current limit, and
33 non-volatile memory on the regulator. This provides the hardware/power-on
39 - New information found during hardware testing. For example, downstream
41 - Hardware workarounds. Problems in the regulator hardware or related hardware
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
| H A D | Application_v1.xml | 1 <?xml version="1.0" encoding="UTF-8"?>
2 <!---->
3 <!--################################################################################ -->
4 <!--# Redfish Schema: Application v1.0.1 -->
5 <!--# -->
6 <!--# For a detailed change log, see the README file contained in the DSP8010 bundle, -->
7 <!--# available at http://www.dmtf.org/standards/redfish -->
8 <!--# Copyright 2014-2024 DMTF. -->
9 <!--# For the full DMTF copyright policy, see http://www.dmtf.org/about/policies/copyright -->
10 <!--################################################################################ -->
[all …]
|
| /openbmc/linux/Documentation/driver-api/memory-devices/ |
| H A D | ti-gpmc.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 * Asynchronous SRAM like memories and application specific integrated
14 * Pseudo-SRAM devices
85 4. read async non-muxed
107 6. read sync non-muxed
131 8. write async non-muxed
157 10. write sync non-muxed
172 Many of gpmc timings are dependent on other gpmc timings (a few
173 gpmc timings purely dependent on other gpmc timings, a reason that
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-connectivity/krb5/krb5/ |
| H A D | debian-suppress-usr-lib-in-krb5-config.patch | 1 Subject: [PATCH] debian: suppress /usr/lib in krb5-config
3 Upstream-Status: Pending
5 Handel multi-arch suppressions
9 Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
10 ---
11 src/build-tools/krb5-config.in | 14 +++++++++-----
12 1 files changed, 9 insertions(+), 5 deletions(-)
14 diff --git a/src/build-tools/krb5-config.in b/src/build-tools/krb5-config.in
16 --- a/src/build-tools/krb5-config.in
17 +++ b/src/build-tools/krb5-config.in
[all …]
|
| /openbmc/linux/Documentation/userspace-api/media/drivers/ |
| H A D | omap3isp-uapi.rst | 1 .. SPDX-License-Identifier: GPL-2.0
17 ------
34 application using the VIDIOC_OMAP3ISP_STAT_REQ IOCTL. The events available
37 - V4L2_EVENT_OMAP3ISP_AEWB
38 - V4L2_EVENT_OMAP3ISP_AF
39 - V4L2_EVENT_OMAP3ISP_HIST
44 omap3isp_stat_event_status.buf_err is set to non-zero.
48 --------------
52 does not fall under the standard IOCTLs --- gamma tables and configuration of
56 containing hardware-dependent functions.
[all …]
|
| /openbmc/linux/Documentation/fb/ |
| H A D | api.rst | 9 ---------------
12 with frame buffer devices. In-kernel APIs between device drivers and the frame
22 ---------------
33 Application should use those capabilities to find out what features they can
36 - FB_CAP_FOURCC
44 --------------------
46 Pixels are stored in memory in hardware-dependent formats. Applications need
58 - FB_TYPE_PACKED_PIXELS
67 - FB_TYPE_PLANES
75 - FB_TYPE_INTERLEAVED_PLANES
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-multimedia/recipes-multimedia/wireplumber/ |
| H A D | wireplumber_0.5.7.bb | 9 DEPENDS = "glib-2.0 glib-2.0-native lua pipewire \
10 ….utils.contains("DISTRO_FEATURES", "gobject-introspection-data", "python3-native python3-lxml-nati…
16 file://90-OE-disable-session-dbus-dependent-features.lua \
21 inherit meson pkgconfig gobject-introspection systemd
26 # Enable system-lua to let wireplumber use OE's lua.
27 # Documentation needs python-sphinx, which is not in oe-core or meta-python2 for now.
30 -Ddoc=disabled \
31 -Dsystem-lua=true \
32 -Delogind=disabled \
33 -Dsystemd-system-unit-dir=${systemd_system_unitdir} \
[all …]
|
| /openbmc/linux/Documentation/hid/ |
| H A D | hidraw.rst | 2 HIDRAW - Raw Access to USB and Bluetooth Human Interface Devices
10 Hidraw should be used if the userspace application knows exactly how to
15 Hidraw is also useful for communicating with non-conformant HID devices
19 communication with these non-conformant devices is impossible using hiddev.
21 these non-conformant devices.
31 directly under /dev (eg: /dev/hidraw0). As this location is distribution-
32 and udev rule-dependent, applications should use libudev to locate hidraw
40 ---------------
43 -------
47 a report available to be read. read() can be made non-blocking, by passing
[all …]
|
| /openbmc/linux/Documentation/networking/device_drivers/ethernet/huawei/ |
| H A D | hinic.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 The driver supports a range of link-speed devices (10GbE, 25GbE, 40GbE, etc.).
14 Some HiNIC devices support SR-IOV. This driver is used for Physical Function
17 HiNIC devices support MSI-X interrupt vector for each Tx/Rx queue and
21 TCP Transmit Segmentation Offload(TSO), Receive-Side Scaling(RSS) and
28 19e5:1822 - HiNIC PF
34 hinic_dev - Implement a Logical Network device that is independent from
37 hinic_hwdev - Implement the HW details of the device and include the components
55 Asynchronous Event Queues(AEQs) - The event queues for receiving messages from
58 Application Programmable Interface commands(API CMD) - Interface for sending
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/mailbox/ |
| H A D | hisilicon,hi6220-mailbox.txt | 13 --------------------
14 - compatible: Shall be "hisilicon,hi6220-mbox"
15 - reg: Contains the mailbox register address range (base
19 - #mbox-cells: Common mailbox binding property to identify the number
26 TX/RX interrupt to application processor,
28 - interrupts: Contains the interrupt information for the mailbox
29 device. The format is dependent on which interrupt
33 --------------------
34 - hi6220,mbox-tx-noirq: Property of MCU firmware's feature, so mailbox driver
40 --------
[all …]
|
| /openbmc/linux/Documentation/infiniband/ |
| H A D | opa_vnic.rst | 2 Intel Omni-Path (OPA) Virtual Network Interface Controller (VNIC)
5 Intel Omni-Path (OPA) Virtual Network Interface Controller (VNIC) feature
6 supports Ethernet functionality over Omni-Path fabric by encapsulating
11 The patterns of exchanges of Omni-Path encapsulated Ethernet packets
12 involves one or more virtual Ethernet switches overlaid on the Omni-Path
13 fabric topology. A subset of HFI nodes on the Omni-Path fabric are
22 application. HFI nodes can have multiple VNICs each connected to a
26 +-------------------+
30 +-------------------+
35 +-----------------------------+ +------------------------------+
[all …]
|