mainmenu "V4L/DVB menu"

source Kconfig.kern

config VIDEO_KERNEL_VERSION

bool "Enable drivers not supported by this kernel"

default n

---help---

Normally drivers that require a kernel newer 2.6.32,

the kernel you are compiling for now, will be disabled.

Turning this switch on will let you enabled them, but be warned

they may not work properly or even compile.

They may also work fine, and the only reason they are listed as

requiring a newer kernel is that no one has tested them with an

older one yet.

If the driver works, please post a report to the V4L mailing list:

linux-media@vger.kernel.org.

Unless you know what you are doing, you should answer N.

#

# Multimedia device configuration

#

menuconfig MEDIA_SUPPORT

tristate "Multimedia support"

depends on HAS_IOMEM

help

If you want to use Webcams, Video grabber devices and/or TV devices

enable this option and other options below.

Additional info and docs are available on the web at

<https://linuxtv.org>

if MEDIA_SUPPORT

comment "Multimedia core support"

#

# Multimedia support - automatically enable V4L2 and DVB core

#

config MEDIA_CAMERA_SUPPORT

bool "Cameras/video grabbers support"

---help---

Enable support for webcams and video grabbers.

Say Y when you have a webcam or a video capture grabber board.

config MEDIA_ANALOG_TV_SUPPORT

bool "Analog TV support"

---help---

Enable analog TV support.

Say Y when you have a TV board with analog support or with a

hybrid analog/digital TV chipset.

Note: There are several DVB cards that are based on chips that

support both analog and digital TV. Disabling this option

will disable support for them.

config MEDIA_DIGITAL_TV_SUPPORT

bool "Digital TV support"

---help---

Enable digital TV support.

Say Y when you have a board with digital support or a board with

hybrid digital TV and analog TV.

config MEDIA_RADIO_SUPPORT

bool "AM/FM radio receivers/transmitters support"

---help---

Enable AM/FM radio support.

Additional info and docs are available on the web at

<https://linuxtv.org>

Say Y when you have a board with radio support.

Note: There are several TV cards that are based on chips that

support radio reception. Disabling this option will

disable support for them.

config MEDIA_SDR_SUPPORT

bool "Software defined radio support"

---help---

Enable software defined radio support.

Say Y when you have a software defined radio device.

config MEDIA_RC_SUPPORT

bool "Remote Controller support"

depends on INPUT

---help---

Enable support for Remote Controllers on Linux. This is

needed in order to support several video capture adapters,

standalone IR receivers/transmitters, and RF receivers.

Enable this option if you have a video capture board even

if you don't need IR, as otherwise, you may not be able to

compile the driver for your adapter.

Say Y when you have a TV or an IR device.

#

# Media controller

# Selectable only for webcam/grabbers, as other drivers don't use it

#

config MEDIA_CONTROLLER

bool "Media Controller API"

depends on MEDIA_CAMERA_SUPPORT || MEDIA_ANALOG_TV_SUPPORT || MEDIA_DIGITAL_TV_SUPPORT

---help---

Enable the media controller API used to query media devices internal

topology and configure it dynamically.

This API is mostly used by camera interfaces in embedded platforms.

config MEDIA_CONTROLLER_DVB

bool "Enable Media controller for DVB (EXPERIMENTAL)"

depends on MEDIA_CONTROLLER

---help---

Enable the media controller API support for DVB.

This is currently experimental.

#

# Video4Linux support

# Only enables if one of the V4L2 types (ATV, webcam, radio) is selected

#

config VIDEO_DEV

tristate

depends on MEDIA_SUPPORT

depends on MEDIA_CAMERA_SUPPORT || MEDIA_ANALOG_TV_SUPPORT || MEDIA_RADIO_SUPPORT || MEDIA_SDR_SUPPORT

default y

config VIDEO_V4L2_SUBDEV_API

bool "V4L2 sub-device userspace API"

depends on VIDEO_DEV && MEDIA_CONTROLLER

---help---

Enables the V4L2 sub-device pad-level userspace API used to configure

video format, size and frame rate between hardware blocks.

This API is mostly used by camera interfaces in embedded platforms.

#

# Generic video config states

#

# Enable the V4L2 core and API

config VIDEO_V4L2

tristate

depends on (I2C || I2C=n) && VIDEO_DEV

default (I2C || I2C=n) && VIDEO_DEV

config VIDEO_ADV_DEBUG

bool "Enable advanced debug functionality on V4L2 drivers"

default n

---help---

Say Y here to enable advanced debugging functionality on some

V4L devices.

In doubt, say N.

config VIDEO_FIXED_MINOR_RANGES

bool "Enable old-style fixed minor ranges on drivers/video devices"

default n

---help---

Say Y here to enable the old-style fixed-range minor assignments.

Only useful if you rely on the old behavior and use mknod instead of udev.

When in doubt, say N.

config VIDEO_PCI_SKELETON

tristate "Skeleton PCI V4L2 driver"

depends on PCI && BUILD_DOCSRC

depends on VIDEO_V4L2 && VIDEOBUF2_CORE

depends on VIDEOBUF2_MEMOPS && VIDEOBUF2_DMA_CONTIG

---help---

Enable build of the skeleton PCI driver, used as a reference

when developing new drivers.

# Used by drivers that need tuner.ko

config VIDEO_TUNER

tristate

# Used by drivers that need v4l2-mem2mem.ko

# V4L2_MEM2MEM_DEV disabled for insufficient kernel version

config V4L2_MEM2MEM_DEV

tristate

depends on VIDEOBUF2_CORE

# Used by LED subsystem flash drivers

# V4L2_FLASH_LED_CLASS disabled for insufficient kernel version

config V4L2_FLASH_LED_CLASS

tristate "V4L2 flash API for LED flash class devices"

depends on VIDEO_V4L2 && VIDEO_V4L2_SUBDEV_API

depends on LEDS_CLASS_FLASH

default n

depends on VIDEO_KERNEL_VERSION

---help---

WARNING! This driver needs at least kernel 3.18.0! It may not

compile or work correctly on your kernel, which is too old.

Say Y here to enable V4L2 flash API support for LED flash

class drivers.

When in doubt, say N.

# Used by drivers that need Videobuf modules

config VIDEOBUF_GEN

tristate

config VIDEOBUF_DMA_SG

tristate

depends on HAS_DMA

select VIDEOBUF_GEN

config VIDEOBUF_VMALLOC

tristate

select VIDEOBUF_GEN

config VIDEOBUF_DMA_CONTIG

tristate

depends on HAS_DMA

select VIDEOBUF_GEN

config VIDEOBUF_DVB

tristate

select VIDEOBUF_GEN

# Used by drivers that need Videobuf2 modules

config VIDEOBUF2_CORE

select DMA_SHARED_BUFFER

tristate

config VIDEOBUF2_MEMOPS

tristate

select FRAME_VECTOR

# VIDEOBUF2_DMA_CONTIG disabled for insufficient kernel version

config VIDEOBUF2_DMA_CONTIG

tristate

depends on HAS_DMA

select VIDEOBUF2_CORE

select VIDEOBUF2_MEMOPS

select DMA_SHARED_BUFFER

config VIDEOBUF2_VMALLOC

tristate

select VIDEOBUF2_CORE

select VIDEOBUF2_MEMOPS

select DMA_SHARED_BUFFER

config VIDEOBUF2_DMA_SG

tristate

depends on HAS_DMA

select VIDEOBUF2_CORE

select VIDEOBUF2_MEMOPS

config VIDEOBUF2_DVB

tristate

select VIDEOBUF2_CORE

#

# DVB Core

# Only enables if one of DTV is selected

#

config DVB_CORE

tristate

depends on MEDIA_SUPPORT

depends on MEDIA_DIGITAL_TV_SUPPORT

default y

select CRC32

config DVB_NET

bool "DVB Network Support"

default (NET && INET)

depends on NET && INET && DVB_CORE

help

This option enables DVB Network Support which is a part of the DVB

standard. It is used, for example, by automatic firmware updates used

on Set-Top-Boxes. It can also be used to access the Internet via the

DVB card, if the network provider supports it.

You may want to disable the network support on embedded devices. If

unsure say Y.

# This Kconfig option is used by both PCI and USB drivers

config TTPCI_EEPROM

tristate

depends on I2C

default n

#

# DVB device configuration

#

config DVB_MAX_ADAPTERS

int "maximum number of DVB/ATSC adapters"

depends on DVB_CORE

default 8

range 1 255

help

Maximum number of DVB/ATSC adapters. Increasing this number

increases the memory consumption of the DVB subsystem even

if a much lower number of DVB/ATSC adapters is present.

Only values in the range 4-32 are tested.

If you are unsure about this, use the default value 8

config DVB_DYNAMIC_MINORS

bool "Dynamic DVB minor allocation"

depends on DVB_CORE

default n

help

If you say Y here, the DVB subsystem will use dynamic minor

allocation for any device that uses the DVB major number.

This means that you can have more than 4 of a single type

of device (like demuxes and frontends) per adapter, but udev

will be required to manage the device nodes.

If you are unsure about this, say N here.

comment "Media drivers"

config RC_CORE

tristate

depends on MEDIA_RC_SUPPORT

depends on INPUT

default y

config RC_MAP

tristate "Compile Remote Controller keymap modules"

depends on RC_CORE

default y

---help---

This option enables the compilation of lots of Remote

Controller tables. They are short tables, but if you

don't use a remote controller, or prefer to load the

tables on userspace, you should disable it.

The ir-keytable program, available at v4l-utils package

provide the tool and the same RC maps for load from

userspace. Its available at

http://git.linuxtv.org/cgit.cgi/v4l-utils.git/

menuconfig RC_DECODERS

bool "Remote controller decoders"

depends on RC_CORE

default y

if RC_DECODERS

config LIRC

tristate "LIRC interface driver"

depends on RC_CORE

---help---

Enable this option to build the Linux Infrared Remote

Control (LIRC) core device interface driver. The LIRC

interface passes raw IR to and from userspace, where the

LIRC daemon handles protocol decoding for IR reception and

encoding for IR transmitting (aka "blasting").

config IR_LIRC_CODEC

tristate "Enable IR to LIRC bridge"

depends on RC_CORE

depends on LIRC

default y

---help---

Enable this option to pass raw IR to and from userspace via

the LIRC interface.

config IR_NEC_DECODER

tristate "Enable IR raw decoder for the NEC protocol"

depends on RC_CORE

select BITREVERSE

default y

---help---

Enable this option if you have IR with NEC protocol, and

if the IR is decoded in software

config IR_RC5_DECODER

tristate "Enable IR raw decoder for the RC-5 protocol"

depends on RC_CORE

select BITREVERSE

default y

---help---

Enable this option if you have IR with RC-5 protocol, and

if the IR is decoded in software

config IR_RC6_DECODER

tristate "Enable IR raw decoder for the RC6 protocol"

depends on RC_CORE

select BITREVERSE

default y

---help---

Enable this option if you have an infrared remote control which

uses the RC6 protocol, and you need software decoding support.

config IR_JVC_DECODER

tristate "Enable IR raw decoder for the JVC protocol"

depends on RC_CORE

select BITREVERSE

default y

---help---

Enable this option if you have an infrared remote control which

uses the JVC protocol, and you need software decoding support.

config IR_SONY_DECODER

tristate "Enable IR raw decoder for the Sony protocol"

depends on RC_CORE

select BITREVERSE

default y

---help---

Enable this option if you have an infrared remote control which

uses the Sony protocol, and you need software decoding support.

config IR_SANYO_DECODER

tristate "Enable IR raw decoder for the Sanyo protocol"

depends on RC_CORE

default y

---help---

Enable this option if you have an infrared remote control which

uses the Sanyo protocol (Sanyo, Aiwa, Chinon remotes),

and you need software decoding support.

config IR_SHARP_DECODER

tristate "Enable IR raw decoder for the Sharp protocol"

depends on RC_CORE

default y

---help---

Enable this option if you have an infrared remote control which

uses the Sharp protocol (Sharp, Denon), and you need software

decoding support.

config IR_MCE_KBD_DECODER

tristate "Enable IR raw decoder for the MCE keyboard/mouse protocol"

depends on RC_CORE

select BITREVERSE

default y

---help---

Enable this option if you have a Microsoft Remote Keyboard for

Windows Media Center Edition, which you would like to use with

a raw IR receiver in your system.

config IR_XMP_DECODER

tristate "Enable IR raw decoder for the XMP protocol"

depends on RC_CORE

select BITREVERSE

default y

---help---

Enable this option if you have IR with XMP protocol, and

if the IR is decoded in software

endif #RC_DECODERS

menuconfig RC_DEVICES

bool "Remote Controller devices"

depends on RC_CORE

if RC_DEVICES

config RC_ATI_REMOTE

tristate "ATI / X10 based USB RF remote controls"

depends on USB_ARCH_HAS_HCD

depends on RC_CORE

select USB

help

Say Y here if you want to use an X10 based USB remote control.

These are RF remotes with USB receivers.

Such devices include the ATI remote that comes with many of ATI's

All-In-Wonder video cards, the X10 "Lola" remote, NVIDIA RF remote,

Medion RF remote, and SnapStream FireFly remote.

This driver provides mouse pointer, left and right mouse buttons,

and maps all the other remote buttons to keypress events.

To compile this driver as a module, choose M here: the module will be

called ati_remote.

config IR_ENE

tristate "ENE eHome Receiver/Transceiver (pnp id: ENE0100/ENE02xxx)"

depends on PNP

depends on RC_CORE

---help---

Say Y here to enable support for integrated infrared receiver

/transceiver made by ENE.

You can see if you have it by looking at lspnp output.

Output should include ENE0100 ENE0200 or something similar.

To compile this driver as a module, choose M here: the

module will be called ene_ir.

# IR_HIX5HD2 disabled for insufficient kernel version

config IR_HIX5HD2

tristate "Hisilicon hix5hd2 IR remote control"

depends on RC_CORE

default n

depends on VIDEO_KERNEL_VERSION

---help---

WARNING! This driver needs at least kernel 3.10.0! It may not

compile or work correctly on your kernel, which is too old.

Say Y here if you want to use hisilicon hix5hd2 remote control.

To compile this driver as a module, choose M here: the module will be

called ir-hix5hd2.

If you're not sure, select N here

config IR_IMON

tristate "SoundGraph iMON Receiver and Display"

depends on USB_ARCH_HAS_HCD

depends on RC_CORE

select USB

---help---

Say Y here if you want to use a SoundGraph iMON (aka Antec Veris)

IR Receiver and/or LCD/VFD/VGA display.

To compile this driver as a module, choose M here: the

module will be called imon.

config IR_MCEUSB

tristate "Windows Media Center Ed. eHome Infrared Transceiver"

depends on USB_ARCH_HAS_HCD

depends on RC_CORE

select USB

---help---

Say Y here if you want to use a Windows Media Center Edition

eHome Infrared Transceiver.

To compile this driver as a module, choose M here: the

module will be called mceusb.

config IR_ITE_CIR

tristate "ITE Tech Inc. IT8712/IT8512 Consumer Infrared Transceiver"

depends on PNP

depends on RC_CORE

---help---

Say Y here to enable support for integrated infrared receivers

/transceivers made by ITE Tech Inc. These are found in

several ASUS devices, like the ASUS Digimatrix or the ASUS

EEEBox 1501U.

To compile this driver as a module, choose M here: the

module will be called ite-cir.

config IR_FINTEK

tristate "Fintek Consumer Infrared Transceiver"

depends on PNP

depends on RC_CORE

---help---

Say Y here to enable support for integrated infrared receiver

/transciever made by Fintek. This chip is found on assorted

Jetway motherboards (and of course, possibly others).

To compile this driver as a module, choose M here: the

module will be called fintek-cir.

config IR_MESON

tristate "Amlogic Meson IR remote receiver"

depends on RC_CORE

depends on ARCH_MESON || COMPILE_TEST

---help---

Say Y if you want to use the IR remote receiver available

on Amlogic Meson SoCs.

To compile this driver as a module, choose M here: the

module will be called meson-ir.

# IR_NUVOTON disabled for insufficient kernel version

config IR_NUVOTON

tristate "Nuvoton w836x7hg Consumer Infrared Transceiver"

depends on PNP

depends on RC_CORE

default n

depends on VIDEO_KERNEL_VERSION

---help---

WARNING! This driver needs at least kernel 3.12.0! It may not

compile or work correctly on your kernel, which is too old.

Say Y here to enable support for integrated infrared receiver

/transciever made by Nuvoton (formerly Winbond). This chip is

found in the ASRock ION 330HT, as well as assorted Intel

DP55-series motherboards (and of course, possibly others).

To compile this driver as a module, choose M here: the

module will be called nuvoton-cir.

config IR_REDRAT3

tristate "RedRat3 IR Transceiver"

depends on USB_ARCH_HAS_HCD

depends on RC_CORE

select NEW_LEDS

select LEDS_CLASS

select USB

---help---

Say Y here if you want to use a RedRat3 Infrared Transceiver.

To compile this driver as a module, choose M here: the

module will be called redrat3.

config IR_STREAMZAP

tristate "Streamzap PC Remote IR Receiver"

depends on USB_ARCH_HAS_HCD

depends on RC_CORE

select USB

---help---

Say Y here if you want to use a Streamzap PC Remote

Infrared Receiver.

To compile this driver as a module, choose M here: the

module will be called streamzap.

config IR_WINBOND_CIR

tristate "Winbond IR remote control"

depends on X86 && PNP

depends on RC_CORE

select NEW_LEDS

select LEDS_CLASS

select BITREVERSE

---help---

Say Y here if you want to use the IR remote functionality found

in some Winbond SuperI/O chips. Currently only the WPCD376I

chip is supported (included in some Intel Media series

motherboards).

To compile this driver as a module, choose M here: the module will

be called winbond_cir.

config IR_IGORPLUGUSB

tristate "IgorPlug-USB IR Receiver"

depends on USB_ARCH_HAS_HCD

depends on RC_CORE

select USB

---help---

Say Y here if you want to use the IgorPlug-USB IR Receiver by

Igor Cesko. This device is included on the Fit-PC2.

Note that this device can only record bursts of 36 IR pulses and

spaces, which is not enough for the NEC, Sanyo and RC-6 protocol.

To compile this driver as a module, choose M here: the module will

be called igorplugusb.

config IR_IGUANA

tristate "IguanaWorks USB IR Transceiver"

depends on USB_ARCH_HAS_HCD

depends on RC_CORE

select USB

---help---

Say Y here if you want to use the IguanaWorks USB IR Transceiver.

Both infrared receive and send are supported. If you want to

change the ID or the pin config, use the user space driver from

IguanaWorks.

Only firmware 0x0205 and later is supported.

To compile this driver as a module, choose M here: the module will

be called iguanair.

config IR_TTUSBIR

tristate "TechnoTrend USB IR Receiver"

depends on USB_ARCH_HAS_HCD

depends on RC_CORE

select USB

select NEW_LEDS

select LEDS_CLASS

---help---

Say Y here if you want to use the TechnoTrend USB IR Receiver. The

driver can control the led.

To compile this driver as a module, choose M here: the module will

be called ttusbir.

config IR_RX51

tristate "Nokia N900 IR transmitter diode"

depends on OMAP_DM_TIMER && ARCH_OMAP2PLUS && LIRC && !ARCH_MULTIPLATFORM

---help---

Say Y or M here if you want to enable support for the IR

transmitter diode built in the Nokia N900 (RX51) device.

The driver uses omap DM timers for generating the carrier

wave and pulses.

# IR_IMG disabled for insufficient kernel version

config IR_IMG

tristate "ImgTec IR Decoder"

depends on RC_CORE

depends on METAG || MIPS || COMPILE_TEST

select IR_IMG_HW if !IR_IMG_RAW

default n

depends on VIDEO_KERNEL_VERSION

---help---

WARNING! This driver needs at least kernel 3.9.0! It may not

compile or work correctly on your kernel, which is too old.

Say Y or M here if you want to use the ImgTec infrared decoder

functionality found in SoCs such as TZ1090.

config IR_IMG_RAW

bool "Raw decoder"

depends on IR_IMG

help

Say Y here to enable the raw mode driver which passes raw IR signal

changes to the IR raw decoders for software decoding. This is much

less reliable (due to lack of timestamps) and consumes more

processing power than using hardware decode, but can be useful for

testing, debug, and to make more protocols available.

config IR_IMG_HW

bool "Hardware decoder"

depends on IR_IMG

help

Say Y here to enable the hardware decode driver which decodes the IR

signals in hardware. This is more reliable, consumes less processing

power since only a single interrupt is received for each scancode,

and allows an IR scancode to be used as a wake event.

config IR_IMG_NEC

bool "NEC protocol support"

depends on IR_IMG_HW

help

Say Y here to enable support for the NEC, extended NEC, and 32-bit

NEC protocols in the ImgTec infrared decoder block.

config IR_IMG_JVC

bool "JVC protocol support"

depends on IR_IMG_HW

help

Say Y here to enable support for the JVC protocol in the ImgTec

infrared decoder block.

config IR_IMG_SONY

bool "Sony protocol support"

depends on IR_IMG_HW

help

Say Y here to enable support for the Sony protocol in the ImgTec

infrared decoder block.

config IR_IMG_SHARP

bool "Sharp protocol support"

depends on IR_IMG_HW

help

Say Y here to enable support for the Sharp protocol in the ImgTec

infrared decoder block.

config IR_IMG_SANYO

bool "Sanyo protocol support"

depends on IR_IMG_HW

help

Say Y here to enable support for the Sanyo protocol (used by Sanyo,

Aiwa, Chinon remotes) in the ImgTec infrared decoder block.

config IR_IMG_RC5

bool "Philips RC5 protocol support"

depends on IR_IMG_HW

help

Say Y here to enable support for the RC5 protocol in the ImgTec

infrared decoder block.

config IR_IMG_RC6

bool "Philips RC6 protocol support"

depends on IR_IMG_HW

help

Say Y here to enable support for the RC6 protocol in the ImgTec

infrared decoder block.

Note: This version only supports mode 0.

config RC_LOOPBACK

tristate "Remote Control Loopback Driver"

depends on RC_CORE

---help---

Say Y here if you want support for the remote control loopback

driver which allows TX data to be sent back as RX data.

This is mostly useful for debugging purposes.

If you're not sure, select N here.

To compile this driver as a module, choose M here: the module will

be called rc_loopback.

# IR_GPIO_CIR disabled for insufficient kernel version

config IR_GPIO_CIR

tristate "GPIO IR remote control"

depends on RC_CORE

default n

depends on VIDEO_KERNEL_VERSION

---help---

WARNING! This driver needs at least kernel 3.4.0! It may not

compile or work correctly on your kernel, which is too old.

Say Y if you want to use GPIO based IR Receiver.

To compile this driver as a module, choose M here: the module will

be called gpio-ir-recv.

# RC_ST disabled for insufficient kernel version

config RC_ST

tristate "ST remote control receiver"

depends on RC_CORE

depends on ARCH_STI || COMPILE_TEST

default n

depends on VIDEO_KERNEL_VERSION

---help---

WARNING! This driver needs at least kernel 3.15.0! It may not

compile or work correctly on your kernel, which is too old.

Say Y here if you want support for ST remote control driver

which allows both IR and UHF RX.

The driver passes raw pulse and space information to the LIRC decoder.

If you're not sure, select N here.

config IR_SUNXI

tristate "SUNXI IR remote control"

depends on RC_CORE

depends on ARCH_SUNXI || COMPILE_TEST

---help---

Say Y if you want to use sunXi internal IR Controller

To compile this driver as a module, choose M here: the module will

be called sunxi-ir.

endif #RC_DEVICES

#

# V4L platform/mem2mem drivers

#

if USB && MEDIA_SUPPORT

menuconfig MEDIA_USB_SUPPORT

bool "Media USB Adapters"

help

Enable media drivers for USB bus.

If you have such devices, say Y.

if MEDIA_USB_SUPPORT

if MEDIA_CAMERA_SUPPORT

comment "Webcam devices"

config USB_VIDEO_CLASS

tristate "USB Video Class (UVC)"

depends on VIDEO_V4L2

select VIDEOBUF2_VMALLOC

---help---

Support for the USB Video Class (UVC). Currently only video

input devices, such as webcams, are supported.

For more information see: <http://linux-uvc.berlios.de/>

config USB_VIDEO_CLASS_INPUT_EVDEV

bool "UVC input events device support"

default y

depends on USB_VIDEO_CLASS

depends on USB_VIDEO_CLASS=INPUT || INPUT=y

---help---

This option makes USB Video Class devices register an input device

to report button events.

If you are in doubt, say Y.

menuconfig USB_GSPCA

tristate "GSPCA based webcams"

depends on VIDEO_V4L2

depends on INPUT || INPUT=n

default m

---help---

Say Y here if you want to enable selecting webcams based

on the GSPCA framework.

See <file:Documentation/video4linux/gspca.txt> for more info.

This driver uses the Video For Linux API. You must say Y or M to

"Video For Linux" to use this driver.

To compile this driver as modules, choose M here: the

module will be called gspca_main.

if USB_GSPCA && VIDEO_V4L2

config USB_M5602

tristate "ALi USB m5602 Camera Driver"

depends on VIDEO_V4L2 && USB_GSPCA

help

Say Y here if you want support for cameras based on the

ALi m5602 connected to various image sensors.

See <file:Documentation/video4linux/m5602.txt> for more info.

To compile this driver as a module, choose M here: the

module will be called gspca_m5602.

config USB_STV06XX

tristate "STV06XX USB Camera Driver"

depends on USB_GSPCA

help

Say Y here if you want support for cameras based on

the ST STV06XX chip.

To compile this driver as a module, choose M here: the

module will be called gspca_stv06xx.

config USB_GL860

tristate "GL860 USB Camera Driver"

depends on VIDEO_V4L2 && USB_GSPCA

help

Say Y here if you want support for cameras based on the GL860 chip.

To compile this driver as a module, choose M here: the

module will be called gspca_gl860.

config USB_GSPCA_BENQ

tristate "Benq USB Camera Driver"

depends on VIDEO_V4L2 && USB_GSPCA

help

Say Y here if you want support for the Benq DC E300 camera.

To compile this driver as a module, choose M here: the

module will be called gspca_benq.

config USB_GSPCA_CONEX

tristate "Conexant Camera Driver"

depends on VIDEO_V4L2 && USB_GSPCA

help

Say Y here if you want support for cameras based on the Conexant chip.

To compile this driver as a module, choose M here: the

module will be called gspca_conex.

config USB_GSPCA_CPIA1

tristate "cpia CPiA (version 1) Camera Driver"

depends on VIDEO_V4L2 && USB_GSPCA

help

Say Y here if you want support for USB cameras based on the cpia

CPiA chip. Note that you need atleast version 0.6.4 of libv4l for

applications to understand the videoformat generated by this driver.

To compile this driver as a module, choose M here: the

module will be called gspca_cpia1.

config USB_GSPCA_DTCS033

tristate "DTCS033 (Scopium) USB Astro-Camera Driver"

depends on VIDEO_V4L2 && USB_GSPCA

help

Say Y here if you want support for the Scopium camera

for planetary astrophotography.

To compile this driver as a module, choose M here: the

module will be called gspca_dtcs033.

config USB_GSPCA_ETOMS

tristate "Etoms USB Camera Driver"

depends on VIDEO_V4L2 && USB_GSPCA

help

Say Y here if you want support for cameras based on the Etoms chip.

To compile this driver as a module, choose M here: the

module will be called gspca_etoms.

config USB_GSPCA_FINEPIX

tristate "Fujifilm FinePix USB V4L2 driver"

depends on VIDEO_V4L2 && USB_GSPCA

help

Say Y here if you want support for cameras based on the FinePix chip.

To compile this driver as a module, choose M here: the

module will be called gspca_finepix.

config USB_GSPCA_JEILINJ

tristate "Jeilin JPEG USB V4L2 driver"

depends on VIDEO_V4L2 && USB_GSPCA

help

Say Y here if you want support for cameras based on this Jeilin chip.

To compile this driver as a module, choose M here: the

module will be called gspca_jeilinj.

config USB_GSPCA_JL2005BCD

tristate "JL2005B/C/D USB V4L2 driver"

depends on VIDEO_V4L2 && USB_GSPCA

help

Say Y here if you want support for cameras based the

JL2005B, JL2005C, or JL2005D chip.

To compile this driver as a module, choose M here: the

module will be called gspca_jl2005bcd.

config USB_GSPCA_KINECT