[lkml]   [2019]   [Dec]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Why is CONFIG_VT forced on?
On 12/30/19 4:53 PM, Rob Landley wrote:
> On 12/30/19 6:36 PM, Randy Dunlap wrote:
>> 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 ^^^^^^^^^^^^^^^^.
> Try to switch it off. It won't let you, it's forced on by something else. The
> help doesn't say what. (That select means it's forcing CONFIG_INPUT on?)
>> Does that explain it? Maybe I don't understand the problem.
> It's possible I don't either. I can disable it when when I start from
> allnoconfig and then switch CONFIG_TTY on (at which point it defaults to y, but
> can be disabled).

# Character devices
# CONFIG_VT is not set

But first you must set/enable EXPERT. See the bool prompt.


 \ /
  Last update: 2019-12-31 02:01    [W:0.051 / U:1.280 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site