From: Samuel Flory <sflory@rackable.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: 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 11:00:31 -0700 [thread overview]
Message-ID: <3F1D7BBF.8070202@rackable.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0307221146120.714-100000@serv>
Roman Zippel wrote:
>Hi,
>
>On Mon, 21 Jul 2003, Samuel Flory wrote:
>
>
>
>> 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.
>
Now that's very confusing. So in order to enable something under the
Character devices menu you need to 1st enable something under "Input
device support". Which for some reason is configured as a module? It
says something that I resorted to editing .config by hand.
Is it too much to ask to make the defaults give us a working
console? Otherwise we will be answering the question of "why does
screen go blank after uncompressing" for the entire 2.6 cycle!! The
number of people who don't want to enable config_vt is fairly small, and
they will be wanting to remove a number of our defaults any way.
--
Once you have their hardware. Never give it back.
(The First Rule of Hardware Acquisition)
Sam Flory <sflory@rackable.com>
next prev parent reply other threads:[~2003-07-22 17:50 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
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 [this message]
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=3F1D7BBF.8070202@rackable.com \
--to=sflory@rackable.com \
--cc=admin@www0.org \
--cc=clepple@ghz.cc \
--cc=linux-kernel@vger.kernel.org \
--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).