title: Debugging or verbose mode for Kconfig?
body: <p>I'm working with a LeopardBoard DM368 and I want to enable some video hardware. The relevant modules are vpfe-capture, isif, and tvp7002. </p>
  
  <p>I've written a defconfig file with what I believe to be the correct set of CONFIG_FOO parameters for everything to work. Judging by the dependencies appearing in the various Kconfig files, I believe I've done everything correctly, but I can't seem to prevent kconf from discarding <code>CONFIG_ISIF</code> and <code>CONFIG_VPFE_CAPTURE</code>.</p>
  
  <p>My very ugly alternative is to go in and start manually hacking makefiles. That works to pick up the modules I want, but it's obviously inconsistent with the design and intent of the Kconfig system, and would break any tools like "make gconfig".</p>
  
  <p>make has a "-d" verbosity flag that explains how it is processing dependencies. Is there anything similar for kconf, where I could get it to explain why it's not giving me the two CONFIGs I'm trying to get?</p>