On Wed, Apr 1, 2009 at 3:11 PM, Matthew Garrett <mjg59@xxxxxxxxxxxxx> wrote: > On Wed, Apr 01, 2009 at 03:06:12PM +1700, Azael Avalos wrote: > >> Indeed, my Satellite X205-9800 uses that method, however, it only provides >> HCI call 0x001E (Hotkey Events) and no System Event FIFO (0x0016), >> instead, hotkeys are entered on a variable called TOHK (TOshiba HotKeys?). >> Located in my model in >> >> PCI0.LPCB.EC0.TOHK > > Ok, interesting. Looking at the DSDTs I have here, TOHK isn't always > present on TOS1900 devices. However: > >> and it appears that it can be _polled_ tru' method INFO >> (TOSH_INTERFACE_2 ".INFO"), >> perhaps a small change in the polling to reflect to that method for >> TOS1900 devices would be necessary. > > The INFO method is, so this looks like a good call. > >> >> On my model the complete call would be: >> >> \\_SB.VALZ.SPFC >> \\_SB.VALZ.INFO >> >> Is it different from \\_SB_.VALZ.SPFC or it simply doesn't matter? > > Yeah, that shouldn't matter. So it simply looks like in the notification > function on these systems we should call the INFO method and that'll > give us the key back? I'll send a test patch later (don't have any > hardware to test right now). Well, on my model after enabling Hotkey Events, Fn-Fx events are entered to that variable according to Toshiba, eg.: Fn-Esc would give me 0x101, etc. I'm at work right now, and will be in the next 2 hours, when I get home I'll test whatever patch you send. By the way, you can find a copy of my DSDT here: http://cig.uacj.mx/~azael/Toshiba/Satellite_X205-S9800.dsl > > -- > Matthew Garrett | mjg59@xxxxxxxxxxxxx > Saludos Azael -- -- El mundo apesta y vosotros apestais tambien -- -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
