Home
last modified time | relevance | path

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

12345678910>>...23

/freebsd/usr.sbin/bluetooth/rtlbtfw/
H A Drtlbtfw.831 .Nd load firmware for Realtek 87XX/88XX Bluetooth USB devices
41 utility downloads the specified firmware file to the specified
47 work with Realtek 87XX/88XX chip based Bluetooth USB devices and some of
49 The identification is currently based on USB vendor ID/product ID pair and
53 and the 0-th interface class/subclass/protocol should be a Bluetooth RF
55 Non-Realtek devices are identified based on USB vendor ID/product ID pair.
57 Firmware files are available in the
58 .Pa comms/rtlbt-firmware
63 utility will query the device to determine which firmware image and board
67 .Bl -tag -width indent
[all …]
/freebsd/share/man/man4/
H A Drtwnfw.429 .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"
45 .Cd "device rtwn-rtl8192cfwE"
46 .Cd "device rtwn-rtl8192cfwT"
[all …]
H A Drtwn.41 .\"-
2 .\" SPDX-License-Identifier: ISC
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
109 firmware license
[all …]
H A Dice.42 .\" SPDX-License-Identifier: BSD-3-Clause
4 .\" Copyright (c) 2019-2020, Intel Corporation
73 .Bl -bullet -compact
89 .Sx Firmware Link Layer Discovery Protocol Agent
91 .Sx Link-Level Flow Control
99 .Sx Firmware Logging
113 .Sx Optics and auto-negotiation
115 .Sx PCI-Express Slot Bandwidth
223 Devices based on the Intel Ethernet 800 Series do not support RDMA when
236 To use RDMA monitoring, more MSI-X interrupts may need to be reserved.
[all …]
H A Dmwl.41 .\"-
39 .Bd -ragged -offset indent
43 .Cd "device firmware"
49 .Bd -literal -offset indent
55 driver provides support for IEEE 802.11n wireless network adapters based on
59 This driver requires the firmware built with the
66 and host-based access point operation modes.
77 algorithm implemented in the firmware.
79 AES-CCM, TKIP, and Michael cryptographic operations.
109 driver come in either Cardbus or mini-PCI packages.
[all …]
H A Dbwi.435 .Bd -ragged -offset indent
39 .Cd "device firmware"
45 .Bd -literal -offset indent
51 driver provides support for Broadcom BCM43xx based
63 This driver requires firmware to be loaded before it will work.
65 .Pa ports/net/bwi-firmware-kmod
72 driver supports Broadcom BCM43xx based wireless devices, including:
73 .Bl -column "Apple Airport Extreme" "BCM4306" "Mini PCI" "a/b/g" -offset 6n
77 .It "ASUS WL-100g BCM4306 CardBus b/g"
78 .It "ASUS WL-138g BCM4318 PCI b/g"
[all …]
H A Dbwn.434 .Bd -ragged -offset indent
44 .Cd "device firmware"
49 .Bd -literal -offset indent
55 driver provides support for Broadcom BCM43xx based
67 This driver requires firmware to be loaded before it will work.
69 .Pa ports/net/bwn-firmware-kmod
82 driver supports Broadcom BCM43xx based wireless devices, including:
83 .Bl -column "Apple Airport Extreme" "BCM4306" "Mini PCI" "a/b/g"
86 .It "ASUS WL-138g BCM4318 PCI b/g"
87 .It "Buffalo WLI-CB-G54S BCM4318 CardBus b/g"
[all …]
H A Dbnxt.431 .Nd "Broadcom NetXtreme-C/NetXtreme-E Family Ethernet driver"
36 .Bd -ragged -offset indent
44 .Bd -literal -offset indent
50 driver provides support for various NICs based on the Broadcom BCM57301/2/4,
58 driver provides support for various NICs based on the Broadcom NetXtreme-C and
59 NetXtreme-
[all...]
H A Dotusfw.420 .Nd "Firmware Module for AR9170 driver"
24 .Bd -ragged -offset indent
28 This will include the firmware image, AR9170, inside the kernel.
32 Alternatively, to load the firmware images as a module at boot time, place
35 .Bd -literal -offset indent
40 This module provides the firmware for the Atheros AR9170 based
44 .Xr firmware 9
H A Drsufw.420 .Nd "Firmware Module for Realtek driver"
24 .Bd -ragged -offset indent
28 This will include the firmware image, RTL8712, inside the kernel.
32 Alternatively, to load the firmware images as a module at boot time, place
35 .Bd -literal -offset indent
36 rsu-rtl8712fw_load="YES"
39 This module provides the firmware for the Realtek RTL8188SU and
40 RTL8192SU chip based USB WiFi adapters.
45 .Xr firmware 9
H A Dubtbcmfw.432 .Nd Firmware driver for Broadcom BCM2033 chip based Bluetooth USB devices
37 .Bd -ragged -offset indent
44 .Bd -literal -offset indent
50 is a firmware driver for Broadcom BCM2033 chip based Bluetooth USB devices.
52 firmware.
81 .Bl -tag -width indent
86 .Bl -tag -width ".Pa /dev/ubtbcmfw Ns Ar N Ns Pa \&. Ns Ar EE" -compact
/freebsd/usr.sbin/bluetooth/iwmbtfw/
H A Diwmbtfw.81 .\"-
2 .\" SPDX-License-Identifier: BSD-2-Clause
6 .\" Copyright (c) 2021 Philippe Michaud-Boudreault <pitwuu@gmail.com>
34 .Nd load firmware for Intel Wireless AC Bluetooth USB devices
45 utility downloads the specified firmware file to the specified
51 work with Intel Wireless 7260/8260/9260 chip based Bluetooth USB devices
53 The identification is currently based on USB vendor ID/product ID pair.
58 Firmware files are available in the
59 .Pa comms/iwmbt-firmware
64 utility will query the device to determine which firmware image and board
[all …]
/freebsd/usr.sbin/bluetooth/ath3kfw/
H A Dath3kfw.81 .\"-
2 .\" SPDX-License-Identifier: BSD-2-Clause
34 .Nd load firmware for Atheros AR3011/AR3012 Bluetooth USB devices
45 utility downloads the specified firmware file to the specified
51 work with Atheros AR3011 and AR3012 chip based Bluetooth USB devices.
52 The identification is currently based on USB vendor ID/product ID pair.
57 Firmware files are available in the linux-firmware RPM.
61 utility will query the device to determine which firmware image and board
65 .Bl -tag -width "-f firmware_path"
73 Specify the directory containing the firmware files to search and upload.
[all …]
/freebsd/sys/contrib/device-tree/Bindings/arm/
H A Darm,scpi.txt2 ----------------------------------------------------------
4 Firmware implementing the SCPI described in ARM document number ARM DUI 0922B
10 - compatible : should be
12 * "arm,scpi-pre-1.0" : For implementations complying to all
14 - mboxes: List of phandle and mailbox channel specifiers
15 All the channels reserved by remote SCP firmware for use by
17 - shmem : List of phandle pointing to the shared memory(SHM) area between the
26 Clock bindings for the clocks based on SCPI Message Protocol
27 ------------------------------------------------------------
34 - compatible : should be "arm,scpi-clocks"
[all …]
H A Darm,scmi.txt2 ----------------------------------------------------------
8 This binding is intended to define the interface the firmware implementing
15 The scmi node with the following properties shall be under the /firmware/ node.
17 - compatible : shall be "arm,scmi" or "arm,scmi-smc" for smc/hvc transports
18 - mboxes: List of phandle and mailbox channel specifiers. It should contain
22 - shmem : List of phandle pointing to the shared memory(SHM) area as per
24 - #address-cells : should be '1' if the device has sub-nodes, maps to
25 protocol identifier for a given sub-node.
26 - #size-cells : should be '0' as 'reg' property doesn't have any size
28 - arm,smc-id : SMC id required when using smc or hvc transports
[all …]
/freebsd/usr.sbin/bluetooth/bcmfw/
H A Dbcmfw.81 .\"-
2 .\" SPDX-License-Identifier: BSD-2-Clause
33 .Nd load 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
48 work with Broadcom BCM2033 chip based Bluetooth USB devices.
49 The identification is currently based on USB vendor ID/product ID pair.
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:
[all …]
/freebsd/sys/contrib/device-tree/Bindings/net/wireless/
H A Dqcom,ath10k.txt4 - compatible: Should be one of the following:
6 * "qcom,ipq4019-wifi"
7 * "qcom,wcn3990-wifi"
9 PCI based devices uses compatible string "qcom,ath10k" and takes calibration
10 data along with board specific data via "qcom,ath10k-calibration-data".
11 Rest of the properties are not applicable for PCI based devices.
13 AHB based devices (i.e. ipq4019) uses compatible string "qcom,ipq4019-wifi"
15 "qcom,ath10k-calibration-data"). It uses "qcom,ath10k-pre-calibration-data"
18 In general, entry "qcom,ath10k-pre-calibration-data" and
19 "qcom,ath10k-calibration-data" conflict with each other and only one
[all …]
/freebsd/sys/contrib/device-tree/Bindings/arm/freescale/
H A Dfsl,scu.txt1 NXP i.MX System Controller Firmware (SCFW)
2 --------------------------------------------------------------------
4 The System Controller Firmware (SCFW) is a low-level system function
5 which runs on a dedicated Cortex-M core to provide power, clock, and
9 The AP communicates with the SC using a multi-ported MU module found
13 with the LSIO DSC IP bus. The SC firmware will communicate with this MU
19 The scu node with the following properties shall be under the /firmware/ node.
22 -------------------
23 - compatible: should be "fsl,imx-scu".
24 - mbox-names: should include "tx0", "tx1", "tx2", "tx3",
[all …]
/freebsd/sys/contrib/device-tree/Bindings/net/
H A Dmarvell-bt-8xxx.txt1 Marvell 8897/8997 (sd8897/sd8997) bluetooth devices (SDIO or USB based)
2 ------
9 - compatible : should be one of the following:
10 * "marvell,sd8897-bt" (for SDIO)
11 * "marvell,sd8997-bt" (for SDIO)
16 - marvell,cal-data: Calibration data downloaded to the device during
20 - marvell,wakeup-pin: It represents wakeup pin number of the bluetooth chip.
21 firmware will use the pin to wakeup host system (u16).
22 - marvell,wakeup-gap-ms: wakeup gap represents wakeup latency of the host
23 platform. The value will be configured to firmware. This
[all …]
/freebsd/sys/contrib/device-tree/Bindings/input/touchscreen/
H A Draspberrypi,firmware-ts.txt1 Raspberry Pi firmware based 7" touchscreen
5 - compatible: "raspberrypi,firmware-ts"
8 - firmware: Reference to RPi's firmware device node
9 - touchscreen-size-x: See touchscreen.txt
10 - touchscreen-size-y: See touchscreen.txt
11 - touchscreen-inverted-x: See touchscreen.txt
12 - touchscreen-inverted-y: See touchscreen.txt
13 - touchscreen-swapped-x-y: See touchscreen.txt
17 firmware: firmware-rpi {
18 compatible = "raspberrypi,bcm2835-firmware";
[all …]
/freebsd/sys/powerpc/conf/
H A DGENERIC642 # GENERIC64 -- Generic kernel configuration file for FreeBSD/powerpc64
7 # https://docs.freebsd.org/en/books/handbook/kernelconfig/#kernelconfig-config
25 makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols
33 options PSERIES # PAPR-compliant systems (e.g. IBM p)
34 options POWERNV # Non-virtualized OpenPOWER systems
38 options NUMA # Non-Uniform Memory Architecture support
55 options UFS_GJOURNAL # Enable gjournal-based UFS journaling
66 options PSEUDOFS # Pseudo-filesystem framework
83 options SYSVSHM # SYSV-style shared memory
84 options SYSVMSG # SYSV-style message queues
[all …]
H A DGENERIC2 # GENERIC -- Generic kernel configuration file for FreeBSD/powerpc
7 # https://docs.freebsd.org/en/books/handbook/kernelconfig/#kernelconfig-config
25 makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols
32 options PSERIES # PAPR-compliant systems
48 options UFS_GJOURNAL # Enable gjournal-based UFS journaling
58 options PSEUDOFS # Pseudo-filesystem framework
74 options SYSVSHM # SYSV-style shared memory
75 options SYSVMSG # SYSV-styl
[all...]
/freebsd/sys/dev/ice/
H A Dice_fwlog.c1 /* SPDX-License-Identifier: BSD-3-Clause */
37 * cache_cfg - Cache FW logging config
43 hw->fwlog_cfg = *cfg; in cache_cfg()
47 * valid_module_entries - validate all the module entry IDs and log levels
64 ice_debug(hw, ICE_DBG_FW_LOG, "num_entries must be non-zero\n"); in valid_module_entries()
71 if (entry->module_id >= ICE_AQC_FW_LOG_ID_MAX) { in valid_module_entries()
73 entry->module_i in valid_module_entries()
[all...]
/freebsd/sys/contrib/device-tree/Bindings/mtd/partitions/
H A Dbrcm,bcm947xx-cfe-partitions.txt6 without any on-flash partition table. On some devices their sizes and/or
13 Most of partitions use ASCII text based magic for determining a type. More
18 1) Bootloader with Broadcom's CFE (Common Firmware Environment)
21 4) TRX firmware container which can hold up to 4 subpartitions
22 5) Backup TRX firmware used after failed upgrade
25 For example both: main firmware and backup firmware use the same TRX format with
26 the same header. To distinguish currently used firmware a CFE's environment
34 - compatible : (required) must be "brcm,bcm947xx-cfe-partitions"
40 compatible = "brcm,bcm947xx-cfe-partitions";
H A Dbrcm,bcm947xx-cfe-partitions.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mtd/partitions/brcm,bcm947xx-cfe-partitions.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
12 partitions without any on-flash partition table. On some devices their sizes
19 Most of partitions use ASCII text based magic for determining a type. More
24 1) Bootloader with Broadcom's CFE (Common Firmware Environment)
27 4) TRX firmware container which can hold up to 4 subpartitions
28 5) Backup TRX firmware used after failed upgrade
31 configuration. For example both: main firmware and backup firmware use the
[all …]

12345678910>>...23