From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+w=401wt.eu-S1756553AbYECXh5@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1756553AbYECXh5 (ORCPT <rfc822;w@1wt.eu>);
	Sat, 3 May 2008 19:37:57 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754573AbYECXhu
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Sat, 3 May 2008 19:37:50 -0400
Received: from khc.piap.pl ([195.187.100.11]:59656 "EHLO khc.piap.pl"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1753068AbYECXht (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Sat, 3 May 2008 19:37:49 -0400
To: Adrian Bunk <bunk@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, Dmitry Torokhov <dmitry.torokhov@gmail.com>,
       linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
       Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Ingo, no more kconfig patches
References: <20080430170125.ZZRA012@mailhub.coreip.homeip.net>
	<20080430211317.GA24633@elte.hu>
	<20080430230100.GK29330@cs181133002.pp.htv.fi>
	<20080501025234.GE27574@elte.hu>
	<20080501115923.GX29330@cs181133002.pp.htv.fi>
	<20080503191445.GF5292@elte.hu>
	<20080503202416.GR5838@cs181133002.pp.htv.fi>
	<m37ieb84ve.fsf@maximus.localdomain>
	<20080503214750.GU5838@cs181133002.pp.htv.fi>
	<m3wsmb6np2.fsf@maximus.localdomain>
	<20080503222943.GX5838@cs181133002.pp.htv.fi>
From: Krzysztof Halasa <khc@pm.waw.pl>
Date: Sun, 04 May 2008 01:37:47 +0200
In-Reply-To: <20080503222943.GX5838@cs181133002.pp.htv.fi> (Adrian Bunk's message of "Sun\, 4 May 2008 01\:29\:43 +0300")
Message-ID: <m3r6cj5584.fsf@maximus.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Adrian Bunk <bunk@kernel.org> writes:

> FB_SGIVW requires X86_VISWS and it's selected automatically.
>
> (which is not good if you want a kernel that runs on a PC)

Not sure what do you mean, it currently seem to "depend" on X86_VISWS:

config FB_SGIVW
        tristate "SGI Visual Workstation framebuffer support"
        depends on FB && X86_VISWS
        select FB_CFB_FILLRECT
        select FB_CFB_COPYAREA
        select FB_CFB_IMAGEBLIT

> Why do we have to bother users with the MII option at all?
>
> "E1000E=m and TULIP=m but MII=y" works, but it doesn't really make 
> sense.

(Obviously it assumes both TULIP and E1000E required MII which is not
exactly the case)

But it makes a perfect sense, I can have modular drivers for (few)
hardware devices (just in case I want to rmmod etc) but most of the
kernel may be not modular. It would be nice if the Kconfig ask me if
I want to "select" the dependency Y or M, even if there is only one
way to make "select" dependencies happy (not counting "Y vs "M").
-- 
Krzysztof Halasa