Message-ID: <3F2AC3DA.6040901@rackable.com>
Date: Fri, 01 Aug 2003 12:47:38 -0700
From: Samuel Flory <sflory@rackable.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030529
MIME-Version: 1.0
To: Greg KH <greg@kroah.com>
CC: linux-usb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: 2.4.22-pre10 compile failure  USB HID
References: <3F2AC00C.1010203@rackable.com> <20030801194406.GA31510@kroah.com>
In-Reply-To: <20030801194406.GA31510@kroah.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1140
Lines: 36

Greg KH wrote:

>On Fri, Aug 01, 2003 at 12:31:24PM -0700, Samuel Flory wrote:
>  
>
>> I'm seeing a linking issue when I compile USB HID support directly 
>>into the kernel.  Looking at my kernel config it looks like it might 
>>have something to do with the fact that I'm compiling CONFIG_INPUT, 
>>CONFIG_INPUT_KEYBDEV, and CONFIG_INPUT_MOUSEDEV as modules.  Should 
>>CONFIG_USB_HID depend on one, or all of the above.
>>    
>>
>
>Yes, that configuration will not work.  I think this has been discussed
>many times on the lists in the past, and the end agreement is, "Don't
>try to do that." :)
>
>It's not an easy configuration language fix from what I remember.
>
>  
>

  I'll take a look it.  It seems to work if you compile in the rest of 
the HID stuff.

-- 
Once you have their hardware. Never give it back.
(The First Rule of Hardware Acquisition)
Sam Flory  <sflory@rackable.com>


-
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/