From: Roman Zippel <zippel@linux-m68k.org>
To: Tomas Szepe <szepe@pinerecords.com>
Cc: Dave Jones <davej@codemonkey.org.uk>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] new kconfig goodies
Date: Tue, 13 May 2003 00:36:27 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.44.0305122257320.5042-100000@serv> (raw)
In-Reply-To: <20030512160029.GJ5376@louise.pinerecords.com>
Hi,
On Mon, 12 May 2003, Tomas Szepe wrote:
> Also, will the config system let the user know that their having
> enabled a certain option has affected other options (possibly in
> different submenus)?
The user will see that he can't disable certain options.
This is basically the same problem as with other dependencies, if the user
selects an option other options may become visible. There is no direct
information, how the config option depend on each other (except xconfig
offers that as a debug option).
> As things work now, there's no way to tell
> if an option has been switched on "by dependency," so in the above
> example, in switching GART_IOMMU off after its switching on has
> enabled AGP, the system won't know to disable AGP again. I'm not
> convinced this is a nice feature in fact. :) Maybe we just need
> something like grayed-out entries with a comment, for instance:
>
> /* [ ] IOMMU support (needs "/dev/agpgard (AGP Support)") */
Of course the same can be done with normal dependencies, but this new
option offers more flexibility. Important options don't have to be hidden
away behind a lot of dependencies. I'm aware that this can be abused, so I
have to watch a bit how it will be used.
bye, Roman
next prev parent reply other threads:[~2003-05-12 22:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 13:39 [PATCH] new kconfig goodies Roman Zippel
2003-05-12 14:16 ` Adrian Bunk
2003-05-12 15:37 ` Roman Zippel
2003-05-12 14:32 ` Dave Jones
2003-05-12 15:39 ` Roman Zippel
2003-05-12 16:08 ` Dave Jones
2003-05-12 16:00 ` Tomas Szepe
2003-05-12 22:36 ` Roman Zippel [this message]
2003-05-12 15:13 ` Geert Uytterhoeven
2003-05-12 15:43 ` Roman Zippel
2003-05-13 1:38 ` Miles Bader
2003-05-13 1:44 ` Miles Bader
2003-05-13 15:27 ` Roman Zippel
2003-05-13 21:17 ` Miles Bader
2003-05-14 19:51 ` Roman Zippel
2003-05-14 20:56 ` Andreas Schwab
2003-05-14 22:11 ` Roman Zippel
2003-05-15 0:21 ` Michael Alan Dorman
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.0305122257320.5042-100000@serv \
--to=zippel@linux-m68k.org \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=szepe@pinerecords.com \
/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).