| /freebsd/sys/contrib/device-tree/Bindings/arm/samsung/ |
| H A D | samsung-secure-firmware.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/arm/samsung/samsung-secure-firmware.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Samsung Exynos Secure Firmware
10 - Krzysztof Kozlowski <krzk@kernel.org>
15 - const: samsung,secure-firmware
19 Address of non-secure SYSRAM used for communication with firmware.
23 - compatible
24 - reg
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/arm/amlogic/ |
| H A D | amlogic,meson-gx-ao-secure.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/arm/amlogic/amlogic,meson-gx-ao-secure.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: Amlogic Meson Firmware registers Interface
11 - Neil Armstrong <neil.armstrong@linaro.org>
15 secure firmware.
22 const: amlogic,meson-gx-ao-secure
24 - compatible
29 - items:
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/arm/ |
| H A D | secure.txt | 1 * ARM Secure world bindings
4 "Normal" and "Secure". Most devicetree consumers (including the Linux
6 world or the Secure world. However some devicetree consumers are
8 visible only in the Secure address space, only in the Normal address
10 virtual machine which boots Secure firmware and wants to tell the
11 firmware about the layout of the machine via devicetree.)
13 The general principle of the naming scheme for Secure world bindings
14 is that any property that needs a different value in the Secure world
15 can be supported by prefixing the property name with "secure-". So for
16 instance "secure-foo" would override "foo". For property names with
[all …]
|
| /freebsd/usr.sbin/bluetooth/iwmbtfw/ |
| H A D | main.c | 1 /*-
2 * SPDX-License-Identifier: BSD-2-Clause
49 #define _DEFAULT_IWMBT_FIRMWARE_PATH "/usr/share/firmware/intel"
93 if ((iwmbt_list[i].product_id == d->idProduct) && in iwmbt_is_supported()
94 (iwmbt_list[i].vendor_id == d->idVendor)) { in iwmbt_is_supported()
156 iwmbt_info("status 0x%02x", ver->status); in iwmbt_dump_version()
157 iwmbt_info("hw_platform 0x%02x", ver->hw_platfor in iwmbt_dump_version()
[all...] |
| /freebsd/lib/libsecureboot/efi/include/Guid/ |
| H A D | GlobalVariable.h | 3 Copyright (c) 2006 - 2018, Intel Corporation. All rights reserved.<BR>
7 http://opensource.org/licenses/bsd-license.php
30 // other internal firmware data variables that are not defined here must be
33 // only permit the creation of variables with a UEFI Specification-defined
37 // L"Boot####" - A boot load option.
38 // L"Driver####" - A driver load option.
39 // L"SysPrep####" - A System Prep application load option.
40 // L"Key####" - Describes hot key relationship with a Boot#### load option.
47 /// The language codes that the firmware supports. This value is deprecated.
57 /// The firmware's boot managers timeout, in seconds, before initiating the default boot selection.
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/firmware/ |
| H A D | intel,stratix10-svc.txt | 3 Intel Stratix10 SoC is composed of a 64 bit quad-core ARM Cortex A53 hard
4 processor system (HPS) and Secure Device Manager (SDM). When the FPGA is
10 communication with SDM, only the secure world of software (EL3, Exception
18 driver also manages secure monitor call (SMC) to communicate with secure monitor
22 -------------------
24 the firmware node.
26 - compatible: "intel,stratix10-svc" or "intel,agilex-svc"
27 - method: smc or hvc
28 smc - Secure Monitor Call
29 hvc - Hypervisor Call
[all …]
|
| H A D | amlogic,meson-gxbb-sm.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/firmware/amlogic,meson-gxbb-sm.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Amlogic Secure Monitor (SM)
10 In the Amlogic SoCs the Secure Monitor code is used to provide access to the
14 - Neil Armstrong <neil.armstrong@linaro.org>
19 - const: amlogic,meson-gxbb-sm
20 - items:
21 - const: amlogic,meson-gx-sm
[all …]
|
| H A D | qcom,scm.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/firmware/qcom,scm.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: QCOM Secure Channel Manager (SCM)
10 Qualcomm processors include an interface to communicate to the secure firmware.
12 These can include CPU power up/down, HDCP requests, loading of firmware,
16 - Bjorn Andersson <bjorn.andersson@linaro.org>
17 - Robert Marko <robimarko@gmail.com>
18 - Guru Das Srinagesh <quic_gurus@quicinc.com>
[all …]
|
| H A D | qcom,scm.txt | 1 QCOM Secure Channel Manager (SCM)
3 Qualcomm processors include an interface to communicate to the secure firmware.
5 can include CPU power up/down, HDCP requests, loading of firmware, and other
9 - compatible: must contain one of the following:
10 * "qcom,scm-apq8064"
11 * "qcom,scm-apq8084"
12 * "qcom,scm-ipq4019"
13 * "qcom,scm-ipq806x"
14 * "qcom,scm-ipq8074"
15 * "qcom,scm-mdm9607"
[all …]
|
| H A D | cznic,turris-mox-rwtm.txt | 1 Turris Mox rWTM firmware driver
4 - compatible : Should be "cznic,turris-mox-rwtm"
5 - mboxes : Must contain a reference to associated mailbox
8 compatible device running the Mox's rWTM firmware in the secure processor (for
9 example it is possible to flash this firmware into EspressoBin).
13 firmware {
14 turris-mox-rwtm {
15 compatible = "cznic,turris-mox-rwtm";
|
| H A D | brcm,kona-smc.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/firmware/brcm,kona-smc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Broadcom Kona family Secure Monitor bounce buffer
10 A bounce buffer used for non-secure to secure communications.
13 - Florian Fainelli <f.fainelli@gmail.com>
18 - enum:
19 - brcm,bcm11351-smc
20 - brcm,bcm21664-smc
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/security/tpm/ |
| H A D | google,cr50.txt | 1 * H1 Secure Microcontroller with Cr50 Firmware on SPI Bus.
3 H1 Secure Microcontroller running Cr50 firmware provides several
4 functions, including TPM-like functionality. It communicates over
8 - compatible: Should be "google,cr50".
9 - spi-max-frequency: Maximum SPI frequency.
17 spi-max-frequency = <800000>;
|
| /freebsd/sys/contrib/device-tree/Bindings/mailbox/ |
| H A D | arm,mhu.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jassi Brar <jaswinder.singh@linaro.org>
13 The ARM's Message-Handling-Unit (MHU) is a mailbox controller that has 3
19 be a 'Secure' resource, hence can't be used by Linux running NS.
22 interrupt signal using a 32-bit register, with all 32-bits logically ORed
28 interrupt. Each of the 32-bits can be used as "doorbell" to alert the remote
37 - arm,mhu
38 - arm,mhu-doorbell
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/firmware/meson/ |
| H A D | meson_sm.txt | 1 * Amlogic Secure Monitor
3 In the Amlogic SoCs the Secure Monitor code is used to provide access to the
6 Required properties for the secure monitor node:
7 - compatible: Should be "amlogic,meson-gxbb-sm"
11 firmware {
12 sm: secure-monitor {
13 compatible = "amlogic,meson-gxbb-sm";
|
| /freebsd/sys/contrib/device-tree/Bindings/firmware/xilinx/ |
| H A D | xlnx,zynqmp-firmware.txt | 1 -----------------------------------------------------------------
2 Device Tree Bindings for the Xilinx Zynq MPSoC Firmware Interface
3 -----------------------------------------------------------------
5 The zynqmp-firmware node describes the interface to platform firmware.
6 ZynqMP has an interface to communicate with secure firmware. Firmware
7 driver provides an interface to firmware APIs. Interface APIs can be
14 - compatible: Must contain any of below:
15 "xlnx,zynqmp-firmware" for Zynq Ultrascale+ MPSoC
16 "xlnx,versal-firmware" for Versal
17 - method: The method of calling the PM-API firmware layer.
[all …]
|
| H A D | xlnx,zynqmp-firmware.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/firmware/xilinx/xlnx,zynqmp-firmware.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Xilinx firmware driver
10 - Nava kishore Manne <nava.kishore.manne@amd.com>
12 description: The zynqmp-firmware node describes the interface to platform
13 firmware. ZynqMP has an interface to communicate with secure firmware.
14 Firmware driver provides an interface to firmware APIs. Interface APIs
23 - description: For implementations complying for Zynq Ultrascale+ MPSoC.
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/arm/firmware/ |
| H A D | tlm,trusted-foundations.txt | 2 -------------------
4 Boards that use the Trusted Foundations secure monitor can signal its
5 presence by declaring a node compatible with "tlm,trusted-foundations"
6 under the /firmware/ node
9 - compatible: "tlm,trusted-foundations"
10 - tlm,version-major: major version number of Trusted Foundations firmware
11 - tlm,version-minor: minor version number of Trusted Foundations firmware
14 firmware {
15 trusted-foundations {
16 compatible = "tlm,trusted-foundations";
[all …]
|
| H A D | tlm,trusted-foundations.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/arm/firmware/tlm,trusted-foundation
[all...] |
| H A D | linaro,optee-tz.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/arm/firmware/linaro,optee-tz.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: OP-TEE
10 - Jens Wiklander <jens.wiklander@linaro.org>
13 OP-TEE is a piece of software using hardware features to provide a Trusted
25 const: linaro,optee-tz
30 This interrupt which is used to signal an event by the secure world
31 software is expected to be either a per-cpu interrupt or an
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/timer/ |
| H A D | arm,arch_timer.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Marc Zyngier <marc.zyngier@arm.com>
11 - Mark Rutland <mark.rutland@arm.com>
13 ARM cores may have a per-core architected timer, which provides per-cpu timers,
17 The per-core architected timer is attached to a GIC to deliver its
18 per-processor interrupts via PPIs. The memory mapped timer is attached to a GIC
24 - items:
25 - const: arm,cortex-a15-timer
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/gpu/host1x/ |
| H A D | nvidia,tegra234-nvdec.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/gpu/host1x/nvidia,tegra234-nvdec.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
15 - Thierry Reding <treding@gmail.com>
16 - Mikko Perttunen <mperttunen@nvidia.com>
20 pattern: "^nvdec@[0-9a-f]*$"
24 - nvidia,tegra234-nvdec
32 clock-names:
34 - const: nvdec
[all …]
|
| /freebsd/share/man/man4/ |
| H A D | wpi.4 | 1 .\"-
2 .\" SPDX-License-Identifier: BSD-2-Clause
4 .\" Copyright (c) 2004-2007
42 .Bd -ragged -offset indent
48 .Cd "device firmware"
63 .Cm adhoc-demo ,
68 This driver requires the wpifw firmware module
79 Wi-Fi Protected Access (WPA-PSK and WPA2-PSK).
83 to secure wireless communication,
95 .Bl -tag -width "/usr/share/doc/legal/intel_wpi.LICENSE" -compact
[all …]
|
| /freebsd/contrib/file/magic/Magdir/ |
| H A D | uf2 | 2 #------------------------------------------------------------------------------
4 # uf2: file(1) magic for UF2 firmware image files
10 0 string UF2\n UF2 firmware image
23 # | jq -r '.[] | ">>28\tlelong\t\(.id)\t\(.description)"' | sort -n -k 3` && \
24 # perl -0777 -i -pe \
42 >>28 lelong 0x2b88d29c ESP32-C2
46 >>28 lelong 0x332726f6 ESP32-H2
48 >>28 lelong 0x3d308e94 ESP32-P4
49 >>28 lelong 0x4b684d71 Sipeed MaixPlay-U4 (BL618)
55 >>28 lelong 0x540ddf62 ESP32-C6
[all …]
|
| H A D | firmware | 1 #------------------------------------------------------------------------------
2 # $File: firmware,v 1.13 2024/09/04 19:04:03 christos Exp $
3 # firmware: file(1) magic for firmware files
6 # https://github.com/MatrixEditor/frontier-smart-api/blob/main/docs/firmware-2.0.md#11-header-struc…
7 # examples: https://github.com/cweiske/frontier-silicon-firmwares
9 >4 lelong 0x7c Frontier Silicon firmware download
14 # HPE iLO firmware update image
19 >16 ubeshort =0xCFDD HPE iLO2 firmware update image
20 >16 ubeshort =0x6444 HPE iLO1 firmware update image
22 0 string iLO3\x20v\x20 HPE iLO3 firmware update image,
[all …]
|
| /freebsd/sys/contrib/device-tree/src/arm64/qcom/ |
| H A D | qcs8550.dtsi | 1 // SPDX-License-Identifier: BSD-3-Clause
3 * Copyright (c) 2023-2024, Qualcomm Innovation Center, Inc. All rights reserved.
8 /delete-node/ &reserved_memory;
11 reserved_memory: reserved-memory {
12 #address-cells = <2>;
13 #size-cells = <2>;
18 * 1. Firmware related regions which aren't shared with kernel.
20 * indicate the firmware related reserved information. Bootloader
26 * used, release note of the firmware have such kind of information.
27 * 2. Firmware related memory regions which are shared with Kernel
[all …]
|