79 lines · plain
1# SPDX-License-Identifier: GPL-2.0-only2config VIDEO_IVTV3 tristate "Conexant cx23416/cx23415 MPEG encoder/decoder support"4 depends on VIDEO_DEV && PCI && I2C5 select I2C_ALGOBIT6 depends on RC_CORE7 select VIDEO_TUNER8 select VIDEO_TVEEPROM9 select VIDEO_CX2341X10 select VIDEO_CX2584011 select VIDEO_MSP340012 select VIDEO_SAA711X13 select VIDEO_SAA717X14 select VIDEO_SAA712715 select VIDEO_CS53L32A16 select VIDEO_M5279017 select VIDEO_WM877518 select VIDEO_WM873919 select VIDEO_VP27SMPX20 select VIDEO_UPD64031A21 select VIDEO_UPD6408322 help23 This is a video4linux driver for Conexant cx23416 or cx23415 based24 PCI personal video recorder devices.25 26 This is used in devices such as the Hauppauge PVR-150/250/350/50027 cards.28 29 To compile this driver as a module, choose M here: the30 module will be called ivtv.31 32config VIDEO_IVTV_ALSA33 tristate "Conexant cx23415/cx23416 ALSA interface for PCM audio capture"34 depends on VIDEO_IVTV && SND35 select SND_PCM36 help37 This driver provides an ALSA interface as another method for user38 applications to obtain PCM audio data from Conexant cx23415/cx2341639 based PCI TV cards supported by the ivtv driver.40 41 The ALSA interface has much wider use in user applications performing42 PCM audio capture, than the V4L2 "/dev/video24" PCM audio interface43 provided by the main ivtv driver.44 45 To compile this driver as a module, choose M here: the46 module will be called ivtv-alsa.47 48config VIDEO_FB_IVTV49 tristate "Conexant cx23415 framebuffer support"50 depends on VIDEO_IVTV && FB51 select FB_IOMEM_HELPERS52 help53 This is a framebuffer driver for the Conexant cx23415 MPEG54 encoder/decoder.55 56 This is used in the Hauppauge PVR-350 card.57 58 To compile this driver as a module, choose M here: the59 module will be called ivtvfb.60 61config VIDEO_FB_IVTV_FORCE_PAT62 bool "force cx23415 framebuffer init with x86 PAT enabled"63 depends on VIDEO_FB_IVTV && X86_PAT64 help65 With PAT enabled, the cx23415 framebuffer driver does not66 utilize write-combined caching on the framebuffer memory.67 For this reason, the driver will by default disable itself68 when initializied on a kernel with PAT enabled (i.e. not69 using the nopat kernel parameter).70 71 The driver is not easily upgradable to the PAT-aware72 ioremap_wc() API since the firmware hides the address73 ranges that should be marked write-combined from the driver.74 75 With this setting enabled, the framebuffer will initialize on76 PAT-enabled systems but the framebuffer memory will be uncached.77 78 If unsure, say N.79