Searched refs:images (Results 1 – 25 of 148) sorted by relevance
123456
10 software images which includes communication between images in12 virtualization extension to isolate software images provided
48 unsigned char images[AK4XXX_IMAGE_SIZE]; /* saved register image */ member77 (ak)->images[(chip) * 16 + (reg)]79 ((ak)->images[(chip) * 16 + (reg)] = (val))
18 The PiSP Back End ISP processes images in tiles. The handling of image25 in DRAM memory and processing them in the PiSP Back End to obtain images usable49 - pispbe-input: output device for images to be submitted to the ISP for53 - 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 by79 tonemapping blocks are used. The `pispbe-stitch_output` writes images to memory
34 The supplied firmware images should work with all adapters.38 version. Alternative binary firmware images can be found somewhere on the41 You can also get the latest firmware images from FORE Systems at48 both little and big endian PCA firmware images.50 Name and location of the new firmware images can be set at kernel
27 Header of Linux/LoongArch kernel images30 Linux/LoongArch kernel images are EFI images. Being PE files, they have
111 https://linux-sunxi.org/images/4/4b/Allwinner_H3_Datasheet_V1.2.pdf156 https://linux-sunxi.org/images/5/5c/Allwinner_H6_V200_Datasheet_V1.1.pdf160 https://linux-sunxi.org/images/4/46/Allwinner_H6_V200_User_Manual_V1.1.pdf166 https://linux-sunxi.org/images/b/b9/H616_Datasheet_V1.0_cleaned.pdf170 https://linux-sunxi.org/images/2/24/H616_User_Manual_V1.0_cleaned.pdf
11 increasing the power of the images centered around13 power of these images.
3 In order to zero-copy import camera images into the 3D or display11 2) Avoid extra copies for padding of images.
11 digitized images in memory. Today nearly all devices can capture at full13 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 YUV54 also define how images are scaled in the process.
7 In order to exchange images between drivers and applications, it is15 to convert images to one of the standard formats when needed. But the20 images to the X Windows screen format when the video is to be displayed.
12 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.
38 the Bootloader images and other modem software images.56 PSI RAM and EBL are the RAM images which are injected to the device when the85 place. Below is the sequence of commands used for each of the firmware images.
59 from docutils.parsers.rst.directives import images64 Figure = images.Figure305 translator.builder.images.pop(img_node['uri'], None)442 class KernelImage(images.Image):456 result = images.Image.run(self)
3 images {
2 images {
8 images {
4 for FILE in Makefile Documentation/images/logo.gif; do
110 multiple 'images'. Each such image has a header containing its name157 'images' in flash devices by putting a table one of the erase159 the offsets, lengths and names of all the images stored in the196 bool "Force read-only for RedBoot system images"199 'FIS directory' images, enable this option.