[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b3cf8faf-ef04-2f55-3ccb-772e18a57d7b@infradead.org>
Date: Mon, 30 Dec 2019 16:36:22 -0800
From: Randy Dunlap <rdunlap@...radead.org>
To: Rob Landley <rob@...dley.net>, linux-kernel@...r.kernel.org
Subject: Re: Why is CONFIG_VT forced on?
On 12/30/19 4:30 PM, 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?
I've never had to resort to that trick.
> Rob
>
config VT
bool "Virtual terminal" if EXPERT
depends on !UML
select INPUT
default y
^^^^^^^^^^^^^^^^^^^
That's all it takes ^^^^^^^^^^^^^^^^.
Does that explain it? Maybe I don't understand the problem.
--
~Randy
Powered by blists - more mailing lists