-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 13 Nov 2002 18:28, Greg KH wrote:
On Wed, Nov 06, 2002 at 06:04:25PM +1100, Brad Hards wrote:
There is a cost to this: more minor numbers required for hiddev.
How many more minor numbers do you think would be needed?
I think the event
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 12 Nov 2002 17:10, Robert Love wrote:
So you think we cannot implement battery status without polling? That is,
uh, gross.
The notification comes through on that LED byte:
Field: 2: app: 10002 phys flags 2 (1 usages) unit 0 exp 0
On Wed, Nov 06, 2002 at 06:04:25PM +1100, Brad Hards wrote:
There is a cost to this: more minor numbers required for hiddev.
How many more minor numbers do you think would be needed?
greg k-h
---
This sf.net email is sponsored by: Are you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 6 Nov 2002 17:51, Pete Zaitcev wrote:
From: Brad Hards [EMAIL PROTECTED]
Date: Wed, 6 Nov 2002 16:48:08 +1100
2. Ask logitech - I have a contact that might work.
Logitech says:
quote
Yes, the battery status information comes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 6 Nov 2002 16:48, Brad Hards wrote:
On Wed, 6 Nov 2002 08:43, Brad Hards wrote:
So I'd say that the device isn't routinely reporting the battery status,
and you have to do a vendor specific query to the device.
Two options:
1.
At one stage hiddev claimed every device. I am not sure when Vojtech
changed this behaviour. I know that some protocols require a sequence of
control commands, and it is bad karma if you get them mixed up (eg if you
want to change the resolution on Logitech dual optical devices, you have to
On Wed, Nov 06, 2002 at 06:04:25PM +1100, Brad Hards wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 6 Nov 2002 17:51, Pete Zaitcev wrote:
This is wonderful, however I am concerned that hiddev cannot be
used while input is using hid. This seems a little too limiting.
How am
I just got that new Logitech MX700 and before that I had a Logitech
Wireless Optical Mouseman. Both are USB.
I believe the Windows driver for both has the ability to read the
battery strength. Greg said the information may be encoded in the HID
information and maybe someone on this list can
From: Robert Love [EMAIL PROTECTED]
Date: 05 Nov 2002 14:26:08 -0500
Just in case nobody else answers:
I believe the Windows driver for both has the ability to read the
battery strength. Greg said the information may be encoded in the HID
information and maybe someone on this list can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 6 Nov 2002 06:41, Robert Love wrote:
On Tue, 2002-11-05 at 14:36, Pete Zaitcev wrote:
HID devices deliver all reports. I am sure Vojtech has cute
proggies to dump the reports, but if everything else fails,
hid has debugging printouts
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 6 Nov 2002 08:28, Robert Love wrote:
On Tue, 2002-11-05 at 15:26, Brad Hards wrote:
Try:
http://www.frogmouth.net/hid-doco/examples/hiddev-misc/dump-events.c
Let us know what it says.
The following is from the Logitech Wireless
Excellent. Then I just need something to parse hiddev and figure out
what report is the battery?
You could try the relevant parts of this patch, and disable DEBUG
in the hid code when you're done.
It sure seems like when you dump the HID descriptors for that mouse
it ought to report a
HID devices deliver all reports. ...
I finally had occasion to start looking at HID stuff, so I'll
stick my nose in here: the spec says otherwise. There's a note
at the top of p.18 that says:
Only Input reports are sent via the Interrupt In pipe.
Feature and Output reports must be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 6 Nov 2002 08:43, Brad Hards wrote:
So I'd say that the device isn't routinely reporting the battery status,
and you have to do a vendor specific query to the device.
Two options:
1. Reverse engineer it, with usb snoopy
2. Ask logitech -
14 matches
Mail list logo
