Home
last modified time | relevance | path

Searched refs:images (Results 1 – 25 of 130) sorted by relevance

123456

/linux/drivers/firmware/arm_ffa/
H A DKconfig10 software images which includes communication between images in
12 virtualization extension to isolate software images provided
/linux/include/sound/
H A Dak4xxx-adda.h48 unsigned char images[AK4XXX_IMAGE_SIZE]; /* saved register image */ member
77 (ak)->images[(chip) * 16 + (reg)]
79 ((ak)->images[(chip) * 16 + (reg)] = (val))
/linux/Documentation/admin-guide/media/
H A Draspberrypi-pisp-be.rst18 The PiSP Back End ISP processes images in tiles. The handling of image
25 in DRAM memory and processing them in the PiSP Back End to obtain images usable
49 - pispbe-input: output device for images to be submitted to the ISP for
53 - pispbe-output0: first capture device for processed images.
54 - pispbe-output1: second capture device for processed images.
69 The `pispbe-tdn_input` output video device receives images to be processed by
79 tonemapping blocks are used. The `pispbe-stitch_output` writes images to memory
/linux/Documentation/gpu/nova/core/
H A Dvbios.rst7 images in the ROM of the GPU. The VBIOS is mirrored onto the BAR 0 space and is read
12 The format of the images in the ROM follow the "BIOS Specification" part of the
13 PCI specification, with Nvidia-specific extensions. The ROM images of type FwSec
51 The VBIOS layout is roughly a series of concatenated images laid out as follows::
97 | (no gap between images) | |
112 | (no gap between images) | |
126 | (no gap between images) | |
178 does not account for the EFI image located between the PciAt and FwSec images.
H A Dfwsec.rst15 before loading various ucode images onto other microcontrollers on the GPU,
30 various ucode images (also known as applications) -- one of them being FWSEC. For how
33 The Falcon data for each ucode images (including the FWSEC image) is a combination
35 ucode images are stored in the same ROM partition and the PMU table is used to look
/linux/Documentation/networking/device_drivers/atm/
H A Dfore200e.rst34 The supplied firmware images should work with all adapters.
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
48 both little and big endian PCA firmware images.
50 Name and location of the new firmware images can be set at kernel
/linux/Documentation/arch/loongarch/
H A Dbooting.rst27 Header of Linux/LoongArch kernel images
30 Linux/LoongArch kernel images are EFI images. Being PE files, they have
/linux/Documentation/arch/arm/
H A Dsunxi.rst111 https://linux-sunxi.org/images/4/4b/Allwinner_H3_Datasheet_V1.2.pdf
156 https://linux-sunxi.org/images/5/5c/Allwinner_H6_V200_Datasheet_V1.1.pdf
160 https://linux-sunxi.org/images/4/46/Allwinner_H6_V200_User_Manual_V1.1.pdf
166 https://linux-sunxi.org/images/b/b9/H616_Datasheet_V1.0_cleaned.pdf
170 https://linux-sunxi.org/images/2/24/H616_User_Manual_V1.0_cleaned.pdf
/linux/Documentation/userspace-api/media/v4l/
H A Ddev-capture.rst11 digitized images in memory. Today nearly all devices can capture at full
13 capture process and move images from the driver into user space.
52 capture, the latter how images are stored in memory, i. e. in RGB or YUV
54 also define how images are scaled in the process.
H A Dpixfmt-intro.rst8 In order to exchange images between drivers and applications, it is
16 to convert images to one of the standard formats when needed. But the
21 images to the X Windows screen format when the video is to be displayed.
H A Ddev-output.rst12 process and move images from user space to the driver.
50 the latter how images are stored in memory, i. e. in RGB or YUV format,
52 define how images are scaled in the process.
/linux/Documentation/networking/devlink/
H A Diosm.rst38 the Bootloader images and other modem software images.
56 PSI RAM and EBL are the RAM images which are injected to the device when the
85 place. Below is the sequence of commands used for each of the firmware images.
/linux/arch/mips/generic/
H A Dboard-luton.its.S3 images {
H A Dboard-boston.its.S2 images {
H A Dboard-marduk.its.S2 images {
H A Dboard-xilfpga.its.S2 images {
H A Dboard-ni169445.its.S2 images {
H A Dboard-serval.its.S3 images {
H A Dboard-ocelot.its.S3 images {
H A Dboard-jaguar2.its.S3 images {
H A Dvmlinux.its.S8 images {
/linux/arch/mips/mobileye/
H A Dboard-epm5.its.S3 images {
H A Dvmlinux.its.S8 images {
/linux/scripts/
H A Dspdxcheck-test.sh4 for FILE in Makefile Documentation/images/logo.gif; do
/linux/drivers/mtd/parsers/
H A DKconfig110 multiple 'images'. Each such image has a header containing its name
157 'images' in flash devices by putting a table one of the erase
159 the offsets, lengths and names of all the images stored in the
196 bool "Force read-only for RedBoot system images"
199 'FIS directory' images, enable this option.

123456