linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Helen Koike <helen.koike@collabora.com>, linux-media@vger.kernel.org
Subject: Re: [PATCH 0/4] media Kconfig reorg - part 2
Date: Thu, 26 Mar 2020 17:07:21 +0100	[thread overview]
Message-ID: <20200326170721.6c71a192@coco.lan> (raw)
In-Reply-To: <6fadc6ea-8512-03ba-da30-43c64d7562f6@collabora.com>

(removed that big c/c list - kept just media)

Em Wed, 25 Mar 2020 16:36:31 -0300
Helen Koike <helen.koike@collabora.com> escreveu:

> Hello,
> 
> On 3/25/20 1:03 PM, Mauro Carvalho Chehab wrote:
> > That's the second part of media Kconfig changes. The entire series is
> > at:
> > 
> > 	https://git.linuxtv.org/mchehab/experimental.git/log/?h=media-kconfig  
> 
> I made a quick experiment (using this branch) with someone who works with the kernel for his master degree, but doesn't have much experience in kernel development in general.
> I asked him to enable Vimc (from default configs, where multimedia starts disabled).
> He knows that Vimc is a virtual camera driver, and this is how he behaved:
> 
> === Start of experiment:
> 
> * He pressed '/' and searched for vimc to see the location path.
> * Then he enabled "Multimedia support" and went straight to "Media drivers" (which just shows USB and PCI).
> * He went back to "Multimedia support", entered "Media device types" and enabled "Test drivers".
> * He went back to "Media drivers" again and didn't find Vimc (nothing changed in this menu).

There was an issue with test driver dependencies. this patch
fixes it:

	https://git.linuxtv.org/mchehab/experimental.git/commit/?h=media-kconfig&id=c267c23e0884172beac4fb4e68c35fc26ff2e615

Basically, the VIDEO_DEV was not selected with MEDIA_TEST_SUPPORT.
So, the "Media drivers" menu would be empty.

After this change, the only thing a .config file would need to build
a test driver would either need to select those:

	CONFIG_MODULES=y
	CONFIG_MEDIA_SUPPORT=m
	CONFIG_MEDIA_SUPPORT_FILTER=y
	CONFIG_MEDIA_TEST_SUPPORT=y
	CONFIG_V4L_TEST_DRIVERS=y
	CONFIG_VIDEO_VIMC=y

	(filtering way)

or those:

	CONFIG_MODULES=y
	CONFIG_MEDIA_SUPPORT=m
	CONFIG_VIDEO_DEV=y
	CONFIG_MEDIA_TEST_SUPPORT=y
	CONFIG_V4L_TEST_DRIVERS=y
	CONFIG_VIDEO_VIMC=y

	(non-filtering way)

(MODULES config is optional. I opted to use modules just to be able
to use make M=drivers/media)

For testing purposes, here, I stored just the above on a file
called media_config, and then I did:

	$ make allnoconfig
	$ cp media_config >.config
	$ make olddefconfig && make init 2>/dev/null
	$ rm $(find drivers/media -name '*.ko') $(find drivers/media -name '*.o') 2>/dev/null
	$ make M=drivers/media
	  CC [M]  drivers/media/common/v4l2-tpg/v4l2-tpg-core.o
	  CC [M]  drivers/media/common/videobuf2/videobuf2-core.o
	  ...
	  MODPOST 8 modules
	  ...
	  LD [M]  drivers/media/v4l2-core/v4l2-dv-timings.ko
	  LD [M]  drivers/media/v4l2-core/videodev.ko

In this specific case, either using the filtered or non-filtered way,
the number of options to enable "vimc" are the same.

Thanks,
Mauro

  parent reply	other threads:[~2020-03-26 16:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-25 16:03 [PATCH 0/4] media Kconfig reorg - part 2 Mauro Carvalho Chehab
2020-03-25 16:03 ` [PATCH 1/4] media: dvb-core: Kconfig: default to use dynamic minors Mauro Carvalho Chehab
2020-03-25 16:03 ` [PATCH 2/4] media: Kconfig files: use select for V4L2 subdevs and MC Mauro Carvalho Chehab
2020-03-25 16:03 ` [PATCH 3/4] media: i2c/Kconfig: reorganize items there Mauro Carvalho Chehab
2020-03-25 16:03 ` [PATCH 4/4] media: Kconfig: don't use visible for device type select Mauro Carvalho Chehab
2020-03-25 19:36 ` [PATCH 0/4] media Kconfig reorg - part 2 Helen Koike
2020-03-25 21:38   ` Mauro Carvalho Chehab
2020-03-25 22:13     ` Laurent Pinchart
2020-03-26  8:28       ` Mauro Carvalho Chehab
2020-03-26 10:13         ` Laurent Pinchart
2020-03-26 12:51           ` Mauro Carvalho Chehab
2020-03-26 16:07   ` Mauro Carvalho Chehab [this message]
2020-04-01 10:59   ` Dan Carpenter
2020-04-02  9:27     ` 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=20200326170721.6c71a192@coco.lan \
    --to=mchehab+huawei@kernel.org \
    --cc=helen.koike@collabora.com \
    --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).