[RFCv2 PATCH 0/7] V4L menu reorganization

[RFCv2 PATCH 0/7] V4L menu reorganization

[Hans Verkuil]

Hi all,

This is the second version of my patch series reorganizing the V4L menu.
It's based on the latest v3.2 staging tree.

Changes to v1:

- Remove unnecessary USB dependency.
- Reorganize the radio menu as well.

I did not sort the drivers alphabetically (yet). I'm not quite sure whether
that's really a good idea, and we can always do that later.

This series is meant for v3.2, but I won't make a pull request until
Guennadi's pull request is merged first. I'm sure I will have to redo my
patches once his series is in.

Regards,

	Hans

[RFCv2 PATCH 1/7] V4L menu: move USB drivers section to the top.

[Hans Verkuil]

From: Hans Verkuil <hans.verkuil@cisco.com>

USB webcams are some of the most used V4L devices, so move it to a more
prominent place in the menu instead of being at the end.

Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
---
 drivers/media/video/Kconfig |  145 ++++++++++++++++++++++---------------------
 1 files changed, 73 insertions(+), 72 deletions(-)

diff --git a/drivers/media/video/Kconfig b/drivers/media/video/Kconfig
index aed5b3d..0f8ccb4 100644
--- a/drivers/media/video/Kconfig
+++ b/drivers/media/video/Kconfig
@@ -573,6 +573,79 @@ config VIDEO_M52790
 
 endmenu # encoder / decoder chips
 
+#
+# USB Multimedia device configuration
+#
+
+menuconfig V4L_USB_DRIVERS
+	bool "V4L USB devices"
+	depends on USB
+	default y
+
+if V4L_USB_DRIVERS && USB
+
+source "drivers/media/video/uvc/Kconfig"
+
+source "drivers/media/video/gspca/Kconfig"
+
+source "drivers/media/video/pvrusb2/Kconfig"
+
+source "drivers/media/video/hdpvr/Kconfig"
+
+source "drivers/media/video/em28xx/Kconfig"
+
+source "drivers/media/video/tlg2300/Kconfig"
+
+source "drivers/media/video/cx231xx/Kconfig"
+
+source "drivers/media/video/tm6000/Kconfig"
+
+source "drivers/media/video/usbvision/Kconfig"
+
+source "drivers/media/video/et61x251/Kconfig"
+
+source "drivers/media/video/sn9c102/Kconfig"
+
+source "drivers/media/video/pwc/Kconfig"
+
+config USB_ZR364XX
+	tristate "USB ZR364XX Camera support"
+	depends on VIDEO_V4L2
+	select VIDEOBUF_GEN
+	select VIDEOBUF_VMALLOC
+	---help---
+	  Say Y here if you want to connect this type of camera to your
+	  computer's USB port.
+	  See <file:Documentation/video4linux/zr364xx.txt> for more info
+	  and list of supported cameras.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called zr364xx.
+
+config USB_STKWEBCAM
+	tristate "USB Syntek DC1125 Camera support"
+	depends on VIDEO_V4L2 && EXPERIMENTAL
+	---help---
+	  Say Y here if you want to use this type of camera.
+	  Supported devices are typically found in some Asus laptops,
+	  with USB id 174f:a311 and 05e1:0501. Other Syntek cameras
+	  may be supported by the stk11xx driver, from which this is
+	  derived, see <http://sourceforge.net/projects/syntekdriver/>
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called stkwebcam.
+
+config USB_S2255
+	tristate "USB Sensoray 2255 video capture device"
+	depends on VIDEO_V4L2
+	select VIDEOBUF_VMALLOC
+	default n
+	help
+	  Say Y here if you want support for the Sensoray 2255 USB device.
+	  This driver can be compiled as a module, called s2255drv.
+
+endif # V4L_USB_DRIVERS
+
 config VIDEO_SH_VOU
 	tristate "SuperH VOU video output driver"
 	depends on VIDEO_DEV && ARCH_SHMOBILE
@@ -994,78 +1067,6 @@ config VIDEO_S5P_MIPI_CSIS
 
 source "drivers/media/video/s5p-tv/Kconfig"
 
-#
-# USB Multimedia device configuration
-#
-
-menuconfig V4L_USB_DRIVERS
-	bool "V4L USB devices"
-	depends on USB
-	default y
-
-if V4L_USB_DRIVERS && USB
-
-source "drivers/media/video/uvc/Kconfig"
-
-source "drivers/media/video/gspca/Kconfig"
-
-source "drivers/media/video/pvrusb2/Kconfig"
-
-source "drivers/media/video/hdpvr/Kconfig"
-
-source "drivers/media/video/em28xx/Kconfig"
-
-source "drivers/media/video/tlg2300/Kconfig"
-
-source "drivers/media/video/cx231xx/Kconfig"
-
-source "drivers/media/video/tm6000/Kconfig"
-
-source "drivers/media/video/usbvision/Kconfig"
-
-source "drivers/media/video/et61x251/Kconfig"
-
-source "drivers/media/video/sn9c102/Kconfig"
-
-source "drivers/media/video/pwc/Kconfig"
-
-config USB_ZR364XX
-	tristate "USB ZR364XX Camera support"
-	depends on VIDEO_V4L2
-	select VIDEOBUF_GEN
-	select VIDEOBUF_VMALLOC
-	---help---
-	  Say Y here if you want to connect this type of camera to your
-	  computer's USB port.
-	  See <file:Documentation/video4linux/zr364xx.txt> for more info
-	  and list of supported cameras.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called zr364xx.
-
-config USB_STKWEBCAM
-	tristate "USB Syntek DC1125 Camera support"
-	depends on VIDEO_V4L2 && EXPERIMENTAL
-	---help---
-	  Say Y here if you want to use this type of camera.
-	  Supported devices are typically found in some Asus laptops,
-	  with USB id 174f:a311 and 05e1:0501. Other Syntek cameras
-	  may be supported by the stk11xx driver, from which this is
-	  derived, see <http://sourceforge.net/projects/syntekdriver/>
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called stkwebcam.
-
-config USB_S2255
-	tristate "USB Sensoray 2255 video capture device"
-	depends on VIDEO_V4L2
-	select VIDEOBUF_VMALLOC
-	default n
-	help
-	  Say Y here if you want support for the Sensoray 2255 USB device.
-	  This driver can be compiled as a module, called s2255drv.
-
-endif # V4L_USB_DRIVERS
 endif # VIDEO_CAPTURE_DRIVERS
 
 menuconfig V4L_MEM2MEM_DRIVERS
-- 
1.7.6.3

[RFCv2 PATCH 2/7] V4L menu: move legacy drivers into their own submenu.

[Hans Verkuil]

From: Hans Verkuil <hans.verkuil@cisco.com>

Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
---
 drivers/media/video/Kconfig |  185 +++++++++++++++++++++++-------------------
 1 files changed, 101 insertions(+), 84 deletions(-)

diff --git a/drivers/media/video/Kconfig b/drivers/media/video/Kconfig
index 0f8ccb4..86fdd7d 100644
--- a/drivers/media/video/Kconfig
+++ b/drivers/media/video/Kconfig
@@ -685,51 +685,6 @@ source "drivers/media/video/omap/Kconfig"
 
 source "drivers/media/video/bt8xx/Kconfig"
 
-config VIDEO_PMS
-	tristate "Mediavision Pro Movie Studio Video For Linux"
-	depends on ISA && VIDEO_V4L2
-	help
-	  Say Y if you have such a thing.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called pms.
-
-config VIDEO_BWQCAM
-	tristate "Quickcam BW Video For Linux"
-	depends on PARPORT && VIDEO_V4L2
-	help
-	  Say Y have if you the black and white version of the QuickCam
-	  camera. See the next option for the color version.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called bw-qcam.
-
-config VIDEO_CQCAM
-	tristate "QuickCam Colour Video For Linux (EXPERIMENTAL)"
-	depends on EXPERIMENTAL && PARPORT && VIDEO_V4L2
-	help
-	  This is the video4linux driver for the colour version of the
-	  Connectix QuickCam.  If you have one of these cameras, say Y here,
-	  otherwise say N.  This driver does not work with the original
-	  monochrome QuickCam, QuickCam VC or QuickClip.  It is also available
-	  as a module (c-qcam).
-	  Read <file:Documentation/video4linux/CQcam.txt> for more information.
-
-config VIDEO_W9966
-	tristate "W9966CF Webcam (FlyCam Supra and others) Video For Linux"
-	depends on PARPORT_1284 && PARPORT && VIDEO_V4L2
-	help
-	  Video4linux driver for Winbond's w9966 based Webcams.
-	  Currently tested with the LifeView FlyCam Supra.
-	  If you have one of these cameras, say Y here
-	  otherwise say N.
-	  This driver is also available as a module (w9966).
-
-	  Check out <file:Documentation/video4linux/w9966.txt> for more
-	  information.
-
-source "drivers/media/video/cpia2/Kconfig"
-
 config VIDEO_VINO
 	tristate "SGI Vino Video For Linux (EXPERIMENTAL)"
 	depends on I2C && SGI_IP22 && EXPERIMENTAL && VIDEO_V4L2
@@ -756,45 +711,6 @@ config VIDEO_MEYE
 
 source "drivers/media/video/saa7134/Kconfig"
 
-config VIDEO_MXB
-	tristate "Siemens-Nixdorf 'Multimedia eXtension Board'"
-	depends on PCI && VIDEO_V4L2 && I2C
-	select VIDEO_SAA7146_VV
-	select VIDEO_TUNER
-	select VIDEO_SAA711X if VIDEO_HELPER_CHIPS_AUTO
-	select VIDEO_TDA9840 if VIDEO_HELPER_CHIPS_AUTO
-	select VIDEO_TEA6415C if VIDEO_HELPER_CHIPS_AUTO
-	select VIDEO_TEA6420 if VIDEO_HELPER_CHIPS_AUTO
-	---help---
-	  This is a video4linux driver for the 'Multimedia eXtension Board'
-	  TV card by Siemens-Nixdorf.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called mxb.
-
-config VIDEO_HEXIUM_ORION
-	tristate "Hexium HV-PCI6 and Orion frame grabber"
-	depends on PCI && VIDEO_V4L2 && I2C
-	select VIDEO_SAA7146_VV
-	---help---
-	  This is a video4linux driver for the Hexium HV-PCI6 and
-	  Orion frame grabber cards by Hexium.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called hexium_orion.
-
-config VIDEO_HEXIUM_GEMINI
-	tristate "Hexium Gemini frame grabber"
-	depends on PCI && VIDEO_V4L2 && I2C
-	select VIDEO_SAA7146_VV
-	---help---
-	  This is a video4linux driver for the Hexium Gemini frame
-	  grabber card by Hexium. Please note that the Gemini Dual
-	  card is *not* fully supported.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called hexium_gemini.
-
 config VIDEO_TIMBERDALE
 	tristate "Support for timberdale Video In/LogiWIN"
 	depends on VIDEO_V4L2 && I2C && DMADEVICES
@@ -1067,6 +983,107 @@ config VIDEO_S5P_MIPI_CSIS
 
 source "drivers/media/video/s5p-tv/Kconfig"
 
+#
+# Legacy drivers configuration
+#
+
+menuconfig V4L_LEGACY_DRIVERS
+	bool "V4L legacy devices"
+	default n
+	---help---
+	  Say Y here to enable support for these legacy drivers. These drivers
+	  are for old and obsure hardware (e.g. parallel port webcams, ISA
+	  drivers, niche hardware).
+
+if V4L_LEGACY_DRIVERS
+
+config VIDEO_PMS
+	tristate "Mediavision Pro Movie Studio Video For Linux"
+	depends on ISA && VIDEO_V4L2
+	help
+	  Say Y if you have the ISA Mediavision Pro Movie Studio
+	  capture card.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called pms.
+
+config VIDEO_BWQCAM
+	tristate "Quickcam BW Video For Linux"
+	depends on PARPORT && VIDEO_V4L2
+	help
+	  Say Y have if you the black and white version of the QuickCam
+	  camera. See the next option for the color version.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called bw-qcam.
+
+config VIDEO_CQCAM
+	tristate "QuickCam Colour Video For Linux (EXPERIMENTAL)"
+	depends on EXPERIMENTAL && PARPORT && VIDEO_V4L2
+	help
+	  This is the video4linux driver for the colour version of the
+	  Connectix QuickCam.  If you have one of these cameras, say Y here,
+	  otherwise say N.  This driver does not work with the original
+	  monochrome QuickCam, QuickCam VC or QuickClip.  It is also available
+	  as a module (c-qcam).
+	  Read <file:Documentation/video4linux/CQcam.txt> for more information.
+
+config VIDEO_W9966
+	tristate "W9966CF Webcam (FlyCam Supra and others) Video For Linux"
+	depends on PARPORT_1284 && PARPORT && VIDEO_V4L2
+	help
+	  Video4linux driver for Winbond's w9966 based Webcams.
+	  Currently tested with the LifeView FlyCam Supra.
+	  If you have one of these cameras, say Y here
+	  otherwise say N.
+	  This driver is also available as a module (w9966).
+
+	  Check out <file:Documentation/video4linux/w9966.txt> for more
+	  information.
+
+source "drivers/media/video/cpia2/Kconfig"
+
+config VIDEO_MXB
+	tristate "Siemens-Nixdorf 'Multimedia eXtension Board'"
+	depends on PCI && VIDEO_V4L2 && I2C
+	select VIDEO_SAA7146_VV
+	select VIDEO_TUNER
+	select VIDEO_SAA711X if VIDEO_HELPER_CHIPS_AUTO
+	select VIDEO_TDA9840 if VIDEO_HELPER_CHIPS_AUTO
+	select VIDEO_TEA6415C if VIDEO_HELPER_CHIPS_AUTO
+	select VIDEO_TEA6420 if VIDEO_HELPER_CHIPS_AUTO
+	---help---
+	  This is a video4linux driver for the 'Multimedia eXtension Board'
+	  TV card by Siemens-Nixdorf.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called mxb.
+
+config VIDEO_HEXIUM_ORION
+	tristate "Hexium HV-PCI6 and Orion frame grabber"
+	depends on PCI && VIDEO_V4L2 && I2C
+	select VIDEO_SAA7146_VV
+	---help---
+	  This is a video4linux driver for the Hexium HV-PCI6 and
+	  Orion frame grabber cards by Hexium.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called hexium_orion.
+
+config VIDEO_HEXIUM_GEMINI
+	tristate "Hexium Gemini frame grabber"
+	depends on PCI && VIDEO_V4L2 && I2C
+	select VIDEO_SAA7146_VV
+	---help---
+	  This is a video4linux driver for the Hexium Gemini frame
+	  grabber card by Hexium. Please note that the Gemini Dual
+	  card is *not* fully supported.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called hexium_gemini.
+
+endif # V4L_LEGACY_DRIVERS
+
 endif # VIDEO_CAPTURE_DRIVERS
 
 menuconfig V4L_MEM2MEM_DRIVERS
-- 
1.7.6.3

[RFCv2 PATCH 3/7] V4L menu: remove the EXPERIMENTAL tag from vino and c-qcam.

[Hans Verkuil]

From: Hans Verkuil <hans.verkuil@cisco.com>

These are really, really old drivers. These are really no longer experimental...

Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
---
 drivers/media/video/Kconfig |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/drivers/media/video/Kconfig b/drivers/media/video/Kconfig
index 86fdd7d..fafc9ba 100644
--- a/drivers/media/video/Kconfig
+++ b/drivers/media/video/Kconfig
@@ -686,8 +686,8 @@ source "drivers/media/video/omap/Kconfig"
 source "drivers/media/video/bt8xx/Kconfig"
 
 config VIDEO_VINO
-	tristate "SGI Vino Video For Linux (EXPERIMENTAL)"
-	depends on I2C && SGI_IP22 && EXPERIMENTAL && VIDEO_V4L2
+	tristate "SGI Vino Video For Linux"
+	depends on I2C && SGI_IP22 && VIDEO_V4L2
 	select VIDEO_SAA7191 if VIDEO_HELPER_CHIPS_AUTO
 	help
 	  Say Y here to build in support for the Vino video input system found
@@ -1018,8 +1018,8 @@ config VIDEO_BWQCAM
 	  module will be called bw-qcam.
 
 config VIDEO_CQCAM
-	tristate "QuickCam Colour Video For Linux (EXPERIMENTAL)"
-	depends on EXPERIMENTAL && PARPORT && VIDEO_V4L2
+	tristate "QuickCam Colour Video For Linux"
+	depends on PARPORT && VIDEO_V4L2
 	help
 	  This is the video4linux driver for the colour version of the
 	  Connectix QuickCam.  If you have one of these cameras, say Y here,
-- 
1.7.6.3

[RFCv2 PATCH 4/7] V4L menu: move all platform drivers to the bottom of the menu.

[Hans Verkuil]

From: Hans Verkuil <hans.verkuil@cisco.com>

Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
---
 drivers/media/video/Kconfig |  106 ++++++++++++++++++++++---------------------
 1 files changed, 55 insertions(+), 51 deletions(-)

diff --git a/drivers/media/video/Kconfig b/drivers/media/video/Kconfig
index fafc9ba..07d31d4 100644
--- a/drivers/media/video/Kconfig
+++ b/drivers/media/video/Kconfig
@@ -646,25 +646,6 @@ config USB_S2255
 
 endif # V4L_USB_DRIVERS
 
-config VIDEO_SH_VOU
-	tristate "SuperH VOU video output driver"
-	depends on VIDEO_DEV && ARCH_SHMOBILE
-	select VIDEOBUF_DMA_CONTIG
-	help
-	  Support for the Video Output Unit (VOU) on SuperH SoCs.
-
-config VIDEO_VIU
-	tristate "Freescale VIU Video Driver"
-	depends on VIDEO_V4L2 && PPC_MPC512x
-	select VIDEOBUF_DMA_CONTIG
-	default y
-	---help---
-	  Support for Freescale VIU video driver. This device captures
-	  video data, or overlays video on DIU frame buffer.
-
-	  Say Y here if you want to enable VIU device on MPC5121e Rev2+.
-	  In doubt, say N.
-
 config VIDEO_VIVI
 	tristate "Virtual Video Driver"
 	depends on VIDEO_DEV && VIDEO_V4L2 && !SPARC32 && !SPARC64
@@ -679,20 +660,8 @@ config VIDEO_VIVI
 	  Say Y here if you want to test video apps or debug V4L devices.
 	  In doubt, say N.
 
-source "drivers/media/video/davinci/Kconfig"
-
-source "drivers/media/video/omap/Kconfig"
-
 source "drivers/media/video/bt8xx/Kconfig"
 
-config VIDEO_VINO
-	tristate "SGI Vino Video For Linux"
-	depends on I2C && SGI_IP22 && VIDEO_V4L2
-	select VIDEO_SAA7191 if VIDEO_HELPER_CHIPS_AUTO
-	help
-	  Say Y here to build in support for the Vino video input system found
-	  on SGI Indy machines.
-
 source "drivers/media/video/zoran/Kconfig"
 
 config VIDEO_MEYE
@@ -711,16 +680,6 @@ config VIDEO_MEYE
 
 source "drivers/media/video/saa7134/Kconfig"
 
-config VIDEO_TIMBERDALE
-	tristate "Support for timberdale Video In/LogiWIN"
-	depends on VIDEO_V4L2 && I2C && DMADEVICES
-	select DMA_ENGINE
-	select TIMB_DMA
-	select VIDEO_ADV7180
-	select VIDEOBUF_DMA_CONTIG
-	---help---
-	  Add support for the Video In peripherial of the timberdale FPGA.
-
 source "drivers/media/video/cx88/Kconfig"
 
 source "drivers/media/video/cx23885/Kconfig"
@@ -735,6 +694,61 @@ source "drivers/media/video/saa7164/Kconfig"
 
 source "drivers/media/video/marvell-ccic/Kconfig"
 
+config VIDEO_VIA_CAMERA
+	tristate "VIAFB camera controller support"
+	depends on FB_VIA
+	select VIDEOBUF_DMA_SG
+	select VIDEO_OV7670
+	help
+	   Driver support for the integrated camera controller in VIA
+	   Chrome9 chipsets.  Currently only tested on OLPC xo-1.5 systems
+	   with ov7670 sensors.
+
+#
+# Platform multimedia device configuration
+#
+
+source "drivers/media/video/davinci/Kconfig"
+
+source "drivers/media/video/omap/Kconfig"
+
+config VIDEO_SH_VOU
+	tristate "SuperH VOU video output driver"
+	depends on VIDEO_DEV && ARCH_SHMOBILE
+	select VIDEOBUF_DMA_CONTIG
+	help
+	  Support for the Video Output Unit (VOU) on SuperH SoCs.
+
+config VIDEO_VIU
+	tristate "Freescale VIU Video Driver"
+	depends on VIDEO_V4L2 && PPC_MPC512x
+	select VIDEOBUF_DMA_CONTIG
+	default y
+	---help---
+	  Support for Freescale VIU video driver. This device captures
+	  video data, or overlays video on DIU frame buffer.
+
+	  Say Y here if you want to enable VIU device on MPC5121e Rev2+.
+	  In doubt, say N.
+
+config VIDEO_TIMBERDALE
+	tristate "Support for timberdale Video In/LogiWIN"
+	depends on VIDEO_V4L2 && I2C && DMADEVICES
+	select DMA_ENGINE
+	select TIMB_DMA
+	select VIDEO_ADV7180
+	select VIDEOBUF_DMA_CONTIG
+	---help---
+	  Add support for the Video In peripherial of the timberdale FPGA.
+
+config VIDEO_VINO
+	tristate "SGI Vino Video For Linux"
+	depends on I2C && SGI_IP22 && VIDEO_V4L2
+	select VIDEO_SAA7191 if VIDEO_HELPER_CHIPS_AUTO
+	help
+	  Say Y here to build in support for the Vino video input system found
+	  on SGI Indy machines.
+
 config VIDEO_M32R_AR
 	tristate "AR devices"
 	depends on M32R && VIDEO_V4L2
@@ -754,16 +768,6 @@ config VIDEO_M32R_AR_M64278
 	  To compile this driver as a module, choose M here: the
 	  module will be called arv.
 
-config VIDEO_VIA_CAMERA
-	tristate "VIAFB camera controller support"
-	depends on FB_VIA
-	select VIDEOBUF_DMA_SG
-	select VIDEO_OV7670
-	help
-	   Driver support for the integrated camera controller in VIA
-	   Chrome9 chipsets.  Currently only tested on OLPC xo-1.5 systems
-	   with ov7670 sensors.
-
 config VIDEO_OMAP3
 	tristate "OMAP 3 Camera support (EXPERIMENTAL)"
 	select OMAP_IOMMU
-- 
1.7.6.3

[RFCv2 PATCH 5/7] VL menu: Move some of the less often used drivers down in the menu list.

[Hans Verkuil]

From: Hans Verkuil <hans.verkuil@cisco.com>

Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
---
 drivers/media/video/Kconfig |   32 ++++++++++++++++----------------
 1 files changed, 16 insertions(+), 16 deletions(-)

diff --git a/drivers/media/video/Kconfig b/drivers/media/video/Kconfig
index 07d31d4..b4a14f3 100644
--- a/drivers/media/video/Kconfig
+++ b/drivers/media/video/Kconfig
@@ -662,22 +662,6 @@ config VIDEO_VIVI
 
 source "drivers/media/video/bt8xx/Kconfig"
 
-source "drivers/media/video/zoran/Kconfig"
-
-config VIDEO_MEYE
-	tristate "Sony Vaio Picturebook Motion Eye Video For Linux"
-	depends on PCI && SONY_LAPTOP && VIDEO_V4L2
-	---help---
-	  This is the video4linux driver for the Motion Eye camera found
-	  in the Vaio Picturebook laptops. Please read the material in
-	  <file:Documentation/video4linux/meye.txt> for more information.
-
-	  If you say Y or M here, you need to say Y or M to "Sony Laptop
-	  Extras" in the misc device section.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called meye.
-
 source "drivers/media/video/saa7134/Kconfig"
 
 source "drivers/media/video/cx88/Kconfig"
@@ -692,6 +676,8 @@ source "drivers/media/video/cx18/Kconfig"
 
 source "drivers/media/video/saa7164/Kconfig"
 
+source "drivers/media/video/zoran/Kconfig"
+
 source "drivers/media/video/marvell-ccic/Kconfig"
 
 config VIDEO_VIA_CAMERA
@@ -704,6 +690,20 @@ config VIDEO_VIA_CAMERA
 	   Chrome9 chipsets.  Currently only tested on OLPC xo-1.5 systems
 	   with ov7670 sensors.
 
+config VIDEO_MEYE
+	tristate "Sony Vaio Picturebook Motion Eye Video For Linux"
+	depends on PCI && SONY_LAPTOP && VIDEO_V4L2
+	---help---
+	  This is the video4linux driver for the Motion Eye camera found
+	  in the Vaio Picturebook laptops. Please read the material in
+	  <file:Documentation/video4linux/meye.txt> for more information.
+
+	  If you say Y or M here, you need to say Y or M to "Sony Laptop
+	  Extras" in the misc device section.
+
+	  To compile this driver as a module, choose M here: the
+	  module will be called meye.
+
 #
 # Platform multimedia device configuration
 #
-- 
1.7.6.3

[RFCv2 PATCH 6/7] V4L menu: remove duplicate USB dependency.

[Hans Verkuil]

From: Hans Verkuil <hans.verkuil@cisco.com>

Thanks to Guennadi Liakhovetski <g.liakhovetski@gmx.de> for pointing this
out to me.

Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
---
 drivers/media/video/Kconfig |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/media/video/Kconfig b/drivers/media/video/Kconfig
index b4a14f3..9408e69 100644
--- a/drivers/media/video/Kconfig
+++ b/drivers/media/video/Kconfig
@@ -582,7 +582,7 @@ menuconfig V4L_USB_DRIVERS
 	depends on USB
 	default y
 
-if V4L_USB_DRIVERS && USB
+if V4L_USB_DRIVERS
 
 source "drivers/media/video/uvc/Kconfig"
 
-- 
1.7.6.3

Re: [RFCv2 PATCH 2/7] V4L menu: move legacy drivers into their own submenu.

[Mauro Carvalho Chehab]

Em 30-09-2011 06:01, Hans Verkuil escreveu:
> From: Hans Verkuil <hans.verkuil@cisco.com>
> 
> Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
> ---
>  drivers/media/video/Kconfig |  185 +++++++++++++++++++++++-------------------
>  1 files changed, 101 insertions(+), 84 deletions(-)
> 
> diff --git a/drivers/media/video/Kconfig b/drivers/media/video/Kconfig
> index 0f8ccb4..86fdd7d 100644
> --- a/drivers/media/video/Kconfig
> +++ b/drivers/media/video/Kconfig
> @@ -685,51 +685,6 @@ source "drivers/media/video/omap/Kconfig"
>  
>  source "drivers/media/video/bt8xx/Kconfig"
>  
> -config VIDEO_PMS
> -	tristate "Mediavision Pro Movie Studio Video For Linux"
> -	depends on ISA && VIDEO_V4L2
> -	help
> -	  Say Y if you have such a thing.
> -
> -	  To compile this driver as a module, choose M here: the
> -	  module will be called pms.
> -
> -config VIDEO_BWQCAM
> -	tristate "Quickcam BW Video For Linux"
> -	depends on PARPORT && VIDEO_V4L2
> -	help
> -	  Say Y have if you the black and white version of the QuickCam
> -	  camera. See the next option for the color version.
> -
> -	  To compile this driver as a module, choose M here: the
> -	  module will be called bw-qcam.
> -
> -config VIDEO_CQCAM
> -	tristate "QuickCam Colour Video For Linux (EXPERIMENTAL)"
> -	depends on EXPERIMENTAL && PARPORT && VIDEO_V4L2
> -	help
> -	  This is the video4linux driver for the colour version of the
> -	  Connectix QuickCam.  If you have one of these cameras, say Y here,
> -	  otherwise say N.  This driver does not work with the original
> -	  monochrome QuickCam, QuickCam VC or QuickClip.  It is also available
> -	  as a module (c-qcam).
> -	  Read <file:Documentation/video4linux/CQcam.txt> for more information.
> -
> -config VIDEO_W9966
> -	tristate "W9966CF Webcam (FlyCam Supra and others) Video For Linux"
> -	depends on PARPORT_1284 && PARPORT && VIDEO_V4L2
> -	help
> -	  Video4linux driver for Winbond's w9966 based Webcams.
> -	  Currently tested with the LifeView FlyCam Supra.
> -	  If you have one of these cameras, say Y here
> -	  otherwise say N.
> -	  This driver is also available as a module (w9966).
> -
> -	  Check out <file:Documentation/video4linux/w9966.txt> for more
> -	  information.
> -
> -source "drivers/media/video/cpia2/Kconfig"
> -
>  config VIDEO_VINO
>  	tristate "SGI Vino Video For Linux (EXPERIMENTAL)"
>  	depends on I2C && SGI_IP22 && EXPERIMENTAL && VIDEO_V4L2
> @@ -756,45 +711,6 @@ config VIDEO_MEYE
>  
>  source "drivers/media/video/saa7134/Kconfig"
>  
> -config VIDEO_MXB
> -	tristate "Siemens-Nixdorf 'Multimedia eXtension Board'"
> -	depends on PCI && VIDEO_V4L2 && I2C
> -	select VIDEO_SAA7146_VV
> -	select VIDEO_TUNER
> -	select VIDEO_SAA711X if VIDEO_HELPER_CHIPS_AUTO
> -	select VIDEO_TDA9840 if VIDEO_HELPER_CHIPS_AUTO
> -	select VIDEO_TEA6415C if VIDEO_HELPER_CHIPS_AUTO
> -	select VIDEO_TEA6420 if VIDEO_HELPER_CHIPS_AUTO
> -	---help---
> -	  This is a video4linux driver for the 'Multimedia eXtension Board'
> -	  TV card by Siemens-Nixdorf.
> -
> -	  To compile this driver as a module, choose M here: the
> -	  module will be called mxb.
> -
> -config VIDEO_HEXIUM_ORION
> -	tristate "Hexium HV-PCI6 and Orion frame grabber"
> -	depends on PCI && VIDEO_V4L2 && I2C
> -	select VIDEO_SAA7146_VV
> -	---help---
> -	  This is a video4linux driver for the Hexium HV-PCI6 and
> -	  Orion frame grabber cards by Hexium.
> -
> -	  To compile this driver as a module, choose M here: the
> -	  module will be called hexium_orion.
> -
> -config VIDEO_HEXIUM_GEMINI
> -	tristate "Hexium Gemini frame grabber"
> -	depends on PCI && VIDEO_V4L2 && I2C
> -	select VIDEO_SAA7146_VV
> -	---help---
> -	  This is a video4linux driver for the Hexium Gemini frame
> -	  grabber card by Hexium. Please note that the Gemini Dual
> -	  card is *not* fully supported.
> -
> -	  To compile this driver as a module, choose M here: the
> -	  module will be called hexium_gemini.
> -
>  config VIDEO_TIMBERDALE
>  	tristate "Support for timberdale Video In/LogiWIN"
>  	depends on VIDEO_V4L2 && I2C && DMADEVICES
> @@ -1067,6 +983,107 @@ config VIDEO_S5P_MIPI_CSIS
>  
>  source "drivers/media/video/s5p-tv/Kconfig"
>  
> +#
> +# Legacy drivers configuration
> +#
> +
> +menuconfig V4L_LEGACY_DRIVERS
> +	bool "V4L legacy devices"
> +	default n
> +	---help---
> +	  Say Y here to enable support for these legacy drivers. These drivers
> +	  are for old and obsure hardware (e.g. parallel port webcams, ISA
> +	  drivers, niche hardware).

As before, I don't like the name "legacy". The drivers themselves are not
legacy, as they work fine, as far as I know.

Parallel port and ISA could be just called as "parallel port and ISA drivers".

With regards to saa7146 drivers, it is hard to say the the hardware is more
legacy than, for example, bttv.

As I said before, defining what's a legacy hardware and what isn't is not
an objective criteria: it is legacy on what sense? I was told that tda18271
were recently discontinued. Should we mark all drivers that use it as legacy?

> +
> +if V4L_LEGACY_DRIVERS
> +
> +config VIDEO_PMS
> +	tristate "Mediavision Pro Movie Studio Video For Linux"
> +	depends on ISA && VIDEO_V4L2
> +	help
> +	  Say Y if you have the ISA Mediavision Pro Movie Studio
> +	  capture card.
> +
> +	  To compile this driver as a module, choose M here: the
> +	  module will be called pms.
> +
> +config VIDEO_BWQCAM
> +	tristate "Quickcam BW Video For Linux"
> +	depends on PARPORT && VIDEO_V4L2
> +	help
> +	  Say Y have if you the black and white version of the QuickCam
> +	  camera. See the next option for the color version.
> +
> +	  To compile this driver as a module, choose M here: the
> +	  module will be called bw-qcam.
> +
> +config VIDEO_CQCAM
> +	tristate "QuickCam Colour Video For Linux (EXPERIMENTAL)"
> +	depends on EXPERIMENTAL && PARPORT && VIDEO_V4L2
> +	help
> +	  This is the video4linux driver for the colour version of the
> +	  Connectix QuickCam.  If you have one of these cameras, say Y here,
> +	  otherwise say N.  This driver does not work with the original
> +	  monochrome QuickCam, QuickCam VC or QuickClip.  It is also available
> +	  as a module (c-qcam).
> +	  Read <file:Documentation/video4linux/CQcam.txt> for more information.
> +
> +config VIDEO_W9966
> +	tristate "W9966CF Webcam (FlyCam Supra and others) Video For Linux"
> +	depends on PARPORT_1284 && PARPORT && VIDEO_V4L2
> +	help
> +	  Video4linux driver for Winbond's w9966 based Webcams.
> +	  Currently tested with the LifeView FlyCam Supra.
> +	  If you have one of these cameras, say Y here
> +	  otherwise say N.
> +	  This driver is also available as a module (w9966).
> +
> +	  Check out <file:Documentation/video4linux/w9966.txt> for more
> +	  information.
> +
> +source "drivers/media/video/cpia2/Kconfig"
> +
> +config VIDEO_MXB
> +	tristate "Siemens-Nixdorf 'Multimedia eXtension Board'"
> +	depends on PCI && VIDEO_V4L2 && I2C
> +	select VIDEO_SAA7146_VV
> +	select VIDEO_TUNER
> +	select VIDEO_SAA711X if VIDEO_HELPER_CHIPS_AUTO
> +	select VIDEO_TDA9840 if VIDEO_HELPER_CHIPS_AUTO
> +	select VIDEO_TEA6415C if VIDEO_HELPER_CHIPS_AUTO
> +	select VIDEO_TEA6420 if VIDEO_HELPER_CHIPS_AUTO
> +	---help---
> +	  This is a video4linux driver for the 'Multimedia eXtension Board'
> +	  TV card by Siemens-Nixdorf.
> +
> +	  To compile this driver as a module, choose M here: the
> +	  module will be called mxb.
> +
> +config VIDEO_HEXIUM_ORION
> +	tristate "Hexium HV-PCI6 and Orion frame grabber"
> +	depends on PCI && VIDEO_V4L2 && I2C
> +	select VIDEO_SAA7146_VV
> +	---help---
> +	  This is a video4linux driver for the Hexium HV-PCI6 and
> +	  Orion frame grabber cards by Hexium.
> +
> +	  To compile this driver as a module, choose M here: the
> +	  module will be called hexium_orion.
> +
> +config VIDEO_HEXIUM_GEMINI
> +	tristate "Hexium Gemini frame grabber"
> +	depends on PCI && VIDEO_V4L2 && I2C
> +	select VIDEO_SAA7146_VV
> +	---help---
> +	  This is a video4linux driver for the Hexium Gemini frame
> +	  grabber card by Hexium. Please note that the Gemini Dual
> +	  card is *not* fully supported.
> +
> +	  To compile this driver as a module, choose M here: the
> +	  module will be called hexium_gemini.
> +
> +endif # V4L_LEGACY_DRIVERS
> +
>  endif # VIDEO_CAPTURE_DRIVERS
>  
>  menuconfig V4L_MEM2MEM_DRIVERS

Re: [RFCv2 PATCH 4/7] V4L menu: move all platform drivers to the bottom of the menu.

[Mauro Carvalho Chehab]

Em 30-09-2011 06:01, Hans Verkuil escreveu:
> From: Hans Verkuil <hans.verkuil@cisco.com>
> 

>From the patch subject: V4L menu: move all platform drivers to the bottom of the menu.

It is clear to me that we're analizing drivers by the bus type.

IMO, what we should do is to arrange the driver as:

menuconfig VIDEO_USB
	bool "USB drivers"
...
menuconfig VIDEO_PCI
	bool "PCI drivers"
...
menuconfig VIDEO_PLATFORM
	bool "Platform drivers"
...
menuconfig VIDEO_ISA_PARPORT
	bool "Isa and Parallel port drivers"

This as a big advantage of the current way, as it helps people to discard drivers
that they will never need:

1) people with modern Desktop PC can just disable VIDEO_PLATFORM and VIDEO_ISA_PARPORT;
2) people with embedded SoC hardware can disable VIDEO_USB, VIDEO_PCI and VIDEO_ISA_PARPORT;
3) people with tablets (and similar stuff) can disable VIDEO_ISA_PARPORT and VIDEO_PCI.

So, things will be easier for the ones that are compiling the kernel, or preparing
distributions.

Regards,
Mauro

> Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
> ---
>  drivers/media/video/Kconfig |  106 ++++++++++++++++++++++---------------------
>  1 files changed, 55 insertions(+), 51 deletions(-)
> 
> diff --git a/drivers/media/video/Kconfig b/drivers/media/video/Kconfig
> index fafc9ba..07d31d4 100644
> --- a/drivers/media/video/Kconfig
> +++ b/drivers/media/video/Kconfig
> @@ -646,25 +646,6 @@ config USB_S2255
>  
>  endif # V4L_USB_DRIVERS
>  
> -config VIDEO_SH_VOU
> -	tristate "SuperH VOU video output driver"
> -	depends on VIDEO_DEV && ARCH_SHMOBILE
> -	select VIDEOBUF_DMA_CONTIG
> -	help
> -	  Support for the Video Output Unit (VOU) on SuperH SoCs.
> -
> -config VIDEO_VIU
> -	tristate "Freescale VIU Video Driver"
> -	depends on VIDEO_V4L2 && PPC_MPC512x
> -	select VIDEOBUF_DMA_CONTIG
> -	default y
> -	---help---
> -	  Support for Freescale VIU video driver. This device captures
> -	  video data, or overlays video on DIU frame buffer.
> -
> -	  Say Y here if you want to enable VIU device on MPC5121e Rev2+.
> -	  In doubt, say N.
> -
>  config VIDEO_VIVI
>  	tristate "Virtual Video Driver"
>  	depends on VIDEO_DEV && VIDEO_V4L2 && !SPARC32 && !SPARC64
> @@ -679,20 +660,8 @@ config VIDEO_VIVI
>  	  Say Y here if you want to test video apps or debug V4L devices.
>  	  In doubt, say N.
>  
> -source "drivers/media/video/davinci/Kconfig"
> -
> -source "drivers/media/video/omap/Kconfig"
> -
>  source "drivers/media/video/bt8xx/Kconfig"
>  
> -config VIDEO_VINO
> -	tristate "SGI Vino Video For Linux"
> -	depends on I2C && SGI_IP22 && VIDEO_V4L2
> -	select VIDEO_SAA7191 if VIDEO_HELPER_CHIPS_AUTO
> -	help
> -	  Say Y here to build in support for the Vino video input system found
> -	  on SGI Indy machines.
> -
>  source "drivers/media/video/zoran/Kconfig"
>  
>  config VIDEO_MEYE
> @@ -711,16 +680,6 @@ config VIDEO_MEYE
>  
>  source "drivers/media/video/saa7134/Kconfig"
>  
> -config VIDEO_TIMBERDALE
> -	tristate "Support for timberdale Video In/LogiWIN"
> -	depends on VIDEO_V4L2 && I2C && DMADEVICES
> -	select DMA_ENGINE
> -	select TIMB_DMA
> -	select VIDEO_ADV7180
> -	select VIDEOBUF_DMA_CONTIG
> -	---help---
> -	  Add support for the Video In peripherial of the timberdale FPGA.
> -
>  source "drivers/media/video/cx88/Kconfig"
>  
>  source "drivers/media/video/cx23885/Kconfig"
> @@ -735,6 +694,61 @@ source "drivers/media/video/saa7164/Kconfig"
>  
>  source "drivers/media/video/marvell-ccic/Kconfig"
>  
> +config VIDEO_VIA_CAMERA
> +	tristate "VIAFB camera controller support"
> +	depends on FB_VIA
> +	select VIDEOBUF_DMA_SG
> +	select VIDEO_OV7670
> +	help
> +	   Driver support for the integrated camera controller in VIA
> +	   Chrome9 chipsets.  Currently only tested on OLPC xo-1.5 systems
> +	   with ov7670 sensors.
> +
> +#
> +# Platform multimedia device configuration
> +#
> +
> +source "drivers/media/video/davinci/Kconfig"
> +
> +source "drivers/media/video/omap/Kconfig"
> +
> +config VIDEO_SH_VOU
> +	tristate "SuperH VOU video output driver"
> +	depends on VIDEO_DEV && ARCH_SHMOBILE
> +	select VIDEOBUF_DMA_CONTIG
> +	help
> +	  Support for the Video Output Unit (VOU) on SuperH SoCs.
> +
> +config VIDEO_VIU
> +	tristate "Freescale VIU Video Driver"
> +	depends on VIDEO_V4L2 && PPC_MPC512x
> +	select VIDEOBUF_DMA_CONTIG
> +	default y
> +	---help---
> +	  Support for Freescale VIU video driver. This device captures
> +	  video data, or overlays video on DIU frame buffer.
> +
> +	  Say Y here if you want to enable VIU device on MPC5121e Rev2+.
> +	  In doubt, say N.
> +
> +config VIDEO_TIMBERDALE
> +	tristate "Support for timberdale Video In/LogiWIN"
> +	depends on VIDEO_V4L2 && I2C && DMADEVICES
> +	select DMA_ENGINE
> +	select TIMB_DMA
> +	select VIDEO_ADV7180
> +	select VIDEOBUF_DMA_CONTIG
> +	---help---
> +	  Add support for the Video In peripherial of the timberdale FPGA.
> +
> +config VIDEO_VINO
> +	tristate "SGI Vino Video For Linux"
> +	depends on I2C && SGI_IP22 && VIDEO_V4L2
> +	select VIDEO_SAA7191 if VIDEO_HELPER_CHIPS_AUTO
> +	help
> +	  Say Y here to build in support for the Vino video input system found
> +	  on SGI Indy machines.
> +
>  config VIDEO_M32R_AR
>  	tristate "AR devices"
>  	depends on M32R && VIDEO_V4L2
> @@ -754,16 +768,6 @@ config VIDEO_M32R_AR_M64278
>  	  To compile this driver as a module, choose M here: the
>  	  module will be called arv.
>  
> -config VIDEO_VIA_CAMERA
> -	tristate "VIAFB camera controller support"
> -	depends on FB_VIA
> -	select VIDEOBUF_DMA_SG
> -	select VIDEO_OV7670
> -	help
> -	   Driver support for the integrated camera controller in VIA
> -	   Chrome9 chipsets.  Currently only tested on OLPC xo-1.5 systems
> -	   with ov7670 sensors.
> -
>  config VIDEO_OMAP3
>  	tristate "OMAP 3 Camera support (EXPERIMENTAL)"
>  	select OMAP_IOMMU

Re: [RFCv2 PATCH 0/7] V4L menu reorganization

[Mauro Carvalho Chehab]

Em 30-09-2011 06:01, Hans Verkuil escreveu:
> Hi all,
> 
> This is the second version of my patch series reorganizing the V4L menu.
> It's based on the latest v3.2 staging tree.
> 
> Changes to v1:
> 
> - Remove unnecessary USB dependency.
> - Reorganize the radio menu as well.
> 
> I did not sort the drivers alphabetically (yet). I'm not quite sure whether
> that's really a good idea, and we can always do that later.

I still think that we need to sort things alphabetically, or to not sort
things at all, as any other sort criteria would be just a random criteria.

E. g. on a non-alphabetical criteria, what should come first between bttv,
saa7134, ivtv and cx88? Except by the alphabetical order, any order between 
them will be just a random criteria, as people will argue that driver "foo"
should be the first one, probably because they have more hardware of that
type ;)

In my case, I would vote for saa7134 as I currently have more hardware of
that type. A few years ago, my vote would be for cx88. I bet you'll vote
for ivtv ;)

> This series is meant for v3.2, but I won't make a pull request until
> Guennadi's pull request is merged first. I'm sure I will have to redo my
> patches once his series is in.

Ok.
> 
> Regards,
> 
> 	Hans
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [RFCv2 PATCH 2/7] V4L menu: move legacy drivers into their own submenu.

[Hans Verkuil]

On Friday, September 30, 2011 13:12:01 Mauro Carvalho Chehab wrote:
> Em 30-09-2011 06:01, Hans Verkuil escreveu:
> > From: Hans Verkuil <hans.verkuil@cisco.com>
> > 
> > Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
> > ---
> >  drivers/media/video/Kconfig |  185 +++++++++++++++++++++++-------------------
> >  1 files changed, 101 insertions(+), 84 deletions(-)
> > 
> > diff --git a/drivers/media/video/Kconfig b/drivers/media/video/Kconfig
> > index 0f8ccb4..86fdd7d 100644
> > --- a/drivers/media/video/Kconfig
> > +++ b/drivers/media/video/Kconfig
> > @@ -685,51 +685,6 @@ source "drivers/media/video/omap/Kconfig"
> >  
> >  source "drivers/media/video/bt8xx/Kconfig"
> >  
> > -config VIDEO_PMS
> > -	tristate "Mediavision Pro Movie Studio Video For Linux"
> > -	depends on ISA && VIDEO_V4L2
> > -	help
> > -	  Say Y if you have such a thing.
> > -
> > -	  To compile this driver as a module, choose M here: the
> > -	  module will be called pms.
> > -
> > -config VIDEO_BWQCAM
> > -	tristate "Quickcam BW Video For Linux"
> > -	depends on PARPORT && VIDEO_V4L2
> > -	help
> > -	  Say Y have if you the black and white version of the QuickCam
> > -	  camera. See the next option for the color version.
> > -
> > -	  To compile this driver as a module, choose M here: the
> > -	  module will be called bw-qcam.
> > -
> > -config VIDEO_CQCAM
> > -	tristate "QuickCam Colour Video For Linux (EXPERIMENTAL)"
> > -	depends on EXPERIMENTAL && PARPORT && VIDEO_V4L2
> > -	help
> > -	  This is the video4linux driver for the colour version of the
> > -	  Connectix QuickCam.  If you have one of these cameras, say Y here,
> > -	  otherwise say N.  This driver does not work with the original
> > -	  monochrome QuickCam, QuickCam VC or QuickClip.  It is also available
> > -	  as a module (c-qcam).
> > -	  Read <file:Documentation/video4linux/CQcam.txt> for more information.
> > -
> > -config VIDEO_W9966
> > -	tristate "W9966CF Webcam (FlyCam Supra and others) Video For Linux"
> > -	depends on PARPORT_1284 && PARPORT && VIDEO_V4L2
> > -	help
> > -	  Video4linux driver for Winbond's w9966 based Webcams.
> > -	  Currently tested with the LifeView FlyCam Supra.
> > -	  If you have one of these cameras, say Y here
> > -	  otherwise say N.
> > -	  This driver is also available as a module (w9966).
> > -
> > -	  Check out <file:Documentation/video4linux/w9966.txt> for more
> > -	  information.
> > -
> > -source "drivers/media/video/cpia2/Kconfig"
> > -
> >  config VIDEO_VINO
> >  	tristate "SGI Vino Video For Linux (EXPERIMENTAL)"
> >  	depends on I2C && SGI_IP22 && EXPERIMENTAL && VIDEO_V4L2
> > @@ -756,45 +711,6 @@ config VIDEO_MEYE
> >  
> >  source "drivers/media/video/saa7134/Kconfig"
> >  
> > -config VIDEO_MXB
> > -	tristate "Siemens-Nixdorf 'Multimedia eXtension Board'"
> > -	depends on PCI && VIDEO_V4L2 && I2C
> > -	select VIDEO_SAA7146_VV
> > -	select VIDEO_TUNER
> > -	select VIDEO_SAA711X if VIDEO_HELPER_CHIPS_AUTO
> > -	select VIDEO_TDA9840 if VIDEO_HELPER_CHIPS_AUTO
> > -	select VIDEO_TEA6415C if VIDEO_HELPER_CHIPS_AUTO
> > -	select VIDEO_TEA6420 if VIDEO_HELPER_CHIPS_AUTO
> > -	---help---
> > -	  This is a video4linux driver for the 'Multimedia eXtension Board'
> > -	  TV card by Siemens-Nixdorf.
> > -
> > -	  To compile this driver as a module, choose M here: the
> > -	  module will be called mxb.
> > -
> > -config VIDEO_HEXIUM_ORION
> > -	tristate "Hexium HV-PCI6 and Orion frame grabber"
> > -	depends on PCI && VIDEO_V4L2 && I2C
> > -	select VIDEO_SAA7146_VV
> > -	---help---
> > -	  This is a video4linux driver for the Hexium HV-PCI6 and
> > -	  Orion frame grabber cards by Hexium.
> > -
> > -	  To compile this driver as a module, choose M here: the
> > -	  module will be called hexium_orion.
> > -
> > -config VIDEO_HEXIUM_GEMINI
> > -	tristate "Hexium Gemini frame grabber"
> > -	depends on PCI && VIDEO_V4L2 && I2C
> > -	select VIDEO_SAA7146_VV
> > -	---help---
> > -	  This is a video4linux driver for the Hexium Gemini frame
> > -	  grabber card by Hexium. Please note that the Gemini Dual
> > -	  card is *not* fully supported.
> > -
> > -	  To compile this driver as a module, choose M here: the
> > -	  module will be called hexium_gemini.
> > -
> >  config VIDEO_TIMBERDALE
> >  	tristate "Support for timberdale Video In/LogiWIN"
> >  	depends on VIDEO_V4L2 && I2C && DMADEVICES
> > @@ -1067,6 +983,107 @@ config VIDEO_S5P_MIPI_CSIS
> >  
> >  source "drivers/media/video/s5p-tv/Kconfig"
> >  
> > +#
> > +# Legacy drivers configuration
> > +#
> > +
> > +menuconfig V4L_LEGACY_DRIVERS
> > +	bool "V4L legacy devices"
> > +	default n
> > +	---help---
> > +	  Say Y here to enable support for these legacy drivers. These drivers
> > +	  are for old and obsure hardware (e.g. parallel port webcams, ISA
> > +	  drivers, niche hardware).
> 
> As before, I don't like the name "legacy". The drivers themselves are not
> legacy, as they work fine, as far as I know.
> 
> Parallel port and ISA could be just called as "parallel port and ISA drivers".
> 
> With regards to saa7146 drivers, it is hard to say the the hardware is more
> legacy than, for example, bttv.

The saa7146 V4L drivers (MXB and Hexium) are very rarely used. It's very hard
to find the hardware and you almost never see questions about it on the list.
The av7110 DVB drivers that are saa7146 based still pop up every now and then.

> As I said before, defining what's a legacy hardware and what isn't is not
> an objective criteria: it is legacy on what sense? I was told that tda18271
> were recently discontinued. Should we mark all drivers that use it as legacy?

Of course not. Legacy drivers are for hardware that is almost never used
anymore (based on the traffic on the mailinglist) and no longer sold since
many years. Bonus points for using an obsolete interface (ISA, parport).

If you really hate this, then I can move the PCI drivers back to the normal
menu.

I don't see a problem here: bttv sees a lot of development and use and hardware
is even still being made today. On the other hand, what was the last time
anyone ever asked something about the Hexium drivers? If it wasn't for the fact
that I got the hardware for Hexium and MXB from Michael Hunold (so that I can
test it) I would have been in favor of removing the drivers altogether.

Regards,

	Hans

> 
> > +
> > +if V4L_LEGACY_DRIVERS
> > +
> > +config VIDEO_PMS
> > +	tristate "Mediavision Pro Movie Studio Video For Linux"
> > +	depends on ISA && VIDEO_V4L2
> > +	help
> > +	  Say Y if you have the ISA Mediavision Pro Movie Studio
> > +	  capture card.
> > +
> > +	  To compile this driver as a module, choose M here: the
> > +	  module will be called pms.
> > +
> > +config VIDEO_BWQCAM
> > +	tristate "Quickcam BW Video For Linux"
> > +	depends on PARPORT && VIDEO_V4L2
> > +	help
> > +	  Say Y have if you the black and white version of the QuickCam
> > +	  camera. See the next option for the color version.
> > +
> > +	  To compile this driver as a module, choose M here: the
> > +	  module will be called bw-qcam.
> > +
> > +config VIDEO_CQCAM
> > +	tristate "QuickCam Colour Video For Linux (EXPERIMENTAL)"
> > +	depends on EXPERIMENTAL && PARPORT && VIDEO_V4L2
> > +	help
> > +	  This is the video4linux driver for the colour version of the
> > +	  Connectix QuickCam.  If you have one of these cameras, say Y here,
> > +	  otherwise say N.  This driver does not work with the original
> > +	  monochrome QuickCam, QuickCam VC or QuickClip.  It is also available
> > +	  as a module (c-qcam).
> > +	  Read <file:Documentation/video4linux/CQcam.txt> for more information.
> > +
> > +config VIDEO_W9966
> > +	tristate "W9966CF Webcam (FlyCam Supra and others) Video For Linux"
> > +	depends on PARPORT_1284 && PARPORT && VIDEO_V4L2
> > +	help
> > +	  Video4linux driver for Winbond's w9966 based Webcams.
> > +	  Currently tested with the LifeView FlyCam Supra.
> > +	  If you have one of these cameras, say Y here
> > +	  otherwise say N.
> > +	  This driver is also available as a module (w9966).
> > +
> > +	  Check out <file:Documentation/video4linux/w9966.txt> for more
> > +	  information.
> > +
> > +source "drivers/media/video/cpia2/Kconfig"
> > +
> > +config VIDEO_MXB
> > +	tristate "Siemens-Nixdorf 'Multimedia eXtension Board'"
> > +	depends on PCI && VIDEO_V4L2 && I2C
> > +	select VIDEO_SAA7146_VV
> > +	select VIDEO_TUNER
> > +	select VIDEO_SAA711X if VIDEO_HELPER_CHIPS_AUTO
> > +	select VIDEO_TDA9840 if VIDEO_HELPER_CHIPS_AUTO
> > +	select VIDEO_TEA6415C if VIDEO_HELPER_CHIPS_AUTO
> > +	select VIDEO_TEA6420 if VIDEO_HELPER_CHIPS_AUTO
> > +	---help---
> > +	  This is a video4linux driver for the 'Multimedia eXtension Board'
> > +	  TV card by Siemens-Nixdorf.
> > +
> > +	  To compile this driver as a module, choose M here: the
> > +	  module will be called mxb.
> > +
> > +config VIDEO_HEXIUM_ORION
> > +	tristate "Hexium HV-PCI6 and Orion frame grabber"
> > +	depends on PCI && VIDEO_V4L2 && I2C
> > +	select VIDEO_SAA7146_VV
> > +	---help---
> > +	  This is a video4linux driver for the Hexium HV-PCI6 and
> > +	  Orion frame grabber cards by Hexium.
> > +
> > +	  To compile this driver as a module, choose M here: the
> > +	  module will be called hexium_orion.
> > +
> > +config VIDEO_HEXIUM_GEMINI
> > +	tristate "Hexium Gemini frame grabber"
> > +	depends on PCI && VIDEO_V4L2 && I2C
> > +	select VIDEO_SAA7146_VV
> > +	---help---
> > +	  This is a video4linux driver for the Hexium Gemini frame
> > +	  grabber card by Hexium. Please note that the Gemini Dual
> > +	  card is *not* fully supported.
> > +
> > +	  To compile this driver as a module, choose M here: the
> > +	  module will be called hexium_gemini.
> > +
> > +endif # V4L_LEGACY_DRIVERS
> > +
> >  endif # VIDEO_CAPTURE_DRIVERS
> >  
> >  menuconfig V4L_MEM2MEM_DRIVERS
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

Re: [RFCv2 PATCH 4/7] V4L menu: move all platform drivers to the bottom of the menu.

[Hans Verkuil]

On Friday, September 30, 2011 13:22:09 Mauro Carvalho Chehab wrote:
> Em 30-09-2011 06:01, Hans Verkuil escreveu:
> > From: Hans Verkuil <hans.verkuil@cisco.com>
> > 
> 
> From the patch subject: V4L menu: move all platform drivers to the bottom of the menu.
> 
> It is clear to me that we're analizing drivers by the bus type.
> 
> IMO, what we should do is to arrange the driver as:
> 
> menuconfig VIDEO_USB
> 	bool "USB drivers"
> ...
> menuconfig VIDEO_PCI
> 	bool "PCI drivers"
> ...
> menuconfig VIDEO_PLATFORM
> 	bool "Platform drivers"
> ...
> menuconfig VIDEO_ISA_PARPORT
> 	bool "Isa and Parallel port drivers"
> 
> This as a big advantage of the current way, as it helps people to discard drivers
> that they will never need:
> 
> 1) people with modern Desktop PC can just disable VIDEO_PLATFORM and VIDEO_ISA_PARPORT;
> 2) people with embedded SoC hardware can disable VIDEO_USB, VIDEO_PCI and VIDEO_ISA_PARPORT;
> 3) people with tablets (and similar stuff) can disable VIDEO_ISA_PARPORT and VIDEO_PCI.
> 
> So, things will be easier for the ones that are compiling the kernel, or preparing
> distributions.

OK, I'll do that. You have a point here.

Regards,

	Hans

> 
> Regards,
> Mauro
> 
> > Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
> > ---
> >  drivers/media/video/Kconfig |  106 ++++++++++++++++++++++---------------------
> >  1 files changed, 55 insertions(+), 51 deletions(-)
> > 
> > diff --git a/drivers/media/video/Kconfig b/drivers/media/video/Kconfig
> > index fafc9ba..07d31d4 100644
> > --- a/drivers/media/video/Kconfig
> > +++ b/drivers/media/video/Kconfig
> > @@ -646,25 +646,6 @@ config USB_S2255
> >  
> >  endif # V4L_USB_DRIVERS
> >  
> > -config VIDEO_SH_VOU
> > -	tristate "SuperH VOU video output driver"
> > -	depends on VIDEO_DEV && ARCH_SHMOBILE
> > -	select VIDEOBUF_DMA_CONTIG
> > -	help
> > -	  Support for the Video Output Unit (VOU) on SuperH SoCs.
> > -
> > -config VIDEO_VIU
> > -	tristate "Freescale VIU Video Driver"
> > -	depends on VIDEO_V4L2 && PPC_MPC512x
> > -	select VIDEOBUF_DMA_CONTIG
> > -	default y
> > -	---help---
> > -	  Support for Freescale VIU video driver. This device captures
> > -	  video data, or overlays video on DIU frame buffer.
> > -
> > -	  Say Y here if you want to enable VIU device on MPC5121e Rev2+.
> > -	  In doubt, say N.
> > -
> >  config VIDEO_VIVI
> >  	tristate "Virtual Video Driver"
> >  	depends on VIDEO_DEV && VIDEO_V4L2 && !SPARC32 && !SPARC64
> > @@ -679,20 +660,8 @@ config VIDEO_VIVI
> >  	  Say Y here if you want to test video apps or debug V4L devices.
> >  	  In doubt, say N.
> >  
> > -source "drivers/media/video/davinci/Kconfig"
> > -
> > -source "drivers/media/video/omap/Kconfig"
> > -
> >  source "drivers/media/video/bt8xx/Kconfig"
> >  
> > -config VIDEO_VINO
> > -	tristate "SGI Vino Video For Linux"
> > -	depends on I2C && SGI_IP22 && VIDEO_V4L2
> > -	select VIDEO_SAA7191 if VIDEO_HELPER_CHIPS_AUTO
> > -	help
> > -	  Say Y here to build in support for the Vino video input system found
> > -	  on SGI Indy machines.
> > -
> >  source "drivers/media/video/zoran/Kconfig"
> >  
> >  config VIDEO_MEYE
> > @@ -711,16 +680,6 @@ config VIDEO_MEYE
> >  
> >  source "drivers/media/video/saa7134/Kconfig"
> >  
> > -config VIDEO_TIMBERDALE
> > -	tristate "Support for timberdale Video In/LogiWIN"
> > -	depends on VIDEO_V4L2 && I2C && DMADEVICES
> > -	select DMA_ENGINE
> > -	select TIMB_DMA
> > -	select VIDEO_ADV7180
> > -	select VIDEOBUF_DMA_CONTIG
> > -	---help---
> > -	  Add support for the Video In peripherial of the timberdale FPGA.
> > -
> >  source "drivers/media/video/cx88/Kconfig"
> >  
> >  source "drivers/media/video/cx23885/Kconfig"
> > @@ -735,6 +694,61 @@ source "drivers/media/video/saa7164/Kconfig"
> >  
> >  source "drivers/media/video/marvell-ccic/Kconfig"
> >  
> > +config VIDEO_VIA_CAMERA
> > +	tristate "VIAFB camera controller support"
> > +	depends on FB_VIA
> > +	select VIDEOBUF_DMA_SG
> > +	select VIDEO_OV7670
> > +	help
> > +	   Driver support for the integrated camera controller in VIA
> > +	   Chrome9 chipsets.  Currently only tested on OLPC xo-1.5 systems
> > +	   with ov7670 sensors.
> > +
> > +#
> > +# Platform multimedia device configuration
> > +#
> > +
> > +source "drivers/media/video/davinci/Kconfig"
> > +
> > +source "drivers/media/video/omap/Kconfig"
> > +
> > +config VIDEO_SH_VOU
> > +	tristate "SuperH VOU video output driver"
> > +	depends on VIDEO_DEV && ARCH_SHMOBILE
> > +	select VIDEOBUF_DMA_CONTIG
> > +	help
> > +	  Support for the Video Output Unit (VOU) on SuperH SoCs.
> > +
> > +config VIDEO_VIU
> > +	tristate "Freescale VIU Video Driver"
> > +	depends on VIDEO_V4L2 && PPC_MPC512x
> > +	select VIDEOBUF_DMA_CONTIG
> > +	default y
> > +	---help---
> > +	  Support for Freescale VIU video driver. This device captures
> > +	  video data, or overlays video on DIU frame buffer.
> > +
> > +	  Say Y here if you want to enable VIU device on MPC5121e Rev2+.
> > +	  In doubt, say N.
> > +
> > +config VIDEO_TIMBERDALE
> > +	tristate "Support for timberdale Video In/LogiWIN"
> > +	depends on VIDEO_V4L2 && I2C && DMADEVICES
> > +	select DMA_ENGINE
> > +	select TIMB_DMA
> > +	select VIDEO_ADV7180
> > +	select VIDEOBUF_DMA_CONTIG
> > +	---help---
> > +	  Add support for the Video In peripherial of the timberdale FPGA.
> > +
> > +config VIDEO_VINO
> > +	tristate "SGI Vino Video For Linux"
> > +	depends on I2C && SGI_IP22 && VIDEO_V4L2
> > +	select VIDEO_SAA7191 if VIDEO_HELPER_CHIPS_AUTO
> > +	help
> > +	  Say Y here to build in support for the Vino video input system found
> > +	  on SGI Indy machines.
> > +
> >  config VIDEO_M32R_AR
> >  	tristate "AR devices"
> >  	depends on M32R && VIDEO_V4L2
> > @@ -754,16 +768,6 @@ config VIDEO_M32R_AR_M64278
> >  	  To compile this driver as a module, choose M here: the
> >  	  module will be called arv.
> >  
> > -config VIDEO_VIA_CAMERA
> > -	tristate "VIAFB camera controller support"
> > -	depends on FB_VIA
> > -	select VIDEOBUF_DMA_SG
> > -	select VIDEO_OV7670
> > -	help
> > -	   Driver support for the integrated camera controller in VIA
> > -	   Chrome9 chipsets.  Currently only tested on OLPC xo-1.5 systems
> > -	   with ov7670 sensors.
> > -
> >  config VIDEO_OMAP3
> >  	tristate "OMAP 3 Camera support (EXPERIMENTAL)"
> >  	select OMAP_IOMMU
> 

Re: [RFCv2 PATCH 0/7] V4L menu reorganization

[Hans Verkuil]

On Friday, September 30, 2011 13:28:28 Mauro Carvalho Chehab wrote:
> Em 30-09-2011 06:01, Hans Verkuil escreveu:
> > Hi all,
> > 
> > This is the second version of my patch series reorganizing the V4L menu.
> > It's based on the latest v3.2 staging tree.
> > 
> > Changes to v1:
> > 
> > - Remove unnecessary USB dependency.
> > - Reorganize the radio menu as well.
> > 
> > I did not sort the drivers alphabetically (yet). I'm not quite sure whether
> > that's really a good idea, and we can always do that later.
> 
> I still think that we need to sort things alphabetically, or to not sort
> things at all, as any other sort criteria would be just a random criteria.
> 
> E. g. on a non-alphabetical criteria, what should come first between bttv,
> saa7134, ivtv and cx88? Except by the alphabetical order, any order between 
> them will be just a random criteria, as people will argue that driver "foo"
> should be the first one, probably because they have more hardware of that
> type ;)

Sort by what, BTW? The driver module name?

I'd like to get a concensus on that before I do this.

Regards,

	Hans

> In my case, I would vote for saa7134 as I currently have more hardware of
> that type. A few years ago, my vote would be for cx88. I bet you'll vote
> for ivtv ;)
> 
> > This series is meant for v3.2, but I won't make a pull request until
> > Guennadi's pull request is merged first. I'm sure I will have to redo my
> > patches once his series is in.
> 
> Ok.
> > 
> > Regards,
> > 
> > 	Hans
> > 
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-media" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

Re: [RFCv2 PATCH 2/7] V4L menu: move legacy drivers into their own submenu.

[Stefan Richter]

On Sep 30 Hans Verkuil wrote:
> +menuconfig V4L_LEGACY_DRIVERS
> +	bool "V4L legacy devices"
> +	default n

default n is redundant.

> +	---help---
> +	  Say Y here to enable support for these legacy drivers. These drivers
> +	  are for old and obsure hardware (e.g. parallel port webcams, ISA
> +	  drivers, niche hardware).

Perhaps add sentences like these which are commonly seen in such
menuconfig variables:

	  This option alone does not add any kernel code.

	  If you say N, all options in this submenu will be skipped and disabled.

There are obviously several already existing menuconfigs in the video section
which do not have these sentences; so maybe don't add the above, or add it
separately across the board, or whatever.  I find these sentences helpful when
running "make oldconfig" or the likes.
-- 
Stefan Richter
-=====-==-== =--= ====-
http://arcgraph.de/sr/

Re: [RFCv2 PATCH 2/7] V4L menu: move legacy drivers into their own submenu.

[Hans Verkuil]

On Friday, September 30, 2011 14:13:29 Stefan Richter wrote:
> On Sep 30 Hans Verkuil wrote:
> > +menuconfig V4L_LEGACY_DRIVERS
> > +	bool "V4L legacy devices"
> > +	default n
> 
> default n is redundant.
> 
> > +	---help---
> > +	  Say Y here to enable support for these legacy drivers. These drivers
> > +	  are for old and obsure hardware (e.g. parallel port webcams, ISA
> > +	  drivers, niche hardware).
> 
> Perhaps add sentences like these which are commonly seen in such
> menuconfig variables:
> 
> 	  This option alone does not add any kernel code.
> 
> 	  If you say N, all options in this submenu will be skipped and disabled.
> 
> There are obviously several already existing menuconfigs in the video section
> which do not have these sentences; so maybe don't add the above, or add it
> separately across the board, or whatever.  I find these sentences helpful when
> running "make oldconfig" or the likes.
> 

Good points. I'll see if I can do this for RFCv4. I might also do this as a
separate cleanup step later.

Regards,

	Hans

Re: [RFCv2 PATCH 2/7] V4L menu: move legacy drivers into their own submenu.

[Mauro Carvalho Chehab]

Em 30-09-2011 08:29, Hans Verkuil escreveu:
> On Friday, September 30, 2011 13:12:01 Mauro Carvalho Chehab wrote:
>> Em 30-09-2011 06:01, Hans Verkuil escreveu:
>>> From: Hans Verkuil <hans.verkuil@cisco.com>
>>>
>>> Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
>>> ---
>>>  drivers/media/video/Kconfig |  185 +++++++++++++++++++++++-------------------
>>>  1 files changed, 101 insertions(+), 84 deletions(-)
>>>
>>> diff --git a/drivers/media/video/Kconfig b/drivers/media/video/Kconfig
>>> index 0f8ccb4..86fdd7d 100644
>>> --- a/drivers/media/video/Kconfig
>>> +++ b/drivers/media/video/Kconfig
>>> @@ -685,51 +685,6 @@ source "drivers/media/video/omap/Kconfig"
>>>  
>>>  source "drivers/media/video/bt8xx/Kconfig"
>>>  
>>> -config VIDEO_PMS
>>> -	tristate "Mediavision Pro Movie Studio Video For Linux"
>>> -	depends on ISA && VIDEO_V4L2
>>> -	help
>>> -	  Say Y if you have such a thing.
>>> -
>>> -	  To compile this driver as a module, choose M here: the
>>> -	  module will be called pms.
>>> -
>>> -config VIDEO_BWQCAM
>>> -	tristate "Quickcam BW Video For Linux"
>>> -	depends on PARPORT && VIDEO_V4L2
>>> -	help
>>> -	  Say Y have if you the black and white version of the QuickCam
>>> -	  camera. See the next option for the color version.
>>> -
>>> -	  To compile this driver as a module, choose M here: the
>>> -	  module will be called bw-qcam.
>>> -
>>> -config VIDEO_CQCAM
>>> -	tristate "QuickCam Colour Video For Linux (EXPERIMENTAL)"
>>> -	depends on EXPERIMENTAL && PARPORT && VIDEO_V4L2
>>> -	help
>>> -	  This is the video4linux driver for the colour version of the
>>> -	  Connectix QuickCam.  If you have one of these cameras, say Y here,
>>> -	  otherwise say N.  This driver does not work with the original
>>> -	  monochrome QuickCam, QuickCam VC or QuickClip.  It is also available
>>> -	  as a module (c-qcam).
>>> -	  Read <file:Documentation/video4linux/CQcam.txt> for more information.
>>> -
>>> -config VIDEO_W9966
>>> -	tristate "W9966CF Webcam (FlyCam Supra and others) Video For Linux"
>>> -	depends on PARPORT_1284 && PARPORT && VIDEO_V4L2
>>> -	help
>>> -	  Video4linux driver for Winbond's w9966 based Webcams.
>>> -	  Currently tested with the LifeView FlyCam Supra.
>>> -	  If you have one of these cameras, say Y here
>>> -	  otherwise say N.
>>> -	  This driver is also available as a module (w9966).
>>> -
>>> -	  Check out <file:Documentation/video4linux/w9966.txt> for more
>>> -	  information.
>>> -
>>> -source "drivers/media/video/cpia2/Kconfig"
>>> -
>>>  config VIDEO_VINO
>>>  	tristate "SGI Vino Video For Linux (EXPERIMENTAL)"
>>>  	depends on I2C && SGI_IP22 && EXPERIMENTAL && VIDEO_V4L2
>>> @@ -756,45 +711,6 @@ config VIDEO_MEYE
>>>  
>>>  source "drivers/media/video/saa7134/Kconfig"
>>>  
>>> -config VIDEO_MXB
>>> -	tristate "Siemens-Nixdorf 'Multimedia eXtension Board'"
>>> -	depends on PCI && VIDEO_V4L2 && I2C
>>> -	select VIDEO_SAA7146_VV
>>> -	select VIDEO_TUNER
>>> -	select VIDEO_SAA711X if VIDEO_HELPER_CHIPS_AUTO
>>> -	select VIDEO_TDA9840 if VIDEO_HELPER_CHIPS_AUTO
>>> -	select VIDEO_TEA6415C if VIDEO_HELPER_CHIPS_AUTO
>>> -	select VIDEO_TEA6420 if VIDEO_HELPER_CHIPS_AUTO
>>> -	---help---
>>> -	  This is a video4linux driver for the 'Multimedia eXtension Board'
>>> -	  TV card by Siemens-Nixdorf.
>>> -
>>> -	  To compile this driver as a module, choose M here: the
>>> -	  module will be called mxb.
>>> -
>>> -config VIDEO_HEXIUM_ORION
>>> -	tristate "Hexium HV-PCI6 and Orion frame grabber"
>>> -	depends on PCI && VIDEO_V4L2 && I2C
>>> -	select VIDEO_SAA7146_VV
>>> -	---help---
>>> -	  This is a video4linux driver for the Hexium HV-PCI6 and
>>> -	  Orion frame grabber cards by Hexium.
>>> -
>>> -	  To compile this driver as a module, choose M here: the
>>> -	  module will be called hexium_orion.
>>> -
>>> -config VIDEO_HEXIUM_GEMINI
>>> -	tristate "Hexium Gemini frame grabber"
>>> -	depends on PCI && VIDEO_V4L2 && I2C
>>> -	select VIDEO_SAA7146_VV
>>> -	---help---
>>> -	  This is a video4linux driver for the Hexium Gemini frame
>>> -	  grabber card by Hexium. Please note that the Gemini Dual
>>> -	  card is *not* fully supported.
>>> -
>>> -	  To compile this driver as a module, choose M here: the
>>> -	  module will be called hexium_gemini.
>>> -
>>>  config VIDEO_TIMBERDALE
>>>  	tristate "Support for timberdale Video In/LogiWIN"
>>>  	depends on VIDEO_V4L2 && I2C && DMADEVICES
>>> @@ -1067,6 +983,107 @@ config VIDEO_S5P_MIPI_CSIS
>>>  
>>>  source "drivers/media/video/s5p-tv/Kconfig"
>>>  
>>> +#
>>> +# Legacy drivers configuration
>>> +#
>>> +
>>> +menuconfig V4L_LEGACY_DRIVERS
>>> +	bool "V4L legacy devices"
>>> +	default n
>>> +	---help---
>>> +	  Say Y here to enable support for these legacy drivers. These drivers
>>> +	  are for old and obsure hardware (e.g. parallel port webcams, ISA
>>> +	  drivers, niche hardware).
>>
>> As before, I don't like the name "legacy". The drivers themselves are not
>> legacy, as they work fine, as far as I know.
>>
>> Parallel port and ISA could be just called as "parallel port and ISA drivers".
>>
>> With regards to saa7146 drivers, it is hard to say the the hardware is more
>> legacy than, for example, bttv.
> 
> The saa7146 V4L drivers (MXB and Hexium) are very rarely used. It's very hard
> to find the hardware and you almost never see questions about it on the list.
> The av7110 DVB drivers that are saa7146 based still pop up every now and then.
> 
>> As I said before, defining what's a legacy hardware and what isn't is not
>> an objective criteria: it is legacy on what sense? I was told that tda18271
>> were recently discontinued. Should we mark all drivers that use it as legacy?
> 
> Of course not. Legacy drivers are for hardware that is almost never used
> anymore (based on the traffic on the mailinglist) and no longer sold since
> many years. Bonus points for using an obsolete interface (ISA, parport).

Low traffic at the ML may simply means that the hardware is well-supported, that
nobody is touching on the driver to break things, or that the users of a particular
hardware aren't comfortable on writing to a ML in English.

> 
> If you really hate this, then I can move the PCI drivers back to the normal
> menu.
> 
> I don't see a problem here: bttv sees a lot of development and use and hardware
> is even still being made today. On the other hand, what was the last time
> anyone ever asked something about the Hexium drivers? If it wasn't for the fact
> that I got the hardware for Hexium and MXB from Michael Hunold (so that I can
> test it) I would have been in favor of removing the drivers altogether.

I'm not doubting that those boards are hard to find, but the point is that
an objective criteria is needed, if some hardware will be classified inside a new
menu. _All_ drivers that meet such criteria should be moved to the new menu.
I don't think we have this criteria for "legacy", as the word could mean several
different things (legacy driver, hardware not manufactured anymore, hardware not
compatible with modern machines, etc).

The worse thing with "legacy" is that it means that it is a temporal definition:
one day, all existing drivers drivers will be moved to this category. This
actually means that we'll need to track when a driver should be moved into it.
For sure I don't want to add this task to my TODO list.

Also, I think that some parport drivers are used on some types of hardware
for medical and astronomy devices. I've no idea if those devices are still
manufactured or not. So, calling them as "legacy" might actually be wrong.

IMO, the better is to just move saa7146 back the PCI menu, maybe adding a 
notice about the obsolescence of the hardware at the Kmenu help.

Regards,
Mauro

Re: [RFCv2 PATCH 0/7] V4L menu reorganization

[Mauro Carvalho Chehab]

Em 30-09-2011 08:34, Hans Verkuil escreveu:
> On Friday, September 30, 2011 13:28:28 Mauro Carvalho Chehab wrote:
>> Em 30-09-2011 06:01, Hans Verkuil escreveu:
>>> Hi all,
>>>
>>> This is the second version of my patch series reorganizing the V4L menu.
>>> It's based on the latest v3.2 staging tree.
>>>
>>> Changes to v1:
>>>
>>> - Remove unnecessary USB dependency.
>>> - Reorganize the radio menu as well.
>>>
>>> I did not sort the drivers alphabetically (yet). I'm not quite sure whether
>>> that's really a good idea, and we can always do that later.
>>
>> I still think that we need to sort things alphabetically, or to not sort
>> things at all, as any other sort criteria would be just a random criteria.
>>
>> E. g. on a non-alphabetical criteria, what should come first between bttv,
>> saa7134, ivtv and cx88? Except by the alphabetical order, any order between 
>> them will be just a random criteria, as people will argue that driver "foo"
>> should be the first one, probably because they have more hardware of that
>> type ;)
> 
> Sort by what, BTW? The driver module name?

I think so.

> 
> I'd like to get a concensus on that before I do this.

Sure.

> 
> Regards,
> 
> 	Hans
> 
>> In my case, I would vote for saa7134 as I currently have more hardware of
>> that type. A few years ago, my vote would be for cx88. I bet you'll vote
>> for ivtv ;)
>>
>>> This series is meant for v3.2, but I won't make a pull request until
>>> Guennadi's pull request is merged first. I'm sure I will have to redo my
>>> patches once his series is in.
>>
>> Ok.
>>>
>>> Regards,
>>>
>>> 	Hans
>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-media" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>