Home
last modified time | relevance | path

Searched +full:one +full:- +full:way (Results 1 – 25 of 1074) sorted by relevance

12345678910>>...43

/openbmc/qemu/target/xtensa/core-dsp3400/
H A Dcore-matmap.h2 * xtensa/config/core-matmap.h -- Memory access and translation mapping
10 * information contained in the core-isa.h header file.
19 * XCHAL_ICACHE_SIZE (presence of I-cache)
20 * XCHAL_DCACHE_SIZE (presence of D-cache)
25 /* Copyright (c) 1999-2010 Tensilica Inc.
49 /*----------------------------------------------------------------------
51 ----------------------------------------------------------------------*/
54 /* Cache Attribute encodings -- lists of access modes for each cache attribute: */
108 * one is returned instead (eg. writethru instead of writeback,
112 #define XCHAL_CA_WRITETHRU 1 /* cache enabled (write-through) mode */
[all …]
/openbmc/linux/scripts/tracing/
Dftrace-bisect.sh
/openbmc/linux/arch/mips/include/asm/octeon/
Dcvmx-l2c.h
/openbmc/linux/Documentation/filesystems/
Dinotify.rst
/openbmc/linux/arch/nios2/mm/
Dtlb.c
/openbmc/linux/Documentation/process/
Dstable-api-nonsense.rst
/openbmc/linux/Documentation/driver-api/pci/
Dp2pdma.rst
/openbmc/docs/designs/
H A Dvpd-collection.md5 Created: 2019-06-11
9 On OpenBMC, Vital Product Data (VPD) collection is limited to only one or two
10 Field Replaceable Units (FRUs) today - one example is the BMC FRU. On OpenPower
11 systems, the BMC also supports just one VPD format, the [OpenPower VPD] [1]
18 - Some of the VPD information such as FRU part number, serial number need to be
21 - Several use cases on the BMC require that the applications decide on a certain
26 - There are use cases for the BMC to send VPD data to the host
31 of certain parameters of the FRU (atypical - for FRUs that do not have an
39 Essentially, the IPZ VPD structure consists of key-value pairs called keywords.
47 laid out one after another.
[all …]
/openbmc/linux/Documentation/input/devices/
Drotary-encoder.rst
/openbmc/linux/Documentation/arch/x86/
Dmicrocode.rst
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/User/Ldap/
H A DConfig.interface.yaml3 User.Ldap.Config interface on one or more objects must implement
7 - name: LDAPServerURI
12 - xyz.openbmc_project.Common.Error.InternalFailure
13 - xyz.openbmc_project.Common.Error.InvalidArgument
14 - xyz.openbmc_project.Common.Error.NoCACertificate
15 - name: LDAPBindDN
21 - xyz.openbmc_project.Common.Error.InternalFailure
22 - xyz.openbmc_project.Common.Error.InvalidArgument
23 - name: LDAPBindDNPassword
29 on the D-bus object itself. Implementation can use the given value and
[all …]
/openbmc/linux/Documentation/admin-guide/acpi/
Dssdt-overlays.rst
/openbmc/qemu/docs/devel/migration/
H A Dmain.rst14 two times. I.e. it can only restore the state in one guest that has
15 the same devices that the one it was saved (this last requirement can
20 requested: migration. This means that QEMU is able to start in one
26 can take a while to move all state from one machine to another. Live
41 - tcp migration: do the migration using tcp sockets
42 - unix migration: do the migration using unix sockets
43 - exec migration: do the migration using the stdin/stdout through a process.
44 - fd migration: do the migration using a file descriptor that is
46 - file migration: do the migration using a file that is passed to QEMU
54 (see add-fd QMP command documentation). This method allows a
[all …]
/openbmc/linux/Documentation/timers/
Dno_hz.rst
/openbmc/linux/Documentation/userspace-api/media/v4l/
Dselection-api-vs-crop-api.rst
/openbmc/linux/Documentation/arch/arm/
Dinterrupts.rst
/openbmc/linux/tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/
Dl1d_cache.json
/openbmc/linux/tools/perf/pmu-events/arch/arm64/arm/neoverse-n1/
Dl1d_cache.json
/openbmc/linux/tools/testing/ktest/examples/
Dtest.conf
/openbmc/linux/Documentation/driver-api/media/
Dv4l2-event.rst
/openbmc/linux/Documentation/ABI/testing/
Dsysfs-bus-rpmsg
/openbmc/u-boot/doc/
H A DREADME.dfutftp1 # SPDX-License-Identifier: GPL-2.0+
7 Device Firmware Upgrade (DFU) - extension to use TFTP
11 ----
22 --------
25 upgrading firmware (e.g. kernel, u-boot, rootfs, etc.)
29 possible to overcome the major problem of USB based DFU -
38 To utilize this feature, one needs to first enable support
42 The "dfu" command has been extended to support transfer via TFTP - one
47 As of this writing (SHA1:8d77576371381ade83de475bb639949b44941e8c v2015.10-rc2)
49 contemporary u-boot tree.
[all …]
/openbmc/linux/Documentation/input/
Dgameport-programming.rst
/openbmc/qemu/target/xtensa/core-de233_fpu/
H A Dcore-matmap.h2 * xtensa/config/core-matmap.h -- Memory access and translation mapping
10 * information contained in the core-isa.h header file.
19 * XCHAL_ICACHE_SIZE (presence of I-cache)
20 * XCHAL_DCACHE_SIZE (presence of D-cache)
25 /* Copyright (c) 1999-2020 Tensilica Inc.
49 /*----------------------------------------------------------------------
51 ----------------------------------------------------------------------*/
55 /* Cache Attribute encodings -- lists of access modes for each cache attribute: */
113 * one is returned instead (eg. writethru instead of writeback,
117 #define XCHAL_CA_WRITETHRU 11 /* cache enabled (write-through) mode */
[all …]
/openbmc/qemu/docs/specs/
H A Divshmem-spec.rst2 Device Specification for Inter-VM shared memory device
5 The Inter-VM shared memory device (ivshmem) is designed to share a
12 can obtain one from an ivshmem server.
27 --------
31 - BAR0 holds device registers (256 Byte MMIO)
32 - BAR1 holds MSI-X table and PBA (only ivshmem-doorbell)
33 - BAR2 maps the shared memory object
37 - If you only need the shared memory part, BAR2 suffices. This way,
41 - If you additionally need the capability for peers to interrupt each
50 IVPosition register (described below) to become non-negative before
[all …]

12345678910>>...43