.. | .. |
---|
| 1 | +# SPDX-License-Identifier: GPL-2.0-only |
---|
1 | 2 | config VIDEO_IVTV |
---|
2 | 3 | tristate "Conexant cx23416/cx23415 MPEG encoder/decoder support" |
---|
3 | 4 | depends on VIDEO_V4L2 && PCI && I2C |
---|
.. | .. |
---|
18 | 19 | select VIDEO_VP27SMPX |
---|
19 | 20 | select VIDEO_UPD64031A |
---|
20 | 21 | select VIDEO_UPD64083 |
---|
21 | | - ---help--- |
---|
| 22 | + help |
---|
22 | 23 | This is a video4linux driver for Conexant cx23416 or cx23415 based |
---|
23 | 24 | PCI personal video recorder devices. |
---|
24 | 25 | |
---|
25 | 26 | This is used in devices such as the Hauppauge PVR-150/250/350/500 |
---|
26 | | - cards. There is a driver homepage at <http://www.ivtvdriver.org>. |
---|
| 27 | + cards. |
---|
27 | 28 | |
---|
28 | 29 | To compile this driver as a module, choose M here: the |
---|
29 | 30 | module will be called ivtv. |
---|
.. | .. |
---|
31 | 32 | config VIDEO_IVTV_DEPRECATED_IOCTLS |
---|
32 | 33 | bool "enable the DVB ioctls abuse on ivtv driver" |
---|
33 | 34 | depends on VIDEO_IVTV |
---|
34 | | - default n |
---|
35 | | - ---help--- |
---|
| 35 | + help |
---|
36 | 36 | Enable the usage of the a DVB set of ioctls that were abused by |
---|
37 | 37 | IVTV driver for a while. |
---|
38 | 38 | |
---|
.. | .. |
---|
45 | 45 | tristate "Conexant cx23415/cx23416 ALSA interface for PCM audio capture" |
---|
46 | 46 | depends on VIDEO_IVTV && SND |
---|
47 | 47 | select SND_PCM |
---|
48 | | - ---help--- |
---|
| 48 | + help |
---|
49 | 49 | This driver provides an ALSA interface as another method for user |
---|
50 | 50 | applications to obtain PCM audio data from Conexant cx23415/cx23416 |
---|
51 | 51 | based PCI TV cards supported by the ivtv driver. |
---|
.. | .. |
---|
63 | 63 | select FB_CFB_FILLRECT |
---|
64 | 64 | select FB_CFB_COPYAREA |
---|
65 | 65 | select FB_CFB_IMAGEBLIT |
---|
66 | | - ---help--- |
---|
| 66 | + help |
---|
67 | 67 | This is a framebuffer driver for the Conexant cx23415 MPEG |
---|
68 | 68 | encoder/decoder. |
---|
69 | 69 | |
---|
70 | | - This is used in the Hauppauge PVR-350 card. There is a driver |
---|
71 | | - homepage at <http://www.ivtvdriver.org>. |
---|
72 | | - |
---|
73 | | - In order to use this module, you will need to boot with PAT disabled |
---|
74 | | - on x86 systems, using the nopat kernel parameter. |
---|
| 70 | + This is used in the Hauppauge PVR-350 card. |
---|
75 | 71 | |
---|
76 | 72 | To compile this driver as a module, choose M here: the |
---|
77 | 73 | module will be called ivtvfb. |
---|
| 74 | + |
---|
| 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 |
---|
| 78 | + help |
---|
| 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). |
---|
| 84 | + |
---|
| 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. |
---|
| 88 | + |
---|
| 89 | + With this setting enabled, the framebuffer will initialize on |
---|
| 90 | + PAT-enabled systems but the framebuffer memory will be uncached. |
---|
| 91 | + |
---|
| 92 | + If unsure, say N. |
---|