public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oliver Feiler <kiza@gmxpro.net>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.19, USB_HID only works compiled in, not as module
Date: Sun, 4 Aug 2002 17:46:56 +0200	[thread overview]
Message-ID: <200208041746.56274.kiza@gmxpro.net> (raw)
In-Reply-To: <60bc.3d4d4347.5dd06@trespassersw.daria.co.uk>

On Sunday 04 August 2002 17:07, Jonathan Hudson wrote:
>
> Not so. USB Mouse works just fine here on 2.4.19.
>
> $ lsmod
> ....
> mousedev                4352   1
> hid                    14112   0 (unused)
> input                   3328   0 [mousedev hid]
> ....
>
> CONFIG_INPUT=m
> # CONFIG_INPUT_KEYBDEV is not set
> CONFIG_INPUT_MOUSEDEV=m
> CONFIG_INPUT_MOUSEDEV_SCREEN_X=1280
> CONFIG_INPUT_MOUSEDEV_SCREEN_Y=1024
>
> CONFIG_USB_HID=m
> CONFIG_USB_HIDINPUT=y
> # CONFIG_USB_HIDDEV is not set
>
> 'cat /dev/input/mice' (a cat and mouse game?) gives output as well.
>
> So there appears to be no generic 2.4.19 problem.

Hm, seems so. The relevant options I used are:

CONFIG_INPUT=y
# CONFIG_INPUT_KEYBDEV is not set
CONFIG_INPUT_MOUSEDEV=m
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_JOYDEV=y
CONFIG_INPUT_EVDEV=m

CONFIG_USB=y
CONFIG_USB_DEVICEFS=y
CONFIG_USB_UHCI=y
CONFIG_USB_HID=m
CONFIG_USB_HIDINPUT=y

I don't know if it's a config problem. First I suspected CONFIG_USB_HIDINPUT 
could be the problem because it's new in 2.4.19. But as I see it works for 
you, so there shouldn't be a problem.

-- 
Oliver Feiler  <kiza@(gmx(pro).net|lionking.org|claws-and-paws.com)>
http://www.lionking.org/~kiza/  <--   homepage
PGP-key ID 0x561D4FD2    --> /pgpkey.shtml
http://www.lionking.org/~kiza/journal/


  reply	other threads:[~2002-08-04 15:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.egf7e0v.kk5a2@ifi.uio.no>
2002-08-04 15:07 ` 2.4.19, USB_HID only works compiled in, not as module Jonathan Hudson
2002-08-04 15:46   ` Oliver Feiler [this message]
2002-08-04 21:51     ` Brad Hards
2002-08-04 22:41       ` Oliver Feiler
2002-08-18 12:52       ` Vojtech Pavlik
2002-08-05  5:34 Tyler Longren
2002-08-05 11:14 ` Brad Hards
2002-08-05 14:00   ` Brad Hards
2002-08-05 14:37     ` K.R. Foley
2002-08-05 16:56     ` Greg KH
2002-08-05 21:02       ` Brad Hards
2002-08-06  5:41         ` Tyler Longren
2002-08-07 10:50         ` Oliver Feiler
2002-08-07 22:24           ` Brad Hards
2002-08-07 22:51             ` Oliver Feiler
  -- strict thread matches above, loose matches on Subject: below --
2002-08-04 14:56 Oliver Feiler
2002-08-04 16:20 ` Greg KH
2002-08-04 16:53   ` Oliver Feiler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200208041746.56274.kiza@gmxpro.net \
    --to=kiza@gmxpro.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox