Home
last modified time | relevance | path

Searched refs:firmware (Results 1 – 25 of 915) sorted by relevance

12345678910>>...37

/freebsd/usr.sbin/fwget/pci/
H A Dpci_network_intel13 # as well as all for those which exists no firmware (yet).
24 # to generate the flavor/firmware Makefile definitions for ports.
29 0x08b1/*/0x4a6c) addpkg "wifi-firmware-iwlwifi-kmod-7000"; return 1 ;;
30 0x08b1/*/0x4a6e) addpkg "wifi-firmware-iwlwifi-kmod-7000"; return 1 ;;
31 0x08b1/*/0x4a70) addpkg "wifi-firmware-iwlwifi-kmod-7000"; return 1 ;;
32 0x08b1/*/0x4c60) addpkg "wifi-firmware-iwlwifi-kmod-7000"; return 1 ;;
33 0x08b1/*/0x4c70) addpkg "wifi-firmware-iwlwifi-kmod-7000"; return 1 ;;
34 0x08b1/*/0x402a) addpkg "wifi-firmware-iwlwifi-kmod-7000"; return 1 ;;
35 0x08b1/*/0x406a) addpkg "wifi-firmware-iwlwifi-kmod-7000"; return 1 ;;
411 0x272b/*/*) addpkg "wifi-firmware-iwlwifi-kmod-bz"; return 1 ;;
[all …]
H A Dpci_video_amd31 addpkg "gpu-firmware-amd-kmod-tahiti"
37 addpkg "gpu-firmware-amd-kmod-oland"
40 addpkg "gpu-firmware-amd-kmod-verde gpu-firmware-amd-kmod-si58"
43 addpkg "gpu-firmware-amd-kmod-hainan"
46 addpkg "gpu-firmware-amd-kmod-kaveri"
52 addpkg "gpu-firmware-amd-kmod-hawaii"
61 addpkg "gpu-firmware-amd-kmod-topaz"
64 addpkg "gpu-firmware-amd-kmod-tonga"
67 addpkg "gpu-firmware-amd-kmod-fiji"
85 addpkg "gpu-firmware-amd-kmod-vegam"
[all …]
H A Dpci_video_intel32 addpkg "gpu-firmware-intel-kmod-skylake"
36 addpkg "gpu-firmware-intel-kmod-broxton"
40 addpkg "gpu-firmware-intel-kmod-geminilake"
44 addpkg "gpu-firmware-intel-kmod-kabylake"
48 addpkg "gpu-firmware-intel-kmod-cannonlake"
52 addpkg "gpu-firmware-intel-kmod-icelake"
56 addpkg "gpu-firmware-intel-kmod-elkhartlake"
60 addpkg "gpu-firmware-intel-kmod-tigerlake"
64 addpkg "gpu-firmware-intel-kmod-rocketlake gpu-firmware-intel-kmod-tigerlake"
68 addpkg "gpu-firmware-intel-kmod-dg1"
[all …]
H A Dpci_network_qca35 # to generate the flavor/firmware Makefile definitions for ports.
39 0x003c) addpkg "wifi-firmware-ath10k-kmod-qca988x_hw20"; return 1 ;;
40 0x003e) addpkg "wifi-firmware-ath10k-kmod-qca6174_hw21"
41 addpkg "wifi-firmware-ath10k-kmod-qca6174_hw30"
43 0x0040) addpkg "wifi-firmware-ath10k-kmod-qca99x0_hw20"; return 1 ;;
44 0x0041) addpkg "wifi-firmware-ath10k-kmod-qca6174_hw21"; return 1 ;;
45 0x0042) addpkg "wifi-firmware-ath10k-kmod-qca6174_hw30"
46 addpkg "wifi-firmware-ath10k-kmod-qca9377_hw10"
48 0x0046) addpkg "wifi-firmware-ath10k-kmod-qca9984_hw10"; return 1 ;;
63 # to generate the flavor/firmware Makefile definitions for ports.
[all …]
H A Dpci_network_mediatek37 # to generate the flavor/firmware Makefile definitions for ports.
41 0x0608) addpkg "wifi-firmware-mediatek-kmod-mt792x"; return 1 ;;
42 0x0616) addpkg "wifi-firmware-mediatek-kmod-mt792x"; return 1 ;;
43 0x0717) addpkg "wifi-firmware-mediatek-kmod-mt792x"; return 1 ;;
44 0x7906) addpkg "wifi-firmware-mediatek-kmod-mt7915"; return 1 ;;
45 0x790a) addpkg "wifi-firmware-mediatek-kmod-mt7915"; return 1 ;;
46 0x7915) addpkg "wifi-firmware-mediatek-kmod-mt7915"; return 1 ;;
47 0x7916) addpkg "wifi-firmware-mediatek-kmod-mt7915"; return 1 ;;
48 0x7922) addpkg "wifi-firmware-mediatek-kmod-mt792x"; return 1 ;;
49 0x7925) addpkg "wifi-firmware-mediatek-kmod-mt792x"; return 1 ;;
[all …]
H A Dpci_network_realtek43 0xd723) addpkg "wifi-firmware-rtw88-kmod-rtw8723d"; return 1 ;;
44 0xb821) addpkg "wifi-firmware-rtw88-kmod-rtw8821c"; return 1 ;;
45 0xc821) addpkg "wifi-firmware-rtw88-kmod-rtw8821c"; return 1 ;;
46 0xb822) addpkg "wifi-firmware-rtw88-kmod-rtw8822b"; return 1 ;;
47 0xc822) addpkg "wifi-firmware-rtw88-kmod-rtw8822c"; return 1 ;;
48 0xc82f) addpkg "wifi-firmware-rtw88-kmod-rtw8822c"; return 1 ;;
65 0xb851) addpkg "wifi-firmware-rtw89-kmod-rtw8851b"; return 1 ;;
66 0x8852) addpkg "wifi-firmware-rtw89-kmod-rtw8852a"; return 1 ;;
67 0xa85a) addpkg "wifi-firmware-rtw89-kmod-rtw8852a"; return 1 ;;
68 0xb852) addpkg "wifi-firmware-rtw89-kmod-rtw8852b"; return 1 ;;
[all …]
/freebsd/sys/contrib/device-tree/Bindings/firmware/xilinx/
H A Dxlnx,zynqmp-firmware.txt5 The zynqmp-firmware node describes the interface to platform firmware.
7 driver provides an interface to firmware APIs. Interface APIs can be
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.
28 firmware {
29 zynqmp_firmware: zynqmp-firmware {
30 compatible = "xlnx,zynqmp-firmware";
38 firmware {
39 versal_firmware: versal-firmware {
[all …]
H A Dxlnx,zynqmp-firmware.yaml4 $id: http://devicetree.org/schemas/firmware/xilinx/xlnx,zynqmp-firmware.yaml#
7 title: Xilinx firmware driver
12 description: The zynqmp-firmware node describes the interface to platform
13 firmware. ZynqMP has an interface to communicate with secure firmware.
24 const: xlnx,zynqmp-firmware
27 const: xlnx,versal-firmware
31 The method of calling the PM-API firmware layer.
73 firmware {
74 zynqmp_firmware: zynqmp-firmware {
83 versal-firmware {
[all …]
/freebsd/sys/contrib/device-tree/Bindings/arm/bcm/
H A Draspberrypi,bcm2835-firmware.yaml7 title: Raspberry Pi VideoCore firmware driver
17 const: raspberrypi,bcm2835-firmware
25 - const: raspberrypi,bcm2835-firmware
37 const: raspberrypi,firmware-clocks
43 firmware messages.
55 const: raspberrypi,firmware-reset
72 const: raspberrypi,firmware-poe-pwm
90 firmware {
95 compatible = "raspberrypi,firmware-clocks";
100 compatible = "raspberrypi,firmware-reset";
[all …]
H A Draspberrypi,bcm2835-firmware.txt1 Raspberry Pi VideoCore firmware driver
5 - compatible: Should be "raspberrypi,bcm2835-firmware"
6 - mboxes: Phandle to the firmware device's Mailbox.
11 firmware {
12 compatible = "raspberrypi,bcm2835-firmware";
/freebsd/sys/contrib/device-tree/Bindings/soc/fsl/cpm_qe/qe/
H A Dfirmware.txt1 * 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.
14 firmware binary. It is a 64-bit number represented
16 - virtual-traps: The virtual traps, taken from the firmware binary.
20 firmware {
/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
17 firmware: firmware-rpi {
18 compatible = "raspberrypi,bcm2835-firmware";
22 compatible = "raspberrypi,firmware-ts";
/freebsd/sys/contrib/device-tree/Bindings/soc/fsl/cpm_qe/
H A Dqe.txt26 - fsl,firmware-phandle:
32 "fsl,qe-firmware".
141 The firmware node itself contains the firmware binary contents, a compatible
144 fsl,firmware-phandle property. Other QE nodes that need the same firmware
145 should define an fsl,firmware-phandle property that points to the firmware node
156 kind of firmware it is. For QE, this should be "fsl,qe-firmware".
158 - fsl,firmware
167 qe_firmware:qe-firmware {
168 compatible = "fsl,qe-firmware";
169 fsl,firmware = [0x70 0xcd 0x00 0x00 0x01 0x46 0x45 ...];
[all …]
/freebsd/sys/dev/cxgb/
H A Dcxgb_t3fw.c21 const struct firmware *fp; in cxgb_t3fw_modevent()
48 MODULE_DEPEND(cxgb_t3fw, firmware, 1, 1, 1);
53 const struct firmware *fp; in cxgb_t3b_protocol_sram_modevent()
80 MODULE_DEPEND(cxgb_t3b_protocol_sram, firmware, 1, 1, 1);
85 const struct firmware *fp; in cxgb_t3b_tp_eeprom_modevent()
112 MODULE_DEPEND(cxgb_t3b_tp_eeprom, firmware, 1, 1, 1);
117 const struct firmware *fp; in cxgb_t3c_protocol_sram_modevent()
144 MODULE_DEPEND(cxgb_t3c_protocol_sram, firmware, 1, 1, 1);
149 const struct firmware *fp; in cxgb_t3c_tp_eeprom_modevent()
176 MODULE_DEPEND(cxgb_t3c_tp_eeprom, firmware, 1, 1, 1);
/freebsd/share/examples/kld/firmware/
H A DREADME2 This is a simple example of the firmware(9) system. It consists of two
6 This is the firmware image (the ascii art of beastie from the boot
7 menu). The Makefile lists the firmware file "firmware.img" and the
8 short handle for this firmware image "beastie".
13 This module tries to get the a firmware image called "beastie",
15 It keeps a reference to the firmware until it is unloaded.
17 This is mainly to demonstrate how to construct firmware image modules.
/freebsd/sys/sys/
H A Dfirmware.h51 struct firmware { struct
58 const struct firmware *firmware_register(const char *, argument
59 const void *, size_t, unsigned int, const struct firmware *);
63 const struct firmware *firmware_get_flags(const char *, uint32_t flags);
64 const struct firmware *firmware_get(const char *);
67 void firmware_put(const struct firmware *, int);
/freebsd/sys/contrib/device-tree/Bindings/gpio/
H A Draspberrypi,firmware-gpio.txt3 The Raspberry Pi 3 GPIO expander is controlled by the VC4 firmware. The
4 firmware exposes a mailbox interface that allows the ARM core to control the
8 firmware node.
12 - compatible : Should be "raspberrypi,firmware-gpio"
21 firmware: firmware-rpi {
22 compatible = "raspberrypi,bcm2835-firmware";
26 compatible = "raspberrypi,firmware-gpio";
/freebsd/sys/contrib/device-tree/Bindings/net/
H A Dmarvell,aquantia.yaml13 Marvell Aquantia Ethernet PHY require a firmware to be loaded to actually
17 - Attached SPI flash directly to the PHY with the firmware. The PHY
18 will self load the firmware in the presence of this configuration.
21 - Manually provided firmware loaded from a file in the filesystem.
48 firmware-name:
49 description: specify the name of PHY firmware to load
52 description: phandle to the firmware nvmem cell
56 const: firmware
75 firmware-name = "AQR-G4_v5.4.C-AQR_CIG_WF-1945_0x8_ID44776_VER1630.cld";
84 nvmem-cell-names = "firmware";
/freebsd/sys/contrib/device-tree/Bindings/arm/samsung/
H A Dsamsung-secure-firmware.yaml4 $id: http://devicetree.org/schemas/arm/samsung/samsung-secure-firmware.yaml#
15 - const: samsung,secure-firmware
19 Address of non-secure SYSRAM used for communication with firmware.
30 firmware@203f000 {
31 compatible = "samsung,secure-firmware";
/freebsd/share/examples/bhyve/
H A Dvmrun.sh183 firmware="${OPTARG}"
268 if [ -z "$firmware" ]; then
271 firmware="${efi_firmware}"
275 firmware="${uboot_firmware}"
281 if [ -n "${firmware}" -a ! -f "${firmware}" ]; then
282 echo "Error: Firmware file ${firmware} doesn't exist."
373 devargs="$devargs -o bootrom=${firmware} "
419 efiargs="${efiargs} -l bootrom,${firmware}"
/freebsd/share/examples/kld/firmware/fwimage/
H A DMakefile5 FIRMWS= firmware.img:beastie
7 CLEANFILES= firmware.img
9 firmware.img: firmware.img.uu
/freebsd/sys/contrib/device-tree/Bindings/nvmem/
H A Dxlnx,zynqmp-nvmem.txt2 = Zynq UltraScale+ MPSoC nvmem firmware driver binding =
5 like soc revision, IDCODE... etc, By using the firmware interface.
17 firmware {
18 zynqmp_firmware: zynqmp-firmware {
19 compatible = "xlnx,zynqmp-firmware";
/freebsd/sys/contrib/device-tree/src/arm64/qcom/
H A Dmsm8996-oneplus3.dts19 firmware-name = "qcom/msm8996/oneplus3/adsp.mbn";
32 firmware-name = "qcom/msm8996/oneplus3/a530_zap.mbn";
37 firmware-name = "qcom/msm8996/oneplus3/mba.mbn",
43 firmware-name = "qcom/msm8996/oneplus3/slpi.mbn";
48 firmware-name = "qcom/msm8996/oneplus3/venus.mbn";
H A Dmsm8996-oneplus3t.dts20 firmware-name = "qcom/msm8996/oneplus3t/adsp.mbn";
33 firmware-name = "qcom/msm8996/oneplus3t/a530_zap.mbn";
38 firmware-name = "qcom/msm8996/oneplus3t/mba.mbn",
44 firmware-name = "qcom/msm8996/oneplus3t/slpi.mbn";
49 firmware-name = "qcom/msm8996/oneplus3t/venus.mbn";
/freebsd/sys/contrib/device-tree/src/arm/broadcom/
H A Dbcm2835-rpi.dtsi5 firmware: firmware { label
6 compatible = "raspberrypi,bcm2835-firmware", "simple-mfd";
16 firmware = <&firmware>;

12345678910>>...37