firmware\-name (full) in projects: freebsd

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched +full:firmware +full:- +full:name (Results 1 – 25 of 1025) sorted by relevance

12 3 4 5 6 7 8 9 10 >>...41

/freebsd/sys/kern/
H A D	subr_firmware.c	`1 /- 2 SPDX-License-Identifier: BSD-2-Clause 4 * Copyright (c) 2005-2008, Sam Leffler <sam@errno.com> 33 #include <sys/firmware.h> 53 * Loadable firmware support. See sys/sys/firmware.h and firmware( 155 lookup(const char * name) lookup() argument 192 char name; firmware_register() local 575 char name; firmware_binary_files() local [all...]`
/freebsd/share/man/man9/
H A D	firmware.9	`27 .Sh NAME 33 .Nd firmware image loading and management 39 .Bd -literal 40 struct firmware { 41 const char name; / system-wide name / 53 .Fa "const struct firmware parent" 62 .Fn firmware_put "const struct firmware *fp" "int flags" 65 .Nm firmware 67 .Nm firmware images 71 .Nm firmware image [all …]`
/freebsd/sys/sys/
H A D	firmware.h	1 /- 2 SPDX-License-Identifier: BSD-2-Clause 31 * Loadable firmware support. 33 * The firmware abstraction provides an interface for loading firmware 36 * Firmware images are usually embedded in kernel loadable modules that can 37 * be loaded on-demand or pre-loaded as desired. Modules may contain 38 * one or more firmware images that are stored as opaque data arrays 39 * and registered with a unique string name. Clients request 40 * firmware by name, and are returned a struct firmware * below on success. 41 * The kernel keeps track of references to firmware images to allow/prevent [all …]
/freebsd/sys/contrib/device-tree/Bindings/remoteproc/
H A D	ti,pru-rproc.yaml	`1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/remoteproc/ti,pru-rpro [all...]`
H A D	ti,k3-m4f-rproc.yaml	`1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/remoteproc/ti,k3-m4f-rproc.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Hari Nagalla <hnagalla@ti.com> 11 - Mathieu Poirier <mathieu.poirier@linaro.org> 20 $ref: /schemas/arm/keystone/ti,k3-sci-common.yaml# 25 - ti,am64-m4fss 27 power-domains: 30 "#address-cells": [all …]`
H A D	ti,omap-remoteproc.yaml	`1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/remoteproc/ti,omap-remotepro [all...]`
/freebsd/usr.sbin/bluetooth/bcmfw/
H A D	bcmfw.8	1 .\"- 2 .\" SPDX-License-Identifier: BSD-2-Clause 31 .Sh NAME 33 .Nd download firmware for Broadcom BCM2033 Bluetooth USB devices 38 .Fl m Ar mini-driver_file_name 43 utility downloads the specified mini-driver and firmware files to the specified 54 Due to copyright issues I will no longer provide mini-driver and firmware 56 These files can be obtained from the Linux BlueZ bluez-firmware package. 62 I am using the following files from the bluez-firmware-1.0 package: 64 .Dl "MD5 (BCM2033-MD.hex) = 5580317158d07fc4ace90af04f8e1c73" [all …]
/freebsd/sys/contrib/device-tree/Bindings/net/
H A D	qualcomm-bluetooth.txt	`2 --------------------- 11 - compatible: should contain one of the following: 12 * "qcom,qca6174-bt" 13 * "qcom,qca9377-bt" 14 * "qcom,wcn3990-bt" 15 * "qcom,wcn3991-bt" 16 * "qcom,wcn3998-bt" 17 * "qcom,qca6390-bt" 19 Optional properties for compatible string qcom,qca6174-bt: 21 - enable-gpios: gpio specifier used to enable chip [all …]`
H A D	qcom,ipa.yaml	`1 # SPDX-License-Identifier: GPL-2.0 OR BSD-2-Clause 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Alex Elder <elder@kernel.org> 21 and has a distinct interrupt and a separately-defined address space. 28 - \| 29 -------- --------- 31 \| AP +<---. .----+ Modem \| 32 \| +--. \| \| .->+ \| 34 -------- \| \| \| \| --------- [all …]`
/freebsd/share/man/man4/
H A D	openfirm.4	`1 .\"- 6 .\" at Lawrence Berkeley Laboratory under DARPA contract BG 91-66 and 17 .\" 3. Neither the name of the University nor the names of its contributors 34 .\"- 62 .Sh NAME 64 .Nd "Open Firmware interface" 73 .Tn Open Firmware 80 .Tn Open Firmware 95 .Bd -literal 128 works in a value-result fashion. [all …]`
H A D	isp.4	1 .\" Copyright (c) 2009-2020 Alexander Motin <mav@FreeBSD.org> 3 .\" Copyright (c) 1998-2001 Matthew Jacob, for NASA/Ames Research Center 13 .\" 3. The name of the author may not be used to endorse or promote products 30 .Sh NAME 37 .Bd -ragged -offset indent 46 .Bd -literal -offset indent 57 Support is available for Public and Private loops, Point-to-Point 60 Supported FC-Tape functionality is highly recommended for connections 62 It encompasses four elements from the T-10 FCP-4 specification: 63 .Bl -bullet -offset indent [all …]
H A D	iwi.4	`1 .\"- 2 .\" SPDX-License-Identifier: BSD-2-Clause 4 .\" Copyright (c) 2004-2006 32 .Sh NAME 39 .Bd -ragged -offset indent 44 .Cd "device firmware" 50 .Bd -literal -offset indent 56 to acknowledge the firmware license (see below): 57 .Bd -literal -offset indent 72 This driver requires the firmware built with the [all …]`
H A D	rtwnfw.4	`10 .\" 2. The name of the author may not be used to endorse or promote products 27 .Sh NAME 29 .Nd "Firmware Module for Realtek Wireless driver" 34 .Bd -ragged -offset indent 38 This will include all firmware images inside the kernel. 39 If you want to pick only the firmware image for your network adapter choose one 41 .Bd -ragged -offset indent 42 .Cd "device rtwn-rtl8188eefw" 43 .Cd "device rtwn-rtl8188eufw" 44 .Cd "device rtwn-rtl8192cfwE_B" [all …]`
H A D	ipw.4	`1 .\"- 2 .\" SPDX-License-Identifier: BSD-2-Clause 4 .\" Copyright (c) 2004-2006 32 .Sh NAME 39 .Bd -ragged -offset indent 44 .Cd "device firmware" 50 .Bd -literal -offset indent 56 to acknowledge the firmware license (see below): 57 .Bd -literal -offset indent 72 This driver requires the firmware built with the [all …]`
H A D	wpi.4	`1 .\"- 2 .\" SPDX-License-Identifier: BSD-2-Clause 4 .\" Copyright (c) 2004-2007 35 .Sh NAME 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). 95 .Bl -tag -width "/usr/share/doc/legal/intel_wpi.LICENSE" -compact [all …]`
H A D	iwm.4	`1 .\"- 2 .\" SPDX-License-Identifier: BSD-2-Clause 4 .\" Copyright (c) 2004-2006 32 .Sh NAME 38 .Bd -ragged -offset indent 42 .Cd "device firmware" 45 You also need to select a firmware for your device. 47 .Bd -ragged -offset indent 60 .Bd -ragged -offset indent 69 .Bd -literal -offset indent [all …]`
H A D	iwn.4	`1 .\"- 2 .\" SPDX-License-Identifier: BSD-2-Clause 4 .\" Copyright (c) 2004-2006 32 .Sh NAME 39 .Bd -ragged -offset indent 43 .Cd "device firmware" 46 You also need to select a firmware for your device. 48 .Bd -ragged -offset indent 65 .Bd -ragged -offset indent 74 .Bd -literal -offset indent [all …]`
H A D	rtwn.4	`1 .\"- 2 .\" SPDX-License-Identifier: ISC 25 .Sh NAME 35 .Bd -ragged -offset indent 41 .Cd "device firmware" 47 .Bd -literal -offset indent 74 interface can be added (Note: RTL8821AU supports two non-monitor 77 All chips have hardware support for WEP, AES-CCM and TKIP encryption. 88 .Bl -bullet -offset indent -compact 106 .Bl -tag -width "/usr/share/doc/legal/realtek.LICENSE" -compact [all …]`
H A D	ipwfw.4	9 .\" 2. The name of the author may not be used to endorse or promote products 26 .Sh NAME 28 .Nd "Firmware Module for Intel PRO/Wireless 2100 driver" 33 .Bd -ragged -offset indent 37 This will include three firmware images inside the kernel. 38 If you want to pick only the firmware image for the mode you want to operate 40 .Bd -ragged -offset indent 49 .Bd -literal -offset indent 55 This module provides access to firmware sets for the 59 For the loaded firmware to be enabled for use the license at [all …]
/freebsd/sys/contrib/device-tree/src/arm64/qcom/
H A D	msm8996-oneplus3t.dts	`1 // SPDX-License-Identifier: GPL-2.0-only 6 /dts-v1/; 8 #include "msm8996-oneplus-common.dtsi" 13 chassis-type = "handset"; 14 qcom,board-id = <8 0 15811 26>, 20 firmware-name = "qcom/msm8996/oneplus3t/adsp.mbn"; 25 charge-full-design-microamp-hours = <3400000>; 26 voltage-max-design-microvolt = <4400000>; 32 zap-shader { 33 firmware-name = "qcom/msm8996/oneplus3t/a530_zap.mbn"; [all …]`
H A D	msm8996-oneplus3.dts	`1 // SPDX-License-Identifier: GPL-2.0-only 6 /dts-v1/; 8 #include "msm8996-oneplus-common.dtsi" 13 chassis-type = "handset"; 14 qcom,board-id = <8 0 15801 15>, <8 0 15801 16>; 15 qcom,msm-id = <246 0x30001>; 19 firmware-name = "qcom/msm8996/oneplus3/adsp.mbn"; 24 charge-full-design-microamp-hours = <3000000>; 25 voltage-max-design-microvolt = <4350000>; 31 zap-shader { [all …]`
/freebsd/sys/compat/linuxkpi/common/src/
H A D	linux_firmware.c	`1 /- 2 SPDX-License-Identifier: BSD-2-Clause 4 * Copyright (c) 2020-2021 The FreeBSD Foundation 36 #include <sys/firmware.h> 43 #include <linux/firmware.h> 44 #undef firmware 46 MALLOC_DEFINE(M_LKPI_FW, "lkpifw", "LinuxKPI firmware"); 62 const struct firmware fbdfw; in _linuxkpi_request_firmware() 70 return (-EINVAL); in _linuxkpi_request_firmware() 80 Linux can have a path in the firmware which is hard to replicate in _linuxkpi_request_firmware() [all …]`
/freebsd/sys/contrib/dev/athk/ath10k/
H A D	zzz_fw_ports_fwget.sh	`2 #- 3 # SPDX-License-Identifier: BSD-2-Clause 15 # linux-firmware.git repository you point this script to. 18 set -e 25 # Check pre-reqs 27 if [ $# -ne 1 ]; then 28 printf "USAGE: %s /path/to/linux-firmware.git\n" $0 >&2 32 if [ ! -e ${CHECKFILE} ]; then 38 if test ! -d ${LFWDIR} -o ! -e ${LFWDIR}/WHENCE; then 39 printf "ERROR: cannot find linux-firmware.git at '%s'\n" ${LFWDIR} >&2 [all …]`
/freebsd/sys/contrib/dev/iwlwifi/
H A D	zzz_fw_ports_fwget.sh	`2 #- 3 # SPDX-License-Identifier: BSD-2-Clause 15 # linux-firmware.git repository you point this script to. 17 # USAGE: please make sure to pre-load if_iwlwifi.ko so that we 25 set -e 27 # sysctl -n compat.linuxkpi.iwlwifi_pci_ids_name > iwlwifi_pci_ids_name.txt 33 # Check pre-reqs 35 if [ $# -ne 1 ]; then 36 printf "USAGE: %s /path/to/linux-firmware.git\n" $0 >&2 40 if [ ! -d cfg/ -o ! -e cfg/bz.c ]; then [all …]`
/freebsd/sys/contrib/device-tree/Bindings/soc/fsl/cpm_qe/qe/
H A D	firmware.txt	1 * Uploaded QE firmware 3 If a new firmware has been uploaded to the QE (usually by the 4 boot loader), then a 'firmware' child node should be added to the QE 5 node. This node provides information on the uploaded firmware that 9 - id: The string name of the firmware. This is taken from the 'id' 10 member of the qe_firmware structure of the uploaded firmware. 12 firmware they want is already present. 13 - extended-modes: The Extended Modes bitfield, taken from the 14 firmware binary. It is a 64-bit number represented 15 as an array of two 32-bit numbers. [all …]

12 3 4 5 6 7 8 9 10 >>...41