linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Simmons <jsimmons@infradead.org>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Samuel Flory <sflory@rackable.com>,
	Charles Lepple <clepple@ghz.cc>, michaelm <admin@www0.org>,
	<linux-kernel@vger.kernel.org>, <vojtech@suse.cz>
Subject: Re: Make menuconfig broken
Date: Tue, 22 Jul 2003 17:47:04 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0307221735160.5483-100000@phoenix.infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0307221146120.714-100000@serv>


> >   Try this in 2.6.0-test1:
> > rm .config
> > make mrproper
> > make menuconfig
> > 
> >   There is no option for CONFIG_VT, and CONFIG_VT_CONSOLE under 
> > character devices in "make menuconfig.
> 
> Try enabling CONFIG_INPUT.
> 
> Vojtech, how about the patch below? This way CONFIG_VT isn't hidden behind 
> CONFIG_INPUT, but CONFIG_INPUT is selected if needed.
> 
> Index: drivers/char/Kconfig
> ===================================================================
> RCS file: /home/other/cvs/linux/linux-2.6/drivers/char/Kconfig,v
> retrieving revision 1.1.1.1
> diff -u -p -r1.1.1.1 Kconfig
> --- drivers/char/Kconfig	14 Jul 2003 09:22:00 -0000	1.1.1.1
> +++ drivers/char/Kconfig	22 Jul 2003 08:08:26 -0000
> @@ -6,7 +6,7 @@ menu "Character devices"
>  
>  config VT
>  	bool "Virtual terminal"
> -	requires INPUT=y
> +	select INPUT
>  	---help---
>  	  If you say Y here, you will get support for terminal devices with
>  	  display and keyboard devices. These are called "virtual" because you

What about the keyboard being built in. People will still not set that. 

The proper solution would be to alter the build system on a default build 
to scan the .config file for CONFIG_PC_KEYB, CONFIG_MOUSE, CONFIG_BUSMOUSE,
CONFIG_PSMOUSE etc. Then convert them to what is needed for 2.6.X. The same 
for framebuffer console stuff. We can scan for CONFIG_FB and if 
CONFIG_FRAMEBUFFER_CONSOLE is not present set it. We only would need to do 
this for a default build. 




  parent reply	other threads:[~2003-07-22 16:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-21 16:35 2.6.0-test1 won't go further than "uncompressing" on a p1/32MB pc michaelm
2003-07-21 16:49 ` James Simmons
2003-07-21 17:02 ` Charles Lepple
2003-07-22  0:37   ` Samuel Flory
2003-07-22  0:42     ` Make menuconfig broken Samuel Flory
2003-07-22  7:19       ` Sam Ravnborg
2003-07-22  9:50       ` Roman Zippel
2003-07-22 13:24         ` Vojtech Pavlik
2003-07-22 16:47         ` James Simmons [this message]
2003-07-22 18:17           ` Christoph Hellwig
2003-07-22 19:16             ` Sam Ravnborg
2003-07-22 19:35               ` Samuel Flory
2003-07-22 19:46                 ` Charles Lepple
2003-07-22 20:30                 ` James Simmons
2003-07-23 22:53                   ` bill davidsen
2003-07-23 22:48             ` bill davidsen
2003-07-22 18:00         ` Samuel Flory
2003-07-22 19:21           ` michaelm
2003-07-22  2:49     ` 2.6.0-test1 won't go further than "uncompressing" on a p1/32MB pc Thomas Molina
2008-02-02 17:29 make menuconfig broken Michal Zachar
2008-02-02 19:50 ` Sam Ravnborg

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=Pine.LNX.4.44.0307221735160.5483-100000@phoenix.infradead.org \
    --to=jsimmons@infradead.org \
    --cc=admin@www0.org \
    --cc=clepple@ghz.cc \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sflory@rackable.com \
    --cc=vojtech@suse.cz \
    --cc=zippel@linux-m68k.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).