mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Brad Hards <bhards@bigpond.net.au>
To: Tyler Longren <tyler@captainjack.com>, kiza@gmx.net
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.19, USB_HID only works compiled in, not as module
Date: Tue, 6 Aug 2002 00:00:55 +1000	[thread overview]
Message-ID: <200208060001.07546.bhards@bigpond.net.au> (raw)
In-Reply-To: <200208052114.15020.bhards@bigpond.net.au>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 5 Aug 2002 21:14, Brad Hards wrote:
> On Mon, 5 Aug 2002 15:34, Tyler Longren wrote:
> > Just to let you know, this problem isn't just happening to you.
> >
> > I compiled 2.4.19 using the same config file I used for 2.4.18 (yes, I
> > also turned on CONFIG_USB_HIDINPUT).  Needless to say, the mouse didn't
> > work on reboot.  I saw your post and compiled everything into the
> > kernel, and everything worked great on reboot.  So, I think this is
> > probably a real 2.4.19 problem.  Not something specific to you.
>
> I'm taking a look now.
I can't duplicate this problem yet.

> Could you (and anyone else with the same problem), mail me the
> lines from .config that matches CONFIG_USB for a configuration
> that fails to work. Off list would be best.
One issue that did come up was the handling of the no-HIDDEV case.

Greg: I think this was one of your patches, associated with the 
HIDINPUT patch. It looks like the return value is wrong. See 
below.

- --- include/linux/hiddev.h.orig Mon Aug  5 23:19:54 2002
+++ include/linux/hiddev.h      Mon Aug  5 23:56:34 2002
@@ -183,7 +183,7 @@
 int __init hiddev_init(void);
 void __exit hiddev_exit(void);
 #else
- -static inline void *hiddev_connect(struct hid_device *hid) { return NULL; }
+static inline void *hiddev_connect(struct hid_device *hid) { return -1; }
 static inline void hiddev_disconnect(struct hid_device *hid) { }
 static inline void hiddev_hid_event(struct hid_device *hid, unsigned int usage, int value) { }
 static inline int hiddev_init(void) { return 0; }

- -- 
http://conf.linux.org.au. 22-25Jan2003. Perth, Australia. Birds in Black.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9ToUbW6pHgIdAuOMRAvrRAJwOdrWv4FEHyW7cwMiC+CrMM/kXrgCbBHGR
Kq110ZnHc98yN4YPJJAuCIU=
=ck4u
-----END PGP SIGNATURE-----


  reply	other threads:[~2002-08-05 14:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-05  5:34 Tyler Longren
2002-08-05 11:14 ` Brad Hards
2002-08-05 14:00   ` Brad Hards [this message]
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
     [not found] <fa.egf7e0v.kk5a2@ifi.uio.no>
2002-08-04 15:07 ` Jonathan Hudson
2002-08-04 15:46   ` Oliver Feiler
2002-08-04 21:51     ` Brad Hards
2002-08-04 22:41       ` Oliver Feiler
2002-08-18 12:52       ` Vojtech Pavlik
  -- 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=200208060001.07546.bhards@bigpond.net.au \
    --to=bhards@bigpond.net.au \
    --cc=kiza@gmx.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tyler@captainjack.com \
    /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

all inboxes | Powered by JetHome®