[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20060831174408.5ef9a143.rdunlap@xenotime.net>
Date: Thu, 31 Aug 2006 17:44:08 -0700
From: "Randy.Dunlap" <rdunlap@...otime.net>
To: Andrew Morton <akpm@...l.org>
Cc: Pavel Machek <pavel@....cz>, "Rafael J. Wysocki" <rjw@...k.pl>,
kernel list <linux-kernel@...r.kernel.org>
Subject: Re: prevent swsusp with PAE
On Thu, 31 Aug 2006 17:16:15 -0700 Andrew Morton wrote:
> On Thu, 31 Aug 2006 16:05:46 -0700
> "Randy.Dunlap" <rdunlap@...otime.net> wrote:
>
> > > > I think what this really points at is a weakness in the menuconfig/xconfig/etc
> > > > user interfaces. It should be possible to navigate to the presently-disabled
> > > > config option and ask it "why can't I turn you on?".
> > >
> > > Yes, but I'll still have users asking me "why I can't turn it on" ;-).
> >
> > menuconfig and xconfig both have Help and Search that can aid
> > with that, but I would still use the "comment" keyword also.
>
> Help and Search options aren't much use if you cannot see the option and if
> you do not know that it exists.
>
> A better UI design would be to show the unselectable option in some
> dimmed-out fashion and then provide an interface which permits the user to
>
> a) query the item to find out why it's not selectable and
>
> b) turn on the depends-on option(s) at the present site, thus making the
> present item selectable (ie: not dimmed any more).
>
> I dont't think any of that would require any Kconfig changes - it's purely
> a UI thing?
Probably. xconfig already has this ability/feature.
I enable/use it all the time. menuconfig could probably be
taught how to do it also. (and gconfig seems to be orphaned)
---
~Randy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists