From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+willy=40w.ods.org@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S261861AbTJMQ7d (ORCPT <rfc822;willy@w.ods.org>);
	Mon, 13 Oct 2003 12:59:33 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261863AbTJMQ7d
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Mon, 13 Oct 2003 12:59:33 -0400
Received: from fw.osdl.org ([65.172.181.6]:49546 "EHLO mail.osdl.org")
	by vger.kernel.org with ESMTP id S261861AbTJMQ7a (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Mon, 13 Oct 2003 12:59:30 -0400
Date: Mon, 13 Oct 2003 09:49:43 -0700
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: "Norman Diamond" <ndiamond@wta.att.ne.jp>
Cc: sam@ravnborg.org, linux-kernel@vger.kernel.org, zippel@linux-m68k.org
Subject: Re: 2.6.0-test7 and HIDBP
Message-Id: <20031013094943.25ea6577.rddunlap@osdl.org>
In-Reply-To: <26ca01c38ff9$f4762d00$5cee4ca5@DIAMONDLX60>
References: <1f8801c38f11$da95c410$5cee4ca5@DIAMONDLX60>
	<20031010073750.001ad559.rddunlap@osdl.org>
	<242001c38fdf$fb165690$5cee4ca5@DIAMONDLX60>
	<20031011111328.GB932@mars.ravnborg.org>
	<26ca01c38ff9$f4762d00$5cee4ca5@DIAMONDLX60>
Organization: OSDL
X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.10; i686-pc-linux-gnu)
X-Face: +5V?h'hZQPB9<D&+Y;ig/:L-F$8p'$7h4BBmK}zo}[{h,eqHI1X}]1UhhR{49GL33z6Oo!`
 !Ys@HV,^(Xp,BToM.;N_W%gT|&/I#H@Z:ISaK9NqH%&|AO|9i/nB@vD:Km&=R2_?O<_V^7?St>kW
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

On Sat, 11 Oct 2003 22:15:50 +0900 "Norman Diamond" <ndiamond@wta.att.ne.jp> wrote:

| Sam Ravnborg replied to me:
| 
| > If there are dofferences between what is shown in xconfig and gconfig,
| > then there is a bug in one of the front-ends.
| > They use the same back-end - and what they display is based on the same
| > input files.
| 
| Or maybe there are bugs in both of these front-ends.  I finally thought of
| looking at two .config files in text editors, one produced by make xconfig
| and one produced by make gconfig.  Both are for kernel 2.6.0-test7 though
| the machines and original distros are different.
| 
| In the .config generated by make xconfig, the following lines exist:
| 
| #
| # USB Human Interface Devices (HID)
| #
| CONFIG_USB_HID=m
| CONFIG_USB_HIDINPUT=y
| # CONFIG_HID_FF is not set
| # CONFIG_USB_HIDDEV is not set
| 
| #
| # USB HID Boot Protocol drivers
| #
| # CONFIG_USB_KBD is not set
| # CONFIG_USB_MOUSE is not set
| # CONFIG_USB_AIPTEK is not set
| # CONFIG_USB_WACOM is not set
| [...]
| 
| OK, aside from making me wonder what HIDDEV refers to and why it isn't set,
| and making it rather non-obvious which drivers are HID Boot Protocol and
| which aren't, the settings look pretty reasonable to me.
| 
| In the .config generated by make gconfig, the following lines exist:
| 
| #
| # USB Human Interface Devices (HID)
| #
| CONFIG_USB_HID=y
| CONFIG_USB_HIDINPUT=y
| # CONFIG_HID_FF is not set
| CONFIG_USB_HIDDEV=y
| # CONFIG_USB_AIPTEK is not set
| # CONFIG_USB_WACOM is not set
| [...]
| 
| With this file in a text editor, searching for string USB_KBD results in the
| string not being found.

Let me see if I am understanding this..
Is the problem that some generated .config files contain different
strings for options that are _not_ set, depending on which
front-end is used?
Or are you discussing a bug in the (on-screen) viewable part of a
config front-end?

If so, I'll confirm that different config front-ends generate different
.config files, and it makes using "vi .config && make oldconfig"
not as usable as I'd like it to be, but I don't know that it's a bug.

--
~Randy