From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Andy Walls <awalls@md.metrocast.net>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [RFC] file tree rearrangement - was: Re: [RFC PATCH 0/3] Improve Kconfig selection for media devices
Date: Mon, 28 May 2012 09:10:43 -0300 [thread overview]
Message-ID: <4FC36B43.90703@redhat.com> (raw)
In-Reply-To: <201205281345.09188.hverkuil@xs4all.nl>
Em 28-05-2012 08:45, Hans Verkuil escreveu:
> On Mon May 28 2012 13:03:42 Mauro Carvalho Chehab wrote:
>> Em 28-05-2012 06:42, Hans Verkuil escreveu:
>>> On Sun May 27 2012 22:15:08 Mauro Carvalho Chehab wrote:
<skip/>
>>> /media-core for the media*.c sources.
>>
>>
>> "media-core" is a very bad name, as "media" is the name of the subsystem. maybe
>> "media-ctrl-core" or something similar.
>
> mc-core?
Ok.
<skip/>
>>> Another thing: I would move 'video grabber' away from webcams and to 'Analog TV/Video support'.
>>> And rename 'Digital TV' to 'Digital TV/Video' as well. A video grabber driver has much more to
>>> do with TV then it does with webcams.
>>
>> From the Kconfig perspective, the difference between the 3 video categories is that:
>>
>> - analog TV: tuner-core is required, and 10 other tuner drivers that are listed inside
>> tuner core;
>>
>> - digital TV: tuners are needed, but those are either customised or auto-selected;
>>
>> - camera/grabber: no tuner is needed.
>>
>> Also, there are several professional camera devices at bttv, cx88, saa7134 and cx25821
>> that don't require tuners, and support for them can be compiled without tuner support.
>>
>> In other words, a camera driver and a grabber driver are very similar. Of course, a webcam
>> will also require a sensor (on several drivers, the sensor is internal to the driver, so
>> no extra modules are needed). Of course, a platform camera driver will also require
>> "media controller", "subdev API", but those features are already enabled via other config options.
>>
>> So, from tuners' perspective, and from Kconfig's perspective, a video grabber is just
>> like a professional camera driver, a cellphone camera or a webcam driver.
>
> I would never have understood that from the menu names. In particular that 'Analog TV' implies
> a tuner. For me it could just as well imply a composite input video grabber.
(the discussion below is a little OT for file rearrangement - It belongs to the
Kconfig selection patches - I'm about to post a version 2 of it)
Can you use analog TV without a tuner? ;)
Analog TV is a clear concept for the end user: it is something that allows
tuning a channel and watch it. So, enabling this feature should enable
both functionality.
For us, this term causes some confusion as we generally use both "analog TV" and "V4L2"
to refer to the same thing.
> How about this:
>
> [ ] Video (aka V4L2) support
DVB is also video. Also Radio is also V4L2 support. So, this seems confusing.
> [ ] Digital TV Tuner (aka DVB) support
On both above, I don't like the idea of using an acronym, as it limits the
scope.
DVB, btw, is a bad name for the user interface, as users with other
digital standards like ATSC may not select it, as they don't have
"DVB" standard.
Also, calling it as "tuner" also limits the scope and, worse than that, enforces
the idea to the user to call the entire device as "tuner" (ok, some manufacturers
do that, but, for us, when someone reports a problem at the tuner, we genrally think
about the PLL, and not about the entire device).
> [ ] Analog TV Tuner support
> [ ] Radio Tuner/Modulator support
> [ ] Remote Controller support
>
> I didn't like the term 'Webcams and video grabbers' as that description is never 100%.
> The help text can clarify this in more detail, of course.
At version 2, I renamed it to: "Cameras/video grabbers support". Maybe we can use
"video capture devices" instead of "video grabbers" to be even more clearer.
Regards,
Mauro
next prev parent reply other threads:[~2012-05-28 12:10 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 15:34 [GIT PULL for v3.5-rc1] media updates for v3.5 Mauro Carvalho Chehab
2012-05-24 15:52 ` Antti Palosaari
2012-05-24 16:33 ` Ezequiel Garcia
2012-05-24 16:44 ` Mauro Carvalho Chehab
2012-05-24 20:42 ` Linus Torvalds
2012-05-24 22:33 ` Mauro Carvalho Chehab
2012-05-24 22:40 ` Linus Torvalds
2012-05-25 12:12 ` Mauro Carvalho Chehab
2012-05-25 14:49 ` Anssi Hannula
2012-05-25 15:21 ` Mauro Carvalho Chehab
2012-05-25 16:01 ` Anssi Hannula
2012-05-25 21:20 ` Guennadi Liakhovetski
2012-05-25 22:38 ` Stefan Richter
2012-05-27 14:47 ` Mauro Carvalho Chehab
2012-05-27 15:54 ` Mauro Carvalho Chehab
2012-05-27 16:56 ` [RFC PATCH 0/3] Improve Kconfig selection for media devices Mauro Carvalho Chehab
2012-05-27 16:56 ` [RFC PATCH 1/3] media: reorganize the main Kconfig items Mauro Carvalho Chehab
2012-05-27 17:15 ` Hans Verkuil
2012-05-27 17:20 ` Mauro Carvalho Chehab
2012-05-27 17:27 ` Sylwester Nawrocki
2012-05-27 16:56 ` [RFC PATCH 2/3] media: Remove VIDEO_MEDIA Kconfig option Mauro Carvalho Chehab
2012-05-27 16:56 ` [RFC PATCH 3/3] media: only show V4L devices based on device type selection Mauro Carvalho Chehab
2012-05-27 17:13 ` [RFC] file tree rearrangement - was: Re: [RFC PATCH 0/3] Improve Kconfig selection for media devices Mauro Carvalho Chehab
2012-05-27 17:25 ` Hans Verkuil
2012-05-27 18:47 ` Andy Walls
2012-05-27 20:15 ` Mauro Carvalho Chehab
2012-05-28 9:42 ` Hans Verkuil
2012-05-28 11:03 ` Mauro Carvalho Chehab
2012-05-28 11:45 ` Hans Verkuil
2012-05-28 12:10 ` Mauro Carvalho Chehab [this message]
2012-05-27 19:54 ` Mauro Carvalho Chehab
2012-05-28 9:12 ` Hans Verkuil
2012-05-28 9:48 ` Stefan Richter
2012-05-28 11:38 ` Mauro Carvalho Chehab
2012-05-28 12:17 ` Stefan Richter
2012-05-28 12:32 ` Mauro Carvalho Chehab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FC36B43.90703@redhat.com \
--to=mchehab@redhat.com \
--cc=awalls@md.metrocast.net \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).