On Wed, Oct 24, 2001 at 09:39:44AM +0200, O. Beaudoux wrote:
> Hi Vojtech,
>
> > > > For this type of access, /dev/input/eventX was designed. It'll give you
> > > > all you describe.
> > >
> > > I have tried it but I cannot make it work. I run it under kernel 2.2.18
> > > and 2.4.0 (SuSE 7.1 inst
Hi Vojtech,
> > > For this type of access, /dev/input/eventX was designed. It'll give you
> > > all you describe.
> >
> > I have tried it but I cannot make it work. I run it under kernel 2.2.18
> > and 2.4.0 (SuSE 7.1 installation). If it can work, I effectively think
> > its the better choice :-
> So I prefer to use the patch mentionned in Dan Streetman and David
> Brownell... or wait for its integration in futur 2.4 kernels...
That shouldn't affect your application though, assuming you're
talking about the patch that lets user mode drivers disconnect
kernel mode ones so they can use th
On Tue, Oct 23, 2001 at 09:47:31AM +0200, O. Beaudoux wrote:
> > > I think its effectively a good choice for a standard mouse usage. But
> > > when I want to use a grapic tablet (a wacom intuos for instance), I'll
> > > need to get stylus pressure information as well as stylus unique ID. And
> > >
> > I think its effectively a good choice for a standard mouse usage. But
> > when I want to use a grapic tablet (a wacom intuos for instance), I'll
> > need to get stylus pressure information as well as stylus unique ID. And
> > if I want to manage a complementary keyboard (a key pad for instance
On Tue, Oct 23, 2001 at 09:17:48AM +0200, O. Beaudoux wrote:
> > > I'm really desapointed by the fact that there is no simple way to dialog
> > > with USB devices from the application level, assuming that all is build
> > > for "standard" things (for instance, we want to show 2 cursors onto the
>
> > I'm really desapointed by the fact that there is no simple way to dialog
> > with USB devices from the application level, assuming that all is build
> > for "standard" things (for instance, we want to show 2 cursors onto the
> > screen when 2 mouses are plugged...).
>
> You don't need to talk
On Mon, 22 Oct 2001, David Brownell wrote:
>> Someone proposed an ioctl() some time ago to force a kernel-module to
>> release an interface, but I never saw it implemented.
>
>It was implemented, and I hope to dust off the patch this week. Check
>list archives for January.
The original posting
On Mon, Oct 22, 2001, David Brownell <[EMAIL PROTECTED]> wrote:
> > Let me guess: You have "hid.o" or "mousedev.o" loaded?
> >
> > As soon as they are loaded they grab the device. Later on, when you use
> > "lsusb", it also tries to grab the device to do an usb_control_msg(),
> > which fails.
>
> Let me guess: You have "hid.o" or "mousedev.o" loaded?
>
> As soon as they are loaded they grab the device. Later on, when you use
> "lsusb", it also tries to grab the device to do an usb_control_msg(),
> which fails.
Control messaging to a device doesn't require that an _interface_ be
claimed
On Mon, Oct 22, 2001 at 10:13:38AM +0200, O.Beaudoux wrote:
> > > I try to get a HID report descriptor using lsusb from usbutils-0.8
> package
> > > for 3 devices:
> > ...
> > > and all is ok except on the HID report descriptor.
> > ...
> > > cannot get report descriptor
> > ...
> > > So what's go
> > I try to get a HID report descriptor using lsusb from usbutils-0.8
package
> > for 3 devices:
> ...
> > and all is ok except on the HID report descriptor.
> ...
> > cannot get report descriptor
> ...
> > So what's going wrong ?
> Let me guess: You have "hid.o" or "mousedev.o" loaded?
Yes.
On Fri, 19 Oct 2001, O. Beaudoux wrote:
> I try to get a HID report descriptor using lsusb from usbutils-0.8 package
> for 3 devices:
...
> and all is ok except on the HID report descriptor.
...
> cannot get report descriptor
...
> So what's going wrong ?
Let me guess: You have "hid.o" or "moused
13 matches
Mail list logo
