From: Brad Hards <bhards@bigpond.net.au>
To: Greg KH <greg@kroah.com>
Cc: Tyler Longren <tyler@captainjack.com>,
kiza@gmx.net, 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 07:02:22 +1000 [thread overview]
Message-ID: <200208060702.29360.bhards@bigpond.net.au> (raw)
In-Reply-To: <20020805165601.GA27503@kroah.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, 6 Aug 2002 02:56, Greg KH wrote:
> On Tue, Aug 06, 2002 at 12:00:55AM +1000, Brad Hards wrote:
> > 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;
> > }
>
> ??? Why return -1 as a void *?
>
> The only caller of hiddev_connect is:
> if (!hiddev_connect(hid))
> hid->claimed |= HID_CLAIMED_HIDDEV;
>
> Hm, seems like you don't want a void * there at all, but a int, right?
I assume so.
> But that doesn't explain the error people are having with the code
> compiled in.
No - while doing the investigation, I noted that dmesg was showing
input0,hiddev0: USB HID v1.10 Keyboard [045e:001d] on usb2:3.0
input1,hiddev0: USB HID v1.10 Pointer [045e:001d] on usb2:3.1
input2,hiddev0: USB HID v1.00 Mouse [Logitech USB-PS/2 Mouse M-BA47] on usb2:4.0
with CONFIG_USB_HIDDEV turned off.
So I chased that down to the above conclusion.
But I still don't see the problem, and can't duplicate it.
Brad
- --
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
iD8DBQE9TufiW6pHgIdAuOMRAojFAKCmSOjjTwcp6z7tPKeR6kaokAF71wCginFW
5/94epXIyAJlfpFGtmQqxOY=
=Ywrd
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2002-08-05 21:04 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
2002-08-05 14:37 ` K.R. Foley
2002-08-05 16:56 ` Greg KH
2002-08-05 21:02 ` Brad Hards [this message]
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=200208060702.29360.bhards@bigpond.net.au \
--to=bhards@bigpond.net.au \
--cc=greg@kroah.com \
--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®