[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191231022859.GB4203@ZenIV.linux.org.uk>
Date: Tue, 31 Dec 2019 02:28:59 +0000
From: Al Viro <viro@...iv.linux.org.uk>
To: Rob Landley <rob@...dley.net>
Cc: linux-kernel@...r.kernel.org
Subject: Re: Why is CONFIG_VT forced on?
On Mon, Dec 30, 2019 at 06:30:15PM -0600, Rob Landley wrote:
> On x86-64 menuconfig, CONFIG_VT is forced on (in drivers->char devices->virtual
> terminal), but the help doesn't mention a "selects", and I didn't spot anything
> obvious in "find . -name 'Kconfig*' | xargs grep -rw VT".
>
> Congratulations, you've reinvented "come from". I'm mostly familiar with the
> kconfig plumbing from _before_ you made it turing complete: how do I navigate this?
>
> I'm guessing "stick printfs into the menuconfig binary" is the recommended next
> step for investigating this? Or is there a trick I'm missing?
config VT
bool "Virtual terminal" if EXPERT
IOW, it's only conrollable if EXPERT is set. Finding CONFIG_EXPERT, setting it
and turning CONFIG_VT off is left as an exercise for reader; ceasing the
indignant whining for long enough to do that might or might not be doable -
up to you.
Powered by blists - more mailing lists