| /openbmc/linux/Documentation/devicetree/bindings/iio/cdc/ |
| H A D | adi,ad7746.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: AD7746 24-Bit Capacitance-to-Digital Converter with Temperature Sensor
10 - Michael Hennerich <michael.hennerich@analog.com>
13 AD7746 24-Bit Capacitance-to-Digital Converter with Temperature Sensor
16 https://www.analog.com/media/en/technical-documentation/data-sheets/ad7291.pdf
21 - adi,ad7745
22 - adi,ad7746
23 - adi,ad7747
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Control/ |
| H A D | README.msl.md | 24 ## Implementation Notes
36 implementation would need to write an application that implements
39 application is general purpose and could meet the needs of others, consider
41 hypothetical fan control card might be an application that validates a number of
46 prevented from powering on. This could be accomplished with a custom application
48 [PDM](https://github.com/openbmc/phosphor-dbus-monitor) rules.
|
| /openbmc/phosphor-logging/extensions/openpower-pels/registry/ |
| H A D | message_registry.json | 21 "Notes": ["The journal should contain more information"] array
37 "Message": "An application had an internal failure",
38 "Notes": ["The journal should contain more information"] array
59 "Notes": ["The journal should contain more information"] array
75 "Notes": ["The journal should contain more information"] array
92 "Notes": ["The journal should contain more information"] array
129 "Notes": [ array
158 "Notes": [ array
187 "Notes": [ array
216 "Notes": [ array
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/iio/adc/ |
| H A D | adi,ad9467.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Analog Devices AD9467 and similar High-Speed ADCs
10 - Michael Hennerich <michael.hennerich@analog.com>
13 The AD9467 and the parts similar with it, are high-speed analog-to-digital
16 lower MSPS, suitable for the intended application of each part.
18 All the parts support the register map described by Application Note AN-877
19 https://www.analog.com/media/en/technical-documentation/application-notes/AN-877.pdf
21 https://www.analog.com/media/en/technical-documentation/data-sheets/AD9265.pdf
[all …]
|
| /openbmc/phosphor-power/phosphor-regulators/docs/config_file/ |
| H A D | compare_vpd.md | 8 from an EEPROM on a Field-Replaceable Unit (FRU). For this reason, VPD is also
11 The phosphor-regulators application obtains VPD keyword values from D-Bus. Other
13 components and publishing it on D-Bus.
17 - CCIN
18 - Manufacturer
19 - Model
20 - PartNumber
21 - HW
31 - The hardware component does not support the keyword.
32 - An error occurred while attempting to read VPD from the hardware component.
[all …]
|
| /openbmc/linux/Documentation/crypto/ |
| H A D | async-tx-api.rst | 1 .. SPDX-License-Identifier: GPL-2.0
22 4 DMAENGINE DRIVER DEVELOPER NOTES
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
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 …]
|
| H A D | api-intro.rst | 1 .. SPDX-License-Identifier: GPL-2.0
12 mode ciphers), this will allow for pages to be encrypted in-place
26 'Transforms' are user-instantiated objects, which maintain state, handle all
34 [transform ops] (per-type logic glue e.g. cipher.c, compress.c)
49 subject to block size requirements (i.e., non-stream ciphers can only
86 Developer Notes
97 across non-aligned page fragment boundaries.
112 Algorithms submitted must also be generally patent-free (e.g. IDEA
118 as well as general application notes such as RFC2451 ("The ESP CBC-Mode
133 linux-crypto@vger.kernel.org
[all …]
|
| /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 …]
|
| /openbmc/docs/development/ |
| H A D | devtool-hello-world.md | 3 **Document Purpose:** Walk through compiling and running an OpenBMC application
7 [Document](https://github.com/openbmc/docs/blob/master/development/dev-environment.md)
16 [phosphor-state-manager](https://github.com/openbmc/phosphor-state-manager.git)
25 devtool modify phosphor-state-manager
33 vi workspace/sources/phosphor-state-manager/bmc_state_manager_main.cpp
43 @@ -17,6 +18,8 @@ int main(int argc, char**)
59 bitbake obmc-phosphor-image
76 <date> romulus phosphor-bmc-state-manager[1089]: Hello World
82 ## Loading an Application Directly Into a Running QEMU
85 re-generating the flash image and booting QEMU again, we're going to just build
[all …]
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | syscall-user-dispatch.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 ----------
11 calls of only a part of their process - the part that has the
12 incompatible code - while being able to execute native syscalls without
19 address back to userspace. The application is in control of a flip
21 multiple-personality application can then flip the switch without
31 personality, and the application simply modifies that variable to
40 non-native applications, it must function on syscalls whose invocation
49 ---------
70 [selector] is a pointer to a char-sized region in the process memory
[all …]
|
| /openbmc/u-boot/drivers/net/ |
| H A D | dm9000x.c | 1 // SPDX-License-Identifier: GPL-2.0+
8 (C)Copyright 1997-1998 DAVICOM Semiconductor,Inc. All Rights Reserved.
15 E5: R25 = ((R24 + NF - 3) & 0x00ff) | 0xc200
28 --------------------------------------
30 12/15/2003 Initial port to u-boot by
34 - Fixed the driver to work with DM9000A.
37 application notes)
38 - Added autodetect of databus width.
39 - Made debug code compile again.
40 - Adapt eth_send such that it matches the DM9000*
[all …]
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-fcoe | 4 Contact: Robert Love <robert.w.love@intel.com>, devel@open-fcoe.org
13 per-port settings and finally write to the fcoe_ctlr_device's
28 Contact: Robert Love <robert.w.love@intel.com>, devel@open-fcoe.org
66 Initialization Protocol (FIP) Keep-Alives (FKA).
78 Notes: ctlr_X (global increment starting at 0)
83 Contact: Robert Love <robert.w.love@intel.com>, devel@open-fcoe.org
117 The FIP Keep-Alive period
121 - "Unknown" - Initialization value
122 - "Disconnected" - No link to the FCF/fabric
123 - "Connected" - Host is connected to the FCF
[all …]
|
| /openbmc/linux/Documentation/arch/arm64/ |
| H A D | legacy_instructions.rst | 13 behaviours and the corresponding values of the sysctl nodes -
43 individual instruction notes for further information.
46 -----------------------------
66 for this feature to be enabled. If a new CPU - which doesn't support mixed
67 endian - is hotplugged in after this feature has been enabled, there could
68 be unexpected results in the application.
|
| /openbmc/telemetry/ |
| H A D | README.md | 7 This application is implementation of Telemetry proposed in OpenBMC design docs
12 - on-demand creation of metric reports,
13 - aggregated sets of sensor values available in system `[2]`,
14 - access to metric report in both pull and push model (triggers),
15 - run-time monitoring of sensor`[3]` updates.
17 ## Use-cases
19 - generic and centralized way to observe telemetry data inside system
20 - back-end for Redfish TelemetryService`[4]`
26 - using bitbake in yocto environment
27 - using meson as native build
[all …]
|
| /openbmc/docs/ |
| H A D | REST-cheatsheet.md | 11 ### Notes on authentication:
13 The original REST server, from the phosphor-rest-server repository, uses
15 use the same cookie jar files for read-only REST methods like GET, but requires
17 the URL for non-read-only methods.
20 server. The phosphor-rest-server repository was archived in October 2022.
24 - Using just the cookie jar files for the phosphor-rest server:
27 …$ curl -c cjar -b cjar -k -H "Content-Type: application/json" -X POST https://${bmc}/login -d "{\"…
29 - If passing in the username/password as part of the URL, no unique login call
40 $ curl -k -X GET https://root:0penBmc@${bmc}/xyz/openbmc_project/list
43 - Token based authentication.
[all …]
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | max20751.rst | 10 Addresses scanned: -
14 Application note: https://pdfserv.maximintegrated.com/en/an/AN5941.pdf
16 Author: Guenter Roeck <linux@roeck-us.net>
20 -----------
29 Usage Notes
30 -----------
32 This driver does not auto-detect devices. You will have to instantiate the
33 devices explicitly. Please see Documentation/i2c/instantiating-devices.rst for
38 ---------------------
44 -------------
|
| /openbmc/linux/Documentation/networking/ |
| H A D | dccp.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 - Introduction
10 - Missing features
11 - Socket options
12 - Sysctl variables
13 - IOCTLs
14 - Other tunables
15 - Notes
22 for real-time and multimedia (streaming) traffic.
26 implementation, this is the TCP-like CCID2 (RFC 4341). Additional CCIDs, such as
[all …]
|
| H A D | cdc_mbim.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 cdc_mbim - Driver for CDC MBIM Mobile Broadband modems
24 -----------
26 :Valid Range: N/Y (0-1)
46 userspace MBIM management application always is required to enable a
51 - mbimcli (included with the libmbim [3] library), and
52 - ModemManager [4]
55 management application:
57 - open the control channel
58 - configure network connection settings
[all …]
|
| /openbmc/openbmc/poky/documentation/ref-manual/ |
| H A D | resources.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
7 .. _resources-intro:
17 .. _resources-contributions:
26 code, see the :doc:`../contributor-guide/index`.
28 .. _resources-bugtracker:
48 - The ":doc:`../contributor-guide/report-defect`"
51 - The Yocto Project :yocto_wiki:`Bugzilla wiki page </Bugzilla_Configuration_and_Bug_Tracking>`
55 .. _resources-mailinglist:
66 - :yocto_lists:`/g/yocto` --- general Yocto Project
69 - :yocto_lists:`/g/yocto-patches` --- patch contribution mailing list for Yocto
[all …]
|
| /openbmc/linux/Documentation/bpf/ |
| H A D | prog_cgroup_sysctl.rst | 1 .. SPDX-License-Identifier: (LGPL-2.1 OR BSD-2-Clause)
8 provides cgroup-bpf hook for sysctl.
31 (``1``). This field is read-only.
34 or written. This field is read-write. Writing to the field sets the starting
38 when it's called by user space on ``file_pos > 0``. Writing non-zero
55 If program returns ``0`` user space will get ``-1`` from ``read(2)`` or
73 on ``ctx->write == 1``;
77 overridden starting from the current ``ctx->file_pos``. If the whole value
79 to the helper. This helper can be used only on ``ctx->write == 1``. New
102 6. Notes
[all …]
|
| /openbmc/linux/Documentation/networking/device_drivers/ethernet/intel/ |
| H A D | iavf.rst | 1 .. SPDX-License-Identifier: GPL-2.0+
8 Copyright(c) 2013-2018 Intel Corporation.
13 - Overview
14 - Identifying Your Adapter
15 - Additional Configurations
16 - Known Issues/Troubleshooting
17 - Support
30 The guest OS loading the iavf driver must support MSI-X interrupts.
53 ---------------------
58 # dmesg -n 8
[all …]
|
| /openbmc/linux/Documentation/riscv/ |
| H A D | boot-image-header.rst | 2 Boot image header in RISC-V Linux
8 This document only describes the boot image header details for RISC-V Linux.
10 The following 64-byte header is present in decompressed Linux kernel image::
25 ARM64 header. Thus, both ARM64 & RISC-V header can be combined into one common
28 Notes subtitle
31 - This header is also reused to support EFI stub for RISC-V. EFI specification
33 load it as an EFI application. In order to support EFI stub, code0 is replaced
37 - version field indicate header version number
47 - The "magic" field is deprecated as of version 0.2. In a future
52 - In current header, the flags field has only one field.
[all …]
|
| /openbmc/openbmc/poky/meta/lib/oe/ |
| H A D | patch.py | 4 # SPDX-License-Identifier: GPL-2.0-only
37 # print("cwd: %s -> %s" % (olddir, dir))
45 stdout = stdout.decode('utf-8')
46 stderr = stderr.decode('utf-8')
53 bb.note("--- Patch fuzz start ---\n%s\n--- Patch fuzz end ---" % format(stdout))
138 for encoding in ['utf-8', 'latin-1']:
144 if line.startswith('--- '):
197 runcmd(["sh", "-c", " ".join(shellcmd)], self.dir)
215 self._removePatch(os.path.join(self.patchdir, patches[-1].strip()))
232 …shellcmd = ["cat", patch['file'], "|", "patch", "--no-backup-if-mismatch", "-p", patch['strippath'…
[all …]
|
| /openbmc/linux/Documentation/usb/ |
| H A D | iuu_phoenix.rst | 10 bring a ttyUSB[0-x] interface. This driver must be
11 used by your favorite application to pilot the IUU
50 - clockmode will provide 3 different base settings commonly adopted by
57 - boost provide a way to overclock the reader ( my favorite :-) )
67 - cdmode permit to setup the signal used to inform the userland ( ioctl answer )
70 - xmas is completely useless except for your eyes. This is one of my friend who was
75 - debug will produce a lot of debugging messages...
78 Last notes
|