From: Vojtech Pavlik <vojtech@suse.cz>
To: Philipp Matthias Hahn <pmhahn@titan.lahn.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux USB Mailinglist <linux-usb-devel@lists.sourceforge.net>,
torvalds@transmeta.com, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [BUG] hiddev.c 2.4.10-pre9
Date: Sun, 16 Sep 2001 12:26:24 +0200 [thread overview]
Message-ID: <20010916122624.A1063@suse.cz> (raw)
In-Reply-To: <Pine.LNX.4.33.0109161202490.30202-100000@titan.lahn.de>
In-Reply-To: <Pine.LNX.4.33.0109161202490.30202-100000@titan.lahn.de>; from pmhahn@titan.lahn.de on Sun, Sep 16, 2001 at 12:09:40PM +0200
On Sun, Sep 16, 2001 at 12:09:40PM +0200, Philipp Matthias Hahn wrote:
> Hello LKML, USB-ML, Vojtech!
>
> The initialization order of hid.o and hiddev.o is wrong:
>
> drivers/usb/hiddev.c:573 hiddev_connect() is called by
> drivers/usb/hid-core.c:1225 hid_probe() before
> drivers/usb/hiddev.c:665 hiddev_init() is called.
>
> This results in hiddev_devfs_handle being NULL for each hid-device handled
> by hiddev, so that all device-nodes are created as /dev/hiddev%d instead
> of /dev/usb/hid/hiddev%d.
And here goes the fix. It also fixes a problem with devices with HID
type interface with no endpoints. Alan, Linus, please apply it.
--- linux-2.4.9-ac10/drivers/usb/hid-core.c Mon Sep 10 10:10:16 2001
+++ linux/drivers/usb/hid-core.c Sun Sep 16 12:25:01 2001
@@ -1281,10 +1281,10 @@
static int __init hid_init(void)
{
- usb_register(&hid_driver);
#ifdef CONFIG_USB_HIDDEV
hiddev_init();
#endif
+ usb_register(&hid_driver);
info(DRIVER_VERSION " " DRIVER_AUTHOR);
--
Vojtech Pavlik
SuSE Labs
prev parent reply other threads:[~2001-09-16 10:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-16 10:09 [BUG] hiddev.c 2.4.10-pre9 Philipp Matthias Hahn
2001-09-16 10:26 ` Vojtech Pavlik [this message]
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=20010916122624.A1063@suse.cz \
--to=vojtech@suse.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=pmhahn@titan.lahn.de \
--cc=torvalds@transmeta.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