| /linux-3.3/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/ |
| D | qe.txt | 25 - fsl,firmware-phandle:
26 Usage: required only if there is no fsl,qe-firmware child node
28 Definition: Points to a firmware node (see "QE Firmware Node" below)
29 that contains the firmware that should be uploaded for this QE.
30 The compatible property for the firmware node should say,
31 "fsl,qe-firmware".
72 * QE Firmware Node
74 This node defines a firmware binary that is embedded in the device tree, for
75 the purpose of passing the firmware from bootloader to the kernel, or from
78 The firmware node itself contains the firmware binary contents, a compatible
[all …]
|
| /linux-3.3/Documentation/firmware_class/ |
| D | README | 9 Today, the most extended way to use firmware in the Linux kernel is linking
12 1) Some firmware is not legal to redistribute.
13 2) The firmware occupies memory permanently, even though it often is just
15 3) Some people, like the Debian crowd, don't consider some firmware free
21 kernel(driver): calls request_firmware(&fw_entry, $FIRMWARE, device)
24 - /sys/class/firmware/xxx/{loading,data} appear.
25 - hotplug gets called with a firmware identifier in $FIRMWARE
27 - hotplug: echo 1 > /sys/class/firmware/xxx/loading
33 /sys/class/firmware/xxx/data
39 - hotplug: echo 0 > /sys/class/firmware/xxx/loading
[all …]
|
| /linux-3.3/drivers/bluetooth/ |
| D | ath3k.c | 28 #include <linux/firmware.h>
64 /* Atheros AR3011 with sflash firmware*/
69 /* Atheros AR9285 Malbec with sflash firmware */
72 /* Atheros AR3012 with sflash firmware*/
75 /* Atheros AR5BBU12 with sflash firmware */
88 /* Atheros AR3012 with sflash firmware*/
99 const struct firmware *firmware) in ath3k_load_firmware() argument
103 int count = firmware->size; in ath3k_load_firmware()
111 BT_ERR("Can't allocate memory chunk for firmware"); in ath3k_load_firmware()
115 memcpy(send_buf, firmware->data, 20); in ath3k_load_firmware()
[all …]
|
| D | bcm203x.c | 3 * Broadcom Blutonium firmware driver
35 #include <linux/firmware.h>
146 BT_ERR("Firmware loading failed"); in bcm203x_complete()
170 const struct firmware *firmware; in bcm203x_probe() local
196 if (request_firmware(&firmware, "BCM2033-MD.hex", &udev->dev) < 0) { in bcm203x_probe()
203 BT_DBG("minidrv data %p size %zu", firmware->data, firmware->size); in bcm203x_probe()
205 size = max_t(uint, firmware->size, 4096); in bcm203x_probe()
210 release_firmware(firmware); in bcm203x_probe()
216 memcpy(data->buffer, firmware->data, firmware->size); in bcm203x_probe()
219 data->buffer, firmware->size, bcm203x_complete, data); in bcm203x_probe()
[all …]
|
| /linux-3.3/drivers/base/ |
| D | Kconfig | 60 bool "Select only drivers that don't need compile-time external firmware" if EXPERIMENTAL
63 Select this option if you don't have magic firmware for drivers that
69 bool "Prevent firmware from being built"
72 Say yes to avoid building firmware. Firmware is usually shipped
73 with the driver and only when updating the firmware should a
78 tristate "Userspace firmware loading support" if EXPERT
82 require userspace firmware loading support, but a module built
86 bool "Include in-kernel firmware blobs in kernel binary"
90 The kernel source tree includes a number of firmware 'blobs'
94 binary files in firmware/ to /lib/firmware/ on your system so
[all …]
|
| D | firmware_class.c | 2 * firmware_class.c - Multi purpose firmware loading support
21 #include <linux/firmware.h>
27 MODULE_DESCRIPTION("Multi purpose firmware loading support");
30 /* Builtin firmware support */
37 static bool fw_get_builtin_firmware(struct firmware *fw, const char *name) in fw_get_builtin_firmware()
52 static bool fw_is_builtin_firmware(const struct firmware *fw) in fw_is_builtin_firmware()
63 #else /* Module case - no builtin firmware support */
65 static inline bool fw_get_builtin_firmware(struct firmware *fw, const char *name) in fw_get_builtin_firmware()
70 static inline bool fw_is_builtin_firmware(const struct firmware *fw) in fw_is_builtin_firmware()
90 struct firmware *fw;
[all …]
|
| /linux-3.3/Documentation/video4linux/ |
| D | extract_xc3028.pl | 19 # cp xc3028-v24.fw /lib/firmware
20 # cp xc3028-v27.fw /lib/firmware
33 die "This firmware requires the md5sum command - see http://www.gnu.org/software/coreutils/\n";
163 # Firmware 0, type: BASE FW F8MHZ (0x00000003), id: (0000000000000000), size: 6635
172 # Firmware 1, type: BASE FW F8MHZ MTS (0x00000007), id: (0000000000000000), size: 6635
181 # Firmware 2, type: BASE FW FM (0x00000401), id: (0000000000000000), size: 6525
190 # Firmware 3, type: BASE FW FM INPUT1 (0x00000c01), id: (0000000000000000), size: 6539
199 # Firmware 4, type: BASE FW (0x00000001), id: (0000000000000000), size: 6633
208 # Firmware 5, type: BASE FW MTS (0x00000005), id: (0000000000000000), size: 6617
217 # Firmware 6, type: STD FW (0x00000000), id: PAL/BG A2/A (0000000100000007), size: 161
[all …]
|
| /linux-3.3/drivers/staging/media/as102/ |
| D | as102_fw.c | 24 #include <linux/firmware.h>
51 * Parse INTEL HEX firmware file to extract address and data.
61 pr_err("invalid firmware file\n"); in parse_hex_line()
106 const struct firmware *firmware) { in as102_firmware_upload() argument
114 for (total_read_bytes = 0; total_read_bytes < firmware->size; ) { in as102_firmware_upload()
119 (u8 *) (firmware->data + total_read_bytes), in as102_firmware_upload()
130 if (total_read_bytes == firmware->size) { in as102_firmware_upload()
168 const struct firmware *firmware; in as102_fw_upload() local
184 /* allocate buffer to store firmware upload command and data */ in as102_fw_upload()
191 /* request kernel to locate firmware file: part1 */ in as102_fw_upload()
[all …]
|
| /linux-3.3/Documentation/ABI/testing/ |
| D | sysfs-firmware-memmap | 1 What: /sys/firmware/memmap/
5 On all platforms, the firmware provides a memory map which the
10 However, on most architectures that firmware-provided memory
16 kexec needs the raw firmware-provided memory map to setup the
19 that reason, /sys/firmware/memmap is an interface that provides
22 The structure is as follows: Under /sys/firmware/memmap there
25 /sys/firmware/memmap/0
26 /sys/firmware/memmap/1
27 /sys/firmware/memmap/2
28 /sys/firmware/memmap/3
[all …]
|
| D | sysfs-firmware-gsmi | 1 What: /sys/firmware/gsmi
5 Some servers used internally at Google have firmware
13 these firmware callbacks. Currently, this functionality
19 /sys/firmware/gsmi/vars:
22 underlying implementation as /sys/firmware/efi/vars.
23 See Documentation/ABI/*/sysfs-firmware-efi-vars
27 /sys/firmware/gsmi/append_to_eventlog - write-only:
30 the firmware to be timestamped and appended to
32 interpreted by the firmware and may change from
36 firmware call.
[all …]
|
| D | sysfs-ibft | 1 What: /sys/firmware/ibft/initiator
4 Description: The /sys/firmware/ibft/initiator directory will contain
5 files that expose the iSCSI Boot Firmware Table initiator data.
8 What: /sys/firmware/ibft/targetX
11 Description: The /sys/firmware/ibft/targetX directory will contain
12 files that expose the iSCSI Boot Firmware Table target data.
18 What: /sys/firmware/ibft/ethernetX
21 Description: The /sys/firmware/ibft/ethernetX directory will contain
22 files that expose the iSCSI Boot Firmware Table NIC data.
|
| D | sysfs-firmware-dmi | 1 What: /sys/firmware/dmi/
5 Many machines' firmware (x86 and ia64) export DMI /
17 length of the entry, as well as a firmware-provided
24 system unless they know for certain what their firmware
38 /sys/firmware/dmi/entries/17-0
39 /sys/firmware/dmi/entries/17-1
40 /sys/firmware/dmi/entries/17-2
41 /sys/firmware/dmi/entries/17-3
44 Instance numbers are used in lieu of the firmware
47 there are likely firmware images that get this wrong in
[all …]
|
| /linux-3.3/drivers/usb/misc/ |
| D | isight_firmware.c | 2 * Driver for loading USB isight firmware
12 * need firmware to be loaded beforehand. After firmware loading, the device
16 * The firmware is non-free and must be extracted by the user. Tools to do this
19 * The isight firmware loading was reverse engineered by Johannes Berg
25 #include <linux/firmware.h>
42 const struct firmware *firmware; in isight_firmware_load() local
50 if (request_firmware(&firmware, "isight.fw", &dev->dev) != 0) { in isight_firmware_load()
51 printk(KERN_ERR "Unable to load isight firmware\n"); in isight_firmware_load()
56 ptr = firmware->data; in isight_firmware_load()
63 "Failed to initialise isight firmware loader\n"); in isight_firmware_load()
[all …]
|
| D | emi26.c | 2 * Emagic EMI 2|6 usb audio interface firmware loader.
19 #include <linux/firmware.h>
23 #define EMI26_PRODUCT_ID 0x0100 /* EMI 2|6 without firmware */
24 #define EMI26B_PRODUCT_ID 0x0102 /* EMI 2|6 without firmware */
27 #define ANCHOR_LOAD_EXTERNAL 0xA3 /* This command is not implemented in the core. Requires firmware…
28 #define ANCHOR_LOAD_FPGA 0xA5 /* This command is not implemented in the core. Requires firmware. Em…
77 const struct firmware *loader_fw = NULL; in emi26_load_firmware()
78 const struct firmware *bitstream_fw = NULL; in emi26_load_firmware()
79 const struct firmware *firmware_fw = NULL; in emi26_load_firmware()
88 dev_err(&dev->dev, "%s - error loading firmware: error = %d\n", in emi26_load_firmware()
[all …]
|
| D | emi62.c | 2 * Emagic EMI 2|6 usb audio interface firmware loader.
17 #include <linux/firmware.h>
20 /* include firmware (variables)*/
33 #define EMI62_PRODUCT_ID 0x0110 /* EMI 6|2m without firmware */
36 #define ANCHOR_LOAD_EXTERNAL 0xA3 /* This command is not implemented in the core. Requires firmware…
37 #define ANCHOR_LOAD_FPGA 0xA5 /* This command is not implemented in the core. Requires firmware. Em…
86 const struct firmware *loader_fw = NULL; in emi62_load_firmware()
87 const struct firmware *bitstream_fw = NULL; in emi62_load_firmware()
88 const struct firmware *firmware_fw = NULL; in emi62_load_firmware()
98 err( "%s - error loading firmware: error = %d", __func__, -ENOMEM); in emi62_load_firmware()
[all …]
|
| /linux-3.3/drivers/staging/line6/ |
| D | control.h | 18 Comments after the number refer to the PODxt Pro firmware version required
36 POD_amp_model = 12, /* firmware: 2.0 */
46 POD_band_1_frequency = 20, /* firmware: 2.0 */
59 …POD_band_2_frequency__bass = 32, /* device: LINE6_BITS_BASSPODXTALL */ /* firmware: 2.0 …
69 …POD_band_2_frequency = 42, /* device: LINE6_BITS_PODXTALL */ /* firmware: 2.0 …
70 …POD_band_3_frequency__bass = 42, /* device: LINE6_BITS_BASSPODXTALL */ /* firmware: 2.0 …
74 …POD_volume_pedal_minimum = 46, /* device: LINE6_BITS_PODXTALL */ /* firmware: 2.0 …
75 …POD_eq_pre_post = 46, /* device: LINE6_BITS_BASSPODXTALL */ /* firmware: 2.0 …
88 …POD_band_3_frequency = 60, /* device: LINE6_BITS_PODXTALL */ /* firmware: 2.0 …
89 …POD_band_4_frequency__bass = 60, /* device: LINE6_BITS_BASSPODXTALL */ /* firmware: 2.0 …
[all …]
|
| /linux-3.3/drivers/scsi/fnic/ |
| D | fcpio.h | 25 * communication by the host driver to the fcp firmware.
81 * Header status codes from the firmware
87 * If a request to the firmware is rejected, the original request
97 * Once a request is processed, the firmware will usually return
118 * to mark commands with a unique tag. When the firmware responds to
121 * The only firmware requests that will use the rx_id/ox_id fields instead
163 * The header for an fcpio request, whether from the firmware or from the
199 * fcpio_icmnd_16: host -> firmware request
247 * fcpio_icmnd_32: host -> firmware request
275 * fcpio_itmf: host -> firmware request
[all …]
|
| /linux-3.3/drivers/net/wireless/orinoco/ |
| D | fw.c | 1 /* Firmware file reading and download helpers
7 #include <linux/firmware.h>
17 /* End markers (for Symbol firmware only) */
78 /* TODO: consider adding a checksum or CRC to the firmware format */ in validate_fw()
83 static inline const struct firmware *
95 /* Download either STA or AP firmware into the card. */
105 const struct firmware *fw_entry; in orinoco_dl_firmware()
109 const char *firmware; in orinoco_dl_firmware() local
119 firmware = fw->ap_fw; in orinoco_dl_firmware()
121 firmware = fw->sta_fw; in orinoco_dl_firmware()
[all …]
|
| /linux-3.3/firmware/ |
| D | README.AddingFirmware | 2 DO NOT ADD FIRMWARE TO THIS DIRECTORY.
5 This directory is only here to contain firmware images extracted from old
9 separation between code and firmware, we put the extracted firmware
12 This directory is _NOT_ for adding arbitrary new firmware images. The
13 place to add those is the separate linux-firmware repository:
15 git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
17 That repository contains all these firmware images which have been
18 extracted from older drivers, as well various new firmware images which
22 To submit firmware to that repository, please send either a git binary
28 identifying the licence under which the firmware is available, and
[all …]
|
| /linux-3.3/Documentation/networking/ |
| D | fore200e.txt | 22 Firmware Copyright Notice
29 Firmware Updates
32 The FORE Systems 200E-series driver is shipped with firmware data being
34 The supplied firmware images should work with all adapters.
36 However, if you encounter problems (the firmware doesn't start or the driver
37 is unable to read the PROM data), you may consider trying another firmware
38 version. Alternative binary firmware images can be found somewhere on the
41 You can also get the latest firmware images from FORE Systems at
43 the 'software updates' pages. The firmware binaries are part of
46 Notice that different versions of the PCA-200E firmware exist, depending
[all …]
|
| /linux-3.3/sound/pci/asihpi/ |
| D | hpidspcd.c | 22 hotplug firmware loader from individual dsp code files
31 /** Firmware descriptor */
32 const struct firmware *firmware; member
40 const struct firmware *firmware; in hpi_dsp_code_open() local
49 err = request_firmware(&firmware, fw_name, &dev->dev); in hpi_dsp_code_open()
51 if (err || !firmware) { in hpi_dsp_code_open()
57 if (firmware->size < sizeof(header)) { in hpi_dsp_code_open()
62 memcpy(&header, firmware->data, sizeof(header)); in hpi_dsp_code_open()
66 || (header.size != firmware->size)) { in hpi_dsp_code_open()
68 "Invalid firmware header size %d != file %zd\n", in hpi_dsp_code_open()
[all …]
|
| /linux-3.3/Documentation/video4linux/cx2341x/ |
| D | fw-calling.txt | 1 This page describes how to make calls to the firmware api.
6 The preferred calling convention is known as the firmware mailbox. The
9 Firmware mailboxes can be located by searching the encoder and decoder memory
16 The firmware implements 20 mailboxes of 20 32-bit words. The first 10 are
17 reserved for API calls. The second 10 are used by the firmware for event
30 perspective of the firmware.
34 2 O Firmware has processed the command.
51 doesn't handle the completed call within the timeout specified, the firmware
57 driver then sets the parameter ready bit (bit 1). The firmware scans the
62 time set in the timeout register, the firmware will reset that mailbox.
[all …]
|
| /linux-3.3/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/qe/ |
| 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.
14 firmware binary. It is a 64-bit number represented
16 - virtual-traps: The virtual traps, taken from the firmware binary.
20 firmware {
|
| /linux-3.3/arch/powerpc/sysdev/qe_lib/ |
| D | qe.c | 345 /* Firmware information stored here for qe_get_firmware_info() */
349 * Set to 1 if QE firmware has been uploaded, and therefore
367 printk(KERN_INFO "qe-firmware: " in qe_upload_microcode()
371 printk(KERN_INFO "qe-firmware: " in qe_upload_microcode()
394 * 'calc_size' is the calculated size, in bytes, of the firmware structure and
399 int qe_upload_firmware(const struct qe_firmware *firmware) in qe_upload_firmware() argument
408 if (!firmware) { in qe_upload_firmware()
409 printk(KERN_ERR "qe-firmware: invalid pointer\n"); in qe_upload_firmware()
413 hdr = &firmware->header; in qe_upload_firmware()
419 printk(KERN_ERR "qe-firmware: not a microcode\n"); in qe_upload_firmware()
[all …]
|
| /linux-3.3/Documentation/dvb/ |
| D | ttusb-dec.txt | 16 Hotplug firmware loader under 2.6 kernels
24 Getting the Firmware
26 To download the firmware, use the following commands:
34 For 2.4 kernels the firmware for the DECs is compiled into the driver itself.
39 Hotplug Firmware Loading for 2.6 kernels
41 For 2.6 kernels the firmware is loaded at the point that the driver module is
42 loaded. See linux/Documentation/dvb/firmware.txt for more information.
44 Copy the three files downloaded above into the /usr/lib/hotplug/firmware or
45 /lib/firmware directory (depending on configuration of firmware hotplug).
|