Re: PROBLEM: atiremote input doesn`t register `device` & `driver` section in sysfs (/sys/class/input/event#)

On Sun, Jun 05, 2005 at 12:21:43PM +0200, Vincent Vanackere wrote:
> > 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.

Thanks; applied.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- PROBLEM: AIPTEK input doesn`t register `device` & `driver` section in sysfs (/sys/class/input/event#)
  - From: "Viktor A. Danilov" <[email protected]>
- Re: PROBLEM: AIPTEK input doesn`t register `device` & `driver` section in sysfs (/sys/class/input/event#)
  - From: Greg KH <[email protected]>
- PROBLEM: atiremote input doesn`t register `device` & `driver` section in sysfs (/sys/class/input/event#)
  - From: Vincent Vanackere <[email protected]>

Prev by Date: Re: how to insert an asm instruction in C code and how to compile it
Next by Date: Re: 2.6.12-mm1 compile failure on PPC64
Previous by thread: PROBLEM: atiremote input doesn`t register `device` & `driver` section in sysfs (/sys/class/input/event#)
Next by thread: Re:[PATCH] zero disk pages used by swsusp on resume
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]