Prev: USB Drive: Can't open /dev/rdsk/c2t0d0s2: I/O error
Next: USB Drive: Can't open /dev/rdsk/c2t0d0s2: I/O error
From: Mr. Nice Guy on 22 Dec 2009 19:22 Hi there. I've been given the task of investigating and, later, implementing a Solaris 10 (SPARC, if it matters) keyboard driver "replacement" that will catch a specific sequence - akin to "ctrl-alt- del" - and allow us to take a particular action when that combo is received. I've read the bolthole information for drivers, and also poked through Sun's documents and some of the OpenSolaris code, but I'm not sure I'm much the better for it. For example, I see that there is more than one driver specifically for the keyboard: # modinfo | grep kbd 80 1376a20 27a8 16 1 conskbd (conskbd multiplexer driver 5.58) #: modinfo | grep key 81 1378da0 4280 - 1 kbtrans (kbtrans (key translation) 1.37) 94 13d4470 1eb4 - 1 usbkbm (USB keyboard streams 1.37) # modinfo | grep hid 91 13cc660 3748 51 1 hid (USB HID Client Driver 1.38) 92 13cf3d0 32f0 - 1 hidparser (HID PARSER 1.14) So, obviously, this isn't a case of "update this one driver and slap it in there with add_drv". Has anyone done something similar to this? Any tales to share after the trip? Suggestions? ("Drink more booze" is being considered as we speak...) Much obliged... Aaron |