From: Vincent Vanackere <vincent.vanackere@gmail.com>
To: linux-kernel@vger.kernel.org, Greg KH <gregkh@suse.de>,
thoffman@arnor.net
Cc: "Viktor A. Danilov" <__die@mail.ru>
Subject: PROBLEM: atiremote input doesn`t register `device` & `driver` section in sysfs (/sys/class/input/event#)
Date: Sun, 5 Jun 2005 12:21:43 +0200 [thread overview]
Message-ID: <65258a580506050321f1eeab0@mail.gmail.com> (raw)
In-Reply-To: <20050412074121.GE1371@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 529 bytes --]
> On Sun, Apr 10, 2005 at 07:21:28PM +0600, Viktor A. Danilov wrote:
> >
> > PROBLEM: aiptek input doesn`t register `device` & `driver` section in sysfs (/sys/class/input/event#)
> > REASON: `dev` - field not filled...
> > SOLUTION: in linux/drivers/usb/input/aiptek.c write
> > aiptek->inputdev.dev = &intf->dev;
> > before calling
> > input_register_device(&aiptek->inputdev);
Hi,
The following (tested) patch fixes the exact same issue with the ATI
Remote input driver.
Best regards,
Vincent
[-- Attachment #2: patch_ati.txt --]
[-- Type: text/plain, Size: 522 bytes --]
--- linux-2.6.11/drivers/usb/input/ati_remote.c 2005-05-09 16:20:19.000000000 +0200
+++ linux-2.6.12-rc5/drivers/usb/input/ati_remote.c 2005-06-05 11:40:58.000000000 +0200
@@ -654,6 +654,7 @@
idev->id.vendor = le16_to_cpu(ati_remote->udev->descriptor.idVendor);
idev->id.product = le16_to_cpu(ati_remote->udev->descriptor.idProduct);
idev->id.version = le16_to_cpu(ati_remote->udev->descriptor.bcdDevice);
+ idev->dev = &(ati_remote->udev->dev);
}
static int ati_remote_initialize(struct ati_remote *ati_remote)
next prev parent reply other threads:[~2005-06-05 10:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-10 13:21 PROBLEM: AIPTEK input doesn`t register `device` & `driver` section in sysfs (/sys/class/input/event#) Viktor A. Danilov
2005-04-12 7:41 ` Greg KH
2005-06-05 10:21 ` Vincent Vanackere [this message]
2005-06-20 15:43 ` PROBLEM: atiremote " Vojtech Pavlik
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=65258a580506050321f1eeab0@mail.gmail.com \
--to=vincent.vanackere@gmail.com \
--cc=__die@mail.ru \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=thoffman@arnor.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.