dtrace discuss - Aug 2006 - DTrace, ::KeyboardConvertScan:entry and my USB keyboard

I have an Acer Ferrari 4000 to which I have connected a Microsoft Natural
Keyboard via USB. In an attempt to get the scancodes for the multitude of
seemingly extraneous keys, I took the advice that Casper had posted about using
dtrace. However, using:

dtrace -n ''::KeyboardConvertScan:entry {printf("%x",
arg1)}''

Doesn''t actually generate anything when using the external keyboard,
but does work as expected on the built-in keyboard. I''m not really sure
if it being USB is the issue, or if the laptop is flukey or what the case may
be, but is there anything I can do get that output for this keyboard?

Thanks.
 
 
This message posted from opensolaris.org

Josh Howard wrote:
> I have an Acer Ferrari 4000 to which I have connected a Microsoft Natural
Keyboard via USB. In an attempt to get the scancodes for the multitude of
seemingly extraneous keys, I took the advice that Casper had posted about using
dtrace. However, using:
> 
> dtrace -n ''::KeyboardConvertScan:entry {printf("%x",
arg1)}''
> 
> Doesn''t actually generate anything when using the external
keyboard, but does work as expected on the built-in keyboard. I''m not
really sure if it being USB is the issue, or if the laptop is flukey or what the
case may be, but is there anything I can do get that output for this keyboard?
I don''t know about the Microsoft keyboard, but, for instance, on my
Dell
keyboard, the extra keys are part of a different device entirely.  See

http://blogs.sun.com/roller/page/dmick?entry=dell_usb_keyboard_volume_keys

perhaps it will help.

Quoting Dan Mick, who wrote the following on Wed, 9 Aug 2006:
> Josh Howard wrote:
>> I have an Acer Ferrari 4000 to which I have connected a Microsoft
Natural
>> Keyboard via USB. In an attempt to get the scancodes for the multitude
of
>> seemingly extraneous keys, I took the advice that Casper had posted
about
>> using dtrace. However, using:
>> 
>> dtrace -n ''::KeyboardConvertScan:entry {printf("%x",
arg1)}''
   This function is part of the kb8042 driver, and so you''ll only see
this
called for PS/2 keyboards;  You''re looking for the equivalent USB
function.

  --S

On Wed, Aug 09, 2006 at 09:39:19AM -0700, Seth Goldberg
wrote:
> 
> 
> Quoting Dan Mick, who wrote the following on Wed, 9 Aug 2006:
> 
> >Josh Howard wrote:
> >>I have an Acer Ferrari 4000 to which I have connected a Microsoft
Natural
> >>Keyboard via USB. In an attempt to get the scancodes for the
multitude of
> >>seemingly extraneous keys, I took the advice that Casper had posted
about
> >>using dtrace. However, using:
> >>
> >>dtrace -n ''::KeyboardConvertScan:entry
{printf("%x", arg1)}''
> 
>   This function is part of the kb8042 driver, and so you''ll only
see this
> called for PS/2 keyboards;  You''re looking for the equivalent USB
function.
kbtrans_streams_key:entry seems to be the underlying routine USB is using...

Cheers,
- jonathan

>  --S
> _______________________________________________
> dtrace-discuss mailing list
> dtrace-discuss at opensolaris.org
-- 
Jonathan Adams, Solaris Kernel Development