On Mon, Apr 16, 2001 at 10:54:06PM +1000, Brad Hards wrote:
> I can get all of the "extra" keys on my keyboards, with UHCI and OHCI on a
> little endian machine. I think that the endianness issues have all been sorted
> for HID, so I can't see that it would make any difference.
> Can you confirm that they are not seen with event interface? Some keyboards
> have this on a second interface, which may not appear as a keyboard. For
> example, the following extract from /proc/bus/usb/devices on this machine.
I've always used lsusb for this, but it looks like the proc file is
delimited by T: lines..
> T: Bus=01 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#= 3 Spd=1.5 MxCh= 0
> D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
> P: Vendor=045e ProdID=001d Rev= 1.11
> S: Product=Microsoft Natural Keyboard Pro
> C:* #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=100mA
> I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01 Driver=hid
> E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl= 10ms
> I: If#= 1 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=hid
> E: Ad=82(I) Atr=03(Int.) MxPS= 3 Ivl= 10ms
>
> Note the two interfaces.
Here are mine:
T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 38 Spd=12 MxCh= 3
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=058f ProdID=9213 Rev= 1.01
S: Manufacturer=ALCOR
S: Product=STRONG MAN KBD HUB
S: SerialNumber=1234
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=255ms
T: Bus=01 Lev=02 Prnt=38 Port=00 Cnt=01 Dev#= 39 Spd=12 MxCh= 0
D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=058f ProdID=9410 Rev= 1.01
S: Manufacturer=ALCOR
S: Product=STRONG MAN KBD HUB
S: SerialNumber=1234
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr= 50mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01 Driver=hid
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl= 10ms
I'm guessing by the D: line that the first is the keyboard's hub. I don't
seem to have the second interface you do.
> So you need to check /dev/input/event0 and also /dev/input/event1 (evtest is
> good, cat is OK), assuming that these are the only HID devices on your
> machine.
event1 was my mouse, event0 did not show any output for either key. I
don't seem to have evtest. The test was done with cat, which as you say
is not a very good way to know what it's doing. I'm not sure which
package contains evtest (or if Debian has a package for it yet) but I'll
look around for it if it's needed.
As I said, this keyboard is designed for a mac, not a PC. Standard 105
key mac layout - a power key, an = key on the numpad, mac Cmd and Option
keys, etc. Bought it because of the layout, because it has real keys
instead of a silly membrane, and because it cost me a fraction of what I'd
pay for a PS/2 keyboard that was as nice. If possible, I'd like that = to
work. I don't care about the power key and one of these days I will
probably have to swap Alt and Meta for the sake of my own sanity, but
that's fixable and veering quickly off topic.. =)
--
Joseph Carter <[EMAIL PROTECTED]> Free software developer
<Chalky> gcc is the best compressor ever ported to linux. it can turn
12MB of kernel source (and that's .debbed) into a 500k kernel
PGP signature