1 # SPDX-License-Identifier: GPL-2.0-only
3 tristate "Conexant cx23416/cx23415 MPEG encoder/decoder support"
4 depends on VIDEO_V4L2 && PCI && I2C
20 select VIDEO_UPD64031A
23 This is a video4linux driver for Conexant cx23416 or cx23415 based
24 PCI personal video recorder devices.
26 This is used in devices such as the Hauppauge PVR-150/250/350/500
29 To compile this driver as a module, choose M here: the
30 module will be called ivtv.
32 config VIDEO_IVTV_DEPRECATED_IOCTLS
33 bool "enable the DVB ioctls abuse on ivtv driver"
36 Enable the usage of the a DVB set of ioctls that were abused by
37 IVTV driver for a while.
39 Those ioctls were not needed for a long time, as IVTV implements
40 the proper V4L2 ioctls since kernel 3.3.
44 config VIDEO_IVTV_ALSA
45 tristate "Conexant cx23415/cx23416 ALSA interface for PCM audio capture"
46 depends on VIDEO_IVTV && SND
49 This driver provides an ALSA interface as another method for user
50 applications to obtain PCM audio data from Conexant cx23415/cx23416
51 based PCI TV cards supported by the ivtv driver.
53 The ALSA interface has much wider use in user applications performing
54 PCM audio capture, than the V4L2 "/dev/video24" PCM audio interface
55 provided by the main ivtv driver.
57 To compile this driver as a module, choose M here: the
58 module will be called ivtv-alsa.
61 tristate "Conexant cx23415 framebuffer support"
62 depends on VIDEO_IVTV && FB
63 select FB_CFB_FILLRECT
64 select FB_CFB_COPYAREA
65 select FB_CFB_IMAGEBLIT
67 This is a framebuffer driver for the Conexant cx23415 MPEG
70 This is used in the Hauppauge PVR-350 card.
72 To compile this driver as a module, choose M here: the
73 module will be called ivtvfb.
75 config VIDEO_FB_IVTV_FORCE_PAT
76 bool "force cx23415 framebuffer init with x86 PAT enabled"
77 depends on VIDEO_FB_IVTV && X86_PAT
79 With PAT enabled, the cx23415 framebuffer driver does not
80 utilize write-combined caching on the framebuffer memory.
81 For this reason, the driver will by default disable itself
82 when initializied on a kernel with PAT enabled (i.e. not
83 using the nopat kernel parameter).
85 The driver is not easily upgradable to the PAT-aware
86 ioremap_wc() API since the firmware hides the address
87 ranges that should be marked write-combined from the driver.
89 With this setting enabled, the framebuffer will initialize on
90 PAT-enabled systems but the framebuffer memory will be uncached.