linux-kernel - Problem starting the input interrupt pipe on the G13

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <a571ebde1bc221dd250a03e9fb33ed66.squirrel@intranet.cs.nmsu.edu>
Date:	Wed, 2 Sep 2009 15:25:50 -0600
From:	"Rick L. Vinyard, Jr." <rvinyard@...nmsu.edu>
To:	"Linux USB" <linux-usb@...r.kernel.org>,
	"LKML" <linux-kernel@...r.kernel.org>
Subject: Problem starting the input interrupt pipe on the G13

Hello,

I'm still working on the G13 driver, but I've run into a problem with the
interrupt in pipe. In essence, I can't figure out how to get it started.

The driver can be found at:
http://g13.svn.sourceforge.net/viewvc/g13/driver/trunk/

I think the root of the problem lies in the fact that the G13 usage page
is 0x00 (undefined). The output and feature reports seem to be working
fine to set the backlight color, the LCD image and the leds on the 'M'
keys.

However, nothing seems to be happening with the input report (there is
only one input report type on endpoint address 0x81 that contains the
joystick and key values).

The problem is getting the input pipe started. I grepped through the other
drivers in the hid directory and I couldn't find any that had to
explicitly start the input interrupt.

Any suggestions?

Thanks,

Rick

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/