Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 5 Sep 2002 03:56:03 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 5 Sep 2002 03:56:02 -0400 Received: from [64.6.248.2] ([64.6.248.2]:19880 "EHLO greenie.frogspace.net") by vger.kernel.org with ESMTP id ; Thu, 5 Sep 2002 03:56:02 -0400 Date: Thu, 5 Sep 2002 01:00:33 -0700 (PDT) From: Peter X-X-Sender: cogweb@greenie.frogspace.net To: linux-kernel@vger.kernel.org Subject: Re: 2.4.19-ac4 build problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1127 Lines: 33 >No, because it works just fine when you build the USB drivers as >modules, and the Input core as modules, which is what the majority of >people do. In that case, let's add this to the help screens for the three device types (CONFIG_INPUT_KEYBDEV, CONFIG_INPUT_MOUSEDEV, CONFIG_INPUT_JOYDEV), after the current text: For the drivers to link correctly, you must make the same selection (Y or M) here as for the USB Human Interface Device (full HID) support. Under CONFIG_USB_HID, likewise add after the current text: For the drivers to link correctly, you must make the same selection (Y or M) here as for Input core support. That said, I suggest that Input core support menu be moved into the USB support menu, where these dependency relations can be automated and made visible to the user. I apologize for not submitting a patch -- it's a skill I lack. Cheers, Peter. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/