Alan Coopersmith wrote: > Christian Thalinger wrote: > >> On Wed, 2009-10-21 at 13:21 -0700, Alan Coopersmith wrote: >> >>> Yes - if you ls -l /dev/usb/hid* you should see those are links to files >>> with names like that, so that humans can type less. >>> >> OK, it works. Almost all keys produce some output but the fn key does >> not (almost means: the eject key does not produce an output too). Does >> that mean the kernel does not forward the key? >> > > Yes, if there's no event for the X server to read from the kernel, there's > nothing we can do until the kernel driver is modified to send us one. > I bought the Apple wired 110 "Aluminum" keyboard. Not the same as Christian's notebook but maybe close enough. Running the dtrace script produces the following output for a press/release of the "fn" key on b126:
# ./input.d 31 32 --- Read 16 bytes from kbd id= 1 value= 1 (down) time= 0.0 (timestamp=8346287343306) --- Read -1 bytes from kbd id= 1 value= 1 (down) time= 0.0 (timestamp=8346287361545) id= 0 value= 0 ( up ) time= 0.0 (timestamp=8346287367178) id= 0 value= 0 ( up ) time= 0.0 (timestamp=8346287372297) id= 0 value= 0 ( up ) time= 0.0 (timestamp=8346287376038) --- Read 16 bytes from kbd id= 1 value= 0 ( up ) time= 0.0 (timestamp=8346343322504) --- Read -1 bytes from kbd id= 1 value= 0 ( up ) time= 0.0 (timestamp=8346343336582) id= 0 value= 0 ( up ) time= 0.0 (timestamp=8346343340288) id= 0 value= 0 ( up ) time= 0.0 (timestamp=8346343343909) id= 0 value= 0 ( up ) time= 0.0 (timestamp=8346343347351) The X server does see something as keypress does take down the cursor in a gnome-terminal window and briefly passes the flashing cursor. Both of these are normal behavior for a keypress.
