/openbmc/linux/Documentation/devicetree/bindings/leds/ |
H A D | awinic,aw200xx.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Martin Kurbanov <mmkurbanov@sberdevices.ru> 19 aw20036 - https://www.awinic.com/en/productDetail/AW20036QNR#tech-docs 20 aw20054 - https://www.awinic.com/en/productDetail/AW20054QNR#tech-docs 21 aw20072 - https://www.awinic.com/en/productDetail/AW20072QNR#tech-docs 26 - awinic,aw20036 27 - awinic,aw20054 28 - awinic,aw20072 [all …]
|
/openbmc/libpldm/docs/checklists/ |
H A D | changes.md | 5 - [Good Practices in Library Design, Implementation, and Maintenance - Ulrich 10 - [How Do I Make This Hard to Misuse? - Rusty Russell][rusty-api-scale-good] 12 [rusty-api-scale-good]: https://ozlabs.org/~rusty/index.cgi/tech/2008-03-30.html 14 - [What If I Don't Actually Like My Users? - Rusty Russell][rusty-api-scale-bad] 16 [rusty-api-scale-bad]: https://ozlabs.org/~rusty/index.cgi/tech/2008-04-01.html 18 - [Red flags that indicate questionable quality - Lennart 19 Poettering][poettering-library-red-flags] 21 [poettering-library-red-flags]: 24 - [Not sure if this is a gcc bug or some weird corner of UB or what... - Andrew 25 Zonenberg][azonenberg-packed-struct] [all …]
|
/openbmc/linux/Documentation/devicetree/bindings/hwmon/ |
H A D | amd,sbrmi.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 8 Sideband Remote Management Interface (SB-RMI) compliant 12 - Akshay Gupta <Akshay.Gupta@amd.com> 15 SB Remote Management Interface (SB-RMI) is an SMBus compatible 17 Mailbox Service Request and resembles a typical 8-pin remote power 24 - amd,sbrmi 30 of the SoC register reference. The SB-RMI address is normally 78h for 34 https://www.amd.com/en/support/tech-docs?keyword=55898 [all …]
|
/openbmc/openbmc/meta-hpe/ |
H A D | README.md | 10 The HPE DL360 Gen10 OpenBMC Proof of Concept is a two-socket, 1U general purpose server. 11 …ttps://buy.hpe.com/us/en/servers/rack-servers/proliant-dl300-servers/proliant-dl360-server/hpe-pro… 15 …l run only on a modified server or on the open source firmware CI system at https://osfci.tech/ci/. 17 This boot process for the GXP ASIC begins with a binary bootblock before starting U-Boot, 30 bitbake obmc-phosphor-image 36 ------------ 38 meta-hpe patches are reviewed using the Gerrit instance at 42 [here](https://github.com/openbmc/docs/blob/master/CONTRIBUTING.md#submitting-changes-via-gerrit-se… 43 https://github.com/openbmc/meta-hpe is a hosting mirror only. GitHub 48 - meta-hpe uses the [OE style [all …]
|
/openbmc/linux/Documentation/hwmon/ |
H A D | sbrmi.rst | 1 .. SPDX-License-Identifier: GPL-2.0-or-later 8 * Sideband Remote Management Interface (SB-RMI) compliant AMD SoC 15 To instantiate this driver on an AMD CPU with SB-RMI 22 As mentioned in AMD's APML specification, The SB-RMI address is 27 Datasheet: The SB-RMI interface and protocol along with the Advanced 31 https://www.amd.com/en/support/tech-docs?keyword=55898 36 ----------- 39 (SB-RMI) module from the external SMBus master that can be used to report socket 40 power on AMD platforms using mailbox command and resembles a typical 8-pin remote 45 sysfs-Interface [all …]
|
/openbmc/qemu/docs/system/i386/ |
H A D | amd-memory-encryption.rst | 6 SEV is an extension to the AMD-V architecture which supports running encrypted 15 AMD secure processor (AMD-SP), which is present in AMD SOCs. Firmware running 16 inside the AMD-SP provides commands to support a common VM lifecycle. This 21 Secure Encrypted Virtualization - Encrypted State (SEV-ES) builds on the SEV 28 Launching (SEV and SEV-ES) 29 -------------------------- 38 For a SEV-ES guest, the ``LAUNCH_UPDATE_VMSA`` command is also used to encrypt the 43 its public Diffie-Hellman key (PDH) and session parameters. These inputs 44 should be treated as a binary blob and must be passed as-is to the SEV firmware. 48 in bad measurement). The guest policy is a 4-byte data structure containing [all …]
|
/openbmc/linux/drivers/ata/ |
H A D | pata_it8213.c | 1 // SPDX-License-Identifier: GPL-2.0-only 3 * pata_it8213.c - iTE Tech. Inc. IT8213 PATA driver 25 * it8213_pre_reset - probe begin 38 struct ata_port *ap = link->ap; in it8213_pre_reset() 39 struct pci_dev *pdev = to_pci_dev(ap->host->dev); in it8213_pre_reset() 40 if (!pci_test_config_bits(pdev, &it8213_enable_bits[ap->port_no])) in it8213_pre_reset() 41 return -ENOENT; in it8213_pre_reset() 47 * it8213_cable_detect - check for 40/80 pin 56 struct pci_dev *pdev = to_pci_dev(ap->host->dev); in it8213_cable_detect() 59 if (tmp & 2) /* The initial docs are incorrect */ in it8213_cable_detect() [all …]
|
/openbmc/docs/designs/ |
H A D | expired-password.md | 7 Created: 2019-07-24 67 - The BMC's initial password must be expired when the new EXPIRED_PASSWORD image 69 - An account with an expired password must not be allowed to use the BMC (except 71 - There must be a way to change the expired password using a supported 76 - The BMC automatically connects to its management network which offers 79 - The BMC is operated from its management network. 83 - The BMC has at least one account with a default password built in. 84 - The BMC can update the password; for example, the `/etc/passwd` file is 93 `passwd --expire root` command. This administratively expires the password 129 This can be either from a network-facing or in-band password changing [all …]
|
/openbmc/linux/Documentation/RCU/ |
H A D | RTFP.txt | 4 This document describes RCU-related publications, and is followed by 19 with short-lived threads, such as the K42 research operating system. 20 However, Linux has long-lived tasks, so more is needed. 23 serialization, which is an RCU-like mechanism that relies on the presence 27 that these overheads were not so expensive in the mid-80s. Nonetheless, 28 passive serialization appears to be the first deferred-destruction 30 has lapsed, so this approach may be used in non-GPL software, if desired. 34 In 1987, Rashid et al. described lazy TLB-flush [RichardRashid87a]. 36 this paper helped inspire the update-side batching used in the later 38 a description of Argus that noted that use of out-of-date values can [all …]
|
/openbmc/linux/Documentation/ABI/testing/ |
H A D | sysfs-devices-system-cpu | 2 Date: pre-git history 3 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org> 18 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org> 37 See Documentation/admin-guide/cputopology.rst for more information. 43 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org> 58 Contact: Linux memory management mailing list <linux-mm@kvack.org> 67 /sys/devices/system/cpu/cpu42/node2 -> ../../node/node2 77 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org> 89 core_siblings_list: human-readable list of the logical CPU 99 thread_siblings_list: human-readable list of cpuX's hardware [all …]
|
/openbmc/qemu/hw/usb/ |
H A D | quirks-ftdi-ids.h | 5 * Philipp Gühring - pg@futureware.at - added the Device ID of the USB relais 24 #define FTDI_4232H_PID 0x6011 /* Quad channel hi-speed device */ 25 #define FTDI_232H_PID 0x6014 /* Single channel hi-speed device */ 26 #define FTDI_FTX_PID 0x6015 /* FT-X series (FT201X, FT230X, FT231X, etc) */ 31 /*** third-party PIDs (using FTDI_VID) ***/ 37 * http://www.open-rd.org 69 #define FTDI_TURTELIZER_PID 0xBDC8 /* JTAG/RS-232 adapter by egnite GmbH */ 79 #define FTDI_NZR_SEM_USB_PID 0xC1E0 /* NZR SEM-LOG16+ */ 82 * RR-CirKits LocoBuffer USB (http://www.rr-cirkits.com) 94 /* www.starting-point-systems.com µChameleon device */ [all …]
|
/openbmc/linux/drivers/hid/ |
H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only 22 most commonly used to refer to the USB-HID specification, but other 27 removed from the HID bus by the transport-layer drivers, such as 30 For docs and specs, see https://www.usb.org/developers/hidpage/ 58 to work on raw hid events when they want to, and avoid using transport-specific 64 tristate "User-space I/O driver support for HID subsystem" 67 Say Y here if you want to provide HID I/O Drivers from user-space. 68 This allows to write I/O drivers in user-space and feed the data from 71 user-space device. 73 This driver cannot be used to parse HID-reports in user-space and write [all …]
|
/openbmc/linux/drivers/usb/serial/ |
H A D | ftdi_sio_ids.h | 1 /* SPDX-License-Identifier: GPL-2.0 */ 6 * Philipp Gühring - pg@futureware.at - added the Device ID of the USB relais 25 #define FTDI_4232H_PID 0x6011 /* Quad channel hi-speed device */ 26 #define FTDI_232H_PID 0x6014 /* Single channel hi-speed device */ 27 #define FTDI_FTX_PID 0x6015 /* FT-X series (FT201X, FT230X, FT231X, etc) */ 28 #define FTDI_FT2233HP_PID 0x6040 /* Dual channel hi-speed device with PD */ 29 #define FTDI_FT4233HP_PID 0x6041 /* Quad channel hi-speed device with PD */ 30 #define FTDI_FT2232HP_PID 0x6042 /* Dual channel hi-speed device with PD */ 31 #define FTDI_FT4232HP_PID 0x6043 /* Quad channel hi-speed device with PD */ 32 #define FTDI_FT233HP_PID 0x6044 /* Dual channel hi-speed device with PD */ [all …]
|
/openbmc/linux/Documentation/admin-guide/ |
H A D | ras.rst | 33 ------------- 47 Self-Monitoring, Analysis and Reporting Technology (SMART). 55 --------------- 68 * **Correctable Error (CE)** - the error detection mechanism detected and 72 * **Uncorrected Error (UE)** - the amount of errors happened above the error 73 correction threshold, and the system was unable to auto-correct. 75 * **Fatal Error** - when an UE error happens on a critical component of the 79 * **Non-fatal Error** - when an UE error happens on an unused component, 87 The mechanism for handling non-fatal errors is usually complex and may 92 ------------------------------------ [all …]
|
/openbmc/linux/Documentation/networking/ |
H A D | arcnet-hardware.rst | 1 .. SPDX-License-Identifier: GPL-2.0 11 2) This file is no longer Linux-specific. It should probably be moved out 17 e-mail apenwarr@worldvisions.ca with any settings for your particular card, 39 There are two "types" of ARCnet - STAR topology and BUS topology. This 46 well-designed standard. It uses something called "modified token passing" 47 which makes it completely incompatible with so-called "Token Ring" cards, 63 programming interface also means that when high-performance hardware 73 although they are generally kept down to the Ethernet-style 1500 bytes. 91 - Avery Pennraun <apenwarr@worldvisions.ca> 92 - Stephen A. Wood <saw@hallc1.cebaf.gov> [all …]
|
/openbmc/openbmc/poky/bitbake/lib/bs4/ |
H A D | CHANGELOG | 37 Two scripts: demonstrate_parser_differences.py and test-all-versions. 169 * If the charset-normalizer Python module 170 (https://pypi.org/project/charset-normalizer/) is installed, Beautiful 188 * Some time ago, the misleadingly named "text" argument to find-type 207 replacement on PyPI, iconv_codecs, is GPL-licensed, so we can't use 208 it--it's also quite old.) 225 definition of 'text' than a user who calls div.get_text()--otherwise 272 https://html.spec.whatwg.org/multipage/parsing.html#parsing-with-a-known-character-encoding 275 byte-order-mark sniffing is run, then encodings in 'user_encodings' 334 * If you encode a document with a Python-specific encoding like [all …]
|
/openbmc/openbmc/poky/meta/conf/distro/include/ |
H A D | maintainers.inc | 1 # Yocto Project / OpenEmbedded-Core (OE-Core) Maintainers File 6 # OE-Core mail list (openembedded-core@lists.openembedded.org) 7 # For recipes in meta-yocto please use the Poky list (poky@lists.yoctoproject.org) 14 # - look in the Yocto Project Bugzilla 18 # - look through recent entries of the appropriate mailing list archives 19 # (http://lists.linuxtogo.org/pipermail/openembedded-core or 26 # RECIPE_MAINTAINER:pn-<recipe name> = "Full Name <address@domain>" 30 RECIPE_MAINTAINER:pn-acl = "Chen Qi <Qi.Chen@windriver.com>" 31 RECIPE_MAINTAINER:pn-acpica = "Ross Burton <ross.burton@arm.com>" 32 RECIPE_MAINTAINER:pn-acpid = "Ross Burton <ross.burton@arm.com>" [all …]
|
/openbmc/linux/ |
H A D | CREDITS | 1 This is at least a partial credits-file of people that have 4 scripts. The fields are: name (N), email (E), web-address 6 snail-mail address (S). 10 ---------- 51 D: in-kernel DRM Maintainer 71 E: tim_alpaerts@toyota-motor-europe.com 75 S: B-2610 Wilrijk-Antwerpen 80 W: http://www-stu.christs.cam.ac.uk/~aia21/ 101 D: Maintainer of ide-cd and Uniform CD-ROM driver, 102 D: ATAPI CD-Changer support, Major 2.1.x CD-ROM update. [all …]
|
H A D | MAINTAINERS | 5 --------------------------------------------------- 21 W: *Web-page* with status/info 23 B: URI for where to file *bugs*. A web-page with detailed bug 28 patches to the given subsystem. This is either an in-tree file, 29 or a URI. See Documentation/maintainer/maintainer-entry-profile.rst 46 N: [^a-z]tegra all files whose path contains tegra 64 ---------------- 83 3WARE SAS/SATA-RAID SCSI DRIVERS (3W-XXXX, 3W-9XXX, 3W-SAS) 85 L: linux-scsi@vger.kernel.org 88 F: drivers/scsi/3w-* [all …]
|